Office Fit-Out Submittal Register starts with a real operational question. An office fit-out submittal register keeps drawings, samples, product data, calculations, and approvals connected to the work they control. It gives a design-build team one visible route from proposal to installation instead of a trail of unsearchable messages. The useful answer is to define the need, test it against the building, and carry the decision through delivery.
Keep the decision proportional to the project, but do not skip the evidence. A small unresolved interface can create a large operational problem when it is repeated across a workplace.
What belongs in a submittal register?
Include shop drawings, coordinated services drawings, material samples, product data, mock-ups, method statements, schedules, test plans, warranties, and handover information where the project requires them. Record the package, location, revision, responsible party, reviewer, due date, and status.
The register should follow the project’s information requirements. Do not create a large list that nobody maintains. Each item should exist because it supports a design decision, procurement release, site activity, test, or handover record.
How should the workflow be controlled?
Give every submittal a unique reference and revision. Show submitted, under review, comments returned, resubmitted, approved, approved with conditions, rejected, or superseded. Keep the current approved version easy to identify at the point of use.
A status word is not enough. Record the decision date, reviewer, comments, response, and any effect on cost or programme. This prevents a verbal approval from being treated as permission to install a changed product.
Who should review each item?
Assign review responsibility by subject. The interior designer may review appearance and detail, the engineer services coordination, the client materials and use, IT technology, facilities maintainability, and building management the landlord interface. The exact matrix depends on the project.
Avoid asking every person to review everything. Targeted ownership makes review faster and keeps accountability clear. Escalate an unresolved interface when it affects safety, operation, cost, or programme rather than letting it disappear in a general comment.
How do submittals protect procurement?
Link the approved item to supplier, lead time, quantity, alternative, warranty, and installation dependency. A material approval should not be separated from the package that must purchase and install it.
If a supplier proposes an alternative, show the original requirement and compare performance, appearance, availability, maintenance, cost, and programme. A cheaper substitute is still a design decision when it changes another trade’s work.
How should site teams use the register?
Make the approved reference available with drawings and inspection records. Inspect the first installed area against the approved submittal and record deviations. Do not rely on a box label or a photograph without checking the reference and location.
The register becomes valuable at site speed. A supervisor should be able to answer what is approved, which revision applies, who accepted it, and what to do with a mismatch.
What should happen at handover?
Carry approved product data, final revisions, test evidence, warranties, maintenance instructions, and asset information into the handover set. Close superseded or rejected items clearly. The final record should describe what was installed, not only what was proposed.
A controlled register reduces disputes and supports future maintenance. It also gives the client a useful history of the decisions that shaped the workplace.
A practical decision check
| Layer | Questions to confirm |
|---|---|
| Purpose | What work or operating problem must this solve? |
| Evidence | Which building, user, technical, or source information supports the choice? |
| Coordination | Which drawings, services, suppliers, approvals, or trades are affected? |
| Ownership | Who approves, operates, maintains, and reviews the result? |
| Proof | What test, inspection, record, or handover evidence will show it works? |
Use this check before the decision is released. If one answer is missing, mark it as an open item with an owner and date rather than hiding it inside a general allowance.
Project checklist
Before the work is released, use this checklist for the decision in this article. It keeps the design connected to the people, building, budget, and operating team.
- Purpose and owner: write the problem, desired outcome, decision owner, and approval date.
- Evidence: label measured conditions, stakeholder inputs, source guidance, assumptions, and open questions.
- Plan: test the decision against adjacency, circulation, capacity, privacy, accessibility, and user journeys.
- Services: coordinate power, data, HVAC, lighting, fire, security, controls, and maintenance access where relevant.
- Procurement: confirm specification, sample, lead time, alternatives, warranty, and cost or programme effect.
- Site: inspect the first representative area, record defects by location, and protect approved work from unreviewed change.
- Commissioning: test normal use, peak or unusual use, controls, failure response, and the evidence required at handover.
- Operations: give facilities and users clear instructions, contacts, maintenance information, and a route for feedback.
- Review: set a post-occupancy check and state what will be measured, who will review it, and what may change.
The checklist does not replace the project brief, engineering design, statutory review, landlord requirements, or specialist advice. It is a final sense check before a decision becomes difficult to reverse.
Frequently asked questions
Start with the real work, users, building conditions, and operating responsibility. Convert those inputs into a short brief that the design and delivery team can test.
Resolve the direction during briefing and test-fit, then carry it through coordinated design, procurement, construction, commissioning, and handover. Late decisions affect several trades.
Use evidence from the building, users, drawings, samples, site inspections, and operating tests. Record assumptions and exceptions instead of presenting an early estimate as a guarantee.
No. The useful response depends on the service model, floor plate, landlord rules, building systems, users, budget, and programme. A local site and stakeholder review is essential.
Sources and further reading
These sources provide background guidance for the standards-oriented parts of this article. Project teams should confirm the requirements that apply to the actual building, brief, and jurisdiction.
Plan the next step
Bring the brief, building information, headcount, work patterns, constraints, and decision date. Vektor Spaces can connect this topic to a practical route covering workplace strategy, design, MEP coordination, procurement, construction, and handover.