Question and scope

This protocol measures how many active operations decisions have no date on which someone will review whether the decision still holds. A decision is active when the team is still operating under it, such as a routing rule, an approval threshold, a vendor choice, or a weekly process. A scheduled review date is a specific calendar date in the decision record, assigned to a named owner, at which the team will confirm, revise, or retire the decision. The result is a share, a count, and a list of decisions that need a review date.

The measure is about whether a decision has a future checkpoint, not whether the original choice was good. A sound decision can become wrong after a volume change, a new system, or a supplier failure. Without a review date, the team usually discovers the mismatch through an incident or a complaint. A scheduled review creates a cheaper moment to notice that the conditions have moved.

Scope is one coordination team, a defined decision inventory, and a stated observation window. Include decisions recorded in a decision log, a process document, a meeting record, or a tracker, provided the team still follows the choice. Exclude decisions that have already been retired and one-time choices that create no ongoing obligation. Name the sources and the window so another analyst can rebuild the population.

What counts as a scheduled review date

A review date qualifies when the record shows a specific day, a named owner, and a question the review will answer. The question can be as short as whether the current approval threshold still matches the volume, or whether the vendor still meets the service requirement. A note that says "review annually" without a date is a cadence, not a scheduled checkpoint. The test is whether a coordinator can find the next review without reconstructing it from memory.

Distinguish a review date from an expiry date. An expiry date ends the decision automatically unless someone renews it, while a review date prompts a person to examine the decision and record an outcome. Some decisions need both, such as a temporary exception with a hard end and a midpoint check. Code the two fields separately so the analysis shows which control is missing.

Unit of analysis and exclusions

The unit is one decision with one scope, one owner, and one operating rule. Split a bundled decision when each part can be changed independently, such as a routing rule for one request type and a separate escalation threshold. Keep one unit when several clauses stand or fall together under a single review. Use the record as it stood at the cut-off rather than a cleaned version rewritten during the audit.

Exclude decisions that were formally retired before the window, decisions that were never adopted, and choices that create no continuing work. Exclude duplicate records created when a meeting note and a decision log describe the same choice, but count the pair once and note the overlap. Report each exclusion category with a count so the denominator is defensible. Keep a short log of what was removed and why.

Building the decision inventory

Start with the decision log if one exists, then add the operating rules that live in process documents and team charters. Search meeting records for choices that changed how work is routed, approved, or prioritized. Add the rules that coordinators apply every week but that no one has written into a formal log. The inventory should cover the decisions the team actually follows, not only the ones with a tidy record.

Give every unit a stable identifier before coding so the same decision can be matched across sources. Record the source, the date the decision was made, the owner, and the scope. Mark decisions found only in meeting notes, since those are the most likely to lack a review date. Freeze the list before reading the review fields to reduce selection bias.

Reading the review fields

Record three fields for each decision: the last review date, the next scheduled review date, and the owner of that review. The last review date shows whether the decision has been examined recently. The next date shows whether a future checkpoint exists. The owner shows who is expected to act. A decision with a next date but no owner is not scheduled in any practical sense.

Flag every decision where the next review date has already passed without a recorded outcome. A stale date is different from a missing date, because someone intended to review the decision and did not. Also flag decisions with a review date but no review question, since the owner may not know what to examine. Separate these conditions in the report so the team can fix the record rather than only adding dates.

Evidence standards for review dates

Accept a review date only when it appears in the record the team uses to operate. A date in a personal reminder is weaker than a date in the shared decision log, because it disappears when that person is unavailable. A verbal agreement to review the decision next quarter is not scheduled until it is written down with a specific day. Record the evidence type so the analysis can show how many dates rest on shared records.

Do not create a review date during the audit and then count the decision as scheduled. That changes the population instead of measuring it. If the team wants to fix the gap while the review is running, record the new date in a separate field and report it as a post-audit change. The original state is what the headline describes. This separation keeps the measure honest and still lets the team act.

Sampling and verification

Use a census when the inventory is small enough to review in full, which is common for a single coordination team. Above roughly one hundred active decisions, draw a random sample and publish the method. Stratify by decision type and by age so a large group of recent rules does not hide older decisions that were never revisited. Freeze the sample before checking the review fields.

Have a second reviewer recode at least ten units and compare the results. Resolve disagreements by returning to the decision record, not by discussing which interpretation sounds better. Record the resolution so a later reviewer can see how the definition was applied. If disagreement is high, rewrite the definitions and recode the full sample before reporting. A stable definition matters more than a large sample, so do not rush past this step.

Decision rules before coding

Decide before coding whether a decision with a review cadence but no specific date counts as scheduled. The stricter answer is no, because a cadence does not tell the owner when to act. Decide whether a review date owned by a team rather than a person counts, and apply the same rule throughout. A shared queue can work if the team checks it, but the record should name how the review enters that queue.

Decide how to treat a decision that was reviewed during the window but whose next date was never set. Code it as missing a future date even though it was recently examined. The measure is about the next checkpoint, and a recent review does not guarantee another one. Note the review outcome separately so the report shows both activity and forward coverage.

Analysis and reporting

Report the share of active decisions with a future review date, the share with only a cadence, and the share with no review field at all. Show raw counts beside every percentage, especially when the inventory is small. Add the share of review dates that have passed without an outcome and the share with no named owner. Those two conditions usually explain more than the headline share.

Break the result down by decision type, age, and owner group. Suppress groups with fewer than five units so one unusual rule does not look like a pattern. Pair the share with the consequence of the decision, because a routing rule that affects every request deserves more attention than a minor formatting choice. The weekly blocked-work review is a natural place to surface decisions whose conditions have changed.

Limits and sources of error

The sources cited here describe internal control and risk practice in general terms; they do not provide a benchmark for decision review coverage. A missing date in the record may mean the team never set one, or that the owner tracks it somewhere the audit cannot see. A decision may also be reviewed informally without a note. Treat a low share as a prompt to inspect the decision log, not as proof that the team never revisits its choices.

Decisions that were never written down are invisible to this measure. Check a sample of meeting notes and process documents to estimate the size of that gap, and report it as a limitation. If many operating rules live only in habit, fix the decision log before setting a coverage target. A precise share built on an incomplete inventory is less useful than a range with a clear caveat.

Review cadence

Review the result at a fixed point and end with one change, one owner, and one check date. A practical first change is to require a review date and a review question before a decision enters the active log. Repeat the measurement after two full cycles before setting a target, because one period may reflect a burst of new rules or a quiet quarter. Keep the definitions and the sample method with the result so the next reviewer can compare like periods.

Retire the measure when every active decision has a future review date with a named owner and the share stops changing. If the team keeps it, publish the missing and stale shares together, because a strict headline can hide a backlog of overdue reviews. Link the result to the decision reversal record when a review changes a choice. The purpose is a decision the team can revisit on purpose, not one it discovers by accident.

Sources