Calculations and formulas in Schedules

[Erik Bjornhage]

So, this is perhaps a bump from previous topics but the full functionality has not yet been solved.

My wish is for spreadsheet style calculations in Schedules.

As a simple example:

A big residential project - with a number of different apartment types (1 bed, 2 bed, 3 bed etc.) which is of course a part of a total number of apartments. Currently we cannot list these apartments and have the schedule display their repective percentages in relation to the total. This would be extremely beneficial to general project management and how and what we can deliver to clients.

[Gonzalo]

First of all, it's very interesting to see others involved in this topic and the solutions they've come up with. One method I've been exploring to have properties that come from an external source or can be the result of a mathematical operation is through tAPIr and Grasshopper. With these tools, you can input data into Archicad properties without having to do it manually, but it involves using Rhino and Grasshopper to achieve it.

I've been able to talk with several people interested in this topic, and the community behind this API and its development is very active on Discord. Some of us have further explored the use of Python and C++ within Archicad, but almost everyone concludes that developing an object with GDL to supplement what Archicad can't do is the way to go. In this case, it requires many hours of planning for a long workaround to achieve something very simple.

https://www.food4rhino.com/en/app/tapir

[Pato99]

@Gonzalo I don't know how you're using tAPIr currently. 

This is what it should look like 

And this is what it is now in AC 28

It's still in very heavy development. 

I was using it for a short while but since GS has dropped support for Rhino 6 in AC 28 I'm sort of back to square one needing new functionality for the default GH plugin but old functionality of the tAPIr plugin.

[Miles Smith]

Hello, everyone! Thank you all for the lively discussion and ideation in this thread. There are a lot of good thoughts in here that are very helpful to Graphisoft. We have been working for several release cycles to continually improve schedules, and are excited to continue to investigate the implementation of Calculations and Formulas in Schedules. As such, the status of this wish is being move to "On the Roadmap".

[thesleepofreason]

@Miles Smith Could you make a link to the roadmap item for reference.

[Angel Berruezo]

We really need this. Please don’t forget to include some IF...THEN functionality with access to object properties — I’m specifically thinking of room area reporting.

[TaniavH]

The ability to show subtotals within schedules for specific data / the ability to use calculation in schedules without having to rely on expressions.

[Moderator: This wish is already on the Roadmap, so this post was merged into the existing wish, along with its Votes.]

[nonpertutti]

I believe the real key to unlocking advanced calculations in Schedules is not just adding formulas to tables but introducing user‑defined global variables in Archicad.

With a simple Variable Manager, users could:

• Define project‑wide variables (e.g., planning limits, roof pitch, derived areas),
• Use them in Schedules, texts, labels, and expressions,
• Optionally drive element parameters (e.g., a single slope value updating multiple beams).

To make this practical and accessible, Archicad could include basic text and spreadsheet tools where these variables can be imported, calculated, and exported. The existing, well‑known workflows in Archicad would stay exactly the same—this would be an optional layer of automation for those who want it.

I’ve described this more fully in a related wishlist request here: https://community.graphisoft.com/t5/Wishlist/User-Defined-and-Calculated-Global-Variables-for-Model-...

[nonpertutti]

I can not edit my comment, so I need to add a new one to be more clear: I an suggesting Model Derived Variables, self updating together and defined by user picking from Schedules where expressions may or may not be used (either single element or a sum). Once we have this, some user input Variables (or we could call them Constants if you like: eg. law requirements, project constants like a roof slope) would be obviously simple to include and equally usefull.

[Kian - Evoke]

It would be really useful if Archicad schedules supported simple conditional statements that can evaluate element parameters and return specified text or values. The aim is to let schedules produce compliance notes, spec call-outs, or automatic classifications without manual checking or duplicate properties.

Why this matters
Right now, schedules can list and format parameters, but they can’t react to them. That means we still have to review items one-by-one for things like Part K, Part M, fire strategy, glazing safety zones, or internal office standards. Conditional logic would reduce coordination risk and speed up spec prep.

Core capability
Add fields in schedules that allow:

• IF / ELSE IF / ELSE logic

• Boolean operators (>, <, ≥, ≤, =, ≠)

• AND / OR

• Works on native and custom properties (doors, windows, walls, slabs, spaces, zones, objects, etc.)

• Returns text strings or numeric outputs

• Optional colour/highlight output for exceptions

Example uses

1. Glazing safety (your example)

   • IF Window Sill Height < 800mm
     THEN “Provide toughened or laminated safety glazing (critical location)”
     ELSE “Standard glazing acceptable”

2. Part M door clear opening

   • IF Door Clear Width < 775mm
     THEN “Non-compliant with Part M – revise door size/leaf”
     ELSE “Compliant with Part M clear opening”

3. Guarding requirement at level changes

   • IF Change in Level > 600mm AND Edge Type = “Open”
     THEN “Guarding required to min 1100mm per Part K”
     ELSE “No guarding required”

4. Fire door identification

   • IF Door Fire Rating ≥ 30min
     THEN “FD30S – self-closing, smoke seals required”
     ELSE “Non-fire door”

5. Means of escape travel distance flag

   • IF Space Travel Distance > 18m (resi)
     THEN “Travel distance exceeds guidance – review layout”
     ELSE “Within guidance”

6. Window opening restrictors

   • IF Window Sill Height < 1100mm AND Space Use = “Bedroom”
     THEN “Provide restrictor / limit opening for safety”
     ELSE “Restrictor not required”

7. Acoustic spec triggers

   • IF Wall Type = “Party Wall”
     THEN “Rw + Ctr ≥ 45 dB target (confirm build-up)”
     ELSE “Standard acoustic target applies”

8. Area efficiency tagging

   • IF Net Internal Area / Gross Internal Area < 0.75
     THEN “Efficiency below target – review cores/circulation”
     ELSE “Efficiency on target”

9. Finish spec by room type

   • IF Zone Category = “Wet Area”
     THEN “Slip-resistant flooring + tanking required”
     ELSE “Standard flooring build-up”

10. Structural thickness warnings

    • IF Slab Thickness < 200mm AND Span > 5m
      THEN “Check structural adequacy – slab likely undersized”
      ELSE “Thickness ok (subject to engineer)”

What good looks like

• A “Conditional Field” type in schedules with a small formula editor (like Excel-lite).

• Clear readable syntax and a dropdown list of available properties.

• Error checking (“unknown property”, “type mismatch”, etc.).

• Ability to save conditions as templates for office standards.
  
  

It would be great if we could apply this to other properties too such as texture or element parameters.