Track preventive versus corrective split measurement with a field-ready workbook that records work, causes, evidence, and post-award outcomes.

Geplaatst op: jul. 03, 2025

Measuring Preventive vs Corrective Split: What to Record

Measuring Preventive vs Corrective Split: What to Record

Workbook control and one-record rule

Use one copy of this workbook for each completed maintenance work order. The purpose is to make preventive versus corrective split measurement repeatable: a reviewer should reproduce the classification from the trigger and evidence, not from the technician’s shorthand. Complete the sheet before closing the source work order.

Direct answer. The one-line answer — preventive versus corrective split measurement is the working record for preventive versus corrective split measurement. preventive versus corrective split measurement is worthless until preventive-vs-corrective-split is attached to it as evidence. A preventive versus corrective split measurement covers the period after handover. It names the owner. preventive versus corrective split measurement is the interval that makes preventive versus corrective split measurement visible before it becomes a complaint.

preventive versus corrective split measurement is used here in the narrow sense set out in preventive versus corrective split measurement. It is a working definition built for preventive versus corrective split measurement. It is not a statutory one, and it has to be read against the market and product concerned.

  • Agree the cadence — define how often preventive versus corrective split measurement is inspected
  • Agree the condition — name the condition that forces a change to preventive-vs-corrective-split
  • Watch the value — keep one metric that shows workbook control is healthy
  • This is the sequence preventive versus corrective split measurement has to follow, anchored on preventive vs corrective split.
Control fieldFill-in entry
Workbook codepreventive-vs-corrective-split
Record identifier[enter unique identifier]
Door or unit identifier[enter object-schedule identifier]
Source work order[enter reference]
Owner and reviewer[enter names or roles]
Reporting period and version[enter both]

Set the preventive versus corrective split boundary before compiling numbers. The default unit is one completed maintenance work order. Project work, product change, general surveys without a maintenance purpose, and investigation-only activity remain outside the split and are reported separately. If planned work uncovers an unexpected fault, keep the planned task preventive and open a linked corrective order for the repair. The catalogue side of this is the smart door locks.

Work classInitiating triggerTypical workTreatment
PreventiveApproved plan before unexpected loss of expected functionScheduled inspection, planned cleaning or planned adjustmentCount completed preventive orders
CorrectiveObserved loss of expected functionDiagnosis, repair, replacement and return to serviceCount completed corrective orders
Project or changeRequested alterationAccess change or product migrationExclude and show separately
Investigation onlyOrigin not yet establishedLinked diagnostic workExclude until origin is confirmed

Capture the work-order header

Transcribe the header rather than reconstructing it later. These fields provide the minimum evidence needed to reproduce a classification and close the work-order trail.

FieldWhat to enterSource or check
Door or unit identifierObject-schedule identifierAsset schedule
Model and variantLabel transcriptionLabel; confirm on the dated product page for the specific SKU if an instruction is needed
Reported timeDate and timeIntake log
Operable again timeDate and timeField closeout
Symptom and observationTechnician wording plus measured observationTechnician
ChecksOrder run and what each ruled outWork note
Parts or unit actionItem fitted or swapped; old unit retainedMaterials record
EvidencePhotograph or readingAttachment
Credential stateBefore and after where relevantAccess record

Use the object-schedule identifier rather than a room label as the join key. Do not overwrite the reported symptom with a later technical label.

CONFIRM-PER-SUPPLIER: Ask whether any model-specific service instruction applies to the exact SKU and retain the dated response.

Classify from the initiating trigger

Classify from the trigger, not from the tool used, elapsed effort or invoice value. A planned task remains preventive even if it consumes substantial time. A task becomes corrective when observed loss of expected function starts the record. A general inspection that finds a fault can split into a preventive inspection and a linked corrective repair.

flowchart TD
    A[Open work order] --> B{Planned before unexpected fault}
    B -->|Yes| C[Preventive]
    B -->|No| D{Unexpected loss observed}
    D -->|Yes| E[Corrective]
    D -->|No| F[Project or investigation]
    C --> G[Complete classification and evidence]
    E --> G
    F --> G
Decision questionPreventive answerCorrective answer
TriggerApproved plan before unexpected lossObserved loss of expected function
PurposeMaintain the planned conditionRestore operability or expected use
State at startNo unexpected loss recordedUnexpected loss recorded
Service resultPlanned work completedFault-initiated work completed
EvidenceTrigger, task and completionSymptom, checks and restoration

Do not classify a mixed visit twice. Retain the preventive task under its approved trigger, create or link the corrective order for the fault, and count each work order once according to its initiating trigger.

Complete both work branches

Use the same evidence discipline for each branch. Complete one preventive maintenance record for planned work; complete one corrective maintenance record when a fault initiates the order.

Preventive fieldFill-in entry
Planned trigger[enter schedule, plan or event reference]
Task completed[enter checklist item and action]
Condition observed[enter before and after observation]
Completion evidence[enter reading, photograph or sign-off]
Unexpected condition[enter found or not found]
Linked corrective order[enter reference if a fault was found]
Next planned follow-up[enter trigger and planned date]

For preventive work, preserve the connection between the approved plan and the completed task. A blank condition field cannot demonstrate whether the planned work was performed or what was found.

Corrective fieldFill-in entry
Reported symptom[enter plain description and affected function]
Expected versus observed[enter functional comparison]
Check sequence[enter order run and what each ruled out]
Cause status[enter confirmed, likely or unknown]
Action[enter adjust, repair, replace, no action or pending parts]
Parts or unit[enter item fitted and old unit retained]
Operable again[enter date, time and supporting evidence]
Repeat or linked order[enter relationship to another record]

Do not convert an unknown cause into a confirmed cause because a repair restored service. Restoration evidence and root-cause evidence are separate conclusions.

Attach check-by-check evidence

The field service log becomes usable evidence when each check states what it ruled out. Record only checks actually performed and follow the approved model-specific instructions.

CheckRecordWhat it helps distinguish
Door, handle and latchObservationAn obstruction, alignment or latch-preload explanation
Manual operationResult when covered by approved instructionsWhether the internal mechanism is seized
Power or alert indicationReading and symptomA power condition from a no-response symptom; an alert is a threshold, not a measurement
Physical and controller stateBoth recorded statesA state mismatch from a drive fault
Credential pathResponse and routeThe credential layer from the drive path
Same symptom across matching unitsAffected-door listConfiguration, firmware or batch investigation before unit replacement

Use root cause evidence as the chain from symptom to cause, not the final label alone. If a check was skipped, record why it was skipped and what uncertainty remains. A missing check is visible evidence; an assumed check is not.

Separate reason, symptom and timing

Use fault classification and work-order coding as separate fields. The symptom says what was seen; the reason code says why the work was initiated.

Code groupAllowed entryControl
Preventive reasonPlanned inspection, cleaning, adjustment or replacementLink the approved trigger
Corrective symptomNo response, no drive, credential not recognized, power alert or physical damageAvoid an inferred cause
Cause statusConfirmed, likely or unknownKeep separate from the symptom
ActionAdjusted, repaired, replaced, no action or pending partsLink the materials record
DispositionOperable, workaround or not operableDefine the closure state
Record relationRepeat, parent or childCount each order once

Record four timestamps when applicable. Response time runs from the report to acknowledgement. On-site attendance time runs from acknowledgement to arrival. Resolution time runs from the report until the door is operable again. These are measurements from the buyer’s own records. Keep administrative closure separate because closing a record does not prove that the door is operable.

Aggregate the completed records

The preventive versus corrective split measurement below uses completed work orders in one stated population and period. Keep work-order count and technician effort as separate views because one planned visit may consume more effort than several fault-initiated tasks.

MeasureEntry ruleResult
Preventive orders, PCount unique completed preventive identifiers[enter]
Corrective orders, CCount unique completed corrective identifiers[enter]
Preventive shareP divided by P plus C[enter percentage]
Corrective shareC divided by P plus C[enter percentage]
Preventive effortSum recorded preventive labour[enter]
Corrective effortSum recorded corrective labour[enter]
Excluded or unclassifiedCount separately with reason[enter]
  • Apply the same population, period and inclusion rules to numerator and denominator.
  • Reconcile P plus C to the source system; do not count linked orders twice.
  • Show exclusions and changed classifications beside the result.
  • Treat the split as work composition, not proof of avoided failures or service quality.
  • Mark a percentage not applicable when its denominator is zero.
  • Group results by site or model only after identifiers and reporting periods reconcile.

Review before closing the workbook

A reviewer should be able to reproduce the classification without contacting the technician. Record both the result and any required rework.

Reviewer checkReviewer entryPass or rework
Trigger supports the selected class[enter][enter]
Every performed check states what it ruled out[enter][enter]
Operable-again time has supporting evidence[enter][enter]
Mixed visit has a linked order[enter][enter]
Counts reconcile to the source records[enter][enter]

CONFIRM-WITH-LOCAL-SITE-POLICY: Confirm the site’s approved access, safety and record-retention instructions before field use.

If the reviewer cannot reproduce the classification, leave that field unresolved and return the record for correction. Do not convert an uncertain class into a convenient percentage.

Connect the measurement to its evidence

Keep the workbook connected to its source records. The Office Smart Lock Site Survey and Smart Lock Retrofit Site Survey provide useful baseline door and constraint information. For adjacent workflows, use Preventive vs Corrective Split Worksheet You Can Fill in on Site for a field worksheet, Preventive vs Corrective Split: From One Site to Twenty for consistent treatment across sites, and Preventive vs Corrective Split Documentation Set to audit the documentation set.

The practical counterpart to this point is the smart lock handover checklist. That is the same question preventive versus corrective split measurement has to answer here.When supplier support is requested, provide the completed workbook, source order, photographs and readings as one evidence pack. Ask the supplier to respond against the exact model and dated product page, and keep its answer separate from the buyer’s classification decision. A completed sheet is ready for aggregation only when its trigger, evidence, scope and reviewer decision all agree.

The next step is to request a quote.

Winkelwagen
Uw ervaring op deze site wordt verbeterd door cookies toe te staan Cookiebeleid
Chat on WhatsApp