On 9 September 2026 we run an Archicad Powersession we have been quietly looking forward to: RaumCreator. It is a short, hands-on morning about the one modelling act every office repeats a thousand times and almost never automates — placing, naming and stamping Räume. We built the session because the room is where a plan turns into a document, and the room is where documents most often drift.

Here is the thing about Archicad that the newcomers in our atelier always underestimate. This is the first BIM software — 1984, out of Hungary, Gábor Bojár’s physicist’s instinct that the processor should do the boring work elegantly. Forty-two years later the boring work is still there, and it is still zones: which polygon is a room, what it is called, where its stamp sits at 1:100 versus 1:50. The system beneath RaumCreator is that a zone in Archicad is data first and a picture second — the same principle that lets the Grasshopper–Archicad connection, now in its tenth year, treat geometry as something you compute rather than draw. Once you treat the room that way, the batch becomes trivial.

←TODAY: In 2026 an architect still hand-nudges hundreds of room stamps before a permit deadline. →3012: In the Zurich-3012 studio the room is a queryable object; nobody drags a label ever again. Fulcrum: The stamp was always data pretending to be a drawing — see both directions and you stop dragging.

That conviction is why PAZ has shipped tools around exactly this seam. Our Raumstempelfix add-on already aligns hundreds of room stamps at once with scale-dependent placement across 1:200, 1:100, 1:50 and 1:20 — the sibling of what RaumCreator teaches by hand. PAZ has covered this thread before; the Powersession is where you learn the logic underneath the button, not just the button.

Atelier: For a Büro adopting AI-assisted BIM this year, the honest trade-off is real — batch automation is only as safe as your zone naming discipline; a mislabelled room propagates faster than a manual one. Your Monday move: pick one live project and run a read-only zone audit (list every Zone and its name) before you let any tool touch stamps — you want the mess visible before it is automated.

Hack: Read your model’s rooms before you touch a single one. Archicad ships a Python API; three lines get you a truthful inventory of every zone, which is the first step of any RaumCreator workflow — and the audit the Atelier just asked for.

from archicad import ACConnection
acc = ACConnection.connect()
zones = acc.commands.GetElementsByType("Zone")
print(f"{len(zones)} Räume im Modell")

Run that against your worst project and the number alone will tell you whether the problem is missing zones or duplicated names. This is the same GDL-and-Python craft the Archicad Bootcamp (PARAM-O, Grasshopper, GDL and Python, 49 CHF) and our Building System Specialist Title lean on — the discipline of talking to the model instead of clicking at it.

Who is the morning for? Archicad power users drowning in repetitive documentation, BIM coordinators enforcing office standards, and anyone who watched our 39 certified Building System Specialists build their own tools and thought I want to stop drawing element by element. It is not a lecture. You leave with a workflow.

If you have read our concept panels, you know the deeper argument: Archicad’s real engineering claim is the coupled model. From Archicad 24 onward the software derives a Structural Analytical Model straight from the physical one and exports it through the Structural Analytical Format (SAF) to solvers like SCIA Engineer or ETABS — the physical element and its data staying one truth, not two. RaumCreator is that same principle at documentation scale: the physical zone and its stamp, coupled. The session details and sign-up live on our Powersession page. Bring one project you dread stamping — that is the one we will fix together.