Narrow scope. Real notices. A record you keep.
The pilot exists to prove one thing on your firm’s own notices: that a managed change-assurance chain produces determinations, ownership and evidence your existing process does not. It is deliberately narrow, deliberately manual, and sized so an operations leader can approve it.
Eight steps, agreed in writing before the first notice.
Select providers & scope
You name the exchanges, clearing houses, data and connectivity providers that matter, and the notice categories in scope.
Record known dependencies
A limited, agreed inventory: memberships, sessions, product universes, schemes, feeds — at the level of detail your firm is comfortable sharing, under NDA.
Monitor official sources
The named providers’ official channels are reviewed throughout the pilot; related notices consolidated, conflicts reconciled.
Process notices
Every in-scope notice is classified and tested for relevance — and every dismissal is logged with its reason.
Ask only what decides it
Where applicability turns on a firm-specific fact not in the inventory, you receive one precise question with a respond-by date — never a questionnaire.
Assign & follow actions
Applicable changes become actions with a named owner, due date and defined closure evidence; deadlines are chased before they are missed.
Document evidence & closure
Closure records are dated, reasoned and countersigned by your owner — including reasoned dismissals.
Deliver the assurance package
At pilot end your firm keeps the complete file: every review, determination, action, closure and dismissal, indexed.
Small enough to approve. Real enough to prove.
- The named providers and venues in scope
- The notice categories covered — and, just as explicitly, what is out of scope
- The defined pilot period and the weekly review meeting
- Response-time expectations in both directions
- Confidentiality: dependency information is held under NDA and returned or destroyed at your election at the end
- Manual, specialist review of every in-scope notice — a person, accountable for the reasoning
- Firm-specific determinations only after your firm supplies the relevant dependency information
- Structured email delivery: Applicability Queries, Action Records, Closure Records, and a weekly one-page summary
- Works alongside your existing email, Jira, ServiceNow or GRC tools — your tickets stay yours; our records reference them
- Disagreements are first-class: challenges and responses are recorded in the review, and neither is erased
Commercial terms are agreed directly and depend on scope — number of providers, notice categories, and the dependency inventory’s depth. There is no published price list because pretending scope doesn’t matter would be false precision.
Success is defined before the pilot starts — in your terms.
A pilot succeeds when your firm can point at concrete results: every in-scope notice triaged within the agreed time; determinations your owners confirmed without rework; at least one change where the review surfaced an action or deadline your incumbent process had not; and — the test that matters most — the ability to answer “show us how you handled change X” from the pilot file alone. If the pilot shows your existing process already does all of this, that finding is delivered with the same candour as everything else.