Tracking · Engine

Submittal Tracker (engine)

The Submittal Tracker engine is the extraction step that normalizes an existing submittal log into tracker records. It reads a spec section, a submittal log or a batch of individual submittals and records ball-in-court, due date, reviewer, status and revision cycles for each, ready to import into the Submittal Tracker workspace.

By Trueleveler Editorial

Engine Phase: Tracking Runtime: Continuous (not per-run) Pro+

What is the Submittal Tracker engine?

Submittal Tracker (engine) is a narrower cousin of Submittal Extractor: it reads a submittal-focused input (spec section, existing submittal log, or batch of individual submittals) and normalizes each record with ball-in-court, due date, architect/engineer reviewer, status, and number of revision cycles. Output imports directly to the Submittal Tracker workspace.

Use this engine when you already have a partially-managed submittal process and want to import or audit state. Use Submittal Extractor when you're starting from a raw spec section.

What do I upload to the Submittal Tracker engine?

Upload an existing submittal log such as a Procore, BIM 360 or Sage export, a spec section to extract the required submittals, or a batch of individual submittals with their cover sheets.

Existing submittal log (Procore / BIM 360 / Sage export)
Spec section (to extract required submittals)
Batch of individual submittal documents with their cover sheets

How do I run the Submittal Tracker engine?

To run the Submittal Tracker engine, open it, upload the source, run it, review and edit the records and import them to the tracker.

Open the engine
Sidebar → Engines → Submittal Tracker.
Upload
Log, spec, or batch.
Run
20–40 seconds.
Review + edit
Each submittal as an editable row.
Import to tracker
Merges by submittal number if already present.

How do I read the Submittal Tracker engine results?

The result is a submittal register table with ball-in-court and overdue flags.

Submittal register table

Number, description, type, spec ref, submittal date, due date, reviewer, status, revision count.

Ball-in-court

Who currently has it — sub, GC, architect, engineer.

Overdue flags

Items past their due date, color-coded.

Every control, explained

Run analysis

One run.

Edit row

Description, type, reviewer, status, ball-in-court.

Import to Submittal Tracker

Push to tracker; merges by submittal number.

Export PDF

Formatted submittal log.

Export XLSX

Raw table for external systems.

Chains

Chains into

Submittal Extractor

Extract More Submittals — Upload additional spec sections to extract more submittal requirements.

Procurement TrackerData

Track Procurement Status — Move approved submittals into procurement tracking for ordering and delivery.

Punch List

Verify Against Submittals — Cross-check punch items against approved submittals for spec compliance.

Warranty CompilerData

Compile Warranties — Approved manufacturer submittals are the source for warranty terms in the closeout package.

Chained from

Submittal ExtractorData

Import to Submittal Tracker — Review & add extracted submittals to the tracker (de-duped).

Procurement Tracker

Track Submittals — Link procurement items to their submittal tracking requirements.

Submittal ReviewerData

Log Review Decision — Reviewed submittal status (Approve / Approve as Noted / Revise / Reject) carries forward into the submittal tracker.

Exports

PDF — submittal log.
XLSX — raw table.
CSV — flat list.

Troubleshooting

Duplicates across sources

Engine merges by submittal number. Ensure numbers are consistent across imports.

Sources

ER 415-1-10: Contractor Submittal ProceduresU.S. Army Corps of EngineersThe Corps of Engineers procedure for registering, reviewing and tracking contractor submittals such as shop drawings and samples.
Summary: A201-2017, General Conditions of the Contract for ConstructionAIA Contract DocumentsThe AIA overview of the general conditions that set out the rights and duties of owner, contractor and architect.