Why 90-day review needs its own control
A executive hiring team can complete a task and still leave the next person unable to verify it. The 90-day review control exists to make the work reconstructable from a source, a decision, and a close.
Start with the source record
The cost is not only rework. When the 90-day review record is thin, managers spend time asking what changed, customers hear a different version, and the next reviewer has to rebuild the story from memory.
Separate preparation from approval
Treat the control as a queue item with an owner, a due time, and a close condition. A task that has no close condition becomes an open loop that survives the week.
Build the routine
Keep a named backup for the 90-day review owner. Coverage during leave or a time-zone gap should be written into the routine, not improvised when the owner is unavailable.
Handle exceptions before they age
When a source is unavailable, record that fact instead of leaving the field blank. Missing, unavailable, and confirmed negative are three different states and should not be collapsed.
Verify, close, and review
Begin with the record that governs 90-day review. Record who created it, the version or date observed, the field it supports, and the owner who can confirm it.
Keep the source and the interpretation in separate fields
Keep the source and the interpretation in separate fields. A forwarded message or a verbal confirmation can be a lead, but it is not proof that the record changed.
When two sources disagree, preserve both values and label
When two sources disagree, preserve both values and label the discrepancy. Do not overwrite the earlier value to make the report look clean.
Do not copy a value from a prior 90-day
Do not copy a value from a prior 90-day review record because it looks familiar. Reopen the source, confirm the version, and record what changed.
Name the owner before the VA prepares any action
Name the owner before the VA prepares any action. The VA may collect, compare, label, calculate, and route; the accountable owner decides whether the evidence is enough.
Write the boundary into the task brief
Write the boundary into the task brief. Name the systems the VA may use, the fields they may change, and the questions they must route.
A complete packet is not an approval
A complete packet is not an approval. A drafted message, a proposed schedule, or a reconciled total still needs the named owner decision when policy or risk is involved.
Close the loop with the person who raised the 90-day review issue
Close the loop with the person who raised the 90-day review issue. A record that is internally complete but never confirmed by the requester is only half closed.
Build a short daily routine for 90-day review
Build a short daily routine for 90-day review: open the queue, check the source, record the exception, and leave a next action with a time.
Use the same fields every day
Use the same fields every day. Consistency makes the work comparable and lets a reviewer spot a missing source without reading the whole thread.
Keep the queue small enough to finish
Keep the queue small enough to finish. A long queue hides the oldest exception and makes the monthly report look better than the operation.
Record the exact 90-day review source and the time it was observed
Record the exact 90-day review source and the time it was observed. A later reviewer should be able to tell whether the value was current when the first action was taken, even if the record has changed since.
Define reason codes for 90-day review
Define reason codes for 90-day review: missing evidence, identity mismatch, conflicting record, stale version, unavailable owner, access failure, and scope change.
Preserve the original request and the correction
Preserve the original request and the correction. A later reviewer should see what was known when the first action was taken.
If the exception affects pay, safety, access, legal
If the exception affects pay, safety, access, legal, or a customer commitment, stop the dependent action and route it. Urgency is not permission to work around the control.
Write the next action as a sentence with an owner and a time
Write the next action as a sentence with an owner and a time. "Review the 90-day review exception" is not a next action; "Mina checks the missing source by 2pm and routes it to the owner" is.
Close 90-day review only when the destination record shows
Close 90-day review only when the destination record shows the approved change. A sent message or a closed ticket is not proof that the schedule, ledger, access, or assignment changed.
Reconcile open cases at the end of the day and explain the carryover
Reconcile open cases at the end of the day and explain the carryover. A case that is silently carried forward becomes an aging exception.
Review a sample each month
Review a sample each month. Check the source, the approval, the execution, and the confirmation. A repeated gap should change the procedure, not only the coaching.
Keep the 90-day review queue separate from the general inbox
Keep the 90-day review queue separate from the general inbox. A shared queue without a named owner hides the oldest item and makes the weekly report look cleaner than the work.
Frequently asked questions
Who owns the decision?
The named executive or hiring owner keeps the decision; the assistant prepares and routes the record.
What evidence should be kept?
Keep the source, the instruction, the output, the reviewer, and the next action.
Ready to define the role?
Use a recent leadership week to scope the support that would make the biggest difference. The consultation is a working conversation, not a generic pitch.
Book a consultation