Leadership Briefing Desk with every item sourced
A dated daily or weekly briefing for executives, drawn only from approved internal and external sources, with every item traced to its source and a list of what could not be reached.
The problem it answers
Executives read ten sources to learn three things, and the Leadership Briefing Desk that iSystematic builds replaces that reading with one dated briefing.
What it does
The Leadership Briefing Desk prepares a dated daily or weekly briefing from approved internal and external sources, with every item traced to its source and a list of what could not be reached.
Each item is checked against its source before it may appear; an item that fails the check is dropped, not softened. A source that could not be read is listed with its last successful read, so a quiet day is never confused with a failed one.
The briefing prepares and people decide: any follow-up message or calendar change it suggests waits for a person's approval.
Built from
It is built from two catalogue workflows and three catalogue patterns.
| Id | Name | What it brings |
|---|---|---|
| W01 | Daily Briefing | Collects items, finds dates and open questions, and produces a dated briefing with a list of missing information |
| W19 | Weekly Owner Review | The weekly view: supplied figures only, with missing data shown as missing |
| P01 | Retrieve, Ground, Draft, Review | Approved sources and cited passages; when sources conflict, the conflict is shown |
| P06 | Scheduled Read-Only Briefing | Runs only on a verified schedule, reads only, and never writes |
| P08 | Fail Visibly | A missing or stale source produces a visible failure, never silence |
What it is built on
Four parts of the framework corpus decide how the briefing behaves, and each leaves a record the client keeps.
| Framework | In this solution | Client keeps |
|---|---|---|
| PEVG | The verifier checks every briefing item against its source before the generator may include it; an item that fails is dropped, not softened | Refusal log |
| Decision-Grade Observability (IP-4) | Every briefing records which sources were read, when, and which could not be reached | Briefing archive with source dates |
| AI Data Governance Framework™ | Only sources on the approved list, each classified; internal sources bounded by who may read the briefing | Approved source register |
| Budget as Boundary (OP-7) | Daily runs under a spend cap that degrades deliberately rather than overspends | Spend log |
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 run leaves records the client keeps.
- A briefing archive with source dates
- A refusal log of every item dropped, and why
- The approved source register
- A spend log
- The five gate records and a BOE Declaration per control, as for every build
Typical buyer
The typical buyer is a chief operating officer or a chief of staff.
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: two weeks, a fixed fee, ten candidate tasks scored. When the briefing is already the clear first task, a six-week Pilot runs it for one team, with the baseline measured first.
Where to go next
Operations leaders
For COOs: iSystematic's two-week Automation Assessment scores ten candidate tasks, recommends three solutions and sets a baseline before anything is built.
Research-to-Decision Office
The Research-to-Decision Office turns a question into an evidence ledger and a one-page decision memo that separates evidence, assumptions and unknowns.
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.
Policy and Regulation Watch
Policy and Regulation Watch checks the official sources you name, records each version and reports real changes, never “no change” when a source failed.
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.