An interior material submittal register is the single status record for every product-data sheet, sample, shop drawing, finish reference, test document, comment, revision, and production-release decision. Build it from the BOQ and drawing set, assign one accountable owner per action, and prevent fabrication until the required evidence reaches the buyer-defined approval state.
Author: Andy, Director of Operations
Technical reviewer: Andy, Director of Operations
Last substantive review: August 13, 2026
Corrections: Use the HOMESEE contact page to submit evidence-based corrections.
Editorial note: Replace all person placeholders with verified HOMESEE names and credentials before publication. This guide defines a buyer-controlled workflow; it does not certify any product, supplier, factory, or project.
Table of contents
- What a submittal register controls
- How it differs from a BOQ, sample log, and RFI log
- Roles and approval authority
- Required register fields
- Status definitions and hold points
- Building the register step by step
- Evidence by material package
- Revision and change control
- Review meetings and dashboards
- Final release checklist and RFQ CTA
What is an interior material submittal register?
The register is an index of decisions, not a folder of files. A folder may contain three versions of a data sheet, two sample photographs, an annotated drawing, and an email saying “looks fine.” The register identifies which version is current, what it is supposed to prove, who must review it, what comments remain open, and whether the item can move to the next procurement stage.
For an overseas project package, the register may cover flooring, wall panels, custom cabinetry, stone or tile, furniture, lighting, doors, hardware, and soft furnishings. The required evidence differs by item, so the register should not force every product through an identical document list. It should apply one governance structure to project-specific evidence.
Architectural Woodwork Institute guidance illustrates the value of this discipline for cabinetry: shop drawings, materials, finishes, dimensions, samples, approvals, and scheduling are connected parts of the submittal. The exact standard or approval authority for your project must be defined by the contract and design team. HOMESEE does not assume that an AWI standard, a destination regulation, or a certificate applies unless the buyer documents that requirement.
The register belongs between early quotation preparation and production release. Use HOMESEE’s quote preparation guide to assemble the initial input, and the sample confirmation guide to understand sample stages. The register then connects those activities to accountable decisions.
How is a submittal register different from other procurement records?
It is not the BOQ
The BOQ defines items, quantities, units, and scope. The submittal register tracks evidence and approval. One BOQ line may need several submittals: product data, shop drawing, finish sample, packing proposal, installation information, and a revised document after comments.
Keep the BOQ item ID in the register so the two records can be joined. Do not duplicate price columns into the approval log unless the project has a controlled commercial-change process.
It is not only a sample log
A sample log tracks physical or digital samples. A submittal register can link to that log, but it also tracks drawings, technical data, buyer comments, required documents, and release decisions. A visually approved sample does not automatically approve dimensions, construction, hardware, packaging, or regulatory suitability.
It is not an RFI or clarification log
An RFI log records questions and answers. A submittal may generate an RFI, but the answer must be incorporated into the correct file and revision before the submittal is closed. Link the RFI ID to the submittal; do not use an email answer as a permanent substitute for an updated drawing or schedule.
It is not proof of compliance by itself
The register tells the team what was submitted and reviewed. It does not make an unsupported claim true. A row reading “certificate received” should identify the document, issuer, scope, product reference, date, and review outcome. If the buyer cannot verify relevance, mark it pending or not accepted.
Define roles and approval authority before creating statuses
A status such as “approved” has no value unless the approver and authority are known. Create a responsibility matrix for at least these functions:
- Buyer procurement lead: owns package scope, commercial coordination, and deadlines.
- Designer or design authority: owns design intent, visible finish, interfaces, and specified performance.
- Quantity surveyor or cost lead: owns quantity and measurement questions where appointed.
- Technical specialist: reviews product-specific performance or destination requirements when needed.
- Supplier / manufacturer: prepares accurate product data, samples, drawings, declarations, and revisions.
- Sourcing coordinator: checks completeness, version, cross-package interfaces, and communication flow.
- Inspection lead: converts approved requirements into measurable inspection points.
- Logistics / packing lead: reviews pack dimensions, labels, handling, loading, and destination handover inputs.
One person may hold more than one function on a small project, but the register should still show which decision that person is making. A sourcing coordinator can route and check a submittal without taking over the designer’s aesthetic approval or the qualified professional’s safety decision.
HOMESEE’s sourcing services page describes possible support scopes. The actual responsibility must be confirmed in the project agreement; this article does not claim that HOMESEE performs every listed role for every project.
Minimum fields for a useful submittal register
| Field | Purpose | Quality rule |
|---|---|---|
| Submittal ID | Unique traceable record | Never recycle an ID for a different deliverable |
| BOQ / package item ID | Connects evidence to scope | Must match the issued procurement baseline |
| Category and zone | Supports filtering and sequence | Use project-controlled names |
| Submittal type | Data, sample, drawing, document, packing, mock-up, other | Do not mix unrelated evidence in one status |
| Required deliverable | States what must be submitted | Describe the decision the evidence supports |
| Requirement source | Drawing, specification, contract, buyer instruction, destination rule | Include revision and responsible authority |
| Supplier owner | Person responsible to submit | Use a real contact, not a generic mailbox where possible |
| Buyer reviewer | Person authorized to decide | Avoid committee-only ownership |
| Planned submission date | Supports procurement sequence | Treat as a plan, not a promised supplier lead time |
| Actual submission date | Records the event | Preserve each revision date |
| File / sample reference | Points to controlled evidence | Include file revision or physical sample ID |
| Review status | Shows current decision | Use defined status codes only |
| Comments / action ID | Links to actionable feedback | One owner and due date per action |
| Fabrication hold | Prevents premature release | Yes until all named prerequisites close |
| Packing / inspection link | Carries approval into later controls | Reference the applicable plan IDs |
| Close date and approver | Creates an audit trail | Never backdate or overwrite history |
Add fields only when somebody will maintain them. A register with fifty empty columns creates the appearance of control without usable information.
Use status definitions that cannot be misread
Choose a small controlled set. The labels can match your contract, but define them in the register instructions.
Planned
The deliverable is required but has not been submitted. A planned row should still have an owner, requirement source, and target sequence.
Submitted — completeness review
The file or sample has arrived, but nobody has confirmed that it contains the required information. This prevents “uploaded” from being mistaken for “ready for technical review.”
Under review
The correct reviewer has the complete current revision. Start the review clock only according to the project’s agreed rule; this article does not invent a default review period.
Revise and resubmit
The supplier must issue a new revision. Comments should be numbered, actionable, and connected to the requirement source. Preserve the rejected revision for history.
Approved as noted / conditional
Use this only if the project permits conditional approval and the remaining notes do not create an unsafe or ambiguous fabrication instruction. State exactly what may proceed and what remains on hold. If the condition affects geometry, construction, finish, interface, quantity, or required evidence, a revised document may still be necessary.
Approved for the stated purpose
Approval should say what it releases: quotation basis, design coordination, physical mock-up, production, packing, or shipment. Avoid one universal “approved” state that lets a concept image release fabrication.
Rejected / not applicable / superseded
Keep these distinct. Rejected means the evidence does not meet the requirement. Not applicable requires a reason and approver. Superseded means a newer controlled revision exists.
Establish hard hold points
The most important column may be “may fabricate?” A project should define the prerequisites for each item before anyone treats schedule pressure as approval.
Typical hold-point candidates include:
- controlling dimensions and interfaces confirmed;
- shop drawing revision released by the authorized reviewer;
- material construction and finish reference approved;
- required product evidence accepted for the stated destination and use;
- hardware, accessories, openings, and service interfaces coordinated;
- inspection characteristics and acceptance response agreed;
- packaging method and label fields defined;
- commercial change approved where the technical revision changes scope.
These are governance examples, not a universal legal or technical checklist. The buyer’s project team must decide which prerequisites apply.
Build the register step by step
Step 1: import the controlled procurement baseline
Start with the latest issued BOQ and package list. If those inputs are inconsistent, normalize them before creating hundreds of submittal rows. The HOMESEE drawing requirements guide helps identify common source documents.
Create one row per required decision deliverable, not one row per email attachment. For example, “cabinet shop drawing set — revision for production approval” is a deliverable; each PDF sheet is part of that set.
Step 2: build a submittal requirements matrix
For each BOQ category, ask what must be known before quotation, sampling, production, inspection, packing, and shipment. Assign the requirement source and reviewer. If the source is only an internal buyer preference, say so. If it is a destination requirement, link the official source and identify who verified applicability.
Step 3: sequence backward from project need dates
Do not copy supplier lead-time claims into the register as fact. Start from the buyer’s required-on-site or required-for-installation sequence, then ask suppliers for their actual sample, drawing, production, inspection, and packing inputs. Mark those durations as supplier responses with dates and revision history.
Where an item depends on field dimensions, design decisions, or another trade, show the dependency. A planned submission date without prerequisite ownership is not a plan.
Step 4: issue the register instructions with the RFQ or order
Tell suppliers how to name files, identify revisions, respond to comments, label samples, and declare deviations. Require the submittal ID and BOQ item ID on the deliverable. This small rule prevents files named “final-new-2.pdf” from becoming the approval record.
Step 5: perform a completeness gate
Before routing to technical reviewers, check that the submission matches the requested item, revision, language, unit, product reference, and evidence type. A data sheet for a similar model is not automatically evidence for the quoted product.
Return incomplete submissions with specific missing fields. Do not ask the designer to discover administrative gaps during aesthetic review.
Step 6: consolidate comments
One controlled response should return to the supplier. If several reviewers comment, a coordinator must reconcile contradictions and confirm who has final authority. Number comments, identify affected sheets or samples, and distinguish mandatory corrections from questions.
Step 7: update the downstream plans
When a submittal is approved, transfer its controlled characteristics into the BOQ revision, finish schedule, inspection plan, packaging specification, and loading data where relevant. Approval information that remains isolated in the register cannot protect later stages.
Step 8: close with evidence, not a color fill
Record the approver, date, purpose, accepted revision, and any residual condition. Lock or audit the history. A green spreadsheet cell without those facts is not a defensible production release.
What evidence may be needed by material package?
The following table is a scoping prompt. The actual list must come from the project, product, destination, and contract.
| Package | Possible submittals | Interface questions |
|---|---|---|
| Flooring | Product data, finish/control sample, layout or zone map, accessory schedule, packing proposal | Substrate, transitions, stairs, skirting, batch-to-zone plan |
| Wall panels | Product/construction data, finish sample, module drawing, edge/joint detail, fixing concept | Doors, corners, outlets, ceiling/floor junctions, backing |
| Cabinetry | Plans, elevations, sections, hardware data, finish samples, appliance/service coordination | Field dimensions, fillers, door/drawer clearance, worktops, MEP |
| Stone/tile | Product/finish sample, range sample where relevant, cutting schedule, layout, edge/cutout details, packing proposal | Batch/lot, joints, substrate, fixtures, handling and crate map |
| Furniture | Item data, construction and finish samples, dimensions, hardware, assembly/packing method | Circulation, floor protection, delivery route, replacement parts |
| Lighting | Fixture data, finish sample, dimensions, control/driver information, qualified technical review evidence | Ceiling coordination, power/control, access, destination requirements |
Do not request a certificate just to fill a row. Name the question that the document must answer. If nobody can explain relevance, pause and obtain qualified advice.
Connect samples without duplicating the sample workflow
The register should record the sample ID, purpose, status, physical location, approving person, approved range or limitations, and linked production item. It should not replace a detailed sample log where dozens of pieces are moving between parties.
Distinguish at least:
- concept or reference sample;
- quotation-basis sample;
- supplier submission sample;
- approved control sample;
- production or lot sample, if required;
- retained sample and return/disposal status.
Photographs support communication but may not reproduce color, texture, sheen, translucency, or scale reliably. State whether a decision was based on a physical sample, controlled digital evidence, or both. For coordinated categories, link the sample to the project color-mismatch control guidance.
Manage revisions and design changes
A revised submittal must identify what changed. Require a revision note or clouded/marked change according to the project standard. Do not approve an entire set again without knowing whether unrelated content moved.
When an approved item changes, trigger an impact check:
- Does the BOQ description, quantity, unit, or accessory scope change?
- Do adjacent finishes or interfaces need review?
- Does the approved sample remain valid?
- Does the inspection plan need a new characteristic or reference?
- Does packaging size, weight, fragility, or label information change?
- Does the load plan or destination handling sequence change?
- Is commercial approval required before production continues?
Create a new approval event; do not overwrite the old approved record. Traceability means the team can reconstruct which revision governed a produced lot.
GS1’s traceability guidance emphasizes recording relationships between items, batches or lots, logistics units, and higher aggregation levels. A construction project may use a different identifier system, but it benefits from the same principle: preserve the link between approved item, produced batch, pack, and shipment.
Run short, decision-focused register reviews
A register meeting should resolve exceptions, not read every row. Filter by:
- fabrication holds that threaten the required sequence;
- overdue actions with one named owner;
- revise-and-resubmit cycles;
- items missing requirement sources;
- cross-category finish or geometry conflicts;
- approved items not transferred to inspection or packing plans;
- documents required before a trial order, balance release, packing, or shipment;
- superseded files still circulating.
Useful dashboard counts are project facts, so generate them from the actual register. Do not publish invented completion percentages. Show the timestamp and included scope with every dashboard.
Submittal register quality checklist
- Every row maps to a BOQ item or defined package.
- Every requirement names its source and decision purpose.
- Every action has one owner and a date.
- Status labels have written definitions.
- “Approved” identifies the purpose and exact revision.
- Physical samples have IDs and locations.
- Conditional approvals cannot bypass fabrication hold points.
- Supplier deviations remain visible.
- Revisions preserve history and identify changes.
- Approved characteristics flow into inspection and packing controls.
- No certificate, test, or compliance claim is accepted without relevance review.
- Named author and technical reviewer are assigned before publishing this guide.
Upload the BOQ, drawings, and current submittal list
To discuss a project-material coordination scope, use the HOMESEE inquiry page. Upload the current BOQ, drawings, finish schedule, reference images, quantity basis, project location, destination port, and any existing submittal register. Mark missing approvals and unknown requirements openly.
Review the broader China building materials sourcing guide, project cases, and article hub to see how this control fits the sourcing workflow.
The goal is not to maximize paperwork. It is to ensure that the right evidence reaches the right decision-maker before money, materials, and production move beyond a recoverable point.