Y5.01.3Procedural deviation reportingdesignresearch

Field deviations must be recorded rather than normalized

Aliases: deviation reporting · work-as-done · operational workaround

What it is

Procedural deviation reporting records where work-as-done differs from work-as-prescribed, including the condition, step, rationale, and disposition. A deviation is not automatically misconduct; it may be adaptation to an equipment fault, an unworkable instruction, or operational pressure. Unrecorded adaptation, however, can become an unofficial routine known only within a crew.

Why it happens

Front-line work must absorb variation that procedures cannot enumerate. When stopping and reporting are costly while a workaround succeeds, the organization receives a false signal that the formal process works. Successful deviations are reinforced without exposing the risk assumptions they violated. Recording turns local adaptation into comparable evidence and makes it possible to separate useful flexibility, procedural defects, and unacceptable boundary crossing.

Studying it

Observations, interviews, execution logs, and deviation reports can be time-aligned to reconstruct triggers, actual actions, alternatives, and outcomes. The unit of analysis should be the situated decision, not a count of “noncompliant people.” Anticipated punishment creates under-reporting, so anonymous channels, near-miss records, and maintenance evidence are useful triangulation. More reports may indicate a healthier reporting climate rather than worsening safety.

Where it stops holding

Documentation is not authorization. Bypassing an interlock, changing an isolation boundary, or exceeding a permit still requires the relevant stop and approval. Emergency action may prevent contemporaneous entry, but the timeline should be captured while memory is fresh. Free text alone imposes high effort; rigid categories alone erase the motive for adaptation.

Applying it

  • Add a “cannot continue as written” path that pre-fills asset, revision, step, and time, then asks for the discrepancy, rationale, and safe disposition.
  • Make stopping and reporting a compliant path without treating every good-faith report as a disciplinary admission.
  • Aggregate recurring deviations and route them to procedure revision, equipment change, training, or resourcing.
  • Verify the loop through closure rate, feedback reaching the reporter, and recurrence of the same deviation—not report count alone.

Related

  • Same group: Y5.01.1 Procedures must match the actual equipment state · Y5.01.2 Outdated procedures induce errors
  • Nearby: Y7.02 Error reporting · Y7.03 Procedural deviation
  • Search terms: procedural deviation · work-as-done · operational adaptation

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/Y5.01.3