Every version, with its cause
Issue a revision and BuildCycle recognizes which sheets it revises and advances the version — with what caused it, an RFI or a re-issue, right on the label.
An RFI got answered, a revision got issued — and the old drawing is still the one taped to the wall. BuildCycle makes the current set unmistakable and keeps every version on the record.
No renaming files, no filing sheets into folders. The set organizes itself.
One PDF, hundreds of sheets, hundreds of megabytes — fine. BuildCycle splits it into individual sheets automatically, reading sheet numbers and titles off the title blocks and filing every discipline.
The split shows its work: anything uncertain is flagged for a human look — a typo’d bookmark, a sheet the index never listed. You confirm or correct in one screen; most sheets need nothing.
Sheets grouped by discipline, searchable, each opening instantly — because a 2MB sheet loads and a 400MB monolith doesn’t. Markers, photos, and observations pin to the sheet itself.
An issued set is a legal document. Nothing here ever deletes one — new issues advance the version, old sheets stay on the record.
Issue a revision and BuildCycle recognizes which sheets it revises and advances the version — with what caused it, an RFI or a re-issue, right on the label.
Observations and punch markers stay pinned to the version they were placed on. The record shows what the field actually saw — not a retrofit.
Open a superseded sheet and it says so — watermarked, with one tap to the current version. Nobody builds off the wrong drawing by accident.
This is where document management stops being a filing cabinet — the drawings are part of the workflow record.
When an RFI comes in, it pins to the sheet version it was asked against. Two revisions later, the record still shows exactly what the question was about.
Your consultant stages the revised sheets with their response; you approve, and the versions advance — the answer and the drawing it changed are one record, not two emails.
Response, attachments, and revised sheets go out together — by email on a clean retrieval page (no login to chase), or as a formal Procore reply when the contractor runs it.
Drive, Dropbox, and the report apps hold your drawings. They don’t manage them.
See the field workflow too: Field reports & punch lists · Full pricing
What document management means when the CA record depends on it.
For a design firm in construction administration, it means keeping the drawing set organized, current, and on the record: individual sheets instead of one giant PDF, tracked versions as revisions are issued, and a clear answer to “which sheet was current when this question was asked.” BuildCycle does this automatically and ties the documents into the CA workflows — RFIs, field reports, and punch lists all reference the managed set.
Yes. When a revision is issued — as a re-upload, added sheets, or drawings attached to an RFI response — BuildCycle recognizes which sheets it revises and advances the version. Superseded sheets stay on the record with a watermark, their markers and history intact, and every RFI stays pinned to the sheet version it was asked against.
Yes — in one motion. Your consultant stages the revised sheets with their response, you approve, and the new versions go out with the answer: to the contractor by email, and as a formal reply in Procore when the GC runs it. The sheet versions advance automatically; nobody re-files anything.
Hundreds of sheets and hundreds of megabytes are fine — that’s the point. BuildCycle splits the monolith into individual sheets and compresses each one, so a set that took minutes to open becomes sheets that load instantly on a phone in the field.
You’ll land in a live CA project — real RFIs, real numbers. One field, no card. We save your spot so you can come back to it.