← Back to resources

Resources / SLP

SLP Annual Report — what you get (client-facing spec)

This is the standard, template‑driven deliverables specification for an Annual SLP Report produced from a controlled baseline (governed inputs + repeatable rules) using figures exported from Insite.

Outcome: a report leadership can stand behind and defend , with targets vs actuals , objective variance explanations, an exception closure trail , pack provenance , and traceability from source → metric → table/section .

What this enables (in plain English):

  • a report that matches your Mine/Mining Right scope and reporting period consistently,
  • targets vs actuals with variance explanations that are reviewable (not “hand‑wavy”),
  • a clear closure view: open exceptions, owners, due dates, and what is blocking release,
  • optional, quantified non‑binding scenarios that show what closure would look like under explicit assumptions (no recommendations).

Important: this document contains no client figures. The actual report we deliver is client‑specific (your mine/entity details, your scope, your figures, and your evidence references) and follows this same consistent structure.

What this pack includes

  • A versioned Annual SLP Report (PDF) per Mining Right per reporting period, populated with your figures (structure aligned to statutory sections used by the mine).
  • Targets vs actual vs variance tables/figures where targets are defined in the SLP.
  • Objective variance explanations and exception closure status (owner + due date + closure evidence pointer).
  • Pack provenance (scope, period, reports used, extract dates, data quality position).
  • Traceability in Insite: drill down from report tables/figures to contributing records; open record‑level trace to source; export source ↔ final record mappings where required.
  • Approval pages: section owners + authorised signatory block.
  • Board summary (optional, 1–2 pages): readiness status, key open exceptions, accepted assumptions, and review/approval position.
  • Variance & closure scenarios (optional, non‑binding): quantified “if X were true” scenarios that show potential closure paths under explicit assumptions/evidence dependencies (no recommendations).

What this pack will not include

  • “Recommendations”, “strategy”, or bespoke advisory narrative.
  • New commitments or rewritten SLP content. Where “strategies” / “action plans” appear, they are quoted from the approved/submitted SLP (a legal document); this report only adds implementation clarification, progress status, and evidence references.
  • Scope creep: out‑of‑scope contractors/entities are not silently included.

Usage rules (non‑negotiable)

  • One report per Mining Right per 12‑month reporting period.
  • Scope is Mining Right + in‑scope contractor footprint (and community entities where applicable). Keep the same scope across every table.
  • Commentary is limited to objective variance explanations and closure status.
  • Every table/chart includes:
    • reporting period label (start → end),
    • Insite quickview name (or report name), and
    • export date/time.
  • Preserve traceability: source → metric → table/section.

Authorisation + release review

  • Insite includes a data owner authorisation step when promoting final imports from staging to production for the reporting cut.
  • Final release review/approval of the exported report is completed outside Insite (review meeting and/or signature pages).

Pack inputs (what must be defined up front)

  • Mine / operation name
  • Mining Right reference number(s)
  • Reporting period (start → end)
  • Submission date (or deadline)
  • Report version identifier (e.g., v1.0)
  • Addressee (DMRE/DMPR regional office) (if a submission letter is included)
  • Entities in scope (list exactly what’s included):
    • mine entity,
    • core contractor(s),
    • community entities (if applicable)
  • Source systems and controlled extracts (as agreed), including export dates/timestamps

Pack structure (example)

The exact headings vary by mine, but a typical structure is:

  1. Submission letter (optional)
  2. Cover page
  3. Executive summary (high‑signal)
  4. Preamble (Reg 46a)
  5. Human Resource Development (Reg 46b)
  6. Local Economic Development (Reg 46c)
  7. Procurement / ESD (as applicable)
  8. Downscaling & retrenchment (Reg 46d)
  9. Financial provision (Regs 46e / budget spend views)
  10. Undertaking (Reg 46f)
  11. Appendices (pack provenance, exception closure summary, approval pages, supporting tables/evidence references)

Output checks (before release)

  • Reporting period label matches the stated start → end dates on every export.
  • Mining Right reference number(s) and scope statement match the pack scope (mine + in‑scope contractors + community entities where applicable).
  • Targets are present where the SLP defines them; tables show target vs actual vs variance.
  • Each table/chart cites its export source (quickview/report name + export date/time).
  • Exceptions are either closed (with evidence) or explicitly accepted (with owner approval recorded on the approval pages).
  • Approval pages are present and signed (outside Insite) or explicitly marked pending approval.
  • If variance/closure scenarios are included, they are labelled as non‑binding scenarios and include assumptions + evidence dependencies (not recommendations).
Request the SLP pack