Note · 2 min · Arturo Ordóñez
What an approval request needs to show
A generic confirmation asks people to rely on a summary. Reviewing an action requires the actual result and a way to correct it before execution.
“Do you want to continue?” may be enough when the action is evident and its effects are visible. If the question covers prepared content, affected data or an external operation, the request needs to show more information.
The review screen should answer four questions:
- What will be used? The specific text, file or change must be available for inspection. A summary helps with orientation but does not replace the material that will reach the destination.
- Where will it take effect? The account, resource or recipient needs to be identifiable. The same operation can have different consequences depending on where it occurs.
- What remains unchecked? Missing information and relevant uncertainty belong before acceptance. People need to distinguish these from what has already been verified.
- How can I correct it? There needs to be a route to adjust or reject the proposal while keeping the work that remains useful.
The system also needs to connect approval with what was shown. If the content changes after review, it should check that the authorisation still applies. Approving a general intention does not automatically settle the decisions in a different version.
This design requires choosing where to request attention. Repeating confirmations at every step can make the important decision harder to recognise. Review belongs where the change is defined and can still be corrected before it takes effect.