Skip to main content
This is 2026.9 documentation. Coverage here is incremental: a page exists only where 2026.9 differs or is newly documented. For any other topic, switch to Current (2026.8 and earlier) in the version selector.
A quantity takeoff and a priced estimate are usually two separate jobs: count elements in a dashboard or export, then take that export somewhere else to apply rates. This page asks for both in one conversation — a takeoff by category, priced against your own rate card, with anything it can’t price flagged instead of guessed.
Speckle Intelligence Chat is available when your workspace plan includes it. On a self-hosted server, it is available only on Speckle Enterprise Server. For deployment setup, see Enterprise license — Intelligence.
This is the Chat-driven route. For a dashboard you can pin, share, and keep open on a screen instead of asking for it each time, build a quantity takeoff dashboard instead — the two approaches read the same published data.

What this workflow does

  • Take off — count and total elements by category, level, or any other property, without building the breakdown in a dashboard first.
  • Price — apply your own unit rates and cost codes instead of a generic estimate.
  • Flag gaps — call out anything with no matching rate, rather than inventing a number.
  • Reuse — pin the rate card once so every future takeoff on any project uses this year’s prices.

Walkthrough

1

Pin your rate card as Knowledge

In workspace Settings → Skills, create a skill and pin your rate card (a spreadsheet, or a live warehouse table if finance keeps it there) as Knowledge. Write the unit rates and cost codes into the skill’s instructions in your own language — elemental, package, or whatever your commercial team already calls them. See Reuse organisation playbooks with Intelligence skills.
2

Ask for the takeoff

In Chat, arm the skill with /skill-name and ask in plain language:
Give me a material takeoff, priced against our rate card.
Intelligence reads quantities from the published model — the same connected, queryable data it uses for any other question — and matches each line against the pinned rate card.
3

Read the breakdown

The reply groups quantities the way your skill’s instructions say to — by category, level, or package — with each line priced. Anything without a matching rate is called out separately instead of estimated, so a missing row is visible rather than silently averaged away.
4

Ask a what-if question

Keep going in the same conversation:
What’s the impact on cost if steel goes up by 15%?
Intelligence recalculates from the same quantities and the same pinned rates, so the answer reflects your actual take-off, not a generic assumption.

Share it beyond the chat

Save the conversation as a Report if you want a shareable artefact — the takeoff and its pricing stay live against the bound version rather than frozen at the moment you asked. For a takeoff someone will keep open and re-filter by level or category on a screen, use the dashboard route in Run a quantity takeoff instead; Element table there also exports straight to CSV.

FAQ

Only if you say so. Put your unit and rounding conventions in the skill’s instructions — Intelligence does not know your commercial team’s conventions unless you tell it once, in the skill.
It gets flagged as unmatched rather than priced by guesswork. Write that behaviour into the skill explicitly (see the cost, carbon, and quantities skill catalogue) if you want the flag to use a specific phrase your commercial team recognises.
Yes. Like every other Intelligence query, a takeoff needs a version in the new data format. Versions still in the old format cannot be queried. See Speckle’s data model is changing.
Yes — just ask for the takeoff without pricing, for example “give me a material takeoff” or “give me a report of quantities by category and level.” Pricing only kicks in once you’ve pinned a rate card in a skill.

See also

Last modified on September 21, 2026