A final review catches mistakes, but by then several people have worked from the wrong information. Place a quality check where it can prevent a consequential error from moving into the next stage. Choose the check from the failure you need to control, not from a desire to approve every action.
Photo by Jakub Żerdzicki on Unsplash.
Identify the failure and its effect
Review recent cases. What was wrong, when could it first have been detected and what happened afterwards? Distinguish a missing required field from a judgement that needs expertise. The appropriate check may be a validation rule, a clearer input or a named reviewer.
Define a useful check
Item or condition being checked.
Evidence or authoritative record.
Person or rule performing the check.
Pass, correction and exception routes.
Record needed by the receiving stage.
Keep the check proportional to the consequence. A checkbox saying “reviewed” adds little if the reviewer has no source information or completion criteria.
An illustrative placement
A team prepares client reports using the wrong reporting period. A period confirmation before extraction may prevent more downstream work than a general review immediately before sending. The final reviewer still checks the completed report, but the earlier control addresses the recurring input problem.
Review the complete effect
Specify what happens after a failed check. Who corrects the input, who may approve an exception and which work must wait? A control without a failure route leaves staff to improvise at the most consequential moment. Trial the route with an unsuitable record before relying on the check in normal delivery.
Related guidance: practical process-mapping guide.
Track error patterns, rework and time spent checking. If the new control creates a queue without addressing the failure, investigate its design and ownership. Do not remove necessary safeguards solely to improve a speed measure. Hili Consulting can help locate practical controls within the actual flow of work.
