Skip to main content
assembl
How it works

How assembl works.

Specialist agents do the first draft. A person signs it off. You get a record of how it was made. Here’s what that looks like.

How a pack works in your business

Install once. Run every day. Show the proof.

Day 1Install.

A shareable link or one line of code. Your team opens the workflow they need from the

kete/ˈkɛteɪ/ Kete is the traditional Māori word for a hand-woven carrying basket. Typically made from indigenous plants like harakeke (New Zealand flax), these baskets are culturally significant taonga (treasures) that symbolize the carrying of knowledge, wisdom, and life-sustaining resources.
. No training week.

DailyRun.

Someone drafts a job (RFI, allergen report, customs entry, board minutes). The agent does the first pass. Your named reviewer signs it off. It goes out.

QuarterlyShow.

Every output sealed in an evidence pack. File it. Forward to your auditor. Footnote for the board.

1

Agents draft it.

Bring a job your team does by hand — an RFI, an allergen report, a customs entry. The agent for that work writes the first draft in seconds, trained on your industry’s rules and your way of doing things.

2

You review and sign off.

The draft lands with a named person who accepts, edits, or rejects it. Nothing leaves your team — nothing sends, publishes, or gets lodged — without that sign-off.

3

You get the evidence pack.

Every signed output comes with its receipt: the sources used, the assumptions made, what changed in review, and who approved it. One file, dated and filed, ready when someone asks.

Built for NZ. Each pack has NZ law, council and sector rules built in from the start.