Editing document details and reference text
2 min read
Updated Apr 13, 2026
Metadata is not decoration. Good document details make board views easier to scan, improve downstream exports, and give teammates better context when several packages are in motion at once.
Before you begin
A new or existing draft
A naming pattern your team can follow
A clear reference or identifier if the document belongs to a larger process
Use descriptive titles
Titles should tell a teammate what the package is without opening it.
Avoid vague titles such as Final or Updated unless the surrounding process truly makes them obvious.
Use description and reference fields well
Descriptions help clarify the workflow purpose, while references are useful for case IDs, contract IDs, or other external identifiers.
Those details make searching and archive review much easier later.
Apply categories and tags consistently
Categories and tags help organize similar work across drafts and sent packages.
Agree on a lightweight taxonomy internally if several senders share one workspace.
Pro Tips
Choose one title pattern and stick to it.
Use references for external system IDs instead of burying them in the title.
Keep tags simple so they stay useful instead of becoming noise.
Was this article helpful?
Use this as a quick signal while the public knowledge base is static.