Common Mistakes in Refresh Versus Replace Economics
The most consequential refresh versus replace economics common mistakes are not dramatic arithmetic errors. They are missing definitions, mismatched baselines and decisions made before the door evidence is complete. This annotated datasheet gives a facility manager one row per field, an explanation of the required entry, the evidence that proves it and the error to remove. Treat every row as refresh-versus-replace-economics evidence, not as a general maintenance note.
Annotated fields for one door decision
Direct answer. Enter each row against one door or unit in the object schedule. A room label may help find it
Set local definitions before entry. A refresh is a planned intervention that retains the installed asset; a replacement substitutes the asset and brings its associated handover and validation tasks. The label alone does not settle the scope. The hardware behind this is in the smart door locks.
| Field | Annotation | Required evidence | Frequent mistake |
|---|---|---|---|
| Decision identifier | One decision, one version | Signed decision reference | Several branches mixed into one total |
| Door or unit identifier | Stable object-schedule identifier | Label and schedule row | Room name used as asset key |
| Required outcome | Define operability, access and administration | Agreed requirement | “Working” left undefined |
| Model and variant | Read from label; confirm on the dated product page for the specific SKU | Dated source reference | Variant inferred from appearance |
| Current state | Record symptom and measured observation | Technician wording plus reading | Alarm treated as diagnosis |
| Checks completed | State order and what each check ruled out | Fault record | Actions listed without conclusions |
| Path scopes | Separate refresh and replacement deliverables | Parts, access, testing and handover | Unlike work bundled together |
| Cost basis | Use one accounting boundary | Estimate and booked-work status | Estimates mixed with actuals |
| Operational effect | Separate planned and observed effects | Timestamps and assumptions | One downtime factor applied to all |
A blank field is an evidence gap, not zero. Keep unresolved items visible until the approver closes or accepts them.
Errors that distort the comparison
A review of refresh versus replace economics common mistakes should challenge the narrative before it challenges the totals. Name the error and its effect.
| Error | Why it distorts the decision | Corrective entry |
|---|---|---|
| Refresh treated as the default | An inherited route masks fit for purpose | Test refresh against the required outcome |
| Whole-lock replacement inferred from one symptom | A symptom is not proof of root cause | Use ordered checks and ruled-out findings |
| Like-for-like assumption | Different work is compared as equal | Normalize scope and accounting boundary |
| Non-hardware work omitted | The path scope is understated | List configuration, handover, testing and disposal |
| Shared work counted twice | Apparent cost rises without added work | Identify common tasks once |
| Outage collapsed to one factor | Disruption is treated as uniform | Separate planned and observed entries |
| Exceptions removed | A difficult door disappears from the portfolio case | Keep an exception register and approver |
| Baselines changed mid-review | Old and new totals are no longer comparable | Version inputs and affected decisions |
Correct the entry before comparing paths. A calculation can be arithmetically correct and still support the wrong refresh or replace decision.
A gate before either path is approved
Use the gate before a refresh or replace decision is approved. It tests the evidence, not the preferred outcome.
flowchart TD
A[Open decision record] --> B{Evidence complete?}
B -->|No| C[Close evidence gap]
B -->|Yes| D[Define required outcome]
D --> E{Refresh meets outcome?}
E -->|No| F[Define replacement scope]
E -->|Yes| G[Define refresh scope]
F --> H[Compare same boundary]
G --> H
H --> I[Review exceptions and approve]
- Confirm the required outcome and comparison boundary.
- Attach current-state evidence and ordered checks.
- For a refresh, document how the work meets the outcome.
- For a replacement, define complete scope and handover tasks.
- Compare the same boundary, review exceptions and approve.
The refresh versus replace economics worksheet provides the write-down. The refresh versus replace economics decision tree appears in Clause Bank: Refresh Versus Replace Economics: Which Branch Do You Take for the branch logic. Neither document supplies missing site evidence.
Same-boundary refresh and replace comparison
Use the same question and boundary in both columns. A value from one path must not repair an omitted item in the other.
| Dimension | Refresh test | Replace test | Record to retain |
|---|---|---|---|
| Required outcome | Demonstrably restores required service | Expected deliverable and validation plan | Acceptance basis |
| Work scope | Defined intervention | Full scope including dependencies | Scope schedule |
| Operational effect | Planned intervention effect | Planned cutover and recovery | Assumption register |
| Continuity | Configuration and credential steps | Migration and handover steps | Before-and-after state |
| Evidence | Checks supporting the path | Parts, disposal and validation | Retained records |
This is the decision-comparison table, not a product scorecard. It keeps smart-lock lifecycle economics anchored to the service outcome and the evidence available at the door.
Evidence attached to the operating record
The refresh versus replace economics measurement record should sit beside the field service cost record. Record the door identifier, model and variant, report time, operable-again time, symptom, measured observation, ordered checks, work performed, parts fitted or unit swapped with the old unit retained, credential state before and after, and supporting photo or reading.
The practical counterpart to this point is smart lock retrofit project planning. That is the same question refresh versus replace economics common mistakes has to answer here.Resolution time runs from fault report to door operable again. MTTR is the mean of those intervals across a defined population and period; it does not expose unreported doors or the long tail. Use How to Measure and Record Refresh Versus Replace Economics to keep the definition and collection method together.
Readers comparing approaches usually start with smart lock installation project planning. That is the same question refresh versus replace economics common mistakes has to answer here.
Keeping portfolio assumptions consistent
Across several sites, installed lock portfolio planning needs a shared field dictionary, baseline date and exception treatment. Use the Smart Lock Retrofit Site Survey to capture door and hardware context without turning a site survey into a replacement instruction. Keep site observations separate from portfolio rules. If an assumption changes, version the decision log and identify every affected record rather than editing totals in place.
Questions to close before authorization
Before authorizing either path, route the open questions to the evidence owner and keep the responses with the decision.
CONFIRM-PER-SUPPLIER: Confirm on the dated product page for the specific SKU the applicable functions and supplied components; request evidence for configuration steps, credential handover and support obligations.
CONFIRM-WITH-LOCAL-AUTHORITY: Confirm with the relevant authority, site safety owner, insurer and contract owner which approval applies to changes affecting controlled doors; attach the written decision.
Use the completed sheet as the field service cost record attached to each refresh or replace decision. Before requesting supplier or internal approval, close blank fields, reconcile both scopes, list exceptions and name the approver. A reviewer should be able to repeat the method from the record without relying on memory. That repeatability, rather than a favored outcome, is the control this datasheet provides.
A quote request turns the written requirement into something a supplier can price: request a quote.

