What is the difference between an investigation and a disciplinary hearing in this pack?

This pack supports the investigation stage (fact-finding) and does not determine outcomes or sanctions.

Can I edit the templates provided?

Yes. Edit for relevance, but preserve neutrality and ACAS alignment; ask for guidance if you’re unsure.

What if I have little or no evidence yet?

Use placeholders, document what’s available, and update as new evidence arrives; escalate to policy as needed.

Investigation Pack (ACAS-aligned)

Verified

@KOwl64

npx machina-cli add skill @KOwl64/transport-investigation-acas-aligned-pack --openclaw

Files (1)

SKILL.md

3.1 KB

Investigation Pack (ACAS-aligned)

PURPOSE

Create an ACAS-aligned investigation starter pack: invite wording, neutral question plan, and evidence log structure for transport incidents and potential misconduct.

WHEN TO USE

“Draft an investigation invite letter for this incident and evidence list.”
“Create investigation questions for this driver interview, ACAS aligned.”
“Summarise these incident notes into a clean manager brief.” (when it feeds an investigation)

DO NOT USE WHEN…

Generic HR queries like “What is a fair disciplinary process?” with no case artefact needed.
You’re drafting outcomes/sanctions without an investigation stage.

INPUTS

REQUIRED:
- Incident summary (what/when/where), parties involved, and what’s alleged/being reviewed
- Evidence available so far (CCTV, telematics, tacho extracts, witness notes, PCN, photos)
- Proposed meeting date window and who will chair/note-take
OPTIONAL:
- Relevant internal policies (paste text), previous similar cases, union/companion info
EXAMPLES:
- “Allegation: falsified manual entry on [date]. Evidence: tacho report + supervisor note.”

OUTPUTS

investigation-invite.md (Word-ready)
question-plan.md
evidence-log.md (Excel-ready table)
Success criteria:
- Neutral tone, no assumptions of guilt
- Includes right-to-be-accompanied wording
- Clear evidence handling and logging

WORKFLOW

Confirm this is an investigation (fact-finding), not a disciplinary hearing.
- IF unclear → STOP AND ASK THE USER what stage they are at.
Draft invite using assets/invite-letter-template.docx-ready.md.
- Include: purpose, date/time, attendees, right-to-be-accompanied, evidence access, and contact route.
Build a neutral question plan using assets/neutral-question-plan-template.md.
- Start broad → then specifics → then mitigation/context → then closing.
Create an evidence log using assets/evidence-log-template.md.
- Include chain-of-custody fields if needed.
Add ACAS alignment checks from references/acas-alignment-checklist.md.
If asked to edit existing documents → ASK FIRST.

OUTPUT FORMAT

# evidence-log.md
| Ref | Evidence item | Source | Date/time captured | Who captured | Storage location | Integrity notes | Relevance | Shared with employee (Y/N, date) |
|-----|---------------|--------|-------------------|-------------|------------------|-----------------|----------|----------------------------------|

SAFETY & EDGE CASES

Don’t provide legal advice; keep to process and neutrality.
If the allegation is serious and outcomes could be dismissal, flag that HR/legal review may be required per internal governance (ask for your policy text).

EXAMPLES

Input: “Invite letter + questions for driver interview”
- Output: invite + question plan + evidence log template populated with known items

Source

git clone https://clawhub.ai/KOwl64/transport-investigation-acas-aligned-packView on GitHub

Overview

Generates an ACAS-aligned invitation, neutral interview questions, and an evidence log structure to start a driver incident investigation. It emphasizes fact-finding, neutral wording, and proper evidence handling to support fair process.

How This Skill Works

The pack guides you through confirming the investigation stage, drafting an invite using the ACAS-aligned template, building a neutral question plan, and creating an evidence log with chain-of-custody considerations. It references templates and checklists to ensure ACAS alignment and proper documentation.

When to Use It

Draft an ACAS-aligned investigation invite letter for this incident and evidence list.
Create investigation questions for this driver interview, ACAS aligned.
Summarise incident notes into a clean manager brief for investigation feeding.
Prepare the evidence log structure for transport incidents with potential misconduct.
Cross-check documents against the ACAS alignment checklist during review.

Quick Start

Step 1: Confirm this is an investigation (fact-finding) and gather incident summary, evidence, and chair/note-taker details.
Step 2: Draft the investigation invite using the invite-letter template and include right-to-be-accompanied and evidence access information.
Step 3: Build the neutral question plan and populate the evidence log template, then run an ACAS alignment check.

Best Practices

Maintain a neutral tone and avoid any assumption of guilt.
Include right-to-be-accompanied wording for the employee and any union reps.
Capture all available evidence clearly (CCTV, telematics, tacho, witness notes) and note access permissions.
Use the suggested chain-of-custody fields in the evidence log template.
Consult internal policies and ACAS checklist before finalising documents.

Example Use Cases

Invite letter drafted for a driver incident with CCTV and tachograph data referenced.
Neutral interview questions plan covering broad to specific topics, then mitigation/context.
Evidence log populated with tacho report, supervisor notes, and witness statements.
Manager brief summarising incident notes for handover to investigation lead.
ACAS alignment checklist applied to ensure templates meet regulatory expectations.

Frequently Asked Questions

Add this skill to your agents