Question and scope
This protocol measures the share of cross-team requests that are reopened after someone marks them complete. A reopening is any return to active work on the same request after a completion event, whether the return is triggered by the requester, the receiving team, or a downstream reviewer. The result is a percentage, a median time to reopening in working days, and a breakdown by request type and receiving team. The measure describes rework that was visible enough for someone to reverse a completion, not every defect that escaped notice.
The question matters because completion is often treated as proof that the work met its purpose. A ticket can be closed when a deliverable is uploaded, even if the requester needed a different format or the downstream team cannot use the output. The closure records an action, while the reopening records a correction. Counting the gap between the two turns a vague complaint about rework into a pattern the coordinator can inspect.
Scope is one coordination team and the cross-team requests it sent or received during a fixed window. Include requests that crossed a team boundary in either direction, because a team that reopens often may also cause reopenings downstream. Exclude internal subtasks that never left the team, and exclude duplicate tickets that were merged into a parent request. Record the trackers searched, the window dates, and the reviewer names so another analyst can rebuild the count.
Why reopening is a rework signal
Most dashboards count completed work and call the remainder open work. That split hides a third category: work that was declared finished and then had to be done again. Reopened requests consume capacity twice, delay the requester's next step, and often reveal a gap in the definition of done. A team can look efficient on a completion chart while a meaningful share of its output is quietly circulating back through the queue.
Reopening also has a social cost that a simple defect count misses. The requester who has to reopen a ticket is signaling that the handoff did not work, and the receiver may read that signal as criticism. If the team has no neutral way to discuss reopenings, people learn to avoid them by asking for more review before closure or by leaving work open longer than necessary. Both behaviors distort the completion data and slow the queue.
Defining the coding unit
The unit is one cross-team request with one named requester, one receiving team, and one expected deliverable. Treat a bundle of unrelated asks as separate requests, because each can be completed and reopened on its own schedule. Keep a single request as one unit even when several people contribute to the deliverable. Write the split rule into the codebook before sampling so two reviewers make the same choice on similar records.
Use the request as it existed when work first started, not the version after later scope changes. A request that grew during delivery may have a different completion standard, and counting the final version can make the original closure look premature. If the scope changed, record the change date and code the reopening against the standard in force at completion. That note lets a reader separate a genuine miss from a legitimate change in requirements.
Locating completion and reopening events
Start with the tracker's status history rather than the current status field. The current field shows where the request sits now, while the history shows whether it ever left the completed state. Export the history with timestamps and actor names so the sequence can be reconstructed. If the tracker keeps only the latest transition, note that limitation before continuing.
Confirm that the completion event represents the deliverable, not a routine sub-step. Some workflows close a review task when the reviewer comments, then open a separate implementation task. That pattern is a normal stage transition, not a reopening, and counting it would inflate the rate. Read the task names and the surrounding comments until the sequence is clear.
Define the observation window before reading the sample, such as thirty calendar days after completion. A reopening that occurs after the window is recorded but excluded from the headline rate. Without a fixed window, a patient reviewer can find a later correction for almost any request and make the team look worse than the period deserves. Choose the window to match the useful life of the deliverable, then state it beside the result.
Building the reopening rubric
Score four elements for every request: the completion event, the reopening event, the reason given, and the person who initiated the return. The completion event must move the request into a done state, and the reopening must move it back into active work. The reason should be recorded in the request or the linked conversation, not inferred from the title. The initiator should be a named person or an explicit automated rule.
Use three levels for the overall score: reopened for a delivery gap, reopened for a changed requirement, and not reopened. The middle category is essential because a requirement change is not the same failure as a missed acceptance criterion. A request that is reopened after a customer changes the brief belongs in the changed-requirement group even if the timing looks suspicious. Keep the definitions short enough to apply consistently during coding.
Sampling and evidence rules
Use a census when the team handled fewer than roughly one hundred cross-team requests in the window. A census removes sampling error and is practical for a single coordinator with a modest queue. Above that threshold, draw a random sample and publish the selection method. Stratify by request type and receiving team so a large volume of routine work does not hide a small set of complex reopenings.
Freeze the sample before reading the requests. Selecting cases after seeing which ones were reopened invites the reviewer to choose the most dramatic examples. Store the random seed or the selection procedure with the sample file, and record every substitution. If a selected request is out of scope, replace it with the next item on the randomized list rather than picking a similar case by hand.
Quote the smallest passage that supports each score and link to the exact status event. A quote anchors the judgment and makes a second review possible, while a paraphrase can add clarity that was not present. When the evidence is a status history, record the timestamp and the actor rather than a summary of the sequence. Do not credit a reopening that exists only in someone's memory of a hallway conversation.
Handling ambiguous cases
Some requests are reopened by a manager on behalf of the requester. Code the initiator as a delegate and note whether the requester later confirmed the problem. Do not treat the manager's action as equivalent to the requester's own rejection unless the team's rule allows delegation. That distinction shows whether the reopening reflects a real delivery gap or a review layer adding its own standard.
When two reviewers disagree, return to the quoted evidence instead of debating intent. If the quote supports both readings, the rubric is ambiguous and should be tightened with a new example. Recode the disputed case and every similar case after the revision, then record the change in a codebook log. The log should name the rule that changed and the date, not just the individual request.
Exclude a request only when the record is genuinely unavailable, such as a deleted project with no export. Mark it unverifiable and report the count separately rather than guessing from memory. A visible gap in the history is itself a finding about tracker hygiene. Hiding that gap inside the reopening percentage makes the process look cleaner than the evidence allows.
Calculating the reopening rate
Report the delivery-gap share as the headline, with the changed-requirement share beside it. The gap between the two numbers shows how much apparent rework was actually a scope change. Include raw counts with every percentage so readers can judge how much weight the number deserves. A rate based on fifteen requests should not be presented like one based on five hundred.
Report the median time to reopening in working days, not calendar days, because a request completed on Friday is not late on Saturday. State the working-hours convention explicitly, including which holidays were applied. A median is more useful than an average here because one request reopened after two months can distort the mean. Show requests that were never reopened as their own line so the denominator is visible.
Break the result down by request type and receiving team, but suppress groups with fewer than five requests. Small groups produce dramatic percentages that invite overreaction. A team that handles complex, permission-heavy work may see more reopenings even with a strong process, so pair the number with the type mix. The coordinator should be able to explain a difference without inventing a cause the data cannot support.
Reporting patterns without blame
Present the first result as a baseline rather than a verdict on any individual. The number describes how the request system behaves, not how hard people are working. Name the most common reopening reason, such as a missing file format or an unstated approval step. Pair each pattern with one specific change to the intake form or the completion checklist.
Publish team-level patterns instead of a ranking by receiver or requester. A leaderboard encourages people to avoid reopening requests rather than to fix them, which pushes the problem into side channels. Share the coding file with the receiving teams so they can see how their requests were judged. Invite one requester from each team to review a small second sample, because that review improves the rubric and adds credibility.
Keep the language precise when a reopening was caused by a changed requirement. Calling every return "rework" blames the receiver for a decision the requester made. Separate the categories in every summary, even when the total is the number leadership wants to see. The definition-of-done measure is a natural companion because it tests the standard that closure depends on.
Limits and sources of error
The sources cited here describe internal control, scheduling, and project communication in general terms; they do not provide a benchmark for reopening rates. The protocol therefore produces a local baseline, not an industry comparison. A team should not present its percentage as evidence that it is better or worse than another organization. Readers should treat the number as a starting point for a local conversation about completion standards.
Reviewer judgment remains the largest source of error. Two careful reviewers can read the same terse comment and disagree about whether the return was a delivery gap or a requirement change. The quote requirement and the second-review sample reduce that risk but do not remove it. Report inter-rater agreement so readers can judge how much confidence the number deserves.
Tracker coverage is a second limit. A request may be reopened in a chat thread or a meeting without any status change, and the protocol will miss it. Note which systems were searchable and which were not. If a team relies heavily on informal reopenings, fix the record-keeping before trusting the rate. The measure is only as complete as the history the team leaves behind.
Review cadence
Review the measure after two full cycles before setting a target. One cycle is a baseline, and a target set from a single period is likely to reflect that period rather than the process. At the end of the review, choose one intake change, one owner, and one check date. A practical first change is to require a named acceptance criterion on every cross-team request.
Retire the measure when the delivery-gap share is low and the changed-requirement share explains most reopenings. If the team keeps it, report both categories together, because a falling total with a rising delivery-gap share can mean the team is closing work later rather than closing it better. Link the result to the request acceptance checklist so the coding rubric and the operating checklist stay aligned. The purpose is to catch a weak handoff while the fix is still cheap.
Sources
- U.S. Government Accountability Office, Standards for Internal Control in the Federal Government, reviewed November 20, 2026.
- U.S. Government Accountability Office, GAO Schedule Assessment Guide, reviewed November 20, 2026.
- Project Management Institute, PMBOK Guide, reviewed November 20, 2026.
- National Institute of Standards and Technology, Cybersecurity Framework, reviewed November 20, 2026.
