The foreman pulls up the plan set in the gang box to check the stub-out location for the mechanical room. The drawing shows 4” from the east wall. His phone shows 6” — a revision the PM uploaded Tuesday. The pour is Thursday.
That gap between what’s in the trailer and what’s current is the plan sheet problem on a commercial construction job. The revision cycle on a complex project runs constantly — structural RFIs change dimensions, mechanical coordination shifts stub-out locations, electrical routing updates after the ceiling coordination meeting. The crew working from last week’s drawing is the crew installing something that has to come back out.
A construction plan viewer app solves one problem: the crew in the field always has the current drawing, without a trip to the trailer, without a printed set that’s a revision behind, without someone remembering to send the updated PDF.
What the Tools You’re Finding Aren’t Built For
Procore Plans is a GC document management system. The GC uploads drawings; the GC’s superintendents, project engineers, and subcontractors access them through Procore. If the GC is running Procore and the sub has a Procore login, the sub’s foreman can access drawings through the GC’s system. What Procore Plans doesn’t do is give the specialty sub his own plan management workflow — uploading his own plan sets, organizing sheets by his own numbering system, pushing updates to his own crew without routing through the GC’s document control process. The GC’s plan viewer is the GC’s tool.
Bluebeam Revu is a desktop PDF markup and review tool used by PMs and engineers in the office. Bluebeam is excellent for redlining drawings, running coordination overlays, and managing document sets from a workstation. It’s not a field plan viewer — it requires a full software license, a capable device, and a setup workflow that doesn’t fit a foreman who needs to pull up the isometric during a five-minute break in the mechanical room.
Generic PDF viewers (Adobe, PDF Expert, Files app) work for pulling up a drawing, but they have no construction context. Sheet naming is whatever the PDF is called. Finding the right sheet means scrolling through a folder. Updates require someone to manually re-send the file. There’s no markup layer tied to the drawing, no pin for the foreman to drop when he finds a conflict, no connection between the drawing and the task the crew is working on.
What a Construction Plan Viewer App Needs to Do
Extract and Name Sheets Automatically
A commercial plan set arrives as a multi-hundred-page PDF. An electrical sub on a four-story office building might receive a single set with architectural, structural, mechanical, and electrical sheets combined — several hundred pages, mixed numbering, architect-assigned sheet titles.
The field crew needs individual sheets, named by discipline and number, findable in under ten seconds. Uploading the full PDF and letting the foreman scroll to page 147 isn’t a field workflow — it’s a recipe for the crew to give up and work from the printed set in the gang box.
A plan viewer that extracts sheets automatically — reads the title block, names each sheet by its drawing number and title, organizes by discipline — turns a 300-page PDF into a searchable library of individual sheets. The fitter looking for the isometric for the fourth-floor mechanical room finds it by searching “M-401” on his phone, not by counting pages.
Push Updates Without Manual Re-Delivery
When the PM uploads a revised sheet, the crew’s phones need to show the current version the next time they open it. Not after someone remembers to re-send the PDF. Not after the foreman checks in at the trailer. Automatically, because the revision was uploaded to the project.
The revision cycle on a commercial job doesn’t stop while the PM is busy. Structural revisions, mechanical coordination changes, electrical updates from the ceiling coordination meeting — each one produces a new sheet that replaces the previous one. If the distribution process is manual (PM sends updated PDF, foreman saves it to his phone, old version gets confused with new version), version control fails at the point of work.
The plan viewer that maintains version history — old revisions accessible but clearly marked superseded, current revision the default — solves the version control problem without relying on anyone remembering to do something.
Markups and Field Notes Tied to the Drawing
When the foreman finds a conflict in the field — the ductwork that’s blocking the conduit run at grid B3, the stub-out location that doesn’t match the plumbing drawing — he needs to mark it on the drawing, not in a text message.
A markup layer tied to the drawing lets the foreman drop a pin at the conflict location, add a note, and attach a photo. The PM on the other end sees the markup on the same sheet, in the same location, with the foreman’s note attached. The conflict documentation that supports a change order starts with a photo and a note at the point of conflict — not with a reconstruction from memory at 5 PM.
Field markups tied to drawings also build the as-built record. The deviations from design that happen during construction — reroutes, field adjustments, coordination compromises — need to be documented somewhere. A markup on the drawing is the right place. A memory at closeout is not.
Works Offline in the Field
Commercial construction crews work in spaces where cell signal is unreliable: mechanical rooms, below-grade spaces, elevator shafts, above ceilings in steel-framed buildings. A plan viewer that requires a live connection fails exactly where the crew is working.
The plan viewer that caches current sheets to the device — available offline, syncing markups and updates when signal returns — works in the mechanical room. The plan viewer that requires a connection to load a sheet sends the foreman to the trailer.
The Workflow That Makes the Printed Set Irrelevant
When the plan viewer works, the printed set in the gang box becomes a backup, not the primary reference. The foreman at the weld checks the isometric on his phone. The fitter at the stub-out confirms the dimension from the current drawing, not the one that was current last Tuesday. The PM uploads a coordination revision and the crew has it before the next morning.
That workflow requires three things to happen without anyone thinking about them: sheets organized and findable on the crew’s phones, revisions pushed without manual re-delivery, and offline availability for the spaces where the work actually happens.
For how plan access fits into the broader field management workflow — task tracking tied to zones, daily reports from field entries, time tracking by cost code — see electrical contractor project management or mechanical contractor software.
See how LogLoon’s plan sheet viewer works for specialty subcontractors, or check the pricing — it’s on the website.