Notice Intake
Pre-advice tax-risk triage for CPA & EA firms
Select a synthetic IRS-notice case to run through rule-based risk-signal triage — the same notice always yields the same result — and generate a professional handoff packet. Every generated output passes a workflow-only safety boundary check.
1 · Pick a synthetic IRS notice
2 · Intake — what the notice says
- Taxpayer
- Anderson Family Trust (trust, KY)
- Notice type
CP14- Tax period
- 2025
- Form referenced
- 1041
- Amount asserted
- $831
- Arrived via
- emailed by trustee
3 · Deadline — computed by rule
2026-05-12 + 21 days = 2026-06-02 — the same notice and date always produce the same deadline.
- CP14 response window
2026-06-02- Lead time
- 5 days
- Status
- open
- Priority
- high
4 · Document checklist 3/5 gathered
5 · Escalation flag — a routing label, not a conclusion
Routine administrative matter. Standard CPA handling; no elevated risk signals detected by the triage engine.
A practitioner can adjust the level — but the engine blocks lowering past a fired trigger floor:
Select a level to see how the engine responds to a CPA override. Raising is always allowed; lowering past a trigger floor is blocked — the practitioner cannot quietly downgrade a flagged case.
6 · Handoff packet — facts only, the rest is yours
Facts auto-filled
- Matter: Anderson Family Trust — CP14 dated 2026-05-12
- Deadline: 2026-06-02 (5 days)
- On file: filed 1041, estimated-payment confirmations 1-3, trust agreement excerpt
- Still needed: IRS account transcript, estimated-payment 4 confirmation
Law left blank
Left for the licensed professional. TaxRiskOS does not write this.
Analysis left blank
Left for the licensed professional. TaxRiskOS does not write this.
Conclusion left blank
Left for the licensed professional. TaxRiskOS does not write this.
The packet assembles facts. It states no legal conclusion — the engine memo says so itself.
Full views: triage detail · full handoff packet
7 · Determinism proof — same input, same output
The handoff packet above is assembled by fixed rules — the same notice and the same date always produce the same result. The panel runs it twice and shows the two passes are byte-identical, with a stable content hash you can re-check.
6a4212c86a4212c86a4212c8. Run it again — the hash does not move, because the same notice and the same date always yield the same output.A generative / AI tool re-phrases on every run, so the same input can give a different answer — and a different hash — each time. This packet is assembled by fixed rules, so the output is reproducible and reviewable: same input, same output.
8 · Audit trail — your session, time-ordered
Interact above — every step is recorded here as an ordered, defensible record.
It documents process, not advice. No advice was emitted.