Start with a stable identifier
Door marks, window marks and room references should point to the same objects everywhere they appear. Decide whether the schedule is instance-based, type-based or a combination, then keep that rule visible. Renaming an item without coordinating dependent drawings and specifications creates a quiet but expensive error.
Record the level, room or opening context needed to find the item. Avoid using descriptive names alone where two locations could share the same construction.
Separate geometry, performance and finish
Dimensions describe the opening or component. Performance fields record requirements such as fire, acoustic, thermal or security criteria. Finish and product fields communicate the selected appearance and hardware or accessory coordination. Keeping these groups distinct makes missing information easier to see and assign.
- Use consistent units and retain canonical dimensions when display units change.
- State whether a value is required, proposed, verified or not applicable.
- Link critical requirements to the relevant specification or detail.
- Resolve blank fields deliberately rather than hiding them before issue.
Review the issue as a deliverable
Before export, scan for duplicate marks, missing ratings, inconsistent types and values that have lost their source. Compare the schedule revision with affected plans, elevations, details and clauses. A clean PDF is useful for review, but the editable project record should remain the controlled source.
The Schedule Builder brings door, window and room-finish inputs into one interface while retaining the type-specific fields that make each deliverable useful.