Door hardware schedule retrofit projects: A retrofit door hardware schedule should capture existing doors, fit, lock functions, evidence, and handover.

Publicado em: dez 12, 2025

Door Hardware Schedule in Retrofit Projects

Door Hardware Schedule in Retrofit Projects

In door hardware schedule retrofit projects, the schedule is pulled between two realities: the doors already standing in a building and the hardware sets proposed for purchase. A catalogue can describe the proposed set; only a survey can establish the existing one. I keep a cross-border diary because each hand-off—survey to schedule, supplier to reviewer, review to installer—can quietly change a dimension, function or responsibility. The entries below form an illustrative method, not a report about a particular building. I record what was observed, what decision followed, and what evidence remains open. That rhythm is what makes a door-hardware-schedule useful: a future reader should be able to build the same door set without calling the person who wrote it. The survey is not a preliminary attachment. It is the passport that lets the schedule, submittal and installation cross between disciplines without losing their meaning.

Direct answer. Condensed to the essential point, door hardware schedule retrofit projects turns a request into a decision record. door hardware schedule retrofit projects and door-hardware-schedule are the two parts of door hardware schedule retrofit projects most often skipped. A door hardware schedule retrofit projects is a working pack for the people who write the requirement. door hardware schedule retrofit projects is the first section handed over. Every door hardware schedule retrofit projects template comes with it.

  • Frame the requirement — use a template that names the physical constraints in door hardware schedule retrofit projects
  • Catalogue the evidence — attach the conformity file for the SKU behind door-hardware-schedule
  • Deliver it in one request — issue one complete package per door class, not one per query
  • Treat this as the door hardware schedule retrofit projects sequence, with door hardware schedule as the reference.

Diary entry 01 — Surveying the boundary

Every opening receives a stable door ID that follows it through survey, schedule, submittal, installation and handover. The retrofit door set survey records what is physically present, while existing door field measurements establish whether the proposed hardware can work with it. I photograph the overall opening, capture the leaf and frame separately, and label every image with the door ID. I also record the swing, the visible construction condition, the existing faceplate and strike, and any survey restriction. A catalogue photograph is not evidence of the installed condition, and a dimension copied from another opening is not a substitute for measuring this one.

The dimensional record names the backset, meaning the distance from the door edge to the centre of the spindle or cylinder. Bore diameter and bolt-to-bore distance are separate entries, not aliases. Faceplate and strike dimensions are recorded as a matched pair because those two halves of the closing edge must agree. Where a mortise, rim lock or multipoint arrangement is present, its location is described without assuming that the replacement will use the same case. The schedule later carries those observations into a clear decision: retain, adapt or replace. That decision is not hidden in a general note; it sits against the affected door ID with the evidence attached. Teams needing a more structured starting point can compare the method with Smart Lock Retrofit Site Survey. Every commercial claim here has to be checked against the smart door locks.

Diary entry 02 — When the catalogue crosses the site record

Here the catalogue crosses the site record, and the crossing rarely happens cleanly. A proposed lock may have the right function yet the wrong relationship to the existing leaf or frame. Lock and frame compatibility is therefore a schedule decision, not a product preference. I open every relevant case, record the lock case type and mounting references, and mark any dimension that the supplier must confirm for the exact submitted configuration. The supplier answers the proposed configuration; the survey answers the building. Neither replaces the other. Door hardware coordination means preserving both answers in the same row.

During an installation walkdown, I saw a neat catalogue pairing fail because the team had compared faceplate width but not the spacing of the fixing holes, and had not linked the strike to the frame that would actually be retained. The lesson was not that a particular model was wrong. It was that the schedule had compressed three different objects into one line. I now give the leaf, frame and locking arrangement separate fields, then add a final interface note. A photograph may prompt a question, but it cannot close a dimensional question. Where openings are assessed within a workplace project, the wider discipline in Office Smart Lock Site Survey still applies: identify the door before comparing products.

flowchart LR
    A[Existing door survey] --> B[Measured door record]
    B --> C[Door set schedule]
    C --> D[Supplier submittal]
    D --> E[Recorded review]
    E --> F[Installation release]
    F --> G[As built handover]

The diagram is the evidence trail from survey to handover.

Diary entry 03 — Composing the schedule grid

I compose the schedule from the door set outward: door leaf, frame, hardware, locks, egress route and locking arrangement. Each line receives the same door ID used in the field. I avoid generic labels such as “smart lock” where the reader needs to know whether the item is a lock case, reader, credential device, exit interface or associated control. A retrofit also needs a status column: field-confirmed, supplier-confirmed, sample-verified or outstanding. That status tells the installer what is safe to fabricate against and tells the reviewer which promise has not yet been earned.

Observed conditionSchedule responseEvidence needed
Leaf and frame differ from the drawing assumptionIssue a door-specific hardware setMeasured survey sheet and recorded decision
A prepared pocket or concealed fixing remains uncertainHold procurement until field verificationDated site check and sample record
Faceplate and strike do not matchCorrect the closing-edge interface before releasePaired dimensions and installation sign-off
The door has a different role from the generic scheduleReassign its function and locking arrangementDoor-by-door design decision
The finish reference conflicts with the retained componentReconcile the interface before orderingAgreed finish reference and sample record

The most useful table is not the largest. It is the one that lets a reviewer answer five questions without a phone call: Which physical door is this? What did the survey find? What is being changed? Which supplier evidence supports the proposal? Who accepted it? When a row cannot answer those questions, I return it as incomplete rather than smoothing over the gap with a general note.

Diary entry 04 — Submittal at the return border

The supplier package arrives with finished hardware, but the reviewer needs an evidence package. I request dimensional drawings for the exact submitted configuration, installation instructions relevant to the retained leaf and frame, finish references, and a list of documents that support the claims made. A brochure can orient the reader; it cannot establish the fit of this door. Where a capability depends on the supplier, I record it as a claim to be substantiated rather than as an established feature.

CONFIRM-PER-SUPPLIER: Confirm each product claim with the named document, its scope, the document holder and the exact submitted configuration.

The review itself then needs a submittal review record. It names the door IDs reviewed, unresolved observations, accepted revisions, the reviewer and the decision date. The submittal is not approved until the review is recorded and dated. For the detailed product-data fields, Door Hardware Schedule: A Smart Lock Specifier Guide is a useful companion; for the final pass, Door Hardware Schedule: Reviewer Checklist keeps the hand-off disciplined. Neither replaces the project record. They help ensure that the project record remains the source for the installed door set.

Diary entry 05 — Questions for deciding authorities

Some retrofit decisions cannot be closed inside a product schedule. I do not answer them with a generic catalogue statement. I state the door role, the proposed change, the unresolved consequence and the person or authority who must decide. The record then travels as a dated question with an attachment set rather than as an implied assumption.

Building-control scope is a per-project question. The record identifies the proposed work and the installed-door criteria requiring review.

CONFIRM-WITH-LOCAL-BUILDING-CONTROL: Confirm the applicable retrofit scope and installed-door criteria with the local building-control authority.

Fire-door and escape-route combinations require the assembly and deciding authority to be identified.

CONFIRM-WITH-FIRE-AUTHORITY: Confirm fire-door, panic-hardware and escape-route decisions with the fire authority or the client’s named fire-strategy authority.

Accessible operation requires the affected door, proposed change and verification method to be stated.

CONFIRM-WITH-ACCESS-CONSULTANT: Confirm operable-part, approach and installed-door verification with the client’s access consultant.

Diary entry 06 — Translating the schedule for installation

The installation package should read the schedule in the same order as the survey. The retrofit installation sequence starts with a released door ID, repeats the critical dimensions, identifies the retained and replaced components, and gives the installer the interface notes that were missed on the first survey. A hold point stays visible until the named evidence closes it. I distinguish a supplier instruction from an installer decision: one tells us how a proposed item is intended to fit; the other records what the site actually required.

The most productive pre-install check is a paper exercise before tools arrive. Using the survey sheet, schedule line and supplier drawing together, the installer marks every fixing reference, cavity, cable route, spindle location and closing-edge interface that will be touched. If a dimension cannot be reconciled, the installer marks it as an exception rather than adapting the closest component on site. This protects the lock and frame compatibility recorded in the schedule and creates a clean instruction for the next trade. It also reveals whether the order was designed around an installed condition or around a catalogue image.

Diary entry 07 — Changing one condition, changing the record

Retrofit work changes after the schedule is issued. A leaf is replaced, a frame is retained, a closer is moved, or a concealed fixing proves different from the survey. The response is not to edit the line silently. I issue a change note carrying the door ID, the condition found, the affected fields, the proposed response and the decision route. A changed faceplate or strike can alter the interface; a changed lock case can alter the prepared openings. The schedule, submittal, installation issue and handover record must all point to the same revision.

When I am tempted to describe a solution as “equivalent”, I stop and name the dimensions, functions and interfaces that must be equivalent for this door. If the evidence does not cover them, the request remains an or-equal question for the specifier, not an installer shortcut. My diary entry records both the request and the reason for the decision. That reason is more valuable later than the final model name because it explains what was checked. It also protects the client from assuming that visual similarity proves operational similarity.

Diary entry 08 — Carrying the record into handover

Handover is the final border crossing. The installed condition must be able to re-enter the documentary system without a site visit. Handover documentation therefore links each door ID to the accepted schedule line, final submittal record, measured exceptions and the party responsible for the information. Photographs help identify the finished appearance, but the attached schedule and records carry the dimensions and decisions.

Handover recordRequired contentCustody at close
Accepted door set scheduleFinal door IDs, functions, interfaces and revision statusDesign authority or appointed record holder
Submittal review recordNamed documents, review comments, decisions and datesDesign team
As-built measurement recordField dimensions, exceptions and marked-up locationsInstaller, then transferred to the appointed client holder
Operations informationCredential and configuration records with maintenance contactsClient’s appointed operator

Ownership is stated by role and confirmed for the contract. The document says who compiled the record, who checked it, who received it and which revision is current. If the client has not appointed a holder, the gap remains visible in the action list. An as-built file that nobody owns is not closure. A dated transfer with a named recipient is.

Diary note — The schedule becomes reusable language

Door hardware schedule retrofit projects are best managed as a chain of evidence rather than a list of preferred products. The survey establishes the door, the schedule states the door set, the submittal answers the proposed configuration, the recorded review accepts or rejects it, the installation issue controls the work, and the handover record closes the loop. Each boundary has a named input and a named owner. A reader can see where a decision was made and which evidence remains conditional.

Readers comparing approaches usually start with smart lock pre shipment inspection china. That is the same question door hardware schedule retrofit projects has to answer here.That is the lasting value of the diary. It preserves the reasoning while products, suppliers and project teams change. Before the next revision, I ask the schedule owner to confirm the door IDs, unresolved fields and authority decisions; before procurement, I ask the supplier to confirm the exact submitted configuration; before installation, I ask the installer to return exceptions against the same IDs. When a request for a quotation or sample arrives, send this record first. The receiving team can respond to a defined door set rather than to a loose product description, and every later answer has a place to land.

Nothing is binding until a supplier prices it, so request a quote.

O seu carrinho
A sua experiência neste site será melhorada se permitir cookies Política de cookies
Chat on WhatsApp