# Work Item Aging for Small Teams: Review the Work That Has Not Finished

<a id="main-content"></a>

Operations &amp; Systems

October 28, 2026  ·  7 min read  ·  Victor Valentine Romo

On this page

1. [Put the Clock Rules Above the Table](<#put-the-clock-rules-above-the-table>)
2. [Calculate Five Ages From Six Fictional Items](<#calculate-five-ages-from-six-fictional-items>)
3. [Keep Four Different Questions Separate](<#keep-four-different-questions-separate>)
4. [Waiting Keeps Its Place in the Interval](<#waiting-keeps-its-place-in-the-interval>)
5. [Copy the Aging-Work Review Table](<#copy-the-aging-work-review-table>)
6. [Turn an Old Item Into a Specific Decision](<#turn-an-old-item-into-a-specific-decision>)
7. [Use Historical Expectations as Questions](<#use-historical-expectations-as-questions>)
8. [Preserve the Review Before the Next One](<#preserve-the-review-before-the-next-one>)
9. [Sources](<#sources>)

A finished-work report leaves an empty space where the oldest open request belongs.

The team closes several small changes. The report looks healthy. One review packet still waits for a decision, carrying the same unresolved question into another day.

Put that unfinished work on its own dated sheet. Record when each item starts, how long it has remained open, and what decision can move it forward.

The [May 2025 Kanban Guide](<https://kanbanguides.org/the-kanban-guide/2025.5/#flow-metrics>) defines work item age as [elapsed time](</articles/excel-durations-over-24-hours/>) from the item's start to the current date. Cycle time runs from start to finish. The worksheet below applies that distinction to fictional service work. Its fields and review rules are proposed methods.

<a id="put-the-clock-rules-above-the-table"></a>

## Put the Clock Rules Above the Table

Define the workflow boundary before calculating anything. For this example, a request starts when a team member accepts it into delivery. An intake entry alone does not start the clock.

A request finishes when its stated delivery conditions are met and acceptance evidence is recorded. Sending an incomplete draft does not meet this example's finish rule. Other [workflows](</articles/automation-workflows-b2b-operations/>) can choose different boundaries. Write the choice where the reader can see it.

Set the review [timestamp](</articles/event-time-processing-time-business-reports/>) to 2026.10.28 at 12:00 UTC. Calculate continuous elapsed time in hours, including nights and weekends. Divide by twenty-four to display days. Preserve the hours beside the display value.

Use a timestamp rather than the label “today.” A worksheet opened tomorrow should still explain what its numbers mean. Save the review timestamp with the export or snapshot used to produce it.

The proposed calculation is direct: review timestamp minus start timestamp, provided the item is started and unfinished at that review. A negative interval needs investigation. A missing start produces [an unknown age, never a zero](</articles/null-blank-zero-business-data/>).

If the team also wants business-time age, define that as a separate display. Specify working hours, holidays, [time zone](</articles/automation-time-zones-daylight-saving/>), and calendar version. Do not switch conventions halfway through a comparison.

<a id="calculate-five-ages-from-six-fictional-items"></a>

## Calculate Five Ages From Six Fictional Items

Every record below is invented. All timestamps use UTC in October 2026. The six items share the same start and finish rules.

| Item | Work | Start | State at October 28, 12:00 | Recorded finish | Current age |
| --- | --- | --- | --- | --- | --- |
| A101 | Review packet | October 20, 12:00 | Blocked | None | 192 hours, 8 days |
| A102 | Page correction | October 23, 12:00 | In review | None | 120 hours, 5 days |
| A103 | Import specification | October 26, 12:00 | In progress | None | 48 hours, 2 days |
| A104 | Access checklist | October 27, 12:00 | Waiting for approval | None | 24 hours, 1 day |
| A105 | Delivery note | October 28, 06:00 | In progress | None | 6 hours, 0.25 days |
| A106 | Report correction | October 22, 12:00 | Finished | October 24, 12:00 | Not applicable |

A101 spans eight complete twenty-four-hour intervals. Eight multiplied by twenty-four gives 192 hours. A105 spans six hours, so its day value is six divided by twenty-four, or 0.25.

A106 has a forty-eight-hour cycle time. It has no current unfinished-work age in this review. Continuing its age clock would put finished work back into the open population.

The worksheet contains six records and five age values. Keep that distinction visible when summarizing it. “Not applicable” on the finished record means excluded by rule. An unfinished record with no start needs an explicit “Unknown” age.

Do not replace either label with zero. Zero would describe an eligible item starting exactly at the review timestamp under this convention.

<a id="keep-four-different-questions-separate"></a>

## Keep Four Different Questions Separate

Item age answers how long this unfinished item has existed inside the chosen workflow boundary. It does not measure every kind of time associated with the request.

Cycle time describes the completed interval after finish evidence exists. Due-date lateness compares an obligation with the review or finish timestamp. [Time spent working](</articles/throughput-busy-time-service-team-reports/>) requires separate activity evidence and a rule for counting it.

Suppose A101 has a fictional agreed due timestamp of October 27 at 12:00 UTC. At this review, its age is eight days and its lateness is one day. Those values answer different questions.

Suppose the same item contains three recorded activity hours. The eight-day age still stands. The record does not establish what occupies every remaining hour. It cannot assign all elapsed time to one person's work or inaction.

A104 can be one day old while its due date remains in the future. A short item can also be late if its obligation is immediate. Sort by age when reviewing age. Add an obligation field when reviewing due commitments.

Use a [business metric dictionary](</articles/business-metric-dictionary-template/>) to preserve those definitions. Give each measure its own unit, population, timestamp rule, and unknown-result state.

<a id="waiting-keeps-its-place-in-the-interval"></a>

## Waiting Keeps Its Place in the Interval

For this worksheet, A101 becomes blocked on October 25 at 12:00 UTC. The team needs a decision about which version of a reference document governs review.

At the review timestamp, the item has eight days of age and three days since the recorded block begins. Keep both intervals available. The second interval adds context to the first.

Moving the card to Blocked does not change its original start. Neither does moving it to another person. A fresh start timestamp would make the request appear younger without establishing a new delivery boundary.

If the source system resets a field during reassignment, preserve that behavior in a data note. Recover the original start from confirmed history when possible. Otherwise mark the age uncertain and name the missing evidence.

Record the block as a concrete condition: “Document owner has not selected reference version.” Add a source reference and the timestamp of the latest confirmed response. “Waiting on someone” leaves too much interpretation inside the label.

The [Kanban Guide's active-management section](<https://kanbanguides.org/the-kanban-guide/2025.5/#actively-managing-items-in-a-workflow>) includes attention to aging and blocked work. It does not prescribe this worksheet or its review schedule. Choose those details for the workflow under review.

<a id="copy-the-aging-work-review-table"></a>

## Copy the Aging-Work Review Table

Keep calculation fields separate from decision fields. Source records establish the start and current condition. A named person owns the next question.

Use the following proposed table after confirming the timestamp convention. All times below use UTC. Each role and decision is fictional.

| Item | Start | Current age | State | Block evidence | Owner | Next decision | Next review |
| --- | --- | --- | --- | --- | --- | --- | --- |
| A101 | Oct 20, 12:00 | 192 hours | Blocked | Version question recorded Oct 25, 12:00; unresolved at cutoff | Document coordinator | Which reference version governs review? | Oct 29, 12:00 |
| A102 | Oct 23, 12:00 | 120 hours | In review | No block recorded; reviewer assignment confirmed | Review coordinator | Does the draft meet the acceptance checklist? | Oct 29, 12:00 |
| A103 | Oct 26, 12:00 | 48 hours | In progress | No block recorded | Specification owner | Is the required sample definition complete? | Oct 29, 12:00 |
| A104 | Oct 27, 12:00 | 24 hours | Waiting for approval | Approval request recorded Oct 27, 15:00 | Access coordinator | Who can decide the access boundary? | Oct 29, 12:00 |
| A105 | Oct 28, 06:00 | 6 hours | In progress | No block recorded | Delivery coordinator | Is the delivery evidence ready for review? | Oct 29, 12:00 |

“No block recorded” describes the evidence available. It does not prove the absence of a block. Ask the owner when the current record leaves that distinction unresolved.

Keep the next review separate from the delivery promise. The table schedules another evidence check. It does not create a commitment that the item finishes by that timestamp.

For a reusable blank row, retain the same eight fields. Require an explicit unknown where a field cannot yet be completed. Assign someone to resolve that unknown.

<a id="turn-an-old-item-into-a-specific-decision"></a>

## Turn an Old Item Into a Specific Decision

Start the review with A101's source record. Confirm that the original start belongs to this request. Confirm that no accepted finish exists before the cutoff.

Then inspect the block evidence. In the fictional record, the team asks which document version applies. The request receives an acknowledgment, but no version decision. An acknowledgment does not resolve the condition.

The coordinator can now ask the document owner to identify the authoritative version. Record who can make that choice. If that person is unknown, resolving authority becomes the next action.

Avoid the instruction “expedite this.” It says nothing about the missing input. A useful action names the answer needed, the person seeking it, and the next review timestamp.

Also ask whether any safe work remains possible while that decision waits. Record the boundary. Preparing a review outline may be possible; approving content against an unknown reference version remains unresolved.

Keep this review beside the [dispatch system](</articles/dispatch-system-client-management/>) rather than rebuilding dispatch inside the sheet. Routing decides where work goes. This table records what an unfinished item needs now.

<a id="use-historical-expectations-as-questions"></a>

## Use Historical Expectations as Questions

A team may have an expectation based on [earlier completed work](</articles/empirical-cumulative-distribution-business-durations/>). Preserve its source, population, elapsed-time convention, and date range before using it beside current age.

The [May 2025 Kanban Guide](<https://kanbanguides.org/the-kanban-guide/2025.5/#defining-and-visualizing-the-workflow>) describes a service level expectation using elapsed time and probability. It treats that expectation as a forecast. It does not turn a particular unfinished item's expected duration into a guaranteed deadline.

For this worksheet, imagine a reference note containing a historical expectation. Ask whether its request types and boundaries match A101. Do not apply a summary from page corrections to review packets without establishing comparability.

If the historical evidence is absent, label the expectation unverified. Review the actual block anyway. An unresolved reference decision remains actionable without a [percentile](</articles/percentile-methods-business-reports/>) beside it.

Avoid concluding that the oldest item is the most valuable or most urgent. Age identifies elapsed exposure inside the workflow. Obligations, impact, and dependencies need their own evidence.

<a id="preserve-the-review-before-the-next-one"></a>

## Preserve the Review Before the Next One

[Save the dated table](</articles/spreadsheet-version-control-business-decisions/>) before refreshing its values. Tomorrow's view should not erase what the team knows at this cutoff.

At October 29, 12:00 UTC, A101 would be nine days old if still unfinished under the same rules. If it finishes earlier, record that finish and remove it from the next open-item population. [Preserve the earlier review](</articles/late-arriving-data-report-revisions/>).

Where timestamp history is weak, the [event-log readiness checklist](</articles/process-mining-event-log-readiness/>) helps identify missing starts, ambiguous cases, and incomplete sequences. An attractive age column cannot repair absent history.

End each review with a recorded decision or an explicit unresolved question. Keep the evidence beside the action. The next person should be able to [continue without reconstructing the meeting](</articles/operations-handover-small-team/>).

Give unfinished work a dated question and an owner.

<a id="sources"></a>

## Sources

- [The Kanban Guide, May 2025](<https://kanbanguides.org/the-kanban-guide/2025.5/>). Work item age, cycle time, active management, and service level expectations. Checked 2026.10.28. Worksheet fields and fictional records are editorial [proposals](</articles/proposal-templates-b2b-services/>).
