Back to the blogplan management

    Plan Management on Site: End the Version Chaos

    AI-generated image: Plan Management on Site: End the Version Chaos

    Plan management on the construction site: how a plan register, indexing, release status and distribution keep crews from building to outdated plans.

    Example: The concrete crew formed the wall to index C. Index D had been valid for two weeks because an opening for building services was moved. The new drawing sat as an email attachment in the office inbox, while the old one hung on site. The result is chiseling, a dispute over costs and delay. Sound plan management on the construction site makes sure exactly one revision is valid and everyone knows it.

    Why plan revisions get lost on site

    A plan circulation process is the defined path of a drawing from creation through review and release to distribution and the withdrawal of outdated revisions. Without it, version chaos follows. The causes are rarely bad intent. They are many parties, parallel changes and changing distribution lists: the architect, several specialist designers, site supervision and contractors all work on the same building at the same time, and every change affects at least one other trade.

    Legally, the principle is clear and the individual case is delicate. Under German construction contract rules (VOB/B, the standard terms for construction work), the client must hand over the documents needed for execution in good time (§ 3 Abs. 1 VOB/B). If the work deviates from the agreed quality, this is generally a defect under § 633 Abs. 2 BGB, the German Civil Code. Anyone who builds to an outdated plan therefore often creates a defect that only shows up at acceptance or later. Who is responsible depends on questions that are hard to answer without evidence: Was the new revision distributed? To whom? When? Did the contractor receive it? This article is not legal advice. It shows which records you need.

    The building blocks of a clean plan circulation process

    Plan register

    The plan register is the list of all drawings in a project with drawing number, title, author, current index, date and status. One row per drawing, one register per project, one responsible person. The register is the only reference: what it does not list as current is not valid.

    Index and change note

    The index is the letter or number that identifies the revision of a drawing, such as A, B, C. Every substantive change creates a new index. Silent corrections to an old revision are the classic mistake. The change note states in the title block what changed compared with the previous index and marks the spot on the drawing, for example with a revision cloud. This tells the crews where to look, so they do not have to compare the whole drawing again.

    Release status

    Every drawing carries a status. Three values are common:

    • Preliminary issue: for coordination, explicitly not for execution.
    • Released for execution: the valid revision, the only one that may be built.
    • Withdrawn: outdated, must no longer be used.

    A release records who grants it, when, and after which review. For specialist designs such as structure, building services, fire protection or landscaping, this means the architect releases only once the contributions are coordinated. Shop and installation drawings from contractors also need a defined review and release. Who handles that belongs in the contract.

    Distribution, proof of receipt and withdrawal

    The distribution list defines who receives which drawing in which form, separated by trade, company and contact person. A drawing that simply goes “to everyone” reaches no one in a binding way.

    This is how an orderly plan change works:

    • Step 1: The design team assigns the new index, enters the change note and sets the status to “released for execution”.
    • Step 2: The plan register is updated before the drawing is sent.
    • Step 3: The drawing goes to the defined distribution list, with a note on the superseded index.
    • Step 4: Each recipient confirms receipt with name and date. The proof of receipt is the acknowledgment that a specific revision reached a specific person.
    • Step 5: The previous revision is withdrawn. Paper copies are collected or clearly marked “void”, and digital folders are replaced.
    • Step 6: At the next site walk, the site supervisor compares the drawings on site with the plan register and records the result in the site walk report.

    Withdrawal is the step that is missing most often. Without it, the old and the new revision lie side by side in the site container, and whichever is closer at hand gets built.

    Responsibilities: architect, specialist designers, contractors

    The project phases of HOAI 2021, the German fee scale for architects and engineers, help with classification. In phase 5, the execution design, the drawings are produced that the building is built from. In phase 8, the construction supervision, the site supervisor checks that the execution matches these drawings (Anlage 10 to § 34 HOAI 2021, service profile for buildings and interiors). An overview of all nine phases is in the article How does a construction project actually work?.

    The HOAI describes services, not the plan circulation process in detail. Who keeps the plan register, who releases and who distributes should therefore be settled in the contract or a project handbook. A common split looks like this:

    • Architect or lead designer: keeps the plan register, coordinates the revisions of the specialist designers, grants the release and distributes.
    • Specialist designers: deliver drawings with index and change note and report changes that affect other trades.
    • Contractors: check the drawing against the plan register before starting work, keep only released revisions on hand and report discrepancies.

    If a contractor has doubts about a drawing, the contractor must state them in writing (§ 4 Abs. 3 VOB/B, a notice of concerns). Only those who did so are generally free of liability for a defect caused by the client’s instructions or specification (§ 13 Abs. 3 VOB/B). How to word the notice in time and with proof is covered in the article Notice of concerns under VOB/B.

    Typical mistakes in daily work

    • Drawings as email attachments: There is no fixed distribution list and no control over who read the attachment. New revisions do not reach everyone, old ones stay in inboxes.
    • Local copies: Files on laptops, phones and USB sticks age unnoticed. Nobody knows which copy is current.
    • Notes on paper drawings: Handwritten changes without an index do not flow back into the design. A verbal instruction written on the drawing is not a controlled plan change.
    • File names like “final_new_2”: They replace neither index nor status.
    • Preliminary issues without a label: An intermediate revision without a clear stamp quickly becomes the construction drawing.
    • Release without a record: Who released a drawing cannot be shown later.

    For evidence, what counts is which revision applied on which day on site. Record the plan revision in the site diary, and for significant work add a photo of the plan stamp. What a site diary should contain and what evidentiary value it has is explained in the article Site diary requirements: content and evidentiary value.

    Checklist

    • Keep one plan register per project with one responsible person.
    • Assign a new index for every substantive change, never a silent correction.
    • Enter a change note in the title block and mark the change on the drawing.
    • Label every drawing with a status: preliminary issue, released for execution or withdrawn.
    • Define a distribution list for each drawing, separated by trade, company and contact person.
    • Have the receipt of each new revision confirmed with name and date.
    • Withdraw the previous revision actively: collect it, mark it “void”, replace the folder.
    • At every site walk, compare the drawings on site with the plan register and record the result.
    • Put responsibilities for keeping the register, release and distribution in writing in the contract or project handbook.

    Frequently asked questions

    What is the difference between an index and a file version?

    The index identifies a formally reviewed drawing revision and appears in the title block and in the plan register. File versions are technical intermediate states that can arise every time a file is saved. Usually only a reviewed and released revision receives a new index.

    May a contractor build from a preliminary issue?

    Generally no. A preliminary issue is meant for coordination and not for execution. Work follows the revision marked “released for execution”. Exceptions, for example for trades that start early, should be recorded in writing.

    Who is responsible for distributing the drawings?

    That follows from the contract. Often the architect handles coordination and distribution as part of the execution design and the construction supervision (phases 5 and 8), and in some projects a project management firm does. Without a clear rule, responsibility is hard to prove in a dispute.

    How long should drawings and the plan register be kept?

    At least as long as claims for defects can still become time-barred. For buildings, the limitation period under the German Civil Code is generally five years (§ 634a Abs. 1 Nr. 2 BGB), and four years under VOB/B if agreed (§ 13 Abs. 4 VOB/B). Also check contractual retention obligations.

    Conclusion

    Plan management on the construction site is less a question of technology than of rules: one register, a new index for every change, a status, a distribution list, proof of receipt and consistent withdrawal. Those who define these steps and check them at every site walk build to the right revision and can document it later.

    Structify, the software for digital construction documentation, connects office and site in one project: site walks and reports, defect management with locations marked on the plan, and site diary entries with photos, deadlines and responsibilities. You invite external parties with a guest link. If you would like to see how this looks on your project, book a short online demo.