Best Practices for Attachments

Attachments are most useful when they provide real context or evidence that supports a work item or approval decision.

Best practice 1: Use clear file names

A file name should help reviewers understand what the file is before opening it.

Best practice 2: Attach only relevant files

Avoid adding files that are not directly useful to the current work item. Too many unrelated files make review harder.

Best practice 3: Add a comment after upload

Use a comment to explain what the file contains and why it matters.

Best practice 4: Use attachments to reduce ambiguity

Diagrams, screenshots, and reference files are especially helpful when a workflow is blocked by unclear technical or operational context.

Best practice 5: Review before converting or approving

Before converting discovery or deciding an approval, review supporting attachments so you are not making decisions without the available evidence.