Hevi works best when you pair better questions with tight scope. This contractor got fast, high-quality outputs by (a) asking precise, outcome-driven prompts and (b) pointing Hevi at the right folder so it only reads the documents that matter. The result: an “awesome” compliance summary with a large table mapping how WHS Acts and Regs work together, plus rapid procedure drafts grounded in legislation.

The customer (anonymised)

• Industry: Resources & safety
• Team: Commercial/safety lead + operations lead
• Use cases: Compliance summaries, legislation mapping, procedure drafting, PDF extraction, day-to-day reporting support

“I’m using Hevi as we speak… The answer was awesome… It created a massive big table.”

The problem they were trying to solve

They needed to quickly explain how multiple pieces of legislation relate (WHS Act, WHS Regulations, WHS for Mines & Petroleum). They also wanted procedures that mirror real site practice—step-by-step, legally sound, and easy to follow during audits or incidents.

What they did in Hevi (simple, repeatable)

1. Nailed the ask (prompt precision).
   They asked for exactly what they needed: a summary plus a table showing how the Acts and Regs connect to achieve compliance. Hevi returned a clean synthesis and a structured matrix the team could use internally.
2. Scoped the right folder (context discipline).
   When Hevi couldn’t “see” a document, they moved files so the selected folder contained the precise set of sources. Instantly, answers snapped into focus. Habit: choose the folder first, then ask.
3. Drafted procedures from law + practice.
   They tested procedure drafting against legislation. Hevi rewrote a procedure and “put more meat on the bones,” with the team supplying format and site-specific steps (Step 1, Step 2…) for production-ready outputs.
4. Pulled from PDFs without pain.
   Instead of messy copy-paste from Word, they read/searched PDFs directly and lifted clean excerpts—less formatting, faster outputs.
5. Kept humans in the loop.
   Hevi’s drafting stays as assistance, not autopilot. Final judgement remains with the people who wear the risk.

Why it worked

• The question was outcome-driven. “Summarise X and produce a table with columns A, B, C” is clear about format and purpose. Hevi excels when you specify what and how.
• The scope was tight. Pointing Hevi at the right folder gave it the smallest useful set of sources. Less noise, better answers.
• Legislation + operations = usable procedures. They fused what the law says with how the work is actually done, so the draft reads like something you can execute, not legalese.
• PDF-first extraction avoided formatting drag. Faster internal reuse, fewer layout fixes.

The result (in plain English)

• A defensible compliance summary explaining how WHS instruments work together.
• A large, structured table mapping Act ↔ Regs relationships—great for internal training and client-facing explanation (even if they keep the table internal).
• Procedure drafts with clearer steps and legislative grounding—ready to tune with site-specific actions (e.g., “action on fire discovery… step 1, step 2…”).
• Faster day-to-day writing with clean PDF extraction.

The playbook they validated (steal this)

1. Pick your folder first.
   Put only the relevant documents there (executed contract, legislation, standards, procedures). Select this folder in Hevi before you ask.
2. Be specific about output.
   “Summarise X and produce a table with columns: Instrument, Clause/Reg, Obligation, Practical Implication, Evidence Required.”
3. Bind law to practice.
   Ask Hevi to reconcile legislation with your on-site steps. Provide a skeleton SOP: “Action on discovery → notify → isolate → escalate → record.”
4. Use PDFs for reference packs.
   If a web page or external summary helps, print to PDF and drop it into the folder. Hevi will read it cleanly.
5. Keep control.
   Treat Hevi as a fast analyst. You review, approve, and send.

Example prompts you can lift

• Compliance synthesis:
  “Create a summary of how these instruments work together to achieve compliance: [list docs]. Include a table with columns: Instrument, Clause/Reg, Obligation, Practical Implication, Evidence Required. Cite each item with a hyperlink.”
• Procedure rewrite:
  “Rewrite this procedure to align with [Act/Reg refs]. Output as Step 1…N with who, what, when, and evidence. Keep it field-ready, not legalese. Cite governing clause after each step.”
• Folder sanity check:
  “Confirm all sources in the current folder. If anything is missing to complete this task, list the missing items and why.”

What this means for leaders

This team didn’t win because they “used AI.” They won because they asked for outcomes and scoped context. The upside shows up as:

• Faster compliance explanations your teams and clients can understand
• Procedure drafts that reflect both law and reality
• Less rework chasing “the right file in the wrong place”
• A more confident, auditable path from legislation → SOP → evidence

“I’m learning how to ask it better questions… I moved a few documents between folders… then off it went.”

Ready to replicate this win?

• Start a Compliance & Procedures folder.
• Drop in your Acts, Regs, Codes, and current SOPs (PDFs are fine).
• Ask for the summary + table first.
• Then ask for stepwise procedures bound to the clauses.
• Keep human approval on anything external.

‍