Use unique marks
Assign every type or opening a stable mark and connect it to plans and elevations. Do not reuse a mark for assemblies with different size, glass, finish or hardware.
State the dimension type
Label rough opening, frame size and daylight opening explicitly. Record width, height, frame depth and surrounding wall condition without silently deducting or rounding.
Add system requirements
List operation, handing, glass, finish, screens, hardware, limit devices, mullions, receptors, panning, subsills and perimeter accessories.
Plan release and delivery
Include required-on-site dates, release groups, floor or elevation labels, crate sequence, unloading responsibility and storage conditions.
Preparing a commercial window and door opening schedule
A coordinated opening schedule connects the design intent, product selection and installation conditions. Use one opening ID from the first quote through receiving and installation.
Identify every assembly
List each opening by ID, quantity, location and drawing reference. Separate the complete assembly size from individual operating panels and fixed lites. Identify which dimensions are preliminary design dimensions and which have been verified in the field. Repeated appearances of the same opening on plans and elevations should use the same identifier.
Describe the required operation
Record fixed or operable glazing, swing direction, panel travel, stacking position and the intended clear opening. For a restaurant or retail opening, show how panels interact with counters, customer circulation and furniture. For a pocketing assembly, include the pocket and access arrangement in the surrounding wall design.
Exterior elevations communicate appearance, while plan views reveal movement and conflicts. Include both where operation matters. Specify divided-lite patterns, adjacent frame alignment and finish intent without assuming all profiles in a material family share the same dimensions.
Attach the performance criteria
Provide the project location, required design pressures and the relevant air, water, thermal, glazing and impact criteria supplied by the design team. Distinguish a required performance value from a published example test result. The submittal should identify the exact assembly and configuration proposed to satisfy each requirement.
Identify accessible entrances, egress paths, safety glazing and required hardware for project review. A residential-looking door or low track does not establish suitability for those commercial conditions.
Coordinate head, jamb and sill conditions
Show the wall substrate, head support, interior and exterior finishes, sill elevations and intended drainage route. Recessed tracks need a coordinated construction section. Confirm the selected attachment detail, tolerances and flashing arrangement before openings or recesses are finalized.
Include a receiving and installation plan
Identify delivery restrictions, unloading responsibility, available equipment, storage conditions and the path to each opening. Obtain packaged dimensions and weights for large assemblies. Assign responsibility for inspecting the shipment and recording any damage before installation begins.
Review the returned submittal against the schedule
- Opening IDs, quantities, frame dimensions and configuration agree.
- Glass, finish, hardware and screening match the intended scope.
- Required test or approval records identify the proposed assembly.
- Floor transitions, recesses, drainage and structural interfaces are coordinated.
- Installation documents and current production information are included.
Keep the final approved revision with the opening schedule so procurement, receiving and installation work from the same information.
Explore the right system
Turn the guide into a real opening schedule.
Keep every dimension, option, pressure, document, and delivery note connected to the same opening ID.
Start the configurationQuestions about this topic
Can plans replace field verification?
Plans support budgeting and submittals, but existing openings and surrounding conditions normally require field verification before final release.