Project Handoffs: Review and Rework Costs

A handoff transfers work between people, teams, or suppliers. Missing requirements, incompatible files, or unclear acceptance criteria can create rework after that transfer. A prevention step costs time too. Compare the additional check with the specific rework outcomes it is expected to change, rather than applying a generic quality percentage to every project.

Define the failure event

Assume a hypothetical deliverable has a 20% chance of a handoff defect requiring six hours of rework at a $60 internal cost rate. The event cost is $360, and expected rework cost is $72 per deliverable. The 20% probability refers to one defined defect event per deliverable, not the share of labor hours wasted or the probability that the whole project fails.

A proposed half-hour review at an $80 internal reviewer rate costs $40 and is assumed to reduce the defect probability to 5%. Its modeled total is $58, or $14 below the existing process. The reduction in probability is an assumption to test, not a guaranteed effect of adding a review. Both alternatives exclude the original production effort because that effort is unchanged.

Find the reduction needed to cover the check

The $40 review requires an expected rework reduction of $40 divided by $360, or 11.11 percentage points of event probability. Starting from 20%, the new defect probability must be no more than approximately 8.89% to cover the added review cost under this model. That is a probability-point threshold, not an 11.11% relative reduction in defects.

If the review merely shifts work that was already included in a final inspection, it is not automatically an extra $40. Reconcile the activities and include only the change between alternatives. Conversely, if the new check delays a scarce specialist, evaluate the displaced work separately using a feasible alternative rather than an invented value for every waiting hour.

Measure the event and its consequences

Record the transferred package, defect category, correction hours, repeated review, and any actual additional supplier charge. Separate correction of an error from newly requested scope. A client asking for another feature does not provide evidence that the original handoff process failed.

If multiple defects can occur on one deliverable, use mutually exclusive outcome scenarios or an expected event count; a single-event probability model may understate cost. Track whether the six-hour severity changes as well as whether defects become less frequent. A 100% probability means the stated event occurs in every modeled case, while zero probability removes that event's expected cost, not all project uncertainty. The analysis supports a process decision and does not guarantee quality, savings, or on-time delivery.

Method references: OpenStax: Relevant Information for Decision-Making. Accessed October 22, 2026. All dollar figures are hypothetical worked examples.