MINI-POD – It is NOT in Procore!

It Is Not in Procore: What Your Project Management Software Cannot Do for You

Here is something Jason Schroeder hears constantly on project visits: “Oh, we have that in Procore.” Buyout status? In Procore. Supply chain? In Procore. Material procurement tracking? In Procore. Financial projections? In Procore.

It is not in Procore. Most of what people believe is being managed in their project management software is not being managed at all. It is being documented, entered, and filed. That is not the same thing.

What You Actually Need to Run a Project

Before getting to the software problem, Jason lays out the instruments that a project team genuinely cannot succeed without.

A schedule is not optional, and it has to exist before field work begins. That schedule needs to be built on Takt planning principles, or at minimum on builder mentalities applied through CPM tools like P6 or Microsoft Project. Pure critical path method alone is not sufficient. The contractors who have succeeded with P6 for decades have been using it with production thinking and buffer management, not with pure CPM logic. The schedule must reflect how the work is actually going to flow.

A quality program that is not a checklist in software but an actual sequence: right scope, right buyout, preconstruction meeting, first in place mockup, ongoing inspections, closeout inspections, and a system that ensures every trade partner arrives prepared and knowing what they are building and how.

A financial projection summary that captures the full picture: original budget versus current budget, buyout contingency, over under by scope, fee, labor gains, gains on bonds and insurance, equipment rental gains, known and projected exposures, contractor contingency balance, pending change orders, and owner or design contingency balance. All of that totaling to a current financial projection that tells the team whether the project is on track to deliver its target gross margin.

A risk and opportunity register that ties directly into the financial projections.

A buyout log and a material procurement log, which are separate documents with separate purposes.

A roadblock removal system and a way to track team health.

That is the baseline. Not the aspirational target. The floor.

What Procore Actually Tracks

Procore has a submittal register. That is not a procurement log. It tracks whether submittals have been submitted, reviewed, and approved. It does not track whether the approved submittal triggered a purchase order at the manufacturing plant, whether that order is in fabrication, whether it is being shipped, whether it has cleared customs, when it is expected on site, what buffer has been built between delivery and installation, or whether the supermarket has room to receive it.

A procurement log tracks the full supply chain from approved submittal to material in the supermarket ready for installation. The difference between having a submittal register and having a procurement log is the difference between knowing that paperwork moved and knowing that materials will arrive on time to support flow.

The same distinction applies to a buyout log. A buyout log is not a list of contracts in a system. It is a living document aligned to the Takt rhythm of the project, showing for each scope whether the trade partner is identified, whether the scope inclusions and exclusions are defined, whether the contract is drafted and signed, whether bonds and insurance are in place, whether safety and quality plans have been submitted, whether the trade partner is pre qualified, and whether everything needed for them to begin work successfully is complete. All of that aligned to the dates when each scope needs to be ready to support the production sequence.

Why the “It’s in Procore” Response Is a Problem

When someone on a project team responds to a request for a procurement log by saying “we have that in Procore,” what they have revealed is that they do not have a procurement log. They have a submittal register and they believe those are the same thing.

This matters because the supply chain problems that derail construction projects are not submittal problems. They are sequencing problems, lead time problems, customs clearance problems, delivery coordination problems, and supermarket management problems. A submittal register cannot surface any of those. A functioning procurement log can surface all of them before they affect the schedule.

The same is true for the buyout log. Knowing that a subcontract exists in a system is not the same as knowing that a trade partner is fully prepared to mobilize when the Takt plan calls for them. Insurance lapses, unsigned scope addenda, missing quality plans: these things do not appear in a subcontract status field. They appear in a rigorous buyout log with clear readiness criteria at each stage.

Here is what that looks like in practice:

• A buyout log aligned to the Takt plan shows that a mechanical contractor needs to be fully ready to mobilize in six weeks, and currently their insurance certificate has not been updated
• A procurement log shows that a long lead specialty item needs to be ordered this week to hit its buffer window ahead of the installation date, but the submittal is still in review
• A financial projection summary shows that two pending change orders represent significant contingency exposure and a decision about contractor contingency needs to happen before the next owner meeting

None of that visibility lives in a submittal register. All of it exists in the instruments that project teams still need to build and maintain separately.

What This Means Going Forward

Jason is direct about the state of the technology. As of this recording, project management platforms have not built the functionality that would replace a proper procurement log, a Takt aligned buyout log, or a financial projection summary. When they do, the improvement will be in the speed and accessibility of that information, not in the elimination of the information itself.

Until then, running a construction project without a separate buyout log and a separate material procurement log is running a project without two of the most important instruments in the kit. The submittal register tells you what the paperwork is doing. The procurement log tells you whether the materials will be there when you need them. Those are not interchangeable.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The Challenge for Your Project

Pull up your current procurement tracking for one active scope on your project. Ask whether it shows: the submittal status, the PO status, the fabrication status, the shipping status, the expected delivery date, the buffer window before installation, and the supermarket location on site where the material will land.

If more than two of those are missing, you do not have a procurement log. You have a submittal register. Find out what is missing and build the tracking that will give you visibility into the full supply chain.

On we go.

Frequently Asked Questions

What is the minimum a buyout log needs to include to be useful?

At minimum: scope name, trade partner, contract status, inclusions and exclusions confirmed, insurance current, safety plan submitted, quality plan submitted, and the date by which full readiness is required based on the Takt plan. Anything less than this is a contract list, not a buyout log.

Should the procurement log be a separate document from the Takt plan or integrated into it?

They should inform each other. The Takt plan drives the dates in the procurement log. The procurement log surfaces whether the material will be ready in time to support the Takt plan. Some teams maintain them as separate documents with shared date references. Others build procurement tracking directly into the Takt plan timeline. Either approach works as long as both exist.

How often should the procurement log be reviewed?

Weekly at minimum, with the superintendent leading the review. For projects with significant long lead items or complex supply chains, more frequent review is appropriate. The procurement meeting is a standing agenda item for the weekly project coordination cycle.

Is a financial projection summary the same as a job cost report?

No. A job cost report shows where money has been spent against budget. A financial projection summary projects where the project will finish financially, incorporating not just actual costs but contingency exposure, pending changes, labor gain or loss projections, and fee status. A job cost report is a lagging indicator. A financial projection is a forward looking management instrument.

What is the most common procurement failure mode on construction projects?

Not accounting for lead time against the production schedule. A trade partner is bought out on time and the submittal is approved on time, but nobody has traced the lead time from PO to fabrication to delivery against when the material is actually needed in the field. The procurement log prevents this by making the full timeline visible at every review.