Sample walkthrough
See what an evidence record actually looks like.
A TimeToPoint record connects actor, authority, scope, action, review, and outcome into one structured view another party can inspect — reviewer-readable today, with cryptographic signing and transparency-log anchoring in higher-assurance deployments.
Evidence first. We show the record, then discuss fit.
Example: AI-assisted vendor delivery.
A vendor submits a £40,000 invoice for AI-assisted research and analysis. The CFO needs to approve payment. The client team says the work was completed. The vendor claims AI helped speed delivery. The risk team wants to know what was reviewed by a human.
TimeToPoint turns this into a structured evidence record across the six Attribution Stack layers.
Sample evidence record
The illustrative record below shows the current deployment (reviewer-readable record) plus advanced assurance options (signed + transparency-log anchored).
EVIDENCE RECORD #ER-2026-04-29-104812
Workflow: AI-assisted vendor delivery, Q1 research engagement
Issued: 2026-04-29T10:48:12Z
Status: Reviewer-readable (initial deployment)
LAYER 1 — INPUT
Source documents: 12 client documents (hashed)
Prompts / instructions: 3 prompt templates (versioned)
Retrieved sources: 142 web sources (URLs hashed)
Prior asset reuse: 2 prior reports referenced
LAYER 2 — CONTRIBUTION
Vendor analyst: 17.5 hours, primary judgement
AI assistant (model X): 4 generations, 3 accepted, 1 rejected
Reviewer: 2 hours, edits applied to AI sections
Approving manager: 30 minutes, sign-off
LAYER 3 — AUTHORITY
Statement of work: SOW-2025-Q4-#288
Scope: Sector A research, no client PII
AI tool permissions: Model X, web retrieval, RAG corpus B
Boundary exceptions: None
LAYER 4 — REVIEW
Reviewer 1: Senior analyst, accepted with edits
Reviewer 2: Engagement lead, accepted as final
Confidence shown: 82% on AI-generated sections
Override reason: N/A (no overrides)
LAYER 5 — OUTCOME
Final report delivered: 2026-04-15
Client acceptance: Recorded 2026-04-22
Downstream errors: None reported
KPI impact: N/A
LAYER 6 — CREDIT / PAY
Vendor invoice: £40,000
Acceptance basis: Layer 5 client acceptance + Layer 4 review trail
Payment recommendation: APPROVE
Evidence weight: HIGH (6/6 layers populated)
Layer 6 advisory note: Payment, settlement, and contribution policy decisions remain with finance and procurement.
The next sample can be your own.
Send us one workflow where AI contribution, delegated work, payment approval, or reviewer evidence is unclear. We will show how the evidence record could be structured for that workflow specifically.