- Prepare a draft
- Show the evidence
- Ask for a decision
- Record approval
- Carry out the action
| The work | The system can prepare | The decision to keep visible |
|---|---|---|
| A quote request | Collect the details and find the approved service information. | Confirm the price, scope, and any commitment before sending. |
| A content draft | Organize supplied evidence and suggest ways to explain it. | Check the argument, facts, rights, and meaning of the finished piece. |
| An unusual enquiry | Keep the original message and summarize what is unresolved. | A named person decides what happens next. |
Example review points. Set the boundaries for your own process and its consequences.
Give the reviewer a decision they can make
When I put a person into a workflow, I want them to have a decision they can actually make. An approval request is easy to send. The difficult part is showing the person what the system understood, what it used, and what will happen next. Without that context, checking the draft can take longer than doing the work from the beginning.
Show the proposed action, the information it used, what is uncertain, and what happens if it is approved. Put the material beside the draft. Ask a concrete question: is this quote correct, is this recipient right, or is this response appropriate for this customer?
Place review before the consequential action
Reviewing a sent email does not protect the customer from the email. Put the decision before the action that needs it. Keep a draft state that cannot call the sending tool, and pass only an explicitly approved version into the action step.
If the draft changes after approval, the changed version needs another decision. The approval should identify the actual text or record, not simply the task name. Otherwise a person can approve one thing while the system sends another.
- Name the reviewer and the fallback.
- Make rejection and correction normal paths.
- Keep approvals tied to the version being acted on.
Make waiting a visible state
An unattended review queue is still unattended work. Decide when a request is due, who can see it, and what happens if nobody responds. A reminder may be enough for an internal draft. A customer-facing promise may need escalation or an honest message that the request is waiting.
Do not treat silence as approval merely to keep the workflow moving. If a task can safely proceed without a person, define the conditions that make that true. Keep the cases outside those conditions in review.
Use corrections to improve the system
Record why someone changed or rejected a draft. Missing context, a wrong fact, poor tone, and an action the business would never approve need different fixes. Feeding every correction back as a style preference hides the actual problem.
Use representative accepted and rejected examples in tests. The aim is to make the person's decision easier and the work more dependable. Keeping a person in the loop does not help if the system gives them no practical way to judge it.
An approval screen should show the actual commitment
Suppose a workflow prepares a reply to a customer asking for a quote. The draft names a service, a price, and a proposed date. The reviewer sees those details beside the request and the records used to prepare them. The screen asks whether this exact reply may be sent to this customer.
The person notices that the requested date is still uncertain and changes the draft. The system retains the change and asks for approval of the revised version. It does not send the previous version because that was the first one marked ready. The action record identifies the approved content and recipient, so the team can reconstruct what happened if the customer later asks.
Now imagine nobody reviews it. The request remains waiting, with its owner and due state visible. The workflow can remind the owner or escalate according to the agreed process. It should not convert the absence of a decision into a customer-facing promise. This is the part to test when the team is busy, because a review step that works only during a demonstration has not resolved the operating problem.
The same reasoning applies to a content draft or an unusual customer message. Give the person enough context to decide, preserve the version they decided on, and connect that decision to the action. A button labelled approve is only the visible end of that arrangement.
Decide which decisions can move out of review
Look at the consequences of a wrong action, the quality of the source information, and the patterns in previous corrections. A routine formatting change and a new customer commitment deserve different treatment. Define the conditions for any automatic action explicitly and keep cases outside those conditions visible.
Do not remove review merely because people have stopped rejecting drafts. They may have stopped checking them. Ask whether the reviewer can still explain a decision from the material shown, and inspect the resulting action as well as the approval record.
Sources you can check
The links support the platform details and technical distinctions. Recommendations and examples are editorial judgement.