A Plan Intake and Design Review Workflow That Doesn't Lose Revisions

Plans arrive by email, designs go out as attachments, and somebody builds from revision two when revision three exists. Here's a workflow that prevents it.

Illustration of an architectural plan sheet with a truss drawn over it and a pencil

Before a truss is cut, there's a whole process that happens on paper and screens: architect plans come in, someone prepares a truss design, the design is reviewed, changes are requested, a new version goes out, and eventually it's approved. In many plants that process runs through email inboxes, shared drives and memory. It mostly works, until a crew builds from an old revision.

This article describes a simple intake and review workflow that keeps plans, designs and decisions together, so the right version always gets built.

The problems with ad hoc intake

When plan intake isn't organized, the same problems repeat:

  • Files in many places. Plans arrive by email to different people, in different formats. Some get saved to a shared drive; some stay in an inbox.
  • Unclear versions. "Final", "final2" and "final-revised" all exist. Nobody's sure which is current.
  • Lost decisions. Someone approved a design on the phone, or requested a change in a hallway conversation. There's no record.
  • No link to the job. The plans for a house aren't connected to the job on the schedule, so it's hard to tell whether a scheduled job has an approved design.

Step 1: One place per job

Every job, or every quote that might become a job, should have one place where its plans and designs live. Call it a plan set. When plans arrive, they go into the plan set, wherever they came from. If an email has the plans attached, the attachments get uploaded; the email itself isn't the record.

Link the plan set to the job on the schedule when there is one. Then anyone looking at a job can find its plans and see whether its design is approved, and anyone looking at a plan set can see when the job ships.

Step 2: Accept the formats you actually receive

Architects and builders send plans in many formats: PDFs, scans, photos of paper plans, CAD files and more. A workable intake process accepts all of them rather than asking customers to convert. What matters is that every file is stored with the job, can be downloaded by the people who need it and, where possible, viewed without special software.

For safety, it's reasonable to refuse executable files. Nobody needs to upload a program as part of a set of plans.

Step 3: Version designs, don't overwrite them

When a design is prepared and sent for review, it should become version 1. When changes are made, the new design becomes version 2, and so on. Old versions stay available but clearly marked as superseded.

Overwriting files ("design.pdf" replaced by a new "design.pdf") is the root of most revision mix-ups. With numbered versions, everyone can see at a glance which is current and what changed between versions.

Step 4: Review with a decision and a reason

Review should end in a clear decision, recorded:

  • Approve: this version is the one to build.
  • Request changes: with a comment explaining what needs to change.

Requiring a comment for change requests matters. "Not right" helps nobody; "the girder at the garage needs to carry the beam shown on sheet A3" lets the designer fix it on the first try.

Step 5: Keep an activity log

Every step should be recorded with who did it and when: plans uploaded, a design sent, changes requested with the comment, the next version sent, approval. That log answers the questions that come up weeks later: "When did we get the revised plans?" "Who approved this?" "What did we change between version 2 and 3?"

A clear status for every plan set

Simple statuses make the queue visible:

StatusMeaning
Waiting for designPlans are in; no design has been sent yet
Design in reviewA design version has been sent and is waiting for a decision
Changes requestedThe reviewer asked for changes; the next version is needed
ApprovedThe current version is approved to build

With these, the design team can see what's waiting for them, reviewers can see what needs a decision, and the office can see which scheduled jobs have approved designs.

Engineering stays with engineers

A workflow tool organizes plans, designs and approvals. It does not make a design correct. Truss designs must be checked by qualified designers and, where required by code, the building official or the customer, sealed or reviewed by a licensed engineer. Building to an unapproved or unreviewed design is never acceptable, however convenient the tool.

The same applies if you use AI to help prepare designs. AI tools can read plans and draft designs faster than ever, but they can and do make mistakes. Their output goes through exactly the same review and engineering approval as anything else. See Using AI assistants with your plant data, safely.

Putting it together

Getting started

  1. Pick one place for plans and designs, per job.
  2. Upload everything there, whatever channel it arrived through.
  3. Number design versions, never overwrite.
  4. Require a decision and a reason at review.
  5. Link plan sets to scheduled jobs.
  6. Check approval status before a job's batches are released to the floor.

Summary

Plan intake and design review don't need to be complicated, but they do need to be in one place. Keep each job's plans and designs together, version every design, record approvals and change requests with reasons, and log every step. Then the right version gets built, and you can always show how you got there.

Plans & design review in Truss Plant Portal works this way: plan sets linked to jobs, any file format up to 100 MB, design versions, approve or request changes with a comment, and an activity log for every set.

Tags: plans design review revisions approvals workflow