Door Hardware Schedule: Cost and Risk Consequences
Use this runbook when a door hardware schedule is being converted into a purchasable door set rather than a list of hardware names. It gives the door hardware consultant a repeatable way to expose installation risk, document churn, service burden, and approval delay before a row becomes a commitment. The controlling discipline is door hardware schedule cost risk: connect every consequential field to its release evidence, owner, and downstream activity.
Direct answer. In short, door hardware schedule cost risk is the subject of this piece. door hardware schedule cost risk is where the work on door hardware schedule cost risk sits. door-hardware-schedule is what has to be evidenced before anyone signs. A door hardware schedule cost risk gives the specifier working documents. door hardware schedule cost risk is the document that decides the requirement. That is what door hardware schedule cost risk turns into.
door hardware schedule cost risk is used here in the narrow sense set out in door hardware schedule cost risk. It is a working definition built for door hardware schedule cost risk. It is not a statutory one, and it has to be read against the market and product concerned.
- State the requirement — use a template that names the physical constraints in door hardware schedule cost risk
- Compile the documents — attach the conformity file for the SKU behind door-hardware-schedule
- Submit once, complete — issue one complete package per door class, not one per query
- This is the sequence door hardware schedule cost risk has to follow, anchored on door hardware schedule.
The companion Door Hardware Schedule: A Smart Lock Specifier Guide covers the field-level schedule structure. This runbook governs the decisions that follow: what must be checked, what must be held, what evidence closes the check, and which cost or risk consequence remains if it does not.
Runbook boundary and required outputs The quote request
The control boundary is one scheduled opening. Treat its door leaf, frame, locks, hardware, locking arrangement, and position within the egress route as one door set. A change to any element can affect the others, so a schedule row should not be released while a consequential interface remains unresolved. The same ground is covered in the published piece Glass Door Smart Lock Price Guide. The catalogue entry point for this is the smart door locks.
The runbook produces four outputs:
- A baseline schedule showing the information used to release each opening.
- A cost-consequence register identifying financial exposure without inventing a cost figure.
- A decision record showing the evidence accepted, the conditions outstanding, and the person accountable.
- A controlled handover package transferred to the installer, supplier, and client operations team.
Use the identifier door-hardware-schedule consistently on the review sheet, issue register, and decision log. It prevents a later reader from confusing the current design baseline with an earlier revision.
Establish the decision roles
The specifier coordinates the review, but does not own every input. Record who supplies evidence, who checks it, and who makes the final decision. This prevents a supplier statement, installer assumption, or client preference from silently becoming a schedule requirement.
| Role | Provides or decides | Must not be left implicit |
|---|---|---|
| Door hardware consultant | Maintains the schedule baseline, checks cross-discipline coherence, records the decision | Approval without a dated review record |
| Supplier | Supplies SKU-specific dimensions, documents, finish references, and written limitations | A generic brochure used as proof of fit |
| Installer | Confirms site conditions, door preparation, fixing, and service access | Verbal assurance that the door set will fit |
| Client representative | Defines operational, security, access, and maintenance needs | A preference without a traceable project source |
| Authority or consultant with approval responsibility | Determines the applicable accessibility, fire, egress, or building-control decision | A general position treated as project approval |
Record a deputy for every role. A gate should not stop merely because the usual reviewer is unavailable; the deputy must have the same access to the evidence and authority to record the result.
Build the door set baseline
A door set specification must make the relationship among the leaf, frame, hardware, and locks inspectable. The schedule should identify what applies at a particular opening, while the supporting documents establish how the supplier proposes to satisfy that entry.
The following baseline catches omissions before a commercial commitment is created.
| Baseline field | Required schedule entry | Consequence of omission | Evidence owner |
|---|---|---|---|
| Opening identity | Door number, location, hand, swing, and schedule revision | Decisions cannot be tied to the correct opening | Specifier |
| Leaf and frame | Relevant construction, dimensions, frame type, and finish reference | Preparation and appearance assumptions may conflict with site conditions | Supplier and installer |
| Lock case | Mortise, rim lock, or multipoint arrangement | The installer cannot plan preparation or identify the faceplate and strike | Supplier |
| Dimensional interface | Backset, bore diameter, bolt-to-bore distance, and faceplate or strike data | A door that cannot be prepared as intended | Supplier |
| Operable hardware | Hinges, closer, pull, push plate, and other operating items | Coordination gaps appear at installation | Specifier |
| Locking arrangement | Locking sequence, free access, free egress, and special-condition interfaces | The door may be installed with the wrong operating logic | Client and security reviewer |
| Service route | Battery change, replacement, wiring, and access requirements | Maintenance may damage the finish or require avoidable removal | Installer and operations team |
| Evidence | Submittal revision, source document, review status, and recorded decision | The schedule cannot show why the selection was released | Specifier |
Backset is the distance from the door edge to the centre of the spindle or cylinder. Bore diameter and bolt-to-bore distance are separate dimensions. Omit one of them and the installer still lacks enough information to verify lock and door fit.
Route each row through the release gates
flowchart TD
A[Schedule rows issued] --> B[Cost and risk register built]
B --> C{Required fields present}
C -->|No| H[Hold row and request record]
C-->|Yes| D[Evidence review]
D-->|Incomplete| H
D-->|Complete| E{Fit evidence accepted}
E-->|Mismatch| H
E-->|Accepted| F{Authority decisions recorded}
F-->|Outstanding| H
F-->|Complete| G[Release door set baseline]
H-->B
The flow is deliberately serial. A later gate does not repair an earlier omission. A fit acceptance, for example, cannot replace missing backset data, and a recorded authority decision cannot substitute for a supplier’s SKU-specific evidence.
Create the cost-consequence register
Do not wait for a later invoice or installation problem to reveal the financial effect of an unresolved field. At schedule review, translate each missing or uncertain decision into the work it may trigger. The result is a risk register, not a forecast presented as fact.
| Decision variable | Release condition | Cost consequence if resolved late | Risk consequence if wrong | Required record |
|---|---|---|---|---|
| Door dimensions and lock interface | Required dimensions match the scheduled door set | Door preparation, replacement, or corrective work may be needed | The supplied lock may not fit the installed opening | Dimensioned product evidence and installer check |
| Hardware coordination | Leaf, frame, hinges, closer, strike, and lock relationships are recorded | Parts may be revised, reordered, or fitted awkwardly | Door operation and maintenance may be compromised | Coordination review record |
| Authority-dependent arrangement | Applicable decision is documented by the responsible authority | The release may be delayed while evidence is developed | The selected arrangement may not suit the project conditions | Dated authority or consultant record |
| Service access | Battery, wiring, and replacement routes are identified | Finished surfaces may need protection or repair after access | Routine service may become disruptive | Maintenance-access sketch or field record |
| Finish and colour reference | Reference and sample status are recorded | Incorrect items may need replacement or refinishing | The delivered door set may appear inconsistent | Dated finish reference and sample decision |
| Supplier evidence | Documents identify scope, revision, and holder | Clarification and repeat review consume project resources | A marketing statement may be mistaken for technical evidence | Indexed submittal register |
Use the client’s own assumptions when a lifecycle cost input is required. Label the source of each assumption and keep unresolved items visible. Do not convert a general expectation about service life into a supplier guarantee or use an unsupported figure to make the schedule appear complete.
Run gate A: schedule completeness
Begin with the schedule itself, not with a supplier question. Compare every row against the baseline and identify the source of each requirement. A requirement without a source may be valid, but it is not yet controlled.
The reviewer should perform the following actions:
- Match each opening to the latest issued door and frame information.
- Separate the lock case, faceplate, strike, hinge, closer, and operable-part decisions.
- Record dimensions in the format the installer can use for checking.
- Identify the locking arrangement and the position of the door within the egress route.
- Mark any field awaiting supplier evidence, client direction, site verification, or authority review.
- Give every marked field an owner and a return point in the review cycle.
Use the Common Door Hardware Schedule Errors that Delay a Project when a row appears complete but hides an unsupported assumption. Typical process failures include a catalogue dimension replacing site information, a finish reference treated as a photograph, and an approval recorded as an intention to approve.
A row that fails completeness is held rather than silently corrected by the consultant. The supplier or installer may provide the missing evidence, but the specifier must return a revised schedule that shows what changed.
Run gate B: submittal review
The submittal review tests whether the proposed item can be checked against the scheduled requirement. Product literature may introduce the item, but it does not replace project-specific evidence.
Ask for a dated product page or product-specific document for the named SKU, then record the source, scope, revision, and holder. For model-level dimensions, capabilities, finish details, or operating limitations, require confirmation on the dated product page for the specific SKU. The supplier’s statement should identify what the evidence covers and what remains outside its scope.
CONFIRM-PER-SUPPLIER: Provide dated, SKU-specific evidence for every product capability or holding relied on in the schedule.
Review the package in a fixed order:
- The proposed item and SKU match the schedule opening.
- The dimensional data can be compared with the door set baseline.
- The faceplate or strike and lock-case arrangement are identified.
- The finish is described by a reference rather than by appearance alone.
- Any interfaces with doors, frames, power, readers, controllers, or exit devices are stated.
- Deviations are listed rather than buried in a general note.
- The review outcome, conditions, reviewer, and date are recorded.
The submittal is not approved until the review is recorded and dated. A supplier’s promise to provide missing evidence later is not approval. The Door Hardware Schedule: Documents a Specifier Should Demand provides a useful document index, but the runbook still requires the reviewer to connect each document to a specific schedule decision.
Run gate C: lock and door fit verification
Fit verification is a comparison exercise. The supplier’s dimensions describe a product condition; the installer’s information describes the actual opening. Neither substitutes for the other.
Ask the installer to confirm the door thickness, edge distance, frame condition, handing, swing, and any site condition that could alter preparation. Compare those conditions with the mortise, rim lock, or multipoint information supplied for the proposed item.
Use this check sequence:
- Confirm the lock case intended for the opening.
- Record backset separately from bore diameter and bolt-to-bore distance.
- Compare the faceplate and strike data with the scheduled door and frame.
- Check fixing positions and preparation notes against the current door information.
- Record any operation that would require cutting, plugging, adaptation, or a different item.
- Use a mock-up or sample to test fit and finish where the project procedure calls for one.
A physical sample evidences fit and finish at the conditions tested. It does not establish every site condition or prove ongoing performance. Record what was tested, who tested it, the door or frame used, and the disposition of each finding.
If the comparison cannot be completed, hold the row. Installing first and resolving dimensions later transfers installation risk to the project and weakens the schedule’s value as a control record.
Run gate D: hardware coordination
Hardware coordination brings the client, installer, and supplier into the same door-set discussion without transferring design responsibility to any one meeting. The schedule identifies the intended relationship; the evidence proves that the selected components can deliver it.
Use the Door Hardware Schedule: Coordination Between Architect and Supplier to assign each interface to a discipline. The coordination record should address hinges, closer, lock case, faceplate, strike, pulls, plates, frame, door leaf, and the selected locking sequence.
For access-controlled openings, also coordinate the reader position, controller connection, door position, and power route with the relevant systems designer. State whether the system needs line supervision or an egress interface, and define the expected signal at each end. Do not assume that a lock’s radio, wiring, or controller arrangement answers the door-position requirement.
Power-loss behavior must reflect the role of the door. The fail-safe or fail-secure decision is a project decision, not an automatic product attribute. Record the intended state, the condition that triggers it, the people affected, and the evidence supporting the arrangement.
Run gate E: authority and consultant decisions
Some schedule fields cannot be closed by the consultant, supplier, or installer alone. Accessibility, fire safety, escape arrangements, and building-control decisions require the responsible authority or specialist to determine the project requirement.
For any escape route, panic hardware, fire-door assembly, or exit-device combination, state the project condition and ask the responsible body to confirm the applicable scope and decision.
CONFIRM-WITH-FIRE-AUTHORITY: Confirm the escape-route, exit-device, panic-hardware, and door-assembly requirements that apply to this project.
For operable parts, approach, movement, or installed-door verification, request the criteria that the access consultant expects the project to apply.
CONFIRM-WITH-ACCESS-CONSULTANT: Confirm the operable-part, force, motion, approach, and installed-door verification criteria for this project.
For any building-control question, identify the decision, the evidence requested, and the authority that will record the outcome.
CONFIRM-WITH-LOCAL-BUILDING-CONTROL: Confirm the review authority, applicable scope, and required evidence for this project.
The schedule should cite the recorded decision and its conditions. It should not convert a general guide, catalogue statement, or earlier project outcome into project approval.
Translate unresolved risk into cost exposure
Cost analysis is most useful when it identifies where effort may be repeated or changed. Keep direct acquisition cost separate from consequences caused by late information, unsuitable coordination, corrective installation, document rework, or an unresolved operational assumption.
A useful entry names the cause, the affected activity, the likely consequence, the evidence that could prevent it, and the person who owns the next decision. Avoid attaching a figure that the client or supplier has not supplied. Avoid converting a general service assumption into a guaranteed life.
Use the following decision-comparison format when deciding whether a row is ready to release.
| Decision state | Direct cost exposure | Downstream risk | Minimum release evidence | Decision owner |
|---|---|---|---|---|
| Release with complete project evidence | Work is planned around the accepted baseline | Changes remain attributable to the recorded decision | Schedule, supplier evidence, coordination record, and dated review | Specifier |
| Release with a bounded condition | The condition must be tracked and closed | An unresolved interface may affect installation or operation | Named owner, return point, and written condition | Client representative and specifier |
| Hold for fit evidence | Preparation and sourcing remain provisional | Incorrect preparation or unsuitable hardware may reach the site | Dimensioned comparison accepted by installer | Supplier and installer |
| Hold for an authority decision | Procurement and sequencing remain constrained | The selected arrangement may not match the project requirement | Dated decision from the responsible authority or consultant | Named authority or consultant |
| Hold for incomplete submittal review | Clarification work continues | A brochure or unsupported claim may be mistaken for approval | Indexed evidence, deviations list, and recorded review | Supplier and specifier |
| Revise after release | Affected items and documents must be traced | Changes may propagate to the frame, controls, finish, or operation | Approved revision and documented impact review | Specifier |
This table is a decision aid rather than a financial forecast. Its purpose is to make the consequences of delay visible while the choices are still manageable.
Apply change control to every consequential substitution
Change control is triggered by a new lock, frame, door material, finish, reader arrangement, controller interface, hardware item, or project requirement. It also applies when an item remains the same but its fit or function changes.
For an or-equal request, do not compare brand names or catalogue families. Compare the complete decision set: lock case, dimensions, faceplate and strike, adjustable or fixed features, finish reference, door and frame interface, operable hardware, service access, control connection, and required evidence.
The specifier records the request, the proposed comparison, the reasons for acceptance or rejection, and the conditions attached to the decision. A substitution remains pending until that record is complete.
Use this impact path for every revision:
- Identify the changed field and its source.
- Mark all directly affected door-set components.
- Test door preparation, operation, service access, and control interfaces.
- Identify any authority or consultant decision that must be revisited.
- Update the cost-consequence register and decision record.
- Issue the revised schedule to every affected recipient.
- Confirm that superseded information is withdrawn from use.
A change approved in isolation can become expensive when the frame, strike, closer, or controller interface is left behind. Review the door set, not only the changed item.
Maintain the review cadence
The schedule should move through a predictable cycle rather than accumulating questions until a deadline. Use the following sequence for each design issue:
| Review point | Required input | Required output | Escalation condition |
|---|---|---|---|
| Baseline review | Current schedule rows and supporting project information | Corrected baseline and open-field list | A consequential requirement has no source or owner |
| Supplier evidence review | Indexed submittal and dated SKU-specific evidence | Accepted, rejected, or conditional evidence status | The supplier and schedule describe different items or conditions |
| Fit and coordination review | Dimensional comparison and interface notes | Recorded fit and coordination findings | The installer cannot verify the proposed arrangement |
| Authority review | Question package and project context | Dated decision or a clearly stated outstanding condition | A required decision remains unassigned |
| Commercial release review | Cost-consequence register and decision record | Released rows and retained holds | A held row has entered procurement without disposition |
| Revision review | Proposed change and impact map | Revised baseline and reissued records | The change affects an approved interface or authority decision |
Keep the action log short. Each entry should identify the opening, field, issue, owner, evidence required, next review point, and status. “Waiting” is not a status; name the person or party expected to act.
Stop and release conditions
Release a schedule row only when its known consequences have an owner and accepted evidence. Apply these stop conditions:
- A required dimensional field is absent or conflicts with the installer’s information.
- The proposed lock case or faceplate cannot be tied to the scheduled door set.
- The supplier evidence does not identify the SKU, source, revision, or scope.
- The locking arrangement lacks a recorded project decision.
- A finish remains described only by appearance.
- Service access is unresolved for an access-controlled opening.
- A proposed substitution has not passed the impact review.
- An issued revision has not reached every affected recipient.
The release record should identify the exact schedule revision, accepted evidence, recorded decisions, outstanding conditions, and the person authorized to approve release. It should also state that any later change returns the affected rows to review.
A completed row is not merely one without questions. It is one whose remaining uncertainty has been named, assigned, and kept out of the released baseline.
Close the loop at handover — door hardware schedule
At handover, transfer the schedule and its evidence together. The installer needs the accepted door-set information and preparation requirements. The client needs the operating decisions and maintenance responsibilities. The supplier needs the released revision and the conditions attached to its item.
Readers comparing approaches usually start with the sl 6301 sample testing. That is the same question door hardware schedule cost risk has to answer here.Separate the as-built record from the original design intent. Record what was installed, where it was installed, which revision it matches, and which exceptional conditions remain. Give each record a named holder and identify the form in which it will be kept.
This overlaps with the earlier coverage in the sl 6301 supplier evaluation. That is the same question door hardware schedule cost risk has to answer here.Before closing the project, check that:
- The final schedule identifies every installed door set.
- The evidence register links each accepted item to its schedule revision.
- Authority and consultant decisions are present where relied upon.
- Exceptions, unresolved site conditions, and client assumptions remain visible.
- Maintenance and operations teams have received the service-access information.
- Superseded documents are withdrawn from active use.
- The final decision log identifies who accepted the handover record.
The operating purpose of door hardware schedule cost risk is not to eliminate every uncertainty. It is to prevent uncertainty from becoming invisible work. When every consequential field has evidence, an owner, and a recorded release decision, the schedule can direct procurement and installation without relying on memory or an untraceable meeting.
Use this runbook as the review brief for the next schedule issue, then carry its register into submittal review, fit coordination, change control, and handover. A controlled record gives the client, installer, and supplier a common basis for moving forward while making the remaining cost and risk visible.
The requirement is ready for request a quote once it is written down.

