1040 intake to ready for preparation

Document one authorized start event, owner, request cadence, and permitted office variants.

All pilot offices use the approved start definition in walkthrough testing.

A versioned standard names the start event, accountable role, cadence, and approved exceptions for each pilot office.

• Office owner interviews
• Engagement authorization definition

Define which portal and shared channels may enter the queue and how rejected sources are handled.

No unapproved source enters the pilot intake queue.

The source allowlist, rejection behavior, exception owner, and audit fields are approved and testable.

• Information security review
• Shared-channel inventory

Normalize receipt events from the portal and approved shared source into an engagement work queue.

95% of pilot receipt events appear in the queue within five minutes.

Each event includes engagement, source, received time, correlation ID, and an explicit rejection result when routing fails.

• Approved channel policy
• Portal API credentials
• Engagement identifier mapping

Apply deterministic hashes and metadata checks before a document is associated to the client file.

100% of pilot documents retain hash, version, source, and rule results.

Duplicate and version tests are deterministic; ambiguous identity, year, or type routes to practitioner review without changing record state.

• Document metadata contract
• Retention policy
• Representative synthetic test set

Update the tax workflow and preparation queue from one successful release event.

No duplicate preparation work items are created during retry testing.

Both consumers acknowledge the same case, release version, correlation ID, and final delivery result.

• Release gate API
• Preparation queue integration

Maintain a source-cited readiness draft as document and reviewer events change.

At least 90% of synthetic scenarios produce the expected open-item state with valid citations.

The agent uses read-only typed tools, records uncertainty, preserves prior conclusions, stops on missing evidence, and cannot send, change status, approve exceptions, or release work.

• Approved tool contracts
• Durable draft state
• Model and security review
• Evaluation dataset

Provide a review queue for ambiguity, readiness decisions, and exact client-message approval.

100% of readiness and communication actions retain reviewer identity and timestamp.

A practitioner can correct the draft, cite evidence, approve or reject readiness, and approve exact message text before any action.

• Role and approval model
• Readiness draft schema

Send only practitioner-approved content and track requested items, due date, delivery, and new evidence.

All pilot follow-ups are consolidated and visible in the workflow record.

The sent content exactly matches the approved draft and delivery, due date, and subsequent evidence are auditable.

• Communication integration
• Exact-text approval control

Permit handoff only for complete cases or cases with a valid manager exception record.

All negative-path release tests prevent the status transition.

The gate stores policy version and evaluated facts, fails closed, and cannot create or infer an exception.

• Approved release policy
• Exception record schema

Capture approval or denial with rationale, evidence, manager identity, and time.

100% of open-item release attempts contain a complete signed decision record.

Only the designated manager role can decide; required evidence is validated; the signed result cannot be overwritten.

• Manager identity mapping
• Exception evidence requirements

Define operating responsibilities, train pilot users, and establish issue triage and feedback review.

All pilot users complete role-based training before production-like testing.

Role guides cover queue ownership, practitioner approvals, manager exceptions, support escalation, and pilot feedback capture.

• Approved pilot operating model
• Stable test environment