Template

Safe Trial Consent & Risk Control Template

A practical, adaptable set of ready-to-use materials for low-risk technology pilots: a plain‑language participant consent form, a detailed risk-control checklist, monitoring and incident reporting templates, rollback procedures, decision criteria, and stakeholder communications. Designed to be edited for your context and to support future interactive capture, audits, and reporting.

Safe Trial Consent & Risk Control Template

This template package helps teams run small, fast technology pilots while protecting participants, the organisation, and public trust. It includes a plain‑language consent form you can give participants, a practical risk control checklist for planners, a monitoring and incident flow, a rollback plan, and stakeholder communication drafts. Adapt every section to local laws, contracts, and operational realities before use.

How to use this template

Copy the sections you need and edit bracketed fields (e.g., [PROJECT NAME], [DATES], [OWNER NAME]). Before the pilot starts, confirm approvals with legal, privacy, compliance, and any relevant operational owners. Keep the consent form with the pilot records and link monitoring logs and incident reports for traceability.

1. Plain‑Language Participant Consent Form (template)

Give this to every participant (or display it in-app) and keep a signed/recorded copy.

Title: Consent to Participate in [PROJECT NAME] Pilot

Purpose: We are testing [brief description of technology and objective]. This pilot will run from [start date] to [end date].

What participation involves: If you agree, you will [list concrete actions participants will take, e.g., use a new feature, wear a device, have your usage logged]. The pilot should take approximately [time commitment].

Risks: The expected risks are low and include [list likely minor risks e.g., incorrect suggestions, temporary service interruption, minor data entry errors]. If anything unexpected happens, the project team will notify you and take steps to protect you.

Benefits: There may be no direct benefit to you. The organisation may learn ways to improve services and safety.

Data we collect and how we use it: We will collect [types of data — e.g., anonymised usage logs, timestamps, survey responses]. Data will be used only for the purposes described above and stored for [retention period]. We will [describe anonymisation, aggregation, or deletion plan].

Confidentiality: Your identity will be protected by [describe measures]. Only authorised project staff will access identifiable data.

Voluntary participation and withdrawal: Participation is voluntary. You may withdraw at any time without penalty. If you withdraw, we will [explain what happens to their data].

Incident and support contacts: If you have concerns or experience an incident, contact [name, role, phone, email]. For privacy questions, contact [privacy officer].

Consent: I have read this form, had the opportunity to ask questions, and agree to participate in the pilot named above.

Participant name: _______________________

Participant signature or recorded consent confirmation: _______________________

Date: _______________________

Project contact: _______________________

2. Risk Control Checklist (for pilot planners)

Use this checklist during planning and as a pre‑launch gate.

  1. Scope & objectives defined: Clear success criteria, duration, participant count, environment (lab, field, customer‑facing) and exclusion criteria documented.
  2. Roles & approvals: Project owner, safety owner, privacy officer, legal reviewer, operations owner, and escalation contacts listed and have approved the pilot.
  3. Consent process: Signed or recorded consent mechanism defined; consent materials reviewed by privacy/comms.
  4. Data minimisation: Only necessary data collected; PII avoided when possible; data fields documented.
  5. Access controls: Access list for project data and systems; least privilege enforced; audit logging enabled.
  6. Monitoring plan: Metrics, thresholds, owners, monitoring frequency, and alerting defined (see Monitoring Plan template).
  7. Rollback & mitigation: Clear rollback triggers, steps, responsible people, and estimated timeline defined (see Rollback Plan template).
  8. Incident reporting: Reporting flow, who to notify, who makes decisions, and contact details confirmed.
  9. Stakeholder briefings: Communications plan for participants, internal stakeholders, and public (if applicable).
  10. Training: Staff supporting the pilot know the plan, escalation path, and privacy measures.
  11. Compliance checks: Regulatory, procurement, and contractual implications reviewed and mitigated.
  12. Opt‑out & compensation: Participant opt‑out process and any compensation policy defined.
  13. Logging & evidence: Versioned artefacts (code, models, configs) recorded to enable reproducible rollback and root cause analysis.
  14. Post‑pilot review: Evaluation plan and learning capture method defined before launch.

3. Monitoring Plan (template)

Define at least one owner for each item and how alerts will be raised.

  • Health & availability: Uptime, error rates — check hourly in early stages; owner: [name].
  • Safety signals: Any report of harm, privacy breach, or significant incorrect output — alert immediately to safety owner and operations; owner: [name].
  • User impact: Number of affected users, severity categories — daily summary to stakeholders.
  • Data quality: Missing/invalid inputs, anomalous values — automated checks daily.
  • Performance & correctness: Key model or feature metrics (accuracy, false positives/negatives) — cadence as appropriate to pilot risk (e.g., daily/weekly).
  • Opt‑outs and complaints: Track opt‑out rate and complaints — investigate trends weekly.

4. Incident Reporting Flow (template)

If an incident is observed or reported, follow these steps:

  1. Immediate containment: Stop the trial activity if participant safety or data exposure is suspected. Who can stop: [roles with authority].
  2. Initial report: Report to the incident inbox and safety owner within [time window, e.g., 1 hour]. Include summary, affected participants, and immediate actions taken.
  3. Assessment: Safety owner + privacy + operations conduct triage and classify severity (low/medium/high). Document evidence and logs.
  4. Decision: For medium/high incidents, follow rollback plan and notify leadership and legal. For low incidents, launch mitigation steps and increase monitoring.
  5. Communication: Notify affected participants and stakeholders per communications template. Keep messages factual and succinct; provide next steps and contact points.
  6. Root cause & lessons: After containment, perform root cause analysis and capture learnings in the post‑pilot review.

5. Rollback Plan (template)

Define triggers and steps clearly so rollback is fast and reversible.

Triggers (examples):

  • Safety incident affecting participants
  • Data breach or exposure of PII
  • Critical system failure causing significant outages
  • Model showing unacceptable error rates beyond thresholds
  • Unexpected regulatory or contractual issues

Rollback steps (high level):

  1. Stop trial input collection and disable feature [how to, e.g., config toggle, feature flag].
  2. Switch traffic to safe baseline or previous stable system.
  3. Preserve logs and snapshots for investigation; lock change windows to prevent further deployments.
  4. Notify stakeholders and participants per communications plan.
  5. Execute remediation tasks and plan for re‑launch only after root cause is resolved and approvals obtained.

Estimated rollback time: [hours].

Recovery owner: [name, role].

6. Stakeholder Communication Templates

Initial participant notice

Hello [Participant name],
Thank you for taking part in the [PROJECT NAME] pilot. This pilot will run from [start] to [end]. If you have questions or need help, contact [contact]. You can withdraw at any time by [describe process].

Internal status update (short)

Subject: [PROJECT NAME] pilot status — [date]
Summary: [one sentence]
Incidents: [none/summary]
Next actions: [short list]
Owner: [name]

Incident notification to participants (example)

Subject: Important update about your participation in [PROJECT NAME]
We experienced an issue on [date] affecting [scope]. We have paused the pilot and are investigating. If you are affected, we will contact you directly with next steps. For questions, contact [contact].

7. Decision Points & Go/No‑Go Criteria

Before launch, confirm these go/no‑go checks:

  • All approvals received from legal, privacy, operations, and safety owner.
  • Consent materials prepared and tested with at least one user.
  • Monitoring and alerts configured and validated.
  • Rollback plan documented and simulation completed (table‑top exercise).
  • Responsible people available during the pilot window.

Define clear success metrics (e.g., reduction in false alerts, user adoption %, qualitative feedback) and stop criteria (e.g., error rate > X, >Y complaints, any safety incident).

8. Post‑pilot Review Checklist

  1. Collect monitoring logs, opt‑outs, and incident records.
  2. Run evaluation against success criteria and document results.
  3. Capture lessons, improvement backlog, and compliance findings.
  4. Decide next steps: scale, iterate, pause, or retire — document rationale.

9. Adaptation Notes & Legal/Compliance Reminder

This template is a practical starting point, not legal advice. Adapt language and controls to local law, sector regulations (healthcare, finance, safety), procurement terms, and contract obligations. Engage legal and privacy counsel when pilots involve regulated data or clinical/medical contexts.

10. Suggested Implementation & Platform Opportunities

To make this template actionable inside your Hunger Engine domain:

  • Turn the checklist and consent into interactive forms to record approvals and signed consents (store with ContentData).
  • Create an incident submission form that feeds stored JSON records for traceability and dashboards.
  • Build monitoring dashboards that surface the metrics named in the Monitoring Plan and raise alerts to owners.
  • Package this resource as part of a Safe Trials toolkit that teams can acquire and tailor to their site.

Version: [v1.0] — Authors: [team or author name]. Keep a version history of edits. For help tailoring this template to your organisation, contact your Hunger Engine librarian or domain owner.

Discuss Ask the Librarian

Discussion

Comments and conversation will live here.