Start with a defined issue

Identify the event, affected activity, reporting period and responsible owner before estimating its cost. Record the requirement or expectation involved and whether its status has been confirmed. A missing record or a customer concern needs assessment; it should not automatically be described as a regulatory violation.

Gather the evidence needed for the immediate decision and assign unresolved questions to an appropriate reviewer. This guide proposes a cost-recording method. It does not determine liability, penalties, reporting obligations or the legal consequences of an event.

Record costs that can be supported

ASQ's cost-of-quality framework provides prevention, appraisal, internal failure and external failure categories. Use them where they fit the quality activity. They are not an exhaustive list of regulatory consequences or evidence that an issue caused every later business loss.

Separate observed impact from speculation

Keep actual expenditure, staff capacity and uncertain wider impacts distinct. If a contract was lost, identify the evidence linking the decision to the event before attributing the loss. Do not assign a financial value to reputation or missed opportunities merely because the issue could have affected them.

Record incomplete information rather than hiding it in a total. A scoped subtotal can still support a decision when its exclusions are clear. Finance and the responsible process owner should agree how costs and allocations are presented.

Use the evidence to choose follow-up

Illustrative workflow: a team investigates an incorrect entry in a sample record. It logs review time, any necessary rework and the time required to verify a correction. The owner checks whether the issue affected earlier decisions and selects a follow-up action. The team then observes comparable work over a defined period. This is a hypothetical workflow, not a documented customer incident or saving.

Compare the cost of the proposed action with the evidence for its likely effect, including uncertainty. Keep required actions separate from optional improvements. An expense register helps explain the work, while accountable review determines the action.

Evaluate a supporting workflow

Use the QMS software evaluation guide to demonstrate recording an issue, assigning follow-up and finding completion evidence. The workflow business-case guide can help compare implementation costs and measured results.

Reference checked 7 October 2026: ASQ's public quality-cost framework above. Software can support collection and follow-up, but this article establishes no universal reduction in risk, protection from penalties or guaranteed business outcome.