Material Approval Register vs Submittal Log vs Procurement Log: What Should Each One Track?
Construction projects often use several trackers that appear to contain the same information.
A material name may appear in:
All three may also contain fields such as:
Tracker-design rule: separate document review, material approval and procurement execution as different control functions. They may share milestone data — or even one spreadsheet on a small project — but each major status should still have one clear owner and one source of truth.
- a Submittal Log;
- a Material Approval Register;
- a Procurement Log.
- Status
- Date
- Supplier
- Package
- Comments
That can create a reasonable question:
Do we really need three different logs?
The answer depends on project size, but the three tools are not interchangeable.
They control different records and answer different questions.
Submittal Log tracks document review. Material Approval Register tracks the material approval decision. Procurement Log tracks purchasing and delivery execution.
The same physical material may appear in all three, but it is being controlled for a different purpose each time.
Why These Three Logs Are Easy to Confuse
Take a hotel bathroom fixture package.
It may appear in the project records as:
Submittal Log
Bathroom Fixtures — Rev 1 — Under Review
Material Approval Register
Bathroom Fixtures — Pending Approval
Procurement Log
Bathroom Fixtures — Supplier Selected
All three records refer to the same material package.
But they answer different questions.
The Submittal Log asks:
Where is the document review?
The Material Approval Register asks:
Has the proposed material been approved?
The Procurement Log asks:
Where is the package in sourcing, ordering, production or delivery?
This distinction is more important than whether the project uses one Excel file or three.
Submittal Log: Track the Document Review
The main control object in a Submittal Log is:
For the detailed revision-control workflow, use the Construction Submittal Log as the primary document-status record.
The submission and its revision
Its purpose is document control.
Typical fields may include:
- Submittal Number
- Material / Package
- Revision
- Submitted Date
- Reviewer
- Review Status
- Returned Date
- Resubmission Required
- Current Revision
Consider a bathroom fixture package.
Rev 0
Submitted:
May 2
Status:
Returned with Comments
Rev 1
Submitted:
May 10
Status:
Approved
The same material has now created multiple records or revision events.
That is normal because the Submittal Log is not primarily asking:
Has the material finally been approved for procurement?
It is asking:
What happened to the submitted documents, and which revision is current?
Submittal Log = Document Review Control
Once the document cycle becomes more complex, this revision history becomes important because “approved” without a revision reference may not be enough.
Material Approval Register: Track the Approval Decision
The main control object in a Material Approval Register is:
Use the Material Approval Register to carry the final approved manufacturer, model, conditions and approval date forward.
The material or material package
Its purpose is to show the current approval position.
Typical fields may include:
- Material Package
- Specification / Category
- Proposed Manufacturer
- Proposed Model
- Approval Status
- Final Approval Date
- Approved Manufacturer
- Approved Model
- Conditions / Comments
- Procurement Release Status
This means the same bathroom fixture package may have generated:
Rev 0 Rev 1 Rev 2
inside the Submittal Log.
But the Material Approval Register may still contain one main row:
Bathroom Fixture Package — Approved
The register is not trying to reproduce every document movement.
It is trying to answer:
What is the final approval status of this material?
That distinction matters when procurement is preparing to place an order.
A procurement team usually needs to know:
- which manufacturer was approved;
- which model was approved;
- when approval was obtained;
- whether any conditions remain.
Material Approval Register = Approval Decision Control
Document review history and material approval are related, but they are not the same record.
Procurement Log: Track Purchasing and Delivery Execution
The main control object in the Procurement Log is:
Once the package enters sourcing and ordering, the Construction Procurement Log becomes the main execution tracker.
The procurement package or order
Its purpose is execution control.
Typical fields may include:
- Procurement Package
- Required Date
- Supplier
- RFQ Status
- Supplier Selection
- Approval Status
- PO Date
- Production Status
- Inspection Status
- Shipment Status
- ETA
- Delivery Status
- Current Risk / Comment
For the same bathroom fixture package, the record may eventually show:
RFQ Complete Supplier Selected Material Approved PO Released Production in Progress Shipment Planned ETA July 18
Notice what happened.
The submittal may already be finished.
The material may already be approved.
But the Procurement Log continues because the package still needs to be:
- ordered;
- produced;
- inspected;
- shipped;
- delivered.
Final approval is one procurement milestone, not the end of procurement control.
So:
Procurement Log = Purchasing and Delivery Execution Control
Three-Log Responsibility Map
| Tool | One Row Mainly Represents | Main Question | Primary Control |
|---|---|---|---|
| Submittal Log | Submission / revision | Where is the document review? | Document status and revision |
| Material Approval Register | Material / material package | Is this material approved? | Approval decision |
| Procurement Log | Procurement package / order | Where is the package in buying and delivery? | Procurement execution |
A useful way to remember the difference is:
Submittal Log
Ends mainly with:
Current approved document / revision
Material Approval Register
Ends mainly with:
Approved material basis
Procurement Log
Ends mainly with:
Received / completed / closed procurement package
One Material Can Create Different Numbers of Records
This is one reason the three logs should not be treated as identical.
Consider:
Bathroom Vanity Package
In the Submittal Log
It may have:
- Rev 0
- Rev 1
- Rev 2
because the documents were revised several times.
In the Material Approval Register
It may remain:
one material package
with:
- approved manufacturer;
- approved model;
- final approval date.
In the Procurement Log
It may become:
- one PO;
- several delivery batches;
- one replacement order.
The same material therefore does not always have the same record structure in every tracker.
Same Material ≠ Same Tracking Record
The correct record granularity depends on what the log is controlling.
Why One “Status” Column Usually Fails
Problems appear when a project tries to collapse all three control functions into one generic field:
Status: Approved
Approved what?
It could mean:
- latest submittal revision approved;
- material approved;
- supplier approved;
- PO approved;
- inspection approved.
Likewise:
Status: Ordered
does not tell the team whether:
- the approved material matches the order;
- a newer revision exists;
- the material is still awaiting consultant approval;
- production has started.
A single status field therefore becomes ambiguous.
Document status, material approval status and procurement status should remain separate concepts.
That is true even if they are stored inside the same spreadsheet.
Can a Small Project Use One Spreadsheet?
Yes.
Three separate Excel files are not always necessary.
A small project may be able to use one master tracker if:
- the number of material packages is limited;
- revision activity is low;
- the approval workflow is simple;
- the procurement team is small;
- the same people manage documents and purchasing.
But the master tracker should still contain separate fields such as:
Submittal Status
Rev 1 Approved
Material Approval Status
Approved
Procurement Status
Production
The mistake is not:
using one spreadsheet.
The mistake is:
using one status logic for three different control functions.
One Spreadsheet Is Possible. One Undifferentiated Status Logic Is Not.
When Separate Logs Become More Useful
As projects become larger, the relationships become more complex.
For example:
One Material
may have:
multiple submittal revisions
One Approved Material
may create:
multiple POs or delivery packages
One Procurement Package
may arrive through:
several shipments
At that point, one very large spreadsheet may become difficult to manage.
Separate logs can improve:
- revision visibility;
- ownership;
- filtering;
- reporting;
- audit trail;
- accountability.
The decision should therefore depend on:
record volume and control complexity
rather than a rule that every project must use three separate files.
How the Three Logs Should Hand Information to Each Other
The three logs should not operate as isolated systems.
The handoff begins inside the Construction Material Submittal Process and should carry the confirmed approval milestone into procurement rather than duplicate all document-control detail.
They should pass important milestones forward.
A simple flow is:
Submittal Log
Current revision reaches final approval
↓
Material Approval Register
Records:
- approved manufacturer;
- approved model;
- final approval date.
↓
Procurement Log
Uses that approval information to control:
- PO release;
- production;
- inspection;
- shipment;
- delivery.
The objective is not to duplicate every field across every tracker.
It is to make sure the important approval milestones reach the next stage.
The logs should exchange milestone information rather than duplicate complete datasets.
Example: One Material Moving Through All Three Logs
Consider a shower hardware package.
After PO release, move order-level milestones into Construction Purchase Order Tracking instead of continuing to use the submittal or approval register as the delivery tracker.
Step 1 — Document Review
Submittal:
SH-023 Rev 0
Status:
Returned with Comments
Then:
SH-023 Rev 1 — Approved
Primary record:
Submittal Log
Step 2 — Material Approval
Material:
Shower Hardware Package
Approved manufacturer:
Supplier X
Approved model:
Model A
Final approval date:
May 16
Primary record:
Material Approval Register
Step 3 — Procurement Execution
PO released:
May 20
Production:
In Progress
Shipment:
Planned
ETA:
July 18
Primary record:
Procurement Log
One material package has now passed through three different control systems.
That does not mean the data is duplicated unnecessarily.
It means the procurement decision has changed.
Which Log Should Be the Source of Truth?
A useful rule is to give each status one primary owner.
When approval timing controls PO release, use Submittal Approval Dates and Procurement PO Control to connect the approval milestone with the downstream purchasing date.
Current Document Revision
Source of truth:
Submittal Log
Final Material Approval
Source of truth:
Material Approval Register
Purchasing / Production / Delivery Status
Source of truth:
Procurement Log
The information can still be referenced elsewhere.
For example, the Procurement Log may contain:
Material Approval Status: Approved
But detailed revision history should remain in the Submittal Log.
This reduces repeated updates and conflicting records.
Each status should have one primary source of truth.
Where Build Procurement Hub Fits
Different procurement-control tasks require different tools.
Within Project Documents & Submittals, procurement teams may need resources for:
- Submittal Logs
- Material Approval Requests
- Material Approval Registers
- Document Control
Within Procurement Planning & Execution, they may need:
- Procurement Logs
- PO Tracking
- Procurement Schedules
- Delivery Tracking
Build Procurement Hub helps users identify which resource fits the task instead of forcing document review, approval and delivery control into one generic tracker.
The important question is not:
Which spreadsheet is best?
It is:
What are we trying to control?
Common Mistakes
Using the Submittal Log as the Entire Procurement Tracker
An approved submittal does not show whether the PO has been released or the material delivered.
Using the Procurement Log as the Revision-Control Record
Procurement status does not replace detailed document history.
Recording “Approved” Without Defining What Was Approved
Keep document, material and procurement statuses separate.
Repeating Every Field Across All Three Logs
Share key milestones instead of duplicating complete records.
Creating Multiple Logs Without Clear Ownership
Each major status should have one source of truth.
Give Each Tracker One Clear Control Job
Use the Submittal Log to control document revisions, the Material Approval Register to control the approved material basis, and the Procurement Log to control purchasing and delivery execution. Share milestone information between them, but keep each major status owned by one primary source of truth.
FAQ
What is the difference between a Submittal Log and a Material Approval Register?
A Submittal Log tracks document submissions, revisions and review status. A Material Approval Register tracks the final approval status of the material or product.
What is the difference between a Material Approval Register and a Procurement Log?
The Material Approval Register shows whether the proposed material is approved. The Procurement Log follows the package through supplier selection, PO, production, shipment and delivery.
Can all three be combined into one spreadsheet?
Yes, especially on smaller projects. However, document status, material approval status and procurement status should still remain separate fields.
Which tracker should control the delivery date?
The Procurement Log or procurement schedule should normally control purchasing and delivery milestones, while approval records provide the approval dates that feed into those milestones.
The core principle is:
Submittal Log tracks document review. Material Approval Register tracks the material approval decision. Procurement Log tracks purchasing and delivery execution. These controls can share data and may even share one spreadsheet on a small project, but they should not share one undifferentiated status logic because they manage different records and different procurement decisions.
