Research-to-Decision Office with the evidence shown
A research brief, source discovery, an evidence ledger and a one-page decision memo that separates evidence, assumptions and unknowns, so a recommendation arrives with what stands behind it.
The problem it answers
Recommendations arrive without the evidence behind them, and iSystematic's Research-to-Decision Office makes the evidence part of the memo.
What it does
It produces a research brief, finds sources, keeps an evidence ledger, and writes a one-page decision memo that separates evidence, assumptions, conflicting claims and unknowns.
Every source is recorded with its date. A citation must support the claim it sits beside, and two models agreeing is not treated as independent evidence.
The memo says what would change the recommendation. The decision, and any action that follows, stays with a person.
Built from
It is built from one catalogue workflow and one catalogue pattern.
| Id | Name | What it brings |
|---|---|---|
| W20 | Research to Decision Memo | Discovery, reading, comparison and a memo, with the decision left to a person |
| P05 | Research, Compare, Decide | Primary sources inspected and compared; handoff between assistants is manual by default |
What it is built on
Three parts of the framework corpus decide what the memo may claim, and each leaves a record the client keeps.
| Framework | In this solution | Client keeps |
|---|---|---|
| PEVG | The verifier holds the line on what may be believed; two models agreeing is not independent evidence | Evidence ledger |
| Decision-Grade Observability (IP-4) | Every source with its date and the version of the routing policy that chose the models | Source record |
| BOE Declaration | The memo separates evidence, assumptions and unknowns, in the same shape as every other record | Decision memo |
Five parts apply to every build and are not repeated here: decision rights, the five gate records, a BOE Declaration per control, a vendor assessment for every vendor, and incident response. How we build sets out all of them.
The evidence it leaves behind
Every question leaves records the client keeps.
- An evidence ledger
- A source record with dates
- The routing policy version behind each memo
- The decision memo
- The five gate records, as for every build
Typical buyer
The typical buyer is a strategy, policy or product team.
Status
Proposed, as of 9 October 2026. A solution becomes Piloting or Released only after a documented pilot, and no result is shown for it before then.
How to start
Most organisations start with the Automation Assessment. When decision memos are already the clear first task, a six-week Pilot runs the office for one team, with the baseline measured first.
Where to go next
Who we work with
Who iSystematic works with: practices and firms, organisations and regulated institutions. Each profile names your job in your words and one way to start.
Leadership Briefing Desk
The Leadership Briefing Desk gives executives a dated briefing from approved sources, every item traced to its source, with a list of what it could not reach.
Board and Committee Pack Preparation
Board and Committee Pack Preparation collects approved inputs, checks them against the agenda and drafts a cover summary with a source map for every paper.
Vendor Intake and AI Diligence
Vendor Intake and AI Diligence runs the AVRF questionnaire with each requester, scores the answers and drafts a gate decision for a named person to sign.
How we build
How iSystematic builds: every solution uses the same deposited frameworks. See what each part decides, what the client keeps, and each specification's DOI.
Conformance is self-declared; no regulator endorses this work.
Start with the Automation Assessment
Two weeks, a fixed fee shared on a short call, ten candidate tasks scored and three solutions recommended.