Skip to content
Professional Discounts - info@expresshardwaredirect.com
Professional Discounts - info@expresshardwaredirect.com
Door Hardware

Submittal Package Checklist for Door Hardware: What to Include and What to Skip

📌 Key Takeaways

Door hardware submittals get approved fast when you include only the four essentials and strip out everything else.

  • Master the Core Four: Every submittal needs a hardware schedule with component mapping, cut sheets for unique items, a finish chart, and a keying matrix.

  • Lean Packets Win Reviews: Submittals under 20 pages for typical residential projects move through review queues faster than bloated, catalog-style packets.

  • Run the Match Test: Before submitting, verify that finish codes, functions, and handing align perfectly across your schedule, cut sheets, and finish chart.

  • Brand Swaps Require Approval: Changing manufacturers—even for equivalent specs—almost always triggers formal substitution requests per AIA A201-2017 standards.

  • Version Control Prevents Rework: Label every page with version numbers and dates in footers to stop old pages from resurfacing mid-review.

Build lean, check thoroughly, submit once.

Contractors and builders managing residential hardware submittals will gain immediate clarity on packet assembly here, preparing them for the detailed checklist and template guidance that follows.

~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~

A reviewer just asked for your hardware submittal. The clock is ticking.

You've got 47 openings, three finish types, a keying plan that's still in your head, and a designer who keeps changing their mind about the entry set. The last thing you need is a rejection email asking for "more detail" when you thought you sent everything.

Here's the problem most builders run into: they treat a submittal like a product catalog. They dump every cut sheet, every finish option, every marketing PDF into a folder and hope the reviewer figures it out. That approach backfires. Thick packets sit in review queues. Lean packets get approved.

A hardware submittal isn't a catalog—it's a decision packet.

The difference between a submittal that sails through and one that bounces back three times comes down to four things: your component list, your cut sheets, your finish chart, and your keying matrix. Get those right, strip out the fluff, and you'll cut days off your approval timeline.

 

The 60-Second Answer: What Reviewers Actually Need

A Lean Packet Beats a Thick Packet (Because It's Reviewable)

Reviewers don't have time to dig through 40 pages of manufacturer brochures to find the one spec they need. When a packet is bloated with marketing materials and redundant data sheets, it doesn't get reviewed faster—it gets pushed to the bottom of the pile.

A lean submittal—often under 20 pages for a typical single-family home depending on complexity—gives reviewers exactly what they need to approve: confirmation that you've specified the right hardware, in the right finish, with the right function, for every opening. Nothing more.

The Core Four: Components, Cut Sheets, Finish Chart, Keying Matrix

Every door hardware submittal needs these four elements:

  1. Hardware Schedule (with Component Mapping) — What hardware goes where, mapped by opening

  2. Cut sheets for unique items — Product data sheets showing SKU, function, and specs

  3. Finish chart — Finish codes mapped to opening types

  4. Keying matrix — How locks are keyed across doors (KA/KD/MK)

Everything else is either conditional (code flags, substitution rules) or unnecessary (full catalogs, marketing brochures). Keep the core four tight, and you're 80% of the way to approval.

Quick Definitions:

  • Cut sheet: The product data sheet for the exact item (SKU/type/function), not the full catalog

  • Finish chart: A one-page map of finish codes and where each finish is used, including exceptions

  • Keying matrix: A door list showing how each lock is keyed (KA/KD/MK) and which doors share keys

  • Substitution rule: What can change without a new review and what requires resubmittal

 

The One-Page Door Hardware Submittal Checklist (Copy/Paste)

Use this checklist every time you build a submittal package. Print it, check each box, and you'll catch gaps before the reviewer does.

Core Items (Required)

  • [ ] Hardware schedule excerpt — Opening ID, finish, handing, and function for each door

  • [ ] Package/component list — Hardware mapped by opening or package ID

  • [ ] Cut sheets — Product data sheet for each unique SKU or item type (not duplicates)

  • [ ] Finish chart — Finish codes with locations where each applies, plus any exceptions

  • [ ] Keying matrix — KA (keyed alike), KD (keyed different), or MK (master keyed) designation with door list

Conditional Items (Only When the Project Needs Them)

  • [ ] Code/label flags — Fire-rated, egress, or accessibility notes where applicable

  • [ ] Substitution rules — What can change without triggering re-review

  • [ ] Delivery/ship-window notes — If review timing is tied to ordering or sequencing

  • [ ] Electrified hardware set notes — If any openings include electrified locks or operators

  • [ ] Special opening details — Pocket doors, barn doors, custom thickness, or other non-standard conditions

How to Label Files So Reviewers Can Approve Fast

Name your files so reviewers don't have to open them to know what's inside. Use a consistent format:

[ProjectName][DocumentType][Version]_[Date]

For example: OakRidge_FinishChart_v2_2025-12-06.pdf

Version control matters. When you update a document, increment the version number and date. Add version and date to the footer of every page inside the PDF to prevent confusion when pages are printed or extracted. Old pages resurfacing mid-review is one of the top rejection triggers.

For projects expecting multiple review rounds, consider adding a brief revision log on page two that tracks what changed between versions.

Business Impact: A lean, well-organized submittal saves days. Fewer RFIs, fewer resubmittals, fewer field substitutions that force callbacks. One clean approval cycle instead of three messy ones.

 

What to Include (And Why It Prevents Review Ping-Pong)

Complete hardware submittal checklist with numbered steps: prepare schedule, list components, include data sheets, develop finishes, create keying, flag codes.

Hardware Schedule Excerpt: Finish, Handing, Function, and Opening ID

The hardware schedule excerpt is your anchor document. It tells the reviewer: "Here's every door, and here's exactly what goes on it." Include the opening ID, finish code, handing (left or right), and function (passage, privacy, keyed entry, etc.).

Without this, reviewers have to cross-reference multiple documents to verify consistency. That's where delays originate.

Component List by Opening (Or Package ID Mapping)

For projects using standardized packages, map each opening to a package ID. For custom specs, list components door by door. Either way, the goal is the same: show exactly what hardware is assigned to each opening so there's no ambiguity.

This is what prevents "approved schedule, wrong box" problems in the field.

Cut Sheets: Show the Exact SKU and Function (Not the Whole Catalog)

A cut sheet is a product data sheet showing the specific SKU, dimensions, function, and finish options. Include one cut sheet per unique item type. If you have 30 passage sets that are all identical, you need one cut sheet—not 30.

The precision matters. When requesting pricing or checking stock status, suppliers need either the part numbers or a description containing the item names, functions, and finishes. Your cut sheets should provide exactly that level of detail.

When referencing specific products, using consistent naming helps. For example, manufacturers like Schlage, Emtek, and Baldwin each have their own finish codes and nomenclature. Match your cut sheets to what's actually being ordered.

Finish Chart: Standard Codes, Where Used, and Exceptions

The finish chart maps finish codes to opening types. It should answer: "Where does Satin Nickel go? Where does Oil Rubbed Bronze go? Are there any exceptions?"

If one bathroom gets a different finish than the rest, flag it. Reviewers need to see that you've thought through consistency—and intentionally chosen any deviations.

Keying Matrix: KA/KD/MK and Door List

The keying matrix clarifies the cylinder plan. Which doors are keyed alike (KA)? Which are keyed different (KD)? Is there a master key (MK) system?

List every keyed opening and its designation. This prevents turnover risk—the last thing you want is a homeowner discovering their front door key opens their neighbor's garage.

Code Flags: Fire/Egress/Accessibility Notes (When Applicable)

If any openings require fire-rated hardware, panic hardware for egress, or ADA-compliant accessibility features, flag them explicitly. Local authority having jurisdiction (AHJ) requirements govern, so note where these apply and confirm compliance.

Substitution Rules: What Can Change Without Re-Submittal

Define what's pre-approved for substitution. Clarifying this upfront prevents delays when procurement realities hit.

Examples of allowed substitutions (verify with specific contract terms):

  • Same brand, newer series with equivalent specs (if original is discontinued)

  • Same function, same handing, same grade, same footprint

Examples requiring resubmittal:

  • Function changes

  • Handing changes

  • Finish changes outside the approved finish chart

  • Changes to any code-affected opening

Technical Note: Code flags (fire, egress, accessibility) must be captured when they apply. Local AHJ requirements govern—check your jurisdiction's specific requirements before finalizing.

 

What to Skip (Common 'Bloat' That Slows Approvals)

Not everything belongs in a submittal. Here's what to leave out:

Item

Include?

Why

Opening-by-opening schedule excerpt

Yes

Review roadmap; prevents RFIs

Package/component list by opening

Yes

Stops "right schedule, wrong shipment"

Cut sheets (unique items only)

Yes

Confirms exact SKU/type/function

Finish chart with exceptions

Yes

Prevents finish drift and field swaps

Keying matrix

Yes

Prevents late cylinder/key chaos

 

The rule is simple: if it doesn't help the reviewer verify what's specified, cut it.

Executive Summary Cover Sheet Template (Use This on Every Submittal)

A one-page executive summary at the front of your packet sets expectations and reduces back-and-forth. Use this template:

DOOR HARDWARE SUBMITTAL — EXECUTIVE SUMMARY

Project: [Project Name]
Address: [Site Address]
Date/Version: [Date] / Version [#]
Submitted By: [Your Company Name]
Reviewer(s): [Name(s)]

Scope: [Number] openings across [Number] door types

Finishes:

  • Primary: [Finish Code + Name]

  • Secondary: [Finish Code + Name]

  • Exceptions: [Note any one-offs]

Keying Approach:

  • [ ] Keyed Alike (KA) — [List door groups]

  • [ ] Keyed Different (KD) — [List doors]

  • [ ] Master Keyed (MK) — [Describe system]

Substitution Rules: [What can be swapped without re-review]

Ship Window / Sequencing Notes: [Any timing dependencies]

Exceptions: [Anything that differs from the standard package]

Project Identifiers, Date/Version Control, and Reviewer List

Always include project name, address, submission date, version number, and who's reviewing. This sounds basic, but missing identifiers cause packets to get lost or misrouted.

Decision Points: Keying, Substitutions, Lead-Time Notes

Surface the key decisions upfront. What's the keying plan? What substitutions are pre-approved? Are there lead-time constraints that affect the review timeline?

'Exceptions' Box: Anything That Differs From the Standard Package

If one door gets special treatment—different finish, different function, upgraded trim—call it out. Exceptions hidden in page 37 of a thick packet get missed. Exceptions on page one get addressed.

Day-to-Day Application: Here's the 10-minute workflow: Print the checklist → Populate cover sheet → Attach only unique cut sheets → Run the match test (finish + function + handing agree everywhere). That's it. You're ready to submit.

 

Right-Size the Packet by Project Type

Single Home: Keep It to 5–12 Pages Total (Typical)

For a single-family residential project, your submittal should fit in a slim packet. Hardware schedule excerpt, component list, cut sheets for unique items, finish chart, keying matrix, and cover sheet. If you're pushing past 12 pages, you're probably including redundant material.

Multi-Unit: One 'Master Set' + Unit Variations and a Keying Appendix

Multi-family projects need a different approach. Create one master hardware set that applies to standard units, then document variations by unit type. Add a keying appendix that maps the master key system across all units.

Don't repeat the full packet per unit. One master packet with a short appendix for variations keeps the submittal reviewable.

When a Hardware Consultant Is Involved: How to Align Formats

If you're working with a hardware consultant, align on format before you start assembling. Different consultants have different templates. Getting on the same page upfront prevents reformatting headaches later.

Match their format, but keep your core rules non-negotiable: opening IDs must be consistent, the finish chart must be single-source, and the keying matrix must be explicit.

 

Reviewer-Proof QA Pass Before You Submit

QA review cycle for hardware submittals: verify substitutions, check finishes, specify LH/RH handing, match SKUs, include keying, update versions, flag fire doors.

The Top 7 Rejection Triggers (And the One-Line Fix for Each)

  1. Missing finish code on schedule — Add finish column to every row

  2. Handing not specified — Mark LH or RH for every opening

  3. Cut sheet doesn't match specified SKU — Verify SKU on schedule matches cut sheet exactly

  4. No keying matrix included — Add KA/KD/MK designations with door list

  5. Old version pages mixed in — Use version numbers and purge outdated files

  6. Code flags missing for fire-rated doors — Review plans for fire-rated openings and flag each

  7. Substitution rules unclear — State what's pre-approved in cover sheet

The 'Match Test': Finish + Function + Handing Must Agree Everywhere

Before you submit, run the match test. Pick any opening at random. Does the finish on the schedule match the finish chart? Does the function match the cut sheet? Does the handing match the door swing shown on plans?

If anything disagrees, fix it. Mismatches are the number one source of review ping-pong.

Version Control: How to Prevent Old Pages From Resurfacing

Label every document with a version number and date. When you update, increment the version and delete old files from your submittal folder. Add version and date to the footer of every page so extracted or printed pages remain traceable.

Reviewers flagging issues from a page you already fixed is frustrating—and avoidable.

Consensus Kit — Who Checks What:

  • GC: Schedule completeness + substitutions rule

  • Designer: Finish intent + exceptions

  • Installer/Super: Handing/function clarity

  • AHJ/Reviewer: Code flags where applicable

 

Next Step (Optional): Turn the Approved Packet Into Clean Ordering

Save the Packet as Your 'Single Source of Truth' for Procurement

Once approved, your submittal becomes your ordering bible. Don't rebuild from scratch—use the approved schedule, finish chart, and component list to generate your purchase order. This prevents the spec-to-order drift that causes field problems.

If You Need a Quote: What Information to Send So You Don't Get Stuck

When requesting pricing, include part numbers or a description with item names, functions, and finishes. Missing details create back-and-forth that delays your quote and your order.

If you need help identifying SKUs or verifying finish availability, Contact Us for assistance. To browse finish and function examples from major manufacturers, explore options from Schlage.

 

FAQ

Do I need cut sheets for every opening or just unique items?

Just unique items. If you have 20 identical passage sets, include one cut sheet for that SKU. Duplicating the same sheet 20 times adds bulk without adding information.

What is a keying matrix and who provides it?

A keying matrix shows how locks are keyed across a project—which doors share keys (keyed alike), which have unique keys (keyed different), and whether there's a master key system. The GC or owner typically defines the keying plan; the hardware supplier or locksmith executes it.

How many pages should a residential door hardware submittal be?

For a typical single-family home, 5 to 12 pages is standard. Multi-unit projects run longer but should still be organized as a master set plus variations, not a monolithic document.

What's the fastest way to show finish consistency across the project?

A finish chart. Map each finish code to the opening types where it applies, note any exceptions, and you've given reviewers a one-page answer to "Is this consistent?"

What should I include for substitutions to avoid re-review?

State the substitution rules in your cover sheet. Define what can be swapped (equivalent SKU from same manufacturer, same finish code, same function) and what triggers re-review (different manufacturer, different finish, different function).

If it can't be reviewed in 10 minutes, it won't be approved fast. Build lean, check thoroughly, and your submittals will move through review instead of bouncing back.

With over 50 years in the hardware business, Express Hardware Direct understands what contractors need to keep projects on schedule. See our Return Policy for details on ordering with confidence.

Disclaimer: This guide is for informational purposes. Always confirm handing, finish requirements, and any code-related constraints for your specific opening conditions and jurisdiction before ordering or installing hardware.

Our Editorial Process

Our expert team uses AI tools to help organize and structure our drafts. Every article is then reviewed by subject-matter experts on our Insights Team to ensure accuracy and clarity.

About the Express Hardware Direct Insights Team

The Express Hardware Direct Insights Team is our dedicated engine for practical, jobsite-friendly hardware guidance. Our content is reviewed for clarity and accuracy and is provided for informational purposes; it should not replace professional advice or local code review.

Previous article Lead-Time Signals: How to Set Ship Windows Without Slipping Your Finish Date
Next article Finish & Handing Map: A Simple Method to Stop Mismatches Across Plans