OPS.11.1:5.4 - Change a report route while retaining its acceptance authority

A laboratory has promised an accepted report. Its operator produces an analysis record; a qualified reviewer examines that record and can require correction. Only the reviewer’s acceptance makes the report available for the promised use. The same person may hold both roles if the applicable rules allow it; their occupied intervals must then be reconciled as one person’s demand.

The solid arrows below pass named work products. The dotted links state conditions supplied by commitments, authority or resources; they do not pass the report or prescribe a sequence.

flowchart LR
  S["Sample and required case data"] --> A["Analyze"]
  A --> D["Analysis record"]
  D --> R["Review"]
  R --> P["Accepted report"]
  R --> C["Correction request"]
  C --> F["Correct the record"]
  F --> D
  K["Promised case and permitted start"] -. "enables" .-> A
  L["Analyzer and eligible operator time"] -. "required during analysis" .-> A
  V["Reviewer authority and available time"] -. "required for review and acceptance" .-> R

Suppose incomplete case data repeatedly occupy reviewer time. One proposal inserts an automated completeness check between the analysis record and review:

flowchart LR
  D["Analysis record"] --> X["Check required fields"]
  X --> Y["Record with required fields present"]
  Y --> R["Review"]
  X --> C["Missing-field report"]
  C --> F["Complete the data"]
  F --> X
  R --> P["Accepted report"]

This second diagram shows only the changed route. The first diagram’s start conditions, review authority, substantive correction return and resource constraints still apply. The automated check establishes field presence, not correctness or acceptance. Add its computing demand and the operator’s completion work to the resource account; compare the saved review work with that added demand. The new route can be worse if it moves the bottleneck to a scarce operator. A simulation or trial is useful only if the remaining uncertainty can change the choice.

These proposals change different things:

Proposal	What changes and what must be obtained
Give an already qualified and authorized reviewer a different case or time slot.	Reconcile that person’s existing assignments and commitments through OPS.10–OPS.13 and OPS.19. The allocation need not change any authority relation.
Insert the completeness check under existing permission.	Compare the changed route and its resource consequences. OPS.16 can govern a useful trial; a locally usable operating arrangement can supply its conditions.
Let the operator accept reports without the previously required reviewer.	The proposed completion and authority relations change. Obtain the relevant professional acceptance decision and organization-design/assignment result before relying on the proposal. A faster route does not authorize it.
Introduce the route where staff cannot yet perform or sustain it.	Establish the needed capability, practice and support. Use the relevant development, Method-introduction or organization-change methods for that question; put their actual learning and support work into the same resource account. An unchanged organization chart does not supply those capabilities.

The result is a comparison of identified changes and their consequences, with any missing decision left visible. It need not become a redesign of the whole organization.

These are constructed operating cases, not measured performance claims.