Everyday work
Review work and approve the next action
Check the result, make corrections, and give a clear decision about what happens next.
Review turns a draft into work you are willing to use. Approval answers a different question: what action may happen next? A message can be well written and still need a decision about its recipient, timing, or delivery method.
Your employee’s permissions come from your setup and working agreement. Do not assume every employee can send or publish, or that every workflow uses the same approval process.
Before you begin
Section titled “Before you begin”Open the current version and keep the original job and sources nearby. Know whether you are reviewing content only or considering an action in another system. If you are unsure, ask for a description before giving approval.
Review in a useful order
Section titled “Review in a useful order”- Purpose: Does the work solve the job you assigned?
- Facts: Are names, figures, dates, and claims supported?
- Commitments: Does it promise anything you have not agreed to?
- Fit: Is the format and tone appropriate for the reader?
- Next action: What exactly will happen, where, and for whom?
Keep this as a draft while I review it. Show the current version, identify any uncertain facts or new commitments, and explain the next action separately. Do not send, publish, or change another system based on this review request.
Give a specific decision
Section titled “Give a specific decision”For a revision, point to the change: “Replace the proposed date with the date in my notes, then return the revised draft.” Review that new version before using it.
For work you will use manually, say so: “The draft is ready. I will send it myself.” That makes the handoff clear without requesting an external action.
When an action is supported and requires approval, use the process shown for your setup. Confirm the exact current content, destination, and timing. A prior approval should not be treated as approval for different content or a new destination.
How do I approve an email?
Section titled “How do I approve an email?”Check the exact message, recipients, attachments, and sending time. If your setup supports sending, follow its approval process for that specific email. If you will send it yourself, say that clearly and copy the reviewed text into your normal email process. Approving the wording alone should not leave either of you guessing whether the email should be sent.
What you should see
Section titled “What you should see”The work should be marked or described accurately as a draft, ready for your use, waiting for approval, or completed. If an external action was authorized, expect confirmation of what actually happened. “Ready to send” is different from “sent.”
If the outcome is uncertain, check the destination or contact support before repeating the action. Repeating an uncertain send can create a duplicate.
Make the next review easier
Section titled “Make the next review easier”- I checked the facts and commitments that matter.
- I am looking at the current version.
- My decision names the next action clearly.
- I know what is finished and what still needs someone.
When a correction should apply to future work, teach it as a scoped preference. Review becomes more focused when both of you share a clear standard.