Safeguarding Report Evidence AI Agent

What this agent does

Builds the file, not the decision to report

A disclosure is made, and it is held word for word, write-once, from whichever channel it arrived on.

A moment of first knowledge is entered by the person who had it, and the clocks run from that moment.

Reason

A clock starts for each body that must receive a report, on the length that body sets, not one shared one.

A destination register is configured for your state, your sport and your governing body.

A roster position is read across for training and screening currency, from the systems already holding it.

Decide

A screening cadence comes from your state, your charter or your governing body, never from the federal statute.

A pack goes to the named reporter, who sends it personally; nothing is smoothed, filled in or inferred.

Out

A retention position runs on your own clock, with the fact of a report held apart from what was said.

Execute write actions only inside the approval boundaries agreed during implementation.

→ Product statement

The agent assembles the record and holds the clocks; a named individual makes the report, and a mis-started clock becomes the evidence of itself.

Example workflow

One disclosure, intake to report

AgentHuman

1Disclosure receivedCoach, front desk, parent, athlete, a written form or a phone call

2Words heldWhat was said, word for word, and the moment the reporter names as first knowledge

3Clocks startedOne clock per destination, each on the length its own rule-maker sets

4Controls appliedWrite-once capture, destination-register checks, roster currency and destination-match confidence

No human action required

Stages 1 to 4 run unaided, and nothing is reported at any of them — the agent is assembling, and the reporter's lane opens at the destination gate.

5DecisionBranches at the destination match

Clear match

Goes to the named reporter to send.

Any doubt

Adds a safeguarding-lead read first.

Reporter review

The pack is held with the words, the clocks and the destinations.

Confirm the moment · Append to the file · Log the report made

Reported — logged by the reporter▼

6Roster and case file updatedOnly where write access and retention policy allow it

7Outcome evaluatedDestination completeness, clock margin, lead corrections and what a later review found

Corrections

Each safeguarding-lead correction is counted in the evaluation.

What should not run autonomously

Human approval stays in control

Outside the boundary — human approval required8 items

Deciding whether a matter is reportable.

Rating, scoring or tiering a disclosure.

Transmitting a report to any destination.

Searching across matters, or linking by name.

Automation boundaryAgent acts unaided

✓Hold what was said word for word, write-once and timestamped.

✓Run the clocks from the moment the reporter says they.

✓Name each destination that must receive one, with its own clock.

✓Show the roster position on training and screening currency.

Nothing leaves the record except by the named reporter, inside the agreed boundaries.

Investigating, or resolving a matter locally.

Editing, tidying or summarising what was said.

Removing anyone from a roster or a session.

Changes to clocks, destinations or retention.

Example output

One disclosure, annotated

Nothing here rates a disclosure — the threshold is suspicion, and the answer is almost always report.

Intake record · single disclosureIllustrative example

Intake

Held as

First knew

Destinations

Confidence

Sent by

Volunteer coach, travel club

Word for word as spoken, write-once, with no edit path

21:05 local

State agency and law enforcement

Held unsent

The named reporter, in person

As receivedTaken from the account given and the moment the reporter names — nothing on this side is summarised.

What is held The words as spoken Moment of first knowledge Each read, logged

Why no rating hereNo score, no tier, no similar-matter panel; the named person decides.

ActionConfirm the momentAppend to the fileLog the report made

What the score decidesBelow the configured threshold the destination set gets a safeguarding-lead read.

Value

Where AI adds value

The same four claims, placed at the point in the workflow where each one applies.

Where the value landsValue 01 – 04

Each disclosureFrom the words as spoken

03Assembly

Work one matter, alone

No search across matters, no linking by name — that is investigation, and the Center holds it.

01Approved path

There is no triage here

A triage feature that cannot ship disabled should not ship at all, so this one was never built.

02Human review

A clock for each destination

Each runs from the moment of first knowledge — and where the federal reach is unsettled, the state clock still runs.

04Build an evidence trail

The words as spoken, the clock they started and the person who reported stay on the record.

Integrations

Typical integrations

Five system groups connect to the same agent. Which of them are in scope is decided in discovery.

Club and roster systemsMindbody · Glofox
ABC Fitness · Perfect Gym

Training recordsSafeSport Trained records
Governing-body member portals

Screening providersJDP · Sterling Volunteers
NCSI · state clearance portals

Agent

Safeguarding report evidence

Holds the words
Runs the clocks
Hands to the reporter

Case and document storeWrite-once object store
Case file · retention policy

Observability & evaluationOpenTelemetry · Langfuse
Supported monitoring/evaluation sources

Integration availability depends on the client's existing systems and API access.

Agent controls

Six checks between the model and the record

Six checks, each assuming the last held. What defeats them all is drawn in the map below.

L6 · Outermost — last line of defenceInward → L1 · closest to the model

L6Rollback / safe modeHold the intake at unsent when evaluation or production signals degrade.Roll back

L5Version monitoringTrack model, prompt, clock-rule and destination-register changes.Track

L4TraceabilityRecord the words, the clocks, the destinations and each read of the file.Record

L3Reporter hand-offHand the pack to the named reporter; Texas and California both make the duty non-delegable in terms.Gate

L2Policy guardrailsTest the pack against the destination register and the write-once rule; a failure returns it.Restrict

L1Match confidenceSend a low-confidence destination set to the safeguarding lead before the reporter sees it.Require review

Model corePack assembled — the words, the clocks, the destinations and match confidence

L1 – L2Test whether a pack may stand

L3Puts the sending in a person's hands

L4 – L5Keep the words and the clock behind them

L6Holds the intake at unsent when signals degrade

How Nestack evaluates it

Evaluate the whole assembly — not only the pack that comes out.

Coverage runs the whole depth of the workflow, and every layer is cut by slice.

Surface — the record a review reads

Depth of coverage ▼

E1Final-output evaluationDid the pack hold the words exactly as they were given?

E2Step-level evaluationDid the agent use the right register, the right clocks and the current roster?

E3Tool evaluationDid it read and write the correct file and the correct field?

E4Confidence calibrationDo low-confidence destination sets actually attract more lead corrections?

E5Slice evaluationHow does performance change across specific intake types?

E6Business outcomeHow many packs needed a correction before the reporter sent them?

Floor — the outcome the organisation answers for

Failure modes

Where each failure originates in the agent

Seven failure modes, each placed at the stage where it begins.

Agent lifecycleDirection of processing →

01 · Retrieval1 mode

HX-03

Stale currency record

Training or screening shown current from an expired record.

Stage gathersThe words, the register, the clocks and the roster

02 · Reasoning2 modes

HX-04

Single shared countdown

One clock is rendered where several are running.

HX-06

Clock started late

The clock runs from the form, not from first knowledge.

Stage proposesThe clocks, the destinations and match confidence

03 · Tool / write2 modes

HX-02

Destination missed

A body that must receive a report is not listed.

HX-05

Fragmented disclosure

Three channels, three fragments, no starting clock.

Stage writesOnly where write access and approval policy allow it

04 · Output1 mode

HX-01

Drafted, never sent

Nothing distinguishes a pack drafted from a report made.

Stage returnsThe pack the reporter sends and a review reads

05 · Change / Version1 mode

HX-07

Silent clock regression

A rule change quietly lengthens or drops a clock.

Stage tracksModel, prompt, clock rules and the register

Sev-1 · a report is late or never sent Sev-2 · a mis-started clock reaches the file Sev-3 · source degrades, pack holds unsent

See the complete Sports & Fitness failure-mode catalogue →

Affected slices

One intake type absorbs the corrections

A programme-level verbatim-capture figure can read clean while one intake type absorbs most of the corrections. Nestack reports the lead-correction rate by intake type, not only in total.

Slice performance — reported separately, not only in aggregateIllustrative example

Slice	Failure rate	Lift	Status
Disclosures across channels	8.8%	3.7×	Review
Multi-body destination sets	6.4%	2.7×	Review
Third-party or anonymous intake	4.0%	1.7×	Watch
Single-destination intakes	1.8%	0.8×	Normal

Bar: lead-correction-rate lift vs. single-destination baseline · scale 0–4.0× · tick marks the 2.0× review threshold 2 of 4 slices over threshold

Evidence-linked improvement

What a missed clock leaves behind

A cycle closes when the late notification is a regression case. That suite is what the next intake held is measured against.

Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn

01Detect

Lead-correction rate rises in one intake type.

02Diagnose

The conversation written up from memory the next morning is read back until one cause is left.

03Improve

The fix carries a number, and the intakes that forced it travel with it.

04Verify

Nothing goes out until every touched intake case has passed again.

05Learn

It is kept permanently, and the clock rules are amended alongside it.

Learn → DetectThe return edge. The next intake is measured against a suite one case longer.

Typical build scope

Twelve workstreams across six weeks

The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, assembly workflow, evaluation, integration, then production validation and handover.

Workstream Week 1Week 2Week 3Week 4Week 5Week 6

01Intake workflow discovery and boundary definition.

02Roster, training and screening sources.

03Destination register, clocks and retention mapping.

04Intake capture and write-once storage.

05Clock logic and first-knowledge binding.

06Destination matching and lead routing.

07Reporter hand-off workflow.

08Roster and case-store integration.

09Clock and destination cases.

10Guardrails and refusal controls.

11Intake-trail instrumentation.

12Deployment, documentation and Agent Care handover.

12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallel Final scope and sequence confirmed in discovery

Engagement tiers

What each tier includes

Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.

Capability✓ in scope · — not at this tier PilotOne site, one governing body ProductionProduction roster systems AdvancedMultiple bodies / states

Introduced at Pilot

Capture and clocks to your rules✓✓✓

Named-reporter hand-off✓✓✓

Verbatim-capture baseline✓✓✓

Introduced at Production

Reporting by destination—✓✓

Hand-off workflow in your systems—✓✓

Approved write-back—✓✓

Roster-and-training integration—✓✓

Introduced at Advanced

Multi-state clock rules——✓

Cross-body destination sets——✓

High intake volume——✓

Multi-body notification controls——✓

Build price From $5,000 From $8,000 Custom quote

Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.

Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.

What we need from you

What you bring, and what we build with it

Each input maps to a piece of build scope and a week in the delivery timeline.

You bringWe build with it

01Your intake channels and record structure → Intake capture and write-once storageWeek 1

02Representative past intakes, redacted → Capture baseline, clock binding and destination matchingWeek 2

03Your destinations, by state and governing body → Destination register, clock rules and the automation boundaryWeek 1

04Access to relevant APIs, feeds or exports → Roster, training and screening assessment, then integration setupWeek 2

05Records you would not want edited → Destination cases and failure testingWeek 4

06What no intake may ever become → Destination matching, lead routing, guardrails and refusal controlsWeek 3

07Named reporters and a safeguarding lead → Reporter hand-off workflow, then pilot and production validationWeeks 5–6

Nothing else is required Deployment, documentation and Agent Care handover are ours.

Delivery timeline

Four phases across six weeks

The chart is drawn from the weeks actually spent, which is the reason the fifth one is doubled.

Phase W1W2W3W4W5W6

Discovery W1

Build W2 – W3

Evaluate W4 – W5

Pilot & Launch W5 – W6

Week focus W1Intake discovery, destination mapping and the automation boundary W2Source integration and the capture baseline W3Assembly workflow, clock logic and hand-off controls W4Evaluation suite, refusal checks and failure-mode testing W5Roster integration, pilot intakes and targeted corrections W6One season run under the named reporter, then Agent Care handover

Reading the bandA bar spans the weeks its own work is named in and no others. The doubled fifth week is real work, not padding.

At the end of W6The final checks clear on live intakes and monitoring moves to Agent Care.

DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.

Next step · Sports & Fitness agent

Build a safeguarding-report agent around the person who has to report.

Show us how a disclosure reaches you today and who would have to report it. The record has to survive a state agency, a governing body and a proceeding reading it back, word for word, years later.

Discuss this agent →

Nestack Agents · Safeguarding report evidenceAGT-SF-17 · Agent Care available after launch