Drawings
Drawing markup shouldn't wait for the office plotter.
The traditional markup loop is a courier route: plot the sheet, red-line it in the trailer, scan it, email it, and hope the person on the other end is looking at the same revision. Every pass around that loop costs a day, and every printed set in circulation is a chance for someone to build from the wrong drawing.
The cost of a stale set
Most drawing problems on site are not drawing problems — they are version problems. A wall gets framed off a superseded sheet, a penetration lands where a revision moved a duct, and the rework bill arrives weeks later. The fix is not more discipline about stamping sets; it is making the current set the only one anyone touches.
Markup is a conversation, not a document
A red-line is really a question or an instruction: can we shift this, watch out for that, confirmed in the field as built. Conversations work better live. When the whole crew can draw, type, and stamp on the same page at the same time — and watch each other's cursors move — the question gets answered in minutes instead of riding a scanner queue. That is what MarkSphere does: real-time markup on shared PDF documents, from any device, including a phone at the work face.
What leaves the room still matters
Live collaboration only helps if the output holds up outside the tool. When a marked-up drawing gets downloaded and sent to an owner or a sub, the markups should be flattened into the PDF itself — visible in any viewer, with no plugin and no missing layers. And every markup should carry who made it and when, because attribution is what turns a scribble into a record.
Start with one active project
You do not need to migrate a drawing archive to change how markup works. Upload the current set for one active project, invite the people who touch it, and run the next revision cycle live. Most teams never plot a markup set again.