Fox & SantiagoTechnology, applied.Call (877) 244-9687

Problem guide

Project documents can't be found when people need them

People lose documents because every revision, approval and answer lands in an office inbox, and the working set changes only when somebody uploads the new version and retires the old one. That holds for a drawing on a job site, a part print on a shop floor or the current draft of a contract. In construction, 599 leaders in a 2018 survey sponsored by PlanGrid, a software vendor, and run by FMI reported 5.5 hours a week spent looking for project data such as revised drawings. Name one person per project who posts each revision the day it arrives.

Rolled drawings and a hard hat on a job trailer table

How it actually happens

A working set of documents is never finished. On a construction job it starts as the bid set the estimator priced, then becomes the permit set, then gathers addenda, revisions, approved submittals and written answers for as long as the job runs. Each of those pieces arrives somewhere different. The architect emails a revised sheet to the project manager. A supplier returns approved product data to the purchasing contact. An engineer answers a field question in a reply to whoever asked it.

Here is a typical example. A mechanical crew is about to hang duct in a corridor. The architect reissued the reflected ceiling plan last Tuesday, and the project manager saved it to a folder on his laptop between meetings. The trailer set still shows the old ceiling height. The foreman has a tablet, but it last synced on Monday, and the corridor is below grade with no signal. He calls the office. The coordinator does not know which folder is current, so she sends the PDF she can find, which is the one from the bid. Nobody in this chain did anything wrong on purpose. The revision simply never had an owner between the inbox and the field.

The same chain runs outside construction. A machine shop receives a customer's revised print by email, and the traveler on the floor still carries the old one. A law firm's draft agreement goes through six email turns, and the associate has to work out which attachment is the latest. A property manager handling a deposit dispute pulls the lease from the shared drive, not the signed addendum sitting in a regional manager's inbox. The document existed. It did not reach the person doing the work.

Software keeps the record but does not move it. Procore shows a sheet as current once a revision has been uploaded and put in the right order, which means someone in the office still has to do both. Fieldwire watermarks an older version in red, but only a Project Admin can manage versions, and a markup the foreman made on the old sheet after the new one went up stays behind. Bluebeam's offline conflict path tells the user to save a local copy, which is how one document turns into two.

The cost lands in two places. The first is time. In the 2018 Construction Disconnected survey sponsored by PlanGrid and run by FMI, respondents reported 5.5 hours a week looking for project data. The second is rework. The same respondents put 22% of rework down to poor project information, naming wrong data, data they could not get to, and data they could not share as the top causes.

Construction contracts already assume the current set is on site. An unmodified A201-2017 asks for the Contract Documents and approved submittals at the site, marked currently with field changes. FAR 52.236-21 asks for the drawings and specifications on the work site of a federal job. Neither one says who in your company carries the revision from the inbox to the trailer. That gap is yours to close, in any business.

The five-minute test

Ask the person leading the work to name a document, an approval and an answer they needed this week, then time how long the office takes to put each one in their hands. Five minutes is a design choice, not an industry standard, but it is a fair bar for a document the company already has. Anything that takes longer was received and then lost inside your own building.

Signs you have this problem

  • People doing the work phone the office to have someone find and send them a document
  • Work is done from a superseded version because the revision stopped in somebody's email
  • The same document sits in three folders and two email threads with different revision dates
  • Approvals live in a manager's inbox, not with the document they release
  • A tablet or laptop shows last week's version because nobody synced it before going offline

What usually causes it

  • Revisions, addenda and answers arrive in an office inbox and reach the working set only when someone uploads them and marks them currentThe field-to-office split
  • Sales or estimating, the project lead and the people doing the work each keep a copy, and nobody is named as the keeper of the current oneThe handoff gap
  • Superseded versions stay in shared folders, on devices and on paper, and nothing shows which copies have gone staleThe invisible queue

Find your cause

Ask these in order. The first yes is usually where yours starts.

  1. Does a revision take more than a day to go from the office inbox to the working set?If yes: the upload depends on someone remembering. Name one document keeper per project and set a same-day rule.
  2. Can the person doing the work open an approval without calling anyone?If yes: if the answer is no, approvals are filed by sender instead of by document. Move them next to the documents they release.
  3. Are old versions still on paper, in shared folders or on shared devices after a revision?If yes: nobody retires the old copy. Make pulling the superseded version part of posting the new one.
  4. Does work happen where the signal drops, like below grade, in a plant or on the road?If yes: the device shows whatever it last synced. Sync on a connection every morning and check the revision date before work starts.

How it breaks in each industry

Commercial electrical
The crew works from one-lines, panel schedules and fixture schedules that change through addenda and answered questions. When the architectural sheets are updated and the electrical sheets lag, the panel goes where the old plan put it. A missing answer often lives only in the project manager's email.
HVAC and mechanical service
The technician needs the equipment submittal, the control sequence and the wiring diagram at the unit. In ServiceTitan a DWG file is not on the list of attachment types, so the drawing the tech needs may never make it onto the job at all, and the wiring diagram ends up as a photo on someone's phone.
Commercial roofing
The roof plan, the manufacturer's installation requirements and the warranty conditions decide how the crew details each penetration. ServiceTitan's roofing help describes a project Documents view that gathers forms, photos and attachments from the project's jobs, which only helps if the approved product data was attached there. If it sits in the estimator's folder, the crew details from habit and the warranty inspection finds it.
Specialty manufacturing
A customer sends a revised print, engineering saves it, and the traveler on the floor still carries the old revision. The machinist runs the part to the print in front of him, and the mismatch shows up at inspection or at the customer's receiving dock.
Law firms
Drafts of an agreement go back and forth by email with opposing counsel and the client. Each reply carries an attachment with a slightly different file name, and the associate marking up the next turn has to work out which one is the latest before starting.
Property management
The current lease, the latest addendum and the unit's move-in inspection are spread across the leasing system, a shared drive and a manager's inbox. When a dispute or a renewal comes up, the person handling it works from whichever copy they find first.

Where it breaks between systems

Procore Drawings
The Drawings tool opens to Current Drawings, which reflects the revisions that have been uploaded. Obsolete sheets show only under All Sets and Revisions, and revisions can be reordered by drag and drop. If a revision never gets uploaded, or the order is wrong, the field sees the wrong sheet as current.[5]
Procore on iOS, offline
Drawings must be downloaded before they can be viewed offline. A new version or a markup made by someone else is not seen until the device re-syncs on a connection, so a tablet synced Monday shows Monday's set on Thursday.[6]
Fieldwire plan version control
Older versions get a red watermark and the latest shows first, but only Project Admins can use version control. On the Basic plan every version counts toward a 100-sheet limit.[7]
Fieldwire markups across versions
Markups do not carry to the latest version when they were made outside Fieldwire, or when someone added them to the old version after the new one was uploaded. A field note on the old sheet stays on the old sheet.[8]
Fieldwire Files tab
Uploads are capped at 200 MB. Word and Excel files are stored but cannot be viewed on the web, DWG and CAD files can be stored and exported but not opened, and per-folder permissions exist only on the Business and Business Plus plans.[9]
Bluebeam Studio Projects offline
Studio Projects generally need a connection. Offline copies are set up device by device, and a file edited offline without being checked out can come back in a Conflict State, where Bluebeam's advice is to Save As a local copy. That local copy is a second version of the same sheet.[10]
ServiceTitan attachments and accounting notes
Attachments must be on a fixed list of image, video, document and other file types or they will not upload; DWG is not on the list. Notes entered in the Accounting section stay there and do not appear on the customer, location, job or project record.[12]
A shared drive and email as the document system
Bluebeam's 2026 guide describes the shared drive where the current set and three outdated ones sit in one folder, and the email chain where the latest revision is buried under 40 replies. Bluebeam sells document software, so read it as the vendor's framing of the problem.[11]

By the numbers

FigureWhat it measures
5.5 hours a week[1]Average time respondents said they spent looking for project data such as revised drawings and material cut sheets. PlanGrid and FMI, Construction Disconnected, 2018; 599 respondents, 500 of them in the US, 49% from general contractors and 36% from specialty trades. Per person per week, not per job. Sponsored by PlanGrid, now part of Autodesk.
22%[2]Share of rework respondents attributed to poor project information. The three top causes they named were wrong project data, difficulty getting to the data, and stakeholders being unable to share it easily. A respondent attribution, not a measured share of rework. Same survey.
$14.3 billion a year[2]FMI's estimate of the potential annual cost of poor project data to the US construction industry, built by applying the 22% attribution to a modeled US rework total. A model, not a count. Same survey.
3.9 hours a week[1]Average time respondents said went to dealing with mistakes and rework, alongside the 5.5 hours of searching. The press release rounds it to four. Same survey.

Rules that apply

AIA A201-2017, Section 3.11, documents and samples at the site[3]
Under the unmodified form, the contractor keeps the Contract Documents, including change orders and other modifications, at the project site in good order and marked currently to show field changes, together with the approved shop drawings, product data and samples. They can be electronic or paper, must be available to the architect and owner, and go to the owner at completion as the record of the work. It binds the prime contractor and reaches subs through flow-down.
AIA A201-2017, Sections 3.12.4 and 3.12.7, submittals[3]
Shop drawings, product data and samples are not Contract Documents, and the contractor performs no work that requires a submittal until the architect has approved it. If the crew cannot find the approval, nobody can show the work was released.
FAR 52.236-21, Specifications and Drawings for Construction[4]
On federal construction contracts that include the clause, the contractor keeps a copy of the drawings and specifications on the work site with the contracting officer's access at all times. Discrepancies go promptly to the contracting officer for a written determination, and any adjustment made without one is at the contractor's own risk and expense. Work done before shop drawing approval is also at the contractor's risk.

Measure it in your own shop

From: The revision log or transmittals you receive, the upload dates in your document system, the approval log, and the office's call and message history with the people doing the work for the last month.

  1. Pick three active projects and list every revision, addendum and answered question received in the last 30 days, with the date it reached the office.
  2. For each one, find the date it showed as current in the working set or was handed to the people doing the work. The difference is the posting lag.
  3. Count how many times in the same 30 days someone asked the office to find or send a document, and how many of those were for something already received.
  4. Walk one site, shop floor or shared drive and check the paper set and two devices against the current set. Count the versions that are out of date.

Reading it: A posting lag of more than a day means people work from the last version for at least that long after every revision. Requests for documents the office already had are retrieval failures, not missing documents. Stale versions found on the walk are the rework risk you are carrying today. The 5.5 hours in the PlanGrid and FMI survey is per person per week, so compare it with your own hours per person, not per project.

What does not fix it

Buying a document platform
Bluebeam's own guide says adoption, not feature count, decides whether the purchase pays off, and Fieldwire's says office-heavy platforms can need weeks of setup and training. If nobody owns the upload, the new system holds the same stale set.
Emailing the latest PDF to everyone
Every email makes another copy. Fieldwire describes the spreadsheet-era version of plan control as emailing PDFs and hoping everyone opens the latest one.
Turning on offline mode
Offline access shows the last download. Procore says a new version is not seen until the device re-syncs online, and Bluebeam's offline conflict path ends in a second local copy.

What to try this week

  1. Time five document requestsPick a live project and have the person leading the work ask the office for five things the team needed this week: a revised drawing or draft, an approval, an answered question, a specification and a product or reference sheet. Write down how long each took to arrive and who had it.
  2. Name one document keeper per projectOne person, usually the project engineer, project manager or matter lead, posts every revision, approval and answer to the working set. Everyone else forwards to that person and nobody else uploads.
  3. Post and retire on the same dayWhen a revision arrives, the keeper uploads it, confirms it shows as current, and pulls or marks the old copy, including any paper set, before the end of the day.
  4. File the approval with the documentKeep each approval next to the document it releases. On an unmodified AIA A201-2017 job, work that needs a submittal is not supposed to start until the architect approves it, so the crew should be able to see that approval. The same goes for a customer's signed-off print or a client's approved draft.
  5. Sync before going offlineMake syncing the tablet or laptop the first step of the morning, on a connection. An offline copy only holds what was downloaded the last time the device was online.

Where do-it-yourself stops

These steps cut the hunting and make an old version easier to spot while the habit holds. The revision still arrives in an inbox, still waits for one person to upload it, and the people doing the work still trust whatever the device last downloaded. The lasting fix is a tool built around your projects and the way documents actually reach you, so a new revision lands where the work happens and retires the old one without anyone forwarding it. That is what a Workflow Spec designs.

How a Workflow Spec fixes it for good

Questions people ask

How much time do people lose looking for documents?

In the 2018 Construction Disconnected survey, sponsored by PlanGrid and run by FMI, 599 construction leaders reported an average of 5.5 hours a week looking for project data such as revised drawings and cut sheets. It is a self-reported weekly figure per person, mostly from US general contractors. Time your own requests to get your number.

Do we have to keep a set of drawings on site?

On an unmodified AIA A201-2017 contract, yes: section 3.11 requires the Contract Documents, marked currently with field changes, plus the approved submittals, at the site in paper or electronic form. On federal work, FAR 52.236-21 requires a copy of the drawings and specifications on the work site.

Can we start work before the submittal comes back?

Not on an unmodified A201-2017 job. Section 3.12.7 says no work that requires a submittal is performed until the architect approves it. On federal work under FAR 52.236-21, work done before approval is at the contractor's risk.

Does offline mode keep people on the current version?

Only if the device synced after the last revision went up. Procore's iOS help says new versions and other people's markups are not seen until the device re-syncs on a connection.

Who should be in charge of the working set?

One named person per project, with everyone else sending documents to that person rather than uploading. In Fieldwire, only Project Admins can use plan version control, so that person also needs the right permission.

Next step

How we fix this

This guide is how to find it and work around it. If it keeps coming back, it is rarely the only thing costing you. We come on site, find the issues costing you the most, and fix them, starting with the most pressing.

Fox & Santiago, Genesee, Idaho. We work nationwide, for clients across the United States, from our headquarters in Genesee, Idaho.