assembllab Simulated · fictional plan and rates

Inside the lab / trades · construction · plan to quote

Take off the plan.
Check it against the Code.
A person sends the quote.

A plan-to-quote desk for a small NZ builder. An agent finds the rooms, measures, asks the consent question, lists the Building Code clauses to check and the defects to look for, prices from your rates with waste, P&G, margin and GST, and drafts a quote. A named person confirms the scale, chooses the provisional sums and approves every quote and variation.

A101 · Floor planloading…
Loading the sheet…

Simulated · fictional plan and rates

Checks · consent, Building Code, defects

Before the price, the checks.

Every measured condition wakes the clauses to check and the defects to look for. The agent proposes; a person decides which risks become provisional sums. Illustrative — not a compliance determination. The council and a licensed building practitioner decide; the links go to MBIE's own pages.

Latest published

Fetching MBIE determinations and Stats NZ building consents…
MBIE determinations
Stats NZ building consents

Fetched by the lab's server from Building CodeHub (MBIE's open copy of the determinations) and Stats NZ, cached for six hours. If a source doesn't answer, the chip says Last known with the date it was captured. Context, not advice.

Does it need a building consent?

The Schedule 1 questions for what is in scope on this sheet, with the lab's likely answer. Building Act 2004, Schedule 1.

Illustrative Work that doesn't need a consent · building.govt.nz

NZ Building Code checks

For each measured element: the clause, the acceptable solution it is usually read against, and one line on what to check on site.

H1 insulation schedule by climate zone Illustrative

Minimum construction R-values for housing under the schedule method, as the lab read H1/AS1 5th edition. Confirm the current amendment at building.govt.nz.

Defects and risk register

Common NZ defects for the element types in scope, by severity, with the photo the agent asks for on site. Tick the ones to hold as a provisional sum; the quote maths picks them up.

IllustrativeProvisional sums are fictional allowances, charged at cost with the record.

Quote maths · yours to edit

Price it from your rates.

Material and labour per unit, NZD, metric: m², lm, ea. Labour becomes hours at each trade's hourly rate; materials carry waste by trade; P&G sits on cost, margin on cost plus P&G; provisional sums are listed on their own; GST at 15% is charged on the whole. Timber sizes are NZS 3604 names used as labels only. Indicative only · not a quote.

TradeConditionUnitMaterialLabour
Trade$ / hourWaste %Hours

Settings

Illustrative NZ figures. Everything resets on reload; nothing is stored.

Quote build-up Indicative only · not a quote

Measure something, or ask the agent, and the trades fill in here.

Every line is drawn quantity × factor × rate. Hours are labour cost ÷ the trade's hourly rate.

Variations · payment claims · site diary

When the job changes, the record changes with it.

A variation is a change the client asks for after the quote is approved. The agent re-measures what it adds, re-runs the quote maths and shows the difference; the same named person approves it, and the receipt chains onto the quote's. A progress payment claim follows the Construction Contracts Act 2002: the section 20 requirements as a checklist, the due date and payment-schedule deadline in working days, and retentions as the 2023 amendments treat them. The site diary is the stub of a record that follows: who decided what, when, and which photos were taken.

Variation

Approve a quote on the desk first. Then raise the variation from the receipt, or here.

Payment claim · CCA 2002 Illustrative · not legal advice

Approve a quote on the desk first. Then build a progress payment claim against it here.

Site diary

  1. Decisions, photo checks and sends land here as the desk works. Nothing is stored.

Agent-ready · the same ten tools over MCP

A builder's own assistant can call the same desk.

The page and the endpoint share one geometry, one condition library and one NZ reference file, so an assistant (Claude, ChatGPT, anything that speaks MCP) measures the same plan, asks the same consent questions and runs the same quote maths the person sees. Stateless and Simulated: the demo sheets only, and drafting never sends anything.

Endpoint

POST https://assembl-lab.vercel.app/api/takeoff/

Streamable HTTP, JSON responses, no sessions, no auth. initialize, tools/list, tools/call, resources/read (takeoff://plans, takeoff://conditions, takeoff://nz-code, takeoff://sheets).

    Try it, live

    Lists the tools, then asks find_rooms, code_checks and quote for A101. Read-only: a request, a record, a hash. find_rooms also takes labels read off any drawing.

    {"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"code_checks","arguments":{"sheet":"A101","lines":[{"conditionId":"floor-tiles","qty":30.7}]}}}

    What stays with people

    • The scale. Tools default to the sheet's nominal scale and say so; a person confirms it before measurements count.
    • The rates. Nothing proposes a price. The builder's own sheet is the only source; the defaults are labelled illustrative.
    • The risks. defect_register proposes; a named person picks which become provisional sums.
    • The quote and every variation. draft_bid and variation return drafts at authority act with approval. A named person sends, changes or withdraws, and each decision is a hashed receipt chained to the last.
    • Compliance. consent_check and code_checks point at MBIE's pages. The council decides; the tool never does.
    • Payment claims. payment_claim drafts against the approved quote with the s 20 checklist and the working-day deadlines. A person serves it; nothing here is legal advice.

    Pattern: enquiry → agent steps with tool calls and records → a named person approves → chained receipt. Built clean-room by the assembl lab; no third-party takeoff code or assets.