How often do accepted research deliverables reopen within thirty days?

A cohort method for measuring reopening rates, separating genuine decision changes from quality failures in accepted research.

How often do accepted research deliverables reopen within thirty days?

Question and scope

This protocol measures how often a research deliverable that was accepted is reopened within thirty days. The scope is written deliverables used by a GTM team, such as a source note, a competitor update, or a segment summary. It excludes a deliberate refresh that was scheduled before the deliverable was accepted. The measure is useful because reopening is one of the clearest signals that acceptance did not mean the work was usable.

The unit is a deliverable, not a request. One request can produce several deliverables, and only the ones that reached acceptance belong in the cohort. A request that was cancelled or deferred is not a reopening. The thirty-day window is a convention for this protocol and should be stated in the report so the reader can compare periods.

Define an accepted deliverable

Write the acceptance criteria before counting. A deliverable is accepted when a named reviewer confirms that it meets the quality bar and the intended reader receives it. If acceptance only means the file was uploaded, the measure will count drafts as finished work. Record the date, the reviewer, and the version that was accepted.

Decide how to treat conditional acceptance. A deliverable approved with a follow-up note is still accepted, but the follow-up should be recorded as an open item rather than a reopening. If the follow-up changes the recommendation, treat it as a reopening. The distinction keeps normal refinement from inflating the rate.

Keep a copy of the accepted version so a later reopening can be compared with what the reader originally received. A live document that changes in place erases the evidence of the change. If the tool keeps version history, record the version identifier in the acceptance record. The comparison is what lets the team decide whether the reopening was a correction or a genuine update.

Define a reopening

A reopening is a change to a deliverable after acceptance that requires the reader to reconsider the finding. That can be a corrected number, a replaced source, a revised recommendation, or a scope change that alters the conclusion. A typo fix or a formatting update is not a reopening. Write the threshold so two coders would classify the same event the same way.

Record who initiated the reopening and why. The initiator may be the original requester, a seller who used the deliverable, or the reviewer who found an error. The reason should be recorded in the initiator's words before the analyst edits the file. This preserves the evidence that the later coding depends on.

Include the reader's response in the record when the reopening changes a decision. A corrected number that never reached the seller has not affected the decision yet. The gap between the correction and the reader's awareness is its own delay. Measure it separately if the team suspects that corrections are not reaching the field.

Build the cohort

Pull every deliverable accepted in a defined period and follow it for thirty days. Include deliverables from different request types and analysts so the cohort reflects the real mix. Record the acceptance date, the request type, the analyst, and the reviewer. Exclude any deliverable whose thirty-day window has not fully elapsed at the time of analysis.

Keep the cohort list stable even if a deliverable is retired during the window. A retired deliverable can still reopen if the reader needs to correct a decision that used it. Note the retirement date separately. A cohort that quietly drops retired items will understate the rate.

Code the causes

Use a small set of causes such as source error, scope miss, changed decision context, new information, and format confusion. Source error and scope miss point to the research process. Changed context and new information may be legitimate reasons to reopen even when the original work was sound. The mix of causes is more useful than the headline rate.

Have a second person code a sample of reopenings and compare the results. Disagreements usually point to an unclear definition rather than careless coding. Resolve the definition and recode the sample before calculating the final rate. Record the agreement level so the reader knows how much confidence the coding supports.

Write one example for each cause code and keep the examples beside the coding sheet. Examples reduce drift when several people code across a quarter. If a reopening fits two codes, choose the cause that the team could have prevented. The coding should point to an action, not just describe the event.

Compute the rate

Divide the number of deliverables that reopened at least once by the number of deliverables in the cohort. Report both the count and the rate, because a small cohort can produce a dramatic percentage from two events. Add the median days to reopening and the share that reopened more than once. These details show whether the problem is early correction or repeated instability.

Break the rate down by request type, analyst, and reviewer. A high rate in one type may reflect ambiguous acceptance criteria rather than weak research. A high rate across every type points to a systemic issue such as unclear briefs or missing sources. Do not publish the breakdown for individual analysts without a fair context and a plan to use it for coaching.

Report the rate for the first thirty days separately from any later reopening. A deliverable that reopens on day three is a different problem from one that reopens on day ninety. The early rate points to acceptance quality, while the later rate points to durability. Keeping the windows separate makes the trend easier to interpret.

Separate legitimate change from defect

Classify each reopening as preventable or contextual using the cause codes. Preventable reopenings are the ones the team could have avoided with a better brief, a source check, or a clearer acceptance bar. Contextual reopenings follow a real change in the market, the product, or the decision. Report the two rates separately so the team does not punish itself for legitimate updates.

A high contextual rate may still be a design problem if the deliverable was presented as durable when it was not. Add a review date or an expiry note when the finding depends on a fast-changing source. The reader then knows when to expect a refresh instead of treating the original as permanent. The distinction turns a reopening into a planned event rather than a surprise.

Set a threshold for what counts as a new decision context. A changed competitor fee is a real change, while a buyer's new preference may be a normal part of the sales cycle. The threshold should be written before the coding begins. Without it, every reopening can be explained as context.

Limits and sources of error

Reopenings are recorded inconsistently when the team works across several tools. A change made in a private message may never reach the deliverable record, while a change in the shared file is easy to count. Note which tools were searched and which periods are incomplete. A rate built on partial records should be labeled as a lower bound.

The cited public sources describe occupational outlook, business survey practice, and information protection. They do not supply a reopening benchmark for this team. Use the result to compare the team with its own prior periods rather than with an external standard. Repeat the cohort measurement each quarter and keep the definition stable so the trend is meaningful.

Use the rate in a review

Bring the rate and the cause mix to the monthly research review. Ask which preventable cause is worth fixing first and assign one owner. A rate without a cause is a score, while a cause with an owner becomes a change. Keep the discussion focused on one cause so the team can see whether the fix worked.

Compare the next cohort with the prior one using the same definition. If the rate falls after a brief or template change, keep the change and document it. If the rate does not move, the cause may have been misclassified. A measurement loop is useful only when it changes a decision, so close the loop with a written follow-up.

Related GTM research