1. Business process and basic terms
Understand the work before learning the code. Iris organizes a quality-control review of a SNAP denial, termination, or suspension.
What problem the app explores
The recorded legacy process moves sample data through Excel workbooks, VBA routines, shared folders, Word templates, Outlook, and a separate corrective-action tracker. People copy data, use folder locations to indicate progress, and reconcile outputs. Iris tests whether one review workspace can make ownership, calculations, approval evidence, and reporting status easier to see.
These problems come from the retained workflow reference. Their frequency and cost have not been measured here. Use interviews and a timed baseline before claiming savings.
A review in plain terms
| Term | Meaning | Example or limit |
|---|---|---|
| SPII | Sensitive personally identifiable information. | The agency data owner identifies which review fields and documents fall in this category and which handling rules apply. |
| Review | One sampled unit of QC work, with its evidence and decisions. | The case number identifies the benefit case. The review number identifies sampled QC work. |
| SNAP Negative | Review of a denial, termination, or suspension. | The app does not decide a live benefit case or issue a payment. |
| FFY | Federal fiscal year, October through September. | September 2026 belongs to FFY 2026. October 2026 belongs to FFY 2027. |
| CAO | County Assistance Office. | Eligibility shows the CAO calculation. The manager records the CAO memo response. |
| PEC | The demo role that records policy decisions. | Confirm the formal team name and its production authority with management. |
| FNS / QCS | Federal reporting context and portal destination recorded in the references. | The demo makes a field TSV. Statistics still owns any actual submission. |
| EPP / DCA | The corrective-action plan/tracker context and its owning corrective-action group. | Confirm formal names with the owners. DCA is a future module, not a current demo role. |
| Valid / Invalid / Drop | User-facing outcomes. | Stored outcomes are clean / error / drop. A drop needs approval and remains in reconciliation. |
Who does what
| Role | Current responsibility | Important restriction |
|---|---|---|
| Examiner | Investigate assigned reviews, edit facts, calculate, and submit. | Facts are editable only while Active or Needs Changes. |
| Supervisor | View team work, check submissions, request changes, approve drops at the supervisor stage. | Can upload evidence. Cannot edit examiner federal facts. |
| Program manager | Program view, coverage, manager drop approval, memo and CAO tracking, reporting release. | Coverage approval does not replace later manager perusal. |
| PEC stakeholder | Read program work and record policy decisions at the PEC stage. | Cannot invent a defect map or edit examiner facts. |
| Admin | Sample intake, document handling, reports and policy access. | Admin is not an unrestricted bypass of workflow permissions. |
| Statistics | Sample intake, reports, rule rebinding and FNS export. | A download does not establish federal acceptance. |
Source: capabilities and scope, state-specific edit rules, and the specification. Policy publication and rule rebinding are distinct permissions. Read the server guards for each action.
The intended demo journey
Synthetic sample files → intake → examiner Active review → saved facts + saved computations → Apply Final Results → Submit → supervisor review → return for changes OR next approval stage Drop: supervisor approval → manager approval → Dropped → transmittal inclusion, excluded from Program Error Summary Non-drop: supervisor routing [currently blocked by defect-map decision] → PEC decision → manager memo → CAO response → reporting release → Program Error Summary and downloadable fields
Current, proposed, and open
| Current demo | Production proposal | Open before acceptance |
|---|---|---|
| Synthetic SNAP Negative investigation and persistence | Approved-data SNAP Negative pilot with agency identity and records controls | Management defect map and memo classification |
| Saved appointments, PDF evidence, memo text/status | Approved templates, generation, print/mail jobs and delivery evidence | Notice text, delivery ownership, deadline calendar |
| Reporting release and field TSV downloads | Certified receiving-system adapter with submission receipts | Federal format and rejection/acceptance process |
| Five verified EPP identity fields in an adapter | Separate DCA workflow and approved handoff | DCA states, deadlines, owners, and Access coexistence |
Exercise and answer key
Explain why a supervisor-approved review may be absent from Program Error Summary. Then explain why a drop can appear in a transmittal but not in that summary.
Answer
Summary eligibility requires the manager reporting-release flag and excludes drops. General supervisor approval is insufficient. A drop uses its separate manager drop-approval flag for transmittal inclusion. Approval stages have separate meanings. They are not one Approved checkbox.
Next: lesson 2. Deep reading: review domain, exports.