Implement pre-adverse action workflow for Door Dashboard background checks

Summary
Design and implement an FCRA‑compliant, repeatable pre-adverse/adverse action workflow for background checks used by the Door Dashboard onboarding flow.

Problem
Background-check results currently flow into onboarding without a documented or automated pre-adverse action process (pre-adverse notice, candidate dispute opportunity, approval gating and timeline tracking). This exposes the company to FCRA compliance risk and leads to inconsistent candidate communications.

Objectives
- Implement a legally compliant pre-adverse notice and adverse-action process tied to background checks.
- Automate generation of notices, internal review gating, and audit logging.
- Provide standard templates, runbooks, and E2E QA for the workflow.

Scope
- Systems: Door Dashboard onboarding flow, background-check provider integration, Legal/HR review queue, email delivery system, audit/logging store.
- Deliverables: approved notice templates, implementation design, integration tasks, QA checklist, runbook updates.

Planned work / Tasks
- Research FCRA requirements and Door Dashboard policy constraints; document required notice content and timing. [ ]
- Map required data fields from the background-check provider (report extracts, reason codes, evidence links) for notice population. [ ]
- Draft pre-adverse notice templates (email) and final adverse-action letters; circulate to Legal for approval. [ ]
- Build internal review queue/ticket for Legal/HR to review flagged reports and approve/reject adverse decisions. [ ]
- Implement automation: trigger pre-adverse notice generation when report meets configured adverse criteria and enqueue for review. [ ]
- Add audit logging: record timestamps (notice generated/sent, candidate response, legal approval), user IDs, and report snapshots. [ ]
- QA: run end-to-end tests with sample reports to verify template variable substitution, timing, and delivery. [ ]
- Update onboarding runbooks and team documentation with process, SLAs, and owner contact info. [ ]

Acceptance criteria
- Pre-adverse notice and final adverse-action templates approved by Legal and stored in repo.
- System generates pre-adverse notices for qualifying reports and places them in the Legal/HR review queue.
- Audit logs capture required timestamps, approver identity, and report snapshot.
- End-to-end QA tests validate correct candidate data population and delivery of notices.

Stakeholders
- Product: Onboarding (owner)
- Engineering: Integrations, Backend, Notifications
- Legal / Compliance
- People Ops / Recruiting

Risks & Compliance Notes
- All notices must meet FCRA content and timing requirements; do not send final adverse action until the waiting period has elapsed and Legal has approved.
- Ensure secure handling of PII from background-check reports and retention policies.

Next steps
1) Confirm Onboarding/Product owner. 2) Legal to review and approve template drafts. 3) Engineering to estimate and schedule integration work.

No files, tests, or entry points are identified. Start by confirming the Onboarding owner and Legal requirements, then map the background-check provider, review queue, notification system, and audit store before defining implementation tasks. Done means approved templates, gated notice automation, required audit data, and end-to-end QA are delivered.

Written by the indexing model from the issue text.