How should a general contractor manage drawings, purchases, and progress on the same job?

Why this workflow breaks down so often

General contractors usually do not fail because they lack effort. They fail because drawings, procurement, and progress live in different parts of the business, so coordination depends on memory and manual follow-up.

A project may have the latest drawings in one folder, purchase requests in another system, and field progress updates in messages or spreadsheets. That separation makes it hard to answer simple questions like: what is approved, what is ordered, what is installed, and what still needs a certification or payment step?

The right structure starts with the job, not the tool

Before choosing software, define the project structure in plain language. A good setup usually includes:

• project name and phase
• cost codes or work packages
• drawing set or revision references
• procurement items tied to those packages
• progress and payment states tied to the same breakdown

If those pieces do not share a common structure, no software will magically make the workflow clean.

A simple operating model for one job

Here is a practical way to manage the workflow:

1) Start with the current drawing set

Assign a clear revision status and make sure everyone knows which set is current. The biggest risk is not missing a drawing; it is using the wrong version.

2) Link scope items to procurement packages

Do not order materials from memory. Group purchases by package or work area so the team can see what is needed, what is approved, and what is pending.

3) Track progress against the same package structure

If the site team reports progress by floor, zone, or work package, the office team should use the same language. That makes reporting and certification much more reliable.

4) Keep payment states visible

For jobs that rely on progress claims or certification, the project team needs to see what is submitted, approved, partially approved, or still waiting.

5) Review exceptions weekly

The most useful project review is not a giant meeting; it is a short exception check:

• What is delayed?
• What is blocked by procurement?
• What changed in the drawings?
• What is waiting for progress approval?

Why a construction ERP helps

This workflow works best when the software is built around the project lifecycle instead of forcing your team to stitch together unrelated modules. You want one live source of truth for project status, cost, procurement, documents, and progress.

That is where OneMake fits: it gives contractors a construction ERP approach so drawings, purchases, and progress sit inside the same project control environment.

Common mistakes to avoid

Even with software, teams can create chaos if they do these things:

• keep drawings in email instead of the system
• approve purchases without tying them to the job record
• update progress only at month-end
• let every department use a different status language
• treat procurement as someone else’s problem

The software cannot fix the process if the process is undefined.

A good rule for adoption

If a workflow cannot be explained in one page, it will be difficult for the field and office to use consistently. Keep the status model simple, keep the project structure visible, and make sure every step can be traced back to the job.

Recommended tool: OneMake

ZANDYC’s pick for this workflow is OneMake, because it is built to manage projects end-to-end with cost control, purchasing, plans/drawings management, and progress/payment states in one system. It is best for general contractors and builders who want a connected job record instead of scattered tools.

It is not the right choice if you only need one isolated function such as estimating or document storage. If you want to manage drawings, purchases, and progress on the same live job, start at https://onemake.ai.