There is a line in PAZ’s own concept library we keep coming back to. In the Generative Architecture — En Ingenieria panel we describe a ladder of autonomy that starts at L0 — the engineer in full control, redrawing every element by hand — and climbs toward a practice where, in the panel’s words, “the human role migrates from author to curator.” Most Swiss offices meet that ladder every month in the least glamorous document they produce: the Wohnungsspiegel.

The apartment schedule — unit number, Zimmer count, net area per room, orientation, total m² — is not a drawing. It is a query over the building. And yet in most ateliers it is still typed, re-typed, and quietly de-synced from the model every time a wall moves. On 16 September 2026 we are running an Archicad Powersession on exactly this: how to make the Wohnungsspiegel fall out of the model instead of being maintained beside it.

←TODAY: In 2026 most Swiss apartment schedules are still hand-kept spreadsheets that drift from the model within a week. →3012: In the Zurich-3012 city, no number a human types twice survives — every schedule is a live view onto one source of truth. Fulcrum: The gap was never the tool — Archicad has queried its own Zones for decades — it was the habit of letting the query, not the typist, own the truth.

None of this is new capability. Archicad shipped as the first BIM platform in 1984, out of Hungary, built by the physicist Gábor Bojár — facts our own Archicad Freebies page likes to repeat, alongside the reminder that the Grasshopper–Archicad connection is now around ten years old. The point of that lineage: the model has been a database, not a stack of sheets, since before most of today’s architects were born. A Zone carries its area and room data; an Interactive Schedule reads that data back as a table that updates when the geometry does. The Wohnungsspiegel is that schedule, filtered and grouped.

On a working desk the pain is concrete. A late layout change moves three partitions; the printed Wohnungsspiegel is now wrong; someone re-measures by hand under Abgabe pressure and a rounding error walks into the Baueingabe. The session’s whole argument is that the fix is structural, not a matter of diligence: stop maintaining the table, define the query once.

Atelier: For a Büro adopting AI and automation, the schedule is the ideal first target — low risk, high repetition, instantly checkable. It is also where our own PAZ-BOX and PAZGPT add-ons earn their keep, letting you interrogate the Archicad model in plain language instead of hunting through menus. Your one Monday move: take your current live project, build a single Interactive Schedule that lists every Zone with its area and room count, and delete the hand-typed apartment table from your issue set. If the schedule can carry it, the spreadsheet was always a liability.

Hack: Read your apartment schedule as a query, not a table. The clearest way to see what Archicad’s Interactive Schedule is actually doing is to write the same intent in SQL — export your Zones to a CSV, and the Wohnungsspiegel is one grouping away:

SELECT apartment, COUNT(*) AS rooms, ROUND(SUM(area_m2), 1) AS total_m2
FROM zones
GROUP BY apartment
ORDER BY apartment;

That is the whole Wohnungsspiegel: one row per apartment, rooms counted, area summed, sorted. Once you can see it as a GROUP BY, the Interactive Schedule stops being a mystery panel and becomes a saved query you trust — and the day you outgrow the UI, the same logic moves into GDL, Python, or the Grasshopper connection unchanged.

The tools keep moving under us — the Graphisoft Community forum is already trailing Archicad 30, due to be shown live at the ATS Convention in Graz on 8 October 2026 — but the habit outlives the version number. Bring one real project to the session and leave with a Wohnungsspiegel that maintains itself. The full brief and sign-up sit on the Archicad Powersession – Wohnungsspiegel page.