Build from the current set. Every time.
One register per project, every sheet at its current revision, issued to the people who need it with a receipt to prove it landed. The trail behind it is the one that settles the argument later.
One live project, five seats, three days
- A-101Ground floor planRev CApproved
- A-102First floor planRev BIn review
- S-210Foundation layoutRev DApproved
- M-301HVAC distributionRev ADraft
- E-405Power reticulationRev BApproved
Somebody built it from a sheet that stopped being current three weeks ago.
Drawings scatter across inboxes, drives and site WhatsApp groups. A revision goes out and someone misses it, work gets done against the old sheet, and the cost of putting it right is argued over for months afterwards.
Three things construction teams notice first
One current set, enforced
Every sheet sits at a marked current revision. Superseded versions stay in the history where they belong, not in somebody's downloads folder.
Issued, received, acknowledged
Transmittals record who you sent it to and when they opened it. The receipt is the answer to 'we never got that drawing'.
Queries that stop going quiet
Raise a site query against the exact sheet, mark up the clash, and the system holds whose move it is until somebody answers.
Three steps, start to finish.
Register the set
Drag in the drawing pack. Sheet numbers, revisions and disciplines are read off the files and the register opens ready to work.
Review and issue
Mark up, compare two revisions side by side, get the approval logged, then transmit to the distribution list in one action.
Close out with the trail
Export the as-built set and the full history as one package on the day you finish, not three weeks into the next job.
Everything a project needs, in one place
No second system for the parts that did not fit the first one.
Subcontractors, consultants and the client can be invited to a single project, and that is all they ever reach.
More of the platform.
Document control
Register, version, issue and mark up every document on one accountable record, so the whole team works from the version that is actually current.
ExploreReview and markup
Comment on the document itself, compare two revisions side by side, sign in the browser, and keep the whole exchange attached to the file it is about.
ExploreBids and proposals
Build the pack, track the deadline, review what came back and award it, with every version and every decision recorded as you go.
ExploreWhat people ask first
Yes. Upload the pack and the reference, revision and title are picked off the files. Anything it gets wrong you fix once, in a review step, before it lands in the register.
Yes, and only where you put them. Invite them to a single project, with an expiry date if the appointment ends.
PDFs, drawings and 3D models open in the browser, ready to mark up and sign. Nobody needs a seat in a desktop package to comment on a sheet.
Put one live project on it this week.
Three days free, five seats, every module. Take the job with the messiest drawing history and see what it looks like straight.
3 days · 5 seats · every module · no card