What is the first step in syncing procurement and progress?

Create one shared project structure that everyone uses for phases, cost codes, drawing revisions, and status.

How do drawing revisions affect purchasing?

Purchasing should always reference the current revision, otherwise materials may be bought for outdated scope or dimensions.

Should progress be tracked separately from payment states?

No, they should be connected so certifications and billing reflect what is actually complete.

Can I manage this with spreadsheets?

You can start there, but as soon as the project gets complex, spreadsheets usually create version drift and manual reconciliation work.

How do I build a project-control workflow that keeps procurement, progress, and drawings in sync?

Why this workflow matters

If procurement, progress, and drawings are not synchronized, every other part of project control gets harder. Buyers may order from an outdated revision, site teams may report progress against the wrong package, and the finance team may certify work that does not match what is actually installed.

A good workflow does not just record events. It keeps the team aligned on the current state of the project.

Step 1: Define one project structure

Start with a structure that every team can use:

Project
Phase or package
Cost code or work section
Drawing set / revision
Purchase and commitment status
Progress and payment state

The goal is not bureaucracy. The goal is to give procurement, site, and finance the same map.

Step 2: Control the latest drawings

Before anything is purchased or executed, establish which drawings are current. If multiple versions are circulating, mark one as authoritative and make it easy to find.

Good practice:

Store drawings in a central location
Name revisions clearly
Keep a revision history
Link revisions to the package or task they affect
Avoid relying on chat threads for “latest file” decisions

Step 3: Connect procurement to the project package

Every purchase request should answer three questions:

Which project is this for?
Which package or cost code does it belong to?
Which drawing revision supports it?

That linkage prevents duplicate orders and helps the team see whether buying is ahead of, behind, or aligned with the work.

Step 4: Track progress in a way that supports payment

Progress should not be a vague status note. It should reflect actual project state enough to support certifications and billing decisions.

A useful approach is to track:

What has been approved for purchase
What has been delivered
What has been installed
What is ready for certification
What has been billed or claimed

This is especially important when progress and payment states are part of the same commercial process.

Step 5: Review the gap regularly

A weekly control review is often enough to catch problems early. Check:

Open procurement items
Changes to drawing revisions
Progress versus plan
Items waiting on approval
Payment states that do not match field reality

The point is not to create more reporting. It is to keep the project moving on the basis of current information.

Common mistakes to avoid

Letting each department keep its own version of the project status
Buying materials before the drawing revision is confirmed
Tracking progress only in narrative form
Building certifications outside the live project record
Using too many isolated tools with no operational bridge between them

How to know the workflow is working

You should notice:

Fewer questions about which drawing is current
Fewer duplicate or premature purchases
Faster preparation of progress and payment states
Better visibility into what is committed versus what is still open
Less time spent reconciling spreadsheets and messages

Where software fits

This workflow can be mapped on paper, but it is hard to sustain if the tools are disconnected. For a growing contractor, the system needs to support the workflow directly rather than force people to rebuild it manually every week.

That is why construction ERP software becomes the natural next step once the process matters enough that mistakes are expensive.

Recommended tool: OneMake

ZANDYC’s pick for this workflow is OneMake because it is designed to connect project management, cost control, purchasing, progress, and plans/drawings management in one system.

It fits this need because it helps you:

Keep procurement tied to the live project structure
Manage drawings as part of the active job rather than a separate archive
Track progress and payment states in the same operational flow
Reduce the manual handoffs that cause confusion between office and field

OneMake is best for construction companies that want one system to coordinate end-to-end project execution. It is not intended for teams looking only for estimating or a single-purpose document repository.

If you are ready to run projects with less drift, start here: https://onemake.ai