Procurement is the quiet engine behind every successful project, because when materials are late or submittals stall in review, your schedule slips and margins erode, and while it can feel like a maze of emails, spreadsheets, and calls, a clear framework paired with the right tools brings order and predictability.
At PLOT, we believe that better tools lead to better projects. This procurement log template is our 'gift' to the industry—a resource that any contractor can download, use, edit, and improve. Whether you need a simple tracking system or a highly customized solution, this spreadsheet gives you a solid foundation to build on.
The submittal log and the procurement log are the same document. Most project teams do not treat them that way, and that disconnect is where projects lose time.
Here is what typically happens. The project engineer maintains a submittal log in Procore. They also maintain a procurement log in Excel. The submittal log tracks whether a shop drawing has been submitted and approved. The procurement log tracks whether the material has been ordered and when it is arriving. These two documents are updated separately, by different people, on different schedules, and the relationship between them - the fact that the order cannot be placed until the submittal is approved, and the order deadline is determined by the required on site date - exists only in the project engineer's head.
When the submittal comes back with comments and needs to be resubmitted, the Excel log does not know. When the architect takes three weeks instead of two to review, the order deadline has already passed by the time anyone recalculates. When a sub finally places the order, no one updates the procurement log to reflect the actual ship date.
PLOT closes that gap by treating submittals, procurement, and vendor coordination as a single connected workflow.
PLOT connects to Procore and Autodesk Construction Cloud and reads submittal status on a daily sync. When a submittal moves from submitted to approved, PLOT reflects that automatically. When a submittal comes back as revise and resubmit, PLOT flags the affected orders and recalculates the downstream impact.
The data model in PLOT is built around the relationship between submittals, materials, and orders. A submittal can reference multiple materials. A material can have multiple orders tied to different schedule activities. An order cannot be placed - in PLOT's tracking - until the linked submittals are approved. That logic is enforced by the system, not by a project engineer checking two spreadsheets against each other.
The submittal deadline in PLOT is derived from the Required On Site date, working backward through your configured durations: review duration, submittal cycles, order window, and lead time. If you expect two rounds of review for a complex mechanical submittal, that cycle count is configured upfront and the submittal deadline reflects it.
Submittal tracking efficiency is not about whether you know the status of a submittal. Procore tells you that. Efficiency is about whether the status of a submittal is immediately connected to every downstream decision it affects.
When a submittal is approved in Procore and PLOT reads that update on the daily sync, the affected order moves from pending to eligible for placement. The trade gets a notification in their next weekly checklist that the approval has come through and the order deadline is approaching. The project engineer does not have to cross-reference two systems to figure out that the submittal cleared and it is now time to push the sub on the order.
When a submittal is late - the architect has had it for three weeks and the two-week review window has passed - PLOT flags the affected orders as at risk because the approval deadline has been missed and every downstream deadline has shifted. The project engineer sees this on the dashboard without running a report. The push schedule shows how far the order deadline and ship date have moved based on actual dates rather than planned ones.
That is what efficiency looks like in practice. Not faster submittal routing - Procore handles that. But instant, automatic propagation of submittal status into the procurement and delivery timeline so the team is always looking at a current picture, not one that is two weeks out of date because no one had time to update the spreadsheet.
The "ball in court" concept - knowing who is responsible for the next action on a submittal at any given moment - is well established in submittal management. Procore tracks it. So does Autodesk. What those platforms do not track is what the ball in court status means for your material orders.
In PLOT, the connection is explicit. If the ball is in the architect's court on a submittal for rooftop units, PLOT knows that the approval has not come through, the order cannot be placed, and the order deadline is three days away. That is an at-risk item that surfaces on the PLOT dashboard without anyone having to work it out manually.
If the ball is in the sub's court for a revise and resubmit, PLOT knows that the submittal cycle count has incremented, the review duration needs to run again, and the order deadline has moved. The push schedule shows the new anticipated dates automatically.
The project engineer does not have to hold this logic in their head or maintain it in a spreadsheet. The system holds it and surfaces exceptions.
Standard submittal tracking tools work well when the relationship is one submittal to one material to one order. Construction projects are rarely that clean.
A lighting fixture submittal might cover forty fixture types across three installation phases, each with its own order placed at a different time tied to a different schedule activity. A door hardware submittal might release in sections as floors complete. A mechanical equipment submittal might require both a product data submittal and a shop drawing submittal, both approved, before fabrication can begin.
PLOT is built to track this complexity. You can link one submittal to multiple materials. You can link one material to multiple orders, each tied to its own schedule activity and carrying its own deadline chain. You can require multiple submittals to be approved before an order is eligible for placement. The visual connector in PLOT shows the full map of relationships so the project engineer can see exactly how a submittal connects to the schedule and what the downstream impact of a delay is.
Submittal approval is only the beginning of vendor coordination. Once an order is placed, the coordination work shifts to confirming that the vendor is on track, that the ship date has not moved, and that the delivery is sequenced to arrive when the site can actually receive and install it.
PLOT handles vendor coordination automatically through scheduled check-ins. When an order is placed and a ship date is on record, PLOT sends the vendor a confirmation request as the date approaches. The vendor responds directly - no account, no login - and the confirmed or revised date updates in the procurement log. If a vendor reports a delay, PLOT's push schedule recalculates the downstream impact immediately so the project team knows what it means for the installation activity before the truck does not show up.
Delivery sequencing is the other half of this. An approved submittal and a placed order do not help if the material arrives when the crane is booked, the laydown area is full, or the installation crew is not on site yet. PLOT connects the procurement timeline to the delivery scheduling system so that confirmed ship dates feed into the delivery coordination calendar. The trade books their delivery slot against the site rules - gate availability, equipment reservations, concurrent delivery limits - and the material arrives when the site is actually ready to receive it.
That end-to-end connection, from submittal approval through vendor coordination to sequenced delivery, is what makes procurement scheduling reliable rather than just tracked.
The most time-consuming part of submittal tracking is not updating the log. It is chasing the people who need to act on it.
Chasing the sub to confirm they submitted. Chasing the architect to find out where the review stands. Chasing the sub again to confirm the order was placed after the approval came through. Chasing the vendor to confirm the ship date is still what it was when the order was placed six weeks ago.
PLOT handles all of that automatically. Trades get a weekly checklist email with only their action items for that week. When a submittal has been approved and an order needs to be placed, that shows up in the trade's checklist. When an order has been placed and the ship date is approaching, PLOT checks in with the vendor automatically to confirm the date is still accurate. The project engineer sees the results of those check-ins in the procurement log without having to make a single call.
The audit trail captures every update, every confirmation, and every change with a timestamp. When something goes wrong - a ship date that changed without anyone noticing, an order that was placed late - the record shows exactly what happened and when.
A connected submittal and procurement workflow changes how a project team spends its time. Instead of maintaining two parallel documents and manually connecting the logic between them, the team has one system that holds the connection and surfaces what needs attention.
Project engineers stop spending time on status updates and start spending time on the decisions that only they can make. Superintendents stop getting surprised by materials that are not ready because the procurement picture is always current. Trade partners know exactly what they need to do and when because the checklist is automatic and specific.
The submittal log does not sit in isolation anymore. It drives the procurement timeline, which drives the delivery schedule, which drives what actually happens at the gate. That chain is only useful if it is connected end to end. PLOT connects it.
PLOT syncs submittal status from Procore and Autodesk Construction Cloud daily and connects submittal approvals directly to procurement deadlines, order placement, and delivery scheduling. If your submittal log and procurement log are two separate documents that someone reconciles by hand, book a demo at getplot.com.
