Report a DIN 276 cost plan to the client

Open the conceptual estimate and put down the first cost frame: gross floor area, quality level and region give a cost per square metre, and the total comes back split across the elemental categories rather than as one number.

Mengapa: The client approves a figure long before there is a bill to price. Holding that early frame in the project is what lets the later, finer plan be read against something instead of arriving as a fresh number nobody recognises.

Work down the bill and give each position its DIN 276 code in the classification column: 300 for the Baukonstruktionen, 400 for the Technische Anlagen, 500 for the Aussenanlagen, down to the three-digit group where the work really sits.

Mengapa: The cost group is what turns a flat list of positions into a plan that can be read by group. A position left uncoded is money that shows up under no heading at all when the client asks what a group contains.

Generate the cost spine from the bill. Each coded position lands on a control account for its cost group, so the plan appears as a tree of Kostengruppen with the totals rolled up from the positions underneath and every line still reachable.

Mengapa: This is the elemental plan itself, and it is generated from the coded positions rather than typed next to them. That is what stops a group total and the detail behind it from drifting apart as the design moves on.

Run validation across the bill and look for positions carrying no cost group at all and for codes that sit outside the group the work belongs to, then go back to the line and correct them.

Mengapa: A single uncoded position makes a group total wrong while the grand total still adds up, so the error survives every check that looks only at the bottom line. Finding it now is cheaper than explaining it in a review.

Go through the spine one cost group at a time and read the estimate against the budget recorded for it, so you can name which Kostengruppe carries the movement and how much of it, before you open the drill-down on the group that moved most.

Mengapa: The budget question is almost never about the total, it is about which group moved and why. Having the answer per group turns a defensive meeting into a short one.

Record the basis behind the numbers: which design state the plan was built on, what each cost group includes and excludes, and which figures are still an allowance rather than a priced quantity.

Mengapa: A cost plan is only defensible with its assumptions attached. Written down while you build it, they answer a challenge months later; reconstructed after the challenge, the same sentences read as an excuse.

Export the plan grouped by Kostengruppe, with the group totals, the variance against the budget and the basis alongside them, in the structure the client and their auditor already read.

Mengapa: A client who receives the plan in the structure they work in every day can approve it. One who has to re-sort a flat total into cost groups first will send it back, and the next meeting is about the format instead of the money.