03 Sep Submittal Register
A capsule house supplier drawing register gives the buyer and project team one controlled view of what information was requested, submitted, reviewed, revised and accepted for a defined purpose. It prevents an outdated attachment or informal message from quietly becoming a design or construction input.
The contract and professional appointments must define actual deliverables, review authority and design responsibility. A register records the workflow; it does not transfer responsibility or make a document technically correct.
Start With Required Information, Not File Names
List each information need by purpose: product selection, site coordination, foundation input, utilities, transport, lifting, installation, finishes, operation or handover. State who needs it, the required date, expected format and the decision it supports.
Use the capsule house RFQ checklist to identify early quotation inputs. After selection, convert relevant requirements into contract deliverables rather than assuming every sales document is suitable for design.
Give Every Submittal a Stable Identity
Record a unique document number, clear title, originator, revision, issue date and stated purpose. Separate drawing revision from register status. A drawing can remain at the same revision while its review status changes, or receive a new revision after comments.
Do not rely on email subject lines. Store the controlled file in the agreed location and link the register entry to it. Preserve superseded revisions for traceability while preventing unintended use.
Define Review Status in Plain Language
Agree a small set of statuses and what each permits. Examples might distinguish received, under review, revise and resubmit, accepted for a stated purpose, or superseded. The project must define its own terms; words such as “approved” can create confusion if authority and purpose are unclear.
Record the reviewer, review date, comment reference and next action. A review should not be interpreted as checking matters outside the reviewer’s appointed scope.
Submittal Register Fields
| Field | Record | Control question |
|---|---|---|
| Requirement | Purpose, requester and needed date | What decision depends on it? |
| Identity | Number, title, revision and issue date | Can the exact file be found? |
| Review | Reviewer, status and comment reference | Is review scope clear? |
| Action | Owner, due point and response | Are comments closed? |
| Use | Permitted purpose and supersession | Could an old revision be used? |
Link Comments to Decisions
Number review comments and keep them separate from casual discussion. Each comment should identify the relevant location, requested clarification or change, responsible party and closure evidence. Avoid marking a comment closed only because a new file arrived.
Where supplier information affects the site, route it to the responsible local designer. The foundation design inputs checklist shows how product interfaces and site information must meet before local design proceeds.
Control Preliminary and Construction Information
Mark preliminary information visibly and state its permitted use. If a project team must work with an assumption, record the assumption, approver and hold point for confirmation. Do not release construction solely because a target date is near.
Before procurement, manufacture or site work, verify that required documents have the correct status for that decision. Record changes that affect quantities, interfaces, logistics, site works or other contracts.
Prepare the Final Document Set
At handover, reconcile the register with the final supplied configuration and accepted revisions. Identify missing items, unresolved comments and documents that remain preliminary. The handover checklist covers the wider closeout package.
To request available product-side information, contact Rovellc with the selected configuration, destination, project stage and required document purpose. The project team should define review authority and verify all local design and approval requirements.