Write the brief for the next decision
- Name the outcome and the audience
- Explain what already exists and what must remain
- Add source links, references, files, and constraints
- State what approval looks like
- Record any fixed launch date or dependency
Use supported rich content
The brief supports formatted text, links, mentions, request references, and reusable templates where enabled. Use headings and short lists so a reviewer can scan the direction before reading every detail.
Recover an interrupted draft
Autosave indicators show when supported request content is being stored. If the browser closes before a draft is finished, the recovery prompt can restore the newer local version. Compare it with the saved request before replacing either copy.
Keep the accepted direction easy to find
Comments are useful for discussion, but the current decision belongs in the brief. When feedback changes the audience, copy, format, or definition of done, update the brief after the team agrees. A new reader should not need to reconstruct the requirement from a long thread.
Check saved state after an interruption
The interface shows when request content is saving. If the browser closes or the connection drops, reopen the same request and confirm the latest sentence or attachment is present before retyping it. Avoid editing the same brief in two tabs because the newest save can replace an older copy.