Here is the blank template. Copy it, fill in five sections, and you have a reusable workflow for one job in your business. Keep it in a document, not a chat window, so you can reuse it next week without retyping anything.
Key takeaways
- Five sections, filled in once per job type.
- Standing material goes in permanently. Job material gets pasted in each run.
- Keep it in a document, a note or a saved project. A chat history is not a Stack.
- Test it against a job you already completed before you trust it on a live one.
- One Stack per job. The second one takes minutes because most layers carry across.
The template
CONTEXT
What we do:
Where we operate:
Who is reading this:
What they already know:
Where we are in the job:
TASK
Produce:
SOURCE
Standing material attached:
- price list
- inclusions and exclusions
- two examples of this document I was happy with
Job material for this run:
-
RULES
- If information is missing, list it at the top and do not assume it.
- Use only the figures and prices supplied.
- Do not promise dates, timelines or outcomes.
- Keep GST separate and state it.
- Keep the scope to our listed services.
- [your trade-specific limits]
OUTPUT
Sections in order:
Must appear:
Must stay separate:
Length:
Leave out:
Filled in, on a roofing quote
CONTEXT
What we do: residential roof repairs and re-roofs
Where we operate: Sunshine Coast and northern Brisbane
Who is reading this: a homeowner who has just had us on the roof
What they already know: there is a leak, not what it costs to fix
Where we are in the job: post-inspection, pre-quote
TASK
Produce: a quote draft from the site notes below
SOURCE
Standing: current price list, standard inclusions and exclusions, two past quotes
Job material: site notes and measurements from 14 September
RULES
- Flag missing measurements at the top. Never estimate one.
- Use only supplied prices.
- No start dates.
- GST as its own line.
- No repair method recommendations.
OUTPUT
Sections in order: scope, itemised table, subtotal, GST, total, exclusions, questions for the estimator
Must appear: every line item with its own price
Must stay separate: GST, exclusions, assumptions
Length: one line per scope item, no introduction
Leave out: marketing language, closing pleasantries
Where to keep it
A document in your drive, a saved note, or a saved project inside your AI tool if it supports one. The test is whether a staff member could open it, paste this week's job material in, and run it without asking you anything.
How to test it before you rely on it
Run it against a job you already completed, then compare the draft with the document you actually sent. Differences are either a missing rule or missing source material. Fix one, rerun the same job, compare again. Three rounds is normal.
Build your own version
Bring one job and its paperwork, with confidential customer detail left out, and we fill this template in together: a full day at Avani Mooloolaba Beach Hotel, A$495 excluding GST, capped at 15 people. See the workshop, or enquire about onsite team training.
Read the full Context Stack, or see three complete worked examples.
Frequently asked questions
Can you use this template with any AI tool?
Yes. The template is information, not software. It works in ChatGPT, Claude, Gemini or Copilot because the layers are what change the output, not the brand. Compare the tools.
Do you paste the whole thing in every time?
Paste the standing layers once into a saved project or document, then add job material per run. If your tool has no saved projects, keep the Stack in a document and paste the lot.
How long does filling it in take?
An hour for the first, including gathering the standing material. Under fifteen minutes for the next Stack in the same business.
What if a section does not apply?
Every section applies to every document task. If Source looks empty, the workflow will invent things, which is the failure the layer exists to prevent. Why Source matters most.
Should each staff member have their own Stack?
One Stack per job, shared. Individual versions are how five people produce five different documents from the same task.
What do you do when prices change?
Update the Source layer only. Nothing else in the Stack moves, which is the practical advantage of keeping the layers separate.