Name the Status and Store the Right Copy
Keep document versions and action states clear so a polished draft is not mistaken for a sent message.
Look around. Try a small click.
This lesson works as a written guide with interactive examples. You can explore here before opening the real application or provider dashboard. A recorded video has not been added yet.
What will make more sense
- Distinguish draft, reviewed, approved and delivered states.
- Read a completion report for the actual scope of work.
One idea to keep
A useful document has a clear status as well as clear words.
The short lesson
Read the explanation at your pace
A document can look finished while still awaiting a decision. That is why its status matters. Draft means wording has been prepared. Reviewed means someone checked a defined aspect. Approved means the appropriate person accepted it for an intended use. Delivered or published means a separate action actually happened. These states are related, but one does not automatically prove the next.
Our review-status.md says the invitation is a fictional draft awaiting owner review. The time and capacity can be compared with the approved fact sheet, but the date and distribution channel are still unresolved. No message has been sent. This note is intentionally plain. It tells the next person what exists without forcing them to infer the state from a filename such as final-new.
Use a clear file arrangement that fits your task. Keep the source note, working draft and review note identifiable. You do not need a separate copy for every tiny edit. When a copy represents a meaningful state, name or label it so the role is clear. A Git history can help track recorded changes, while the visible document status still explains its business use.
Ask your assistant to report the actual state at the end of the task. For example: saved the invitation draft, checked the time and capacity against current-facts.md, left the date unresolved and sent nothing. That is a useful completion report. It does not claim that the owner approved the message or that a real communication system accepted it.
Approval also has scope. A person may approve wording for an internal example without approving a mass mailing or a paid advertisement. If the intended use changes, confirm what review is still needed. The assistant should not treat a casual comment such as looks good as permission for any account action it could technically perform.
The browser activity asks which label matches the prepared work. Choose draft awaiting review. You are not slowing the work down by naming its state accurately. You are preventing a later teammate or agent from skipping an important decision. Clear status lets ordinary drafting move forward with less confusion about which copy to use and what should happen next.
Try it here
Name the current document state
Explore the prepared example, then choose a response. Your choice reveals its explanation immediately.
This is a local learning example with prepared responses. It does not run VS Code or contact an AI service.
The wording exists but owner review is pending and nothing was sent. What is it?
A tiny next step, if you want one
Optional: try 2 small actions at your own pace
You can finish this lesson by exploring the example above. These real-app actions are optional, and there is nothing to submit.
- Optional: open review-status.md and find the current status.
- Optional: compare its remaining questions with current-facts.md.
A quick confidence check
These checkmarks are a personal reminder. Choose what feels familiar, and come back whenever you want.
Your place is saved in this browser when storage is available. There is no grading or account sync.
Try a short question
Choose an answer to see why it fits. You can try again or explore every explanation.
Does saving a draft prove the owner approved it?
What should a completion report say about delivery?
If something looks different
A teammate cannot tell which file is ready to use.
Point to the current working copy and its review status. Clarify the intended use before treating it as an approved release.
Sources and further help
Read the official product guidance and related learning resources when you need them. You do not need to read every reference now.