Preventive versus corrective split portfolio planning: plan a smart-lock portfolio refresh by separating preventive work from corrective action, assigning.

نُشر في: ديسمبر 24, 2025

Planning Preventive vs Corrective Split Across a Portfolio Refresh

Planning Preventive vs Corrective Split Across a Portfolio Refresh

Use this tearoff after a portfolio refresh is funded but before its field schedule is released. It turns a mixed list of inspections, planned replacements, troubleshooting, and repair work into two controlled lanes. Preventive versus corrective split portfolio planning means deciding which action is intended to reduce a defined future risk, which action answers an observed fault, and where ownership changes. Fill one line per door population and one line per proposed action; do not use room labels as a substitute for the object schedule.

Direct answer. Pair this portfolio-level decision with the Preventive vs Corrective Split Worksheet You Can Fill in on Site.

Freeze the portfolio boundary before work is classified

The refresh boundary needs a stable population before a task can be called preventive. If that denominator changes later, portfolio refresh planning comparisons become unreliable. The baseline reading is Smart Lock Access Point Planning.

  • Use the door or unit identifier from the object schedule, not a room number alone.
  • Record the model and variant from the label or catalogue row; confirm on the dated product page for the specific SKU before planning SKU-dependent work.
  • State the approved refresh reason for each cohort: condition, configuration, component change, operational requirement, or another documented reason.
  • Assign each cohort an operational priority and a named planning owner.
  • Freeze the population revision date so later additions appear as a recorded change rather than silently changing the plan.

Turn proposed tasks into a maintenance work classification

Classify an action by its trigger and purpose. An action planned before a fault is preventive only when it is tied to a defined risk or approved refresh criterion. Work initiated by an observed fault is corrective.

Proposed activityClassification laneRequired basis
Scheduled condition inspection before a fault is reportedPreventiveApproved refresh criterion and task record
Planned component change during the refreshPreventiveApproved change criterion and documented scope
Troubleshooting after a fault reportCorrectiveReported symptom and ordered diagnostic checks
Repair or unit replacement after a faultCorrectiveRepair evidence, fitted part or swapped unit, and return-to-service record
Control introduced after a cluster of faultsPreventive only after validationEvidence linking the control to the cause, plus an owner and review point

Anything that does not have a documented trigger remains unclassified. Do not place it on a technician’s schedule merely to keep the queue moving.

Build the smart lock preventive maintenance checklist

This is where preventive versus corrective split portfolio planning becomes a control rather than a label. Each task should enter only one queue, although both queues may feed the same review meeting.

  • Preventive lane: record the cohort, approved scope, owner, planned window, prerequisites, completion evidence, and exception route.
  • Corrective lane: record the fault reference, report time, acknowledgement, attendance, diagnosis, corrective action, and operable-again time.
  • Link each queue item to the relevant door or unit identifier.
  • Prevent one task from appearing in both queues unless the relationship is explained.
  • Do not convert a corrective repair into preventive work without evidence that the underlying cause was controlled.
  • Carry an unresolved preventive task into the next portfolio review rather than silently dropping it.
flowchart TD
    A["Set the portfolio boundary"] --> B["Classify each proposed action"]
    B --> C{"Preventive or corrective?"}
    C -->|Preventive| D["Preventive queue"]
    C -->|Corrective| E["Corrective queue"]
    D --> F["Complete refresh gate"]
    E --> G["Resolve and document fault"]
    F --> H["Review portfolio evidence"]
    G --> H

Require one evidence packet at every refresh gate

A task is complete only when its record can explain what happened and what was ruled out.

  • Door or unit identifier, model, and variant from the label or catalogue row, supported by the dated product page for the specific SKU.
  • Date and time the fault was reported and date and time the door was operable again, where a fault exists.
  • Symptom in the technician’s words, followed by the measured observation.
  • Checks performed in order and a record of what each check ruled out.
  • Parts fitted or unit swapped, with the removed unit retained under the buyer’s disposition process.
  • Credential state before and after the intervention, where credentials were involved.
  • Photograph, reading, or other supporting output used to reach the conclusion.
  • Confirmation that any SKU-dependent procedure matches the dated product page before the technician starts work.

Control the corrective queue without blocking preventive work

Treat response time, on-site attendance time, and resolution time as separate intervals. Calculate MTTR only across a defined population and period; it does not reveal unreported doors or the tail of unresolved cases.

  • Record the report through the agreed channel and capture acknowledgement separately from attendance.
  • Follow the Preventive vs Corrective Split Triage: The Branch to Follow First to order checks at the door.
  • Use the Escalation Path for Preventive vs Corrective Split when ownership, severity, or missing evidence prevents a normal close.
  • Move a proposed preventive control into the preventive queue only after its cause-and-effect relationship has been validated.
  • Keep the fault escalation path visible in the corrective record, including every handoff and the reason for escalation.

Compare release decisions across the two lanes

A task should not be released merely because its scheduled date has arrived. Compare the evidence against the lane’s purpose.

Decision pointPreventive release testCorrective release testPortfolio action when evidence is incomplete
Work authorizationScope matches an approved refresh criterionFault is recorded and the response route is assignedHold the task and identify the missing owner or record
Field completionRequired inspection or change evidence is attachedDoor-operability record and corrective evidence are attachedKeep the item open and prevent it from entering the completed baseline
Cause-control decisionControl is linked to a documented riskRoot-cause evidence justifies moving work into the preventive laneRetain the action in its original lane pending validation
Portfolio reviewTrend against the frozen population is availableFault pattern and closure evidence are availableRevise the population record and explain the change

Use the Measuring Preventive vs Corrective Split: What to Record to align both lanes with the same population and record structure.

Close the tearoff with owner sign-off and controlled exceptions

The portfolio owner should sign the classification, not merely the purchase schedule. The corrective owner should sign each return-to-service record, while the preventive owner signs completion against the approved criterion.

  • Match every completed record to the frozen portfolio population.
  • List incomplete, deferred, and cancelled tasks with a named decision owner.
  • Confirm that each exception has a reason, evidence, and next review point.
  • Attach the current tearoff to the installed lock lifecycle plan and relevant work orders.
  • Use the Preventive vs Corrective Split: From One Site to Twenty when one cohort’s pattern must be reviewed across the wider portfolio.

Before approval, check site-specific obligations.CONFIRM-WITH-LOCAL-AUTHORITIES: Confirm which access-control, fire-door, occupancy, and insurer requirements apply to the selected doors and service tasks before the plan is approved.

Once the requirement is written down, request a quote is the move.

عربة التسوق الخاصة بك
سيتم تحسين تجربتك على هذا الموقع من خلال السماح بملفات تعريف الارتباط سياسة ملفات تعريف الارتباط
Chat on WhatsApp