# ReguShield AI — Pilot Timeline

A practical 4-week plan for your ReguShield AI pilot. The pilot is designed to be **light: roughly 2–4 hours per week** for your nominated pilot lead. Each week builds on the last, ending in an executive review and an expansion discussion.

---

## Overview

| Week | Theme | Light effort | Key outcome |
|---|---|---|---|
| 1 | Activation, Upload & Analysis | ~2–4 hrs | First dataset analysed end to end |
| 2 | Review, Feedback & Gap Identification | ~2–4 hrs | Findings understood; gaps catalogued |
| 3 | Optimization, Decision Review & Evidence Refinement | ~2–4 hrs | Refined decisions and evidence set |
| 4 | Executive Review, Success Metrics & Expansion | ~2–4 hrs | Audit-ready report + next-step decision |

---

## Week 1 — Activation, Upload & Analysis

**Goal:** get into the workspace and run your first full analysis.

**Activities:**
- Request access at `/pilot-access`, receive your activation email (single-use link, valid 7 days), set your password.
- Complete `/pilot/onboarding` to set your organisation profile and frameworks in scope.
- Prepare a representative single-file dataset (see the Data Preparation Guide) and upload it.
- Run the analysis and confirm the expected frameworks triggered on your data.

**Effort:** ~2–4 hours, mostly in preparing a clean data file.

**Outcome:** your first dataset is analysed end to end — every record scored, mapped, and visible in the workspace.

---

## Week 2 — Review, Feedback & Gap Identification

**Goal:** understand the results and catalogue what's missing.

**Activities:**
- Walk through **Cases** — review the risk-scored decision for each record.
- Review **Evidence** requirements raised by control/evidence gaps.
- Review **Actions** recommended for flagged records.
- Note where outputs are clear and where they need refinement; share structured feedback with the ReguShield team.

**Effort:** ~2–4 hours, focused on review and feedback.

**Outcome:** your team understands the findings, and a catalogue of gaps and feedback is captured.

---

## Week 3 — Optimization, Decision Review & Evidence Refinement

**Goal:** tighten the analysis and the evidence set.

**Activities:**
- Re-upload an improved dataset where data quality or coverage was the issue, and re-run analysis.
- Review the **Compliance Graph** (Transaction → Regulation → Obligation → Risk → Decision → Action → Audit) to validate the reasoning chain.
- Refine which evidence requirements and recommended actions are most relevant to your operations.
- Confirm decisions with your compliance team as decision-support inputs.

**Effort:** ~2–4 hours, focused on iteration.

**Outcome:** a refined set of decisions and evidence requirements that reflect your real controls and data.

---

## Week 4 — Executive Review, Success Metrics & Expansion

**Goal:** produce the audit-ready output and decide next steps.

**Activities:**
- Generate the **Executive Report** and export it as PDF / DOCX / XLSX / TXT (each export carries a content hash, signature block, and audit envelope).
- Review results against the pilot **success criteria** with your stakeholders.
- Hold an executive review with the ReguShield team.
- Discuss **expansion** — broader data coverage, additional frameworks in scope, and a path to ongoing use.

**Effort:** ~2–4 hours, focused on review and decision.

**Outcome:** an audit-ready Executive Report you can take into an audit conversation, plus a clear go-forward decision.

---

## A Note on Scope

Throughout the pilot, remember that ReguShield AI is **compliance decision-support, not legal advice**. Its scores, mappings, evidence requirements, and recommended actions are inputs to your team's decisions. Final regulatory decisions — STRs, CDD completions, supervisory filings — remain with your authorised compliance personnel.

---

## Support

Questions at any point in the timeline: **hello@regushield.ai**.

---

ReguShield AI — compliance decision-support, not legal advice. Questions: hello@regushield.ai