Create a Task Analysis for site work under HSWA 2015

A Task Analysis is the New Zealand industry default for documenting how a job will be done safely under the Health and Safety at Work Act 2015. Riskora structures the TA — hazards, controls, sequence and worker sign-on — for the PCBU. 100+ industries supported.

New Zealand (JSA) example document — Kitchen Reconfiguration & Beam Install — 42 Tinakori Road, Wellington. Client: Mr & Mrs Henderson (Private Client). Site: 42 Tinakori Road, Thorndon, Wellington 6011. Scope: Removal of a load-bearing internal wall in an existing 1910 weatherboard villa, installation of a 250 UB engineered steel beam to form a 4.8 m opening, replacement of kitchen joinery, services first/second fix, and minor strip-out of pre-2000 sheet linings. Works occur in an occupied dwelling within a Heritage Area 1 zone.

Example New Zealand (JSA) front cover produced by Riskora
Try the new compact mode. Same document, just more compact

Full version

Preview first. No card needed. Download when you're happy.

  • Free to start
  • No signup to preview
  • Done in ~60 seconds

Riskora helps structure your safety document. A competent person must review it before use. Native NZ terminology — PCBU, worker engagement, hierarchy of controls and WorkSafe-aligned hazard categories. Not a UK RAMS template with the flag swapped.

  • UK · IE · US · CA · AU · NZ
  • RAMS · SWMS · JHA · JSA · COSHH · Task Analysis · Toolbox Talks
  • Site-specific — not a blank template
  • First document free · No card required
You're probably here because…
  • Main contractor or client wants the TA before site induction.
  • WorkSafe inspector visit or notifiable event in front of you.
  • Existing TA is generic — needs site-specific detail.
  • New worker starting on site tomorrow.
What to add to the box
  • Main contractor's request for a TA
  • Your scope of works or quote
  • A site supervisor's text message
  • Previous Task Analysis to update
  • Tender or pre-qual paperwork
Inside the document

What Riskora builds into every Task Analysis

Job-specific hazards

Hazards drawn from the task, the site and the scope you describe — not a stock list.

Hierarchy of controls

Elimination first, PPE last. Initial and residual risk shown side by side.

Step-by-step method

Sequenced steps with a person responsible for each, written for this Task Analysis.

PPE & equipment

Task-specific PPE, plant and inspection requirements.

Emergency arrangements

First aid, fire, spill and rescue arrangements specific to the work.

Chemicals & substances

Substance prompts appear when materials in scope need a hazardous-substance assessment.

Permits & hold points

Hot work, working at height, confined space and inspection hold points where they apply.

Briefing & sign-off

Pre-start briefing register, version lock and an audit-ready workflow.

Site-ready Task Analysis PDF

Branded, paginated PDF you can issue without reformatting.

Example output

A New Zealand Task Analysis

PCBU named, hazards tied to the hierarchy of controls, sequence of work, sign-on register and a worker-engagement record built into the PDF.

Not a blank template

Riskora isn't a blank template or a generic AI text generator

Riskora asks for your job and site context, then structures a client-ready, site-specific JSA: hazards, controls, method steps, PPE, emergency arrangements and sign-off — not a paragraph of AI prose. You stay in control of every section and the output is built for an audit-ready workflow.

Inside the document

What your JSA actually contains

Riskora builds a structured, client-facing document — not a generic AI paragraph. Every section is shaped around your job, your site and your team.

  • Hazards

    Task-specific hazards for the job, captured row by row — not a generic list pulled from an old JSA.

  • Controls

    Control measures mapped to each hazard with residual risk scoring after controls are applied.

  • PPE

    PPE requirements tied to the activity and site, ready to brief to the team.

  • Method steps

    Step-by-step method statement structured around how the work is actually sequenced on site.

  • Emergency arrangements

    First aid, rescue plan, emergency contacts and site-specific escalation routes.

  • COSHH prompts

    Substance prompts when the work involves chemicals, dusts, fumes or sealants — flagged early, not missed at review.

  • Sign-off

    Operative sign-off captured against the document — names, dates and acknowledgement of the brief.

  • Version history

    Every change tracked so you can show what was issued, when, and which version the team signed.

  • Approval status

    Clear approval state on every document — draft, in review, approved, issued — visible across the team.

  • Audit trail

    Who created it, who reviewed it, who signed it. A complete trail you can hand to a principal contractor or auditor.

Before & after

From copied-and-pasted to site-specific

The reason JSA get rejected is rarely the format — it's that the document is obviously generic. Riskora rebuilds it around this job, this site and this task.

Before

Generic template copied from an old job.

  • • Hazards and controls that don't match this site or task.
  • • Method steps written for a different sequence of work.
  • • No emergency arrangements specific to the location.
  • • Client flags it as generic and asks for a rewrite.
After

Site-specific document structured around this job, site and task.

  • • Hazards captured from the actual scope you pasted in.
  • • Method steps sequenced for how the work runs on site.
  • • Emergency arrangements and rescue plan tied to the location.
  • • Approved internally, briefed to the team, signed off and stored.
How it works

From job details to signed-off document

A four-step workflow used by contractors, consultants and safety teams to turn informal job details into client-ready safety paperwork.

  1. 1
    Paste job details

    Drop in a client email, a WhatsApp from the site manager, a scope of works or a tender note. Anything that describes the job.

  2. 2
    Riskora structures the document

    Riskora turns your brief into hazards, controls, method steps, PPE, emergency arrangements and COSHH prompts.

  3. 3
    Review, edit and download

    You stay in control of every section. Tweak anything, then download a clean PDF or share a link.

  4. 4
    Brief the team and record sign-off

    Brief operatives, capture their sign-off and keep a full audit trail of who signed which version.

Built for site reality

Built by people who've written this paperwork on real sites

Riskora is built by a founder with hands-on site and document experience — designed for contractors, consultants and safety teams who need to issue, brief and prove safety paperwork without losing a day to admin.

  • Built for contractors, consultants and teams
    Solo trades, principal contractors and in-house safety teams all run on the same workflow.
  • Supports multiple countries
    UK, Ireland, Australia, New Zealand, US and Canada — wording and document types match the local standard.
  • Not just documents
    Sign-off, approvals, version history and an audit trail — the management workflow around the paperwork.
Start in seconds

Describe the job details — get a structured JSA

Describe the job details, scope of works, email or WhatsApp message. Riskora structures the rest.

Preview first. No card needed. Download when you're happy.

FAQ

Questions for this exact situation

Task Analysis is the most common NZ term for the document — SWMS is used by some Australian-owned principals working in NZ. Both describe the safe system of work, the hazards and the controls. Riskora can produce either.

Yes. PCBU duties, worker engagement and the hierarchy of controls are the structural backbone of every TA Riskora produces.

Yes — every worker who is briefed on the TA signs on before work starts.

Yes — first TA is free, no card.

Riskora helps structure a site-specific safety document. It does not replace competent review, site supervision, client requirements or legal duties. Always check the final document before issue.