Calculate Bad-Record Costs Without Invented Revenue
Model bad-record costs using direct correction and review effort, avoiding double counting and unsupported claims about lost lifetime revenue.
10/24/20263 min read
An incorrect account record can create visible correction work and uncertain downstream consequences. Those consequences should not all receive the same financial label. A documented repair, a possible delay and an imagined lost lifetime customer are different kinds of evidence.
Use an attribution card to decide which cost claims are supportable for a particular defect. This is different from a general rework ledger, which classifies operational return events. Here the task is to stop an individual bad record from accumulating unrelated costs or an unsupported revenue story as it moves through a business case.
Define the causal question narrowly
Identify the specific defect, affected record version and decision that relied on it. Ask what activity occurred because of that defect, rather than what happened nearby in time. A customer postponing a meeting after a correction does not establish that the correction caused the postponement.
W3C's provenance overview describes information origins. Trace the evidence behind each proposed attribution. The card below is an original reasoning aid, not a causal study or a method for determining legal damages.
A completed fictional attribution card
An invented account brief assigns a branch to the wrong operating entity. The mistake is copied into two internal views. A researcher corrects the shared source once; a reviewer then checks both dependent views. A commercial draft proposes describing the incident as thousands of dollars of lost opportunity.
Direct correction: a hypothetical work log records twelve researcher minutes repairing the source. Supported category: attributable staff effort, assuming the log and defect relationship are verified.
Dependent-view review: another hypothetical log records six reviewer minutes checking both views together. Supported category: six minutes total, not six minutes automatically charged to each view.
Meeting delay: the meeting moved, but the reason is unconfirmed. Supported category: unresolved association. No defect-attributed delay cost enters the subtotal.
Opportunity loss: no rejection reason or causal evidence links the defect to a lost sale. Disposition: remove the asserted lost-revenue amount from the business case.
Recurrence exposure: the shared source could have spread further. Disposition: investigate the dependency, but do not charge hypothetical future corrections as though they already occurred.
All events and quantities are invented. The card demonstrates how to constrain a claim; it does not report an actual incident or prove a typical defect cost.
Calculate only the supported boundary
For illustration, use assumed internal planning rates of US$24 per researcher hour and US$36 per reviewer hour. Twelve minutes is one fifth of an hour, giving US$4.80 of research effort. Six minutes is one tenth of an hour, giving US$3.60 of review effort. The modeled attributable resource subtotal is US$8.40 for this incident.
Do not call that a universal cost per bad row. One defective source produced two dependent views, but the repair was shared. Dividing or multiplying by whichever row count makes the business case larger would obscure what was actually done. Report one incident, three affected representations and eighteen staff minutes as separate measures.
The subtotal excludes unconfirmed consequences. That does not prove those consequences were zero. It means the available evidence cannot quantify or attribute them reliably. Preserve the unknowns in a separate section rather than filling them with optimistic or alarming guesses.
Keep cash, capacity and opportunity distinct
Allocated staff time is not necessarily an avoidable cash payment. Fixing the process may free capacity while leaving salaries unchanged. An outside correction invoice, if genuinely attributable and verified, would belong to a different cash-cost category.
Likewise, an opportunity value is not automatically revenue lost because of a defect. Even a documented complaint may establish dissatisfaction without establishing the full commercial counterfactual. If a consequential financial or legal valuation is needed, use appropriate expertise rather than extending this operational worksheet beyond its purpose.
Use the card to choose a proportionate remedy
The fictional incident suggests checking entity assignment before the shared source feeds dependent views. Estimate the proposed prevention effort separately. A check applied to every future record might cost more than repairing an occasional low-consequence defect, while a serious decision consequence can justify attention even when direct labor is modest.
Do not force every quality concern into a dramatic revenue figure. Present the verified defect, attributable resource boundary, unresolved consequences and proposed validation step. A decision-maker can then consider the issue honestly without mistaking a plausible story for measured financial harm.
Sources and scope
The worked examples and decision tools are original editorial proposals, not reported customer results. References support the identified context, not endorsement or validation of these methods.