Procurement pack
Order-form draft, DPA summary, security posture, subprocessors, retention notes, and the support/contact route for procurement questions.
Pilot request
Find out whether the ECCTA Defence File Pilot is a useful next step.
This is a qualification request for General Counsel, compliance, financial-crime, governance, or adviser teams preparing failure-to-prevent-fraud evidence. It is not a request for legal advice.
What we assess
Whether your scope uncertainty, evidence state, and board/adviser timing match the pilot.
What happens next
A short review of fit, then a working session — run by a named, ECCTA-literate reviewer who is introduced to you, with their background, before any evidence is shared. Focused on scope posture, evidence gaps, attestations, review blockers, and board-pack readiness.
What we avoid
No fake certification, no legal opinion, no generic policy-template package, and no promise that a statutory defence will succeed.
Qualification outcomes
Likely fit requests are routed toward a short qualification call. Unclear requests get a human follow-up for missing context. Poor-fit requests are redirected toward public ECCTA guidance or a later conversation, without treating the screen as legal advice.
Five-minute request
Share enough context to make the first reply useful.
The fields below qualify whether DefenceFile is a fit for a 90-day ECCTA defence-file pilot. Keep legal analysis, privileged material, and sensitive evidence out of this public request.
Pilot package
GBP 2,500 setup + GBP 950/month
Pilot length
90 days
Annual lock-in
None — month-to-month after the pilot
Setup guarantee
Setup fee waived if first-session artifacts are not produced
Procurement details
Commercial and procurement shape for internal review.
The pilot is designed to be reviewed by legal, compliance, procurement, security, and finance before evidence is shared. Figures below describe the current pilot offer; signed terms control any live engagement.
Use this section to brief finance, procurement, security, and advisers before sharing sensitive evidence. The public request should only contain fit context, not privileged analysis or source documents.
Implementation plan
Kickoff, scope confirmation, evidence import, associated-person run, named review, board-pack export, and handover in a 90-day pilot window.
Pilot success criteria
Success means a named owner can show scoped entities, associated-person coverage, reviewed evidence, open blockers, and a hashed board-pack export.
Exit path
No annual lock-in — month-to-month after the pilot. Export the board pack, evidence register, audit trail, and unresolved blocker list before deciding whether to continue.
Does the pilot provide legal advice?
No. DefenceFile organises evidence, source dates, review trails, and blockers so counsel and compliance teams can inspect the work.
What does the setup guarantee cover?
Only first-session workflow artifacts: scope screen, evidence gap map, attestation chase list, and board-pack blockers. It does not certify scope or defence adequacy.
What if we are not a clear fit?
Unclear requests get a human follow-up for missing fit context. Poor-fit requests are redirected toward public ECCTA guidance or a later conversation.
What still needs customer evidence?
Production email delivery, signed order form, signed DPA, customer UAT, deployed health, field metrics, and backup restore evidence remain external proof items.