Start Here: Tell Us About Today

• In a few sentences, describe your current enrollment footprint: number of sites, typical daily applicants per site, and the credentials you issue.
• Which enrollment channels are actively used right now? Options: In-person at agency offices (fixed sites), Mobile enrollment units, Online/remote identity proofing, Partner / third-party kiosks, Field outreach events, Other
• Do you track average end-to-end enrollment time per applicant today? Options: Yes — consistently tracked, Yes — sporadically tracked, No, but we estimate, No, we do not track
• What single enrollment metric does your leadership most often ask for (e.g., average time, backlog, error rate)?
• How confident are you that your current process reliably prevents duplicate identities? Options: Very confident, Somewhat confident, Not confident, Unsure
• Tell us about one recent enrollment day that felt unusually difficult — what happened and how did it feel for staff and customers?

Are We Just Patching Around the Real Problem?

• What part of your enrollment system do you suspect is an illusion of working—something you tolerate that actually causes most downstream pain?
• What workarounds or manual hacks have staff built to keep the process moving? Select all that apply. Options: Paper overrides, Manual photo uploads, Local spreadsheets for reconciliation, Shadow databases, Ad-hoc phone/verification calls, Other
• How often do those workarounds trigger a follow-up investigation, complaint, or rework order? Options: Daily, Weekly, Monthly, Rarely, Never
• Share a concrete example where a workaround led to a customer-facing failure or an internal crisis: what happened and who noticed it first?
• Which of these costs best describes the impact of these patches on your program right now? Options: Increased staff hours / overtime, Slower throughput / longer queues, Higher error/appeal rates, Regulatory risk / audits, Reputational damage, Other
• How willing is leadership to replace a familiar but fragile process with a new approach that may change roles or systems? Options: Very willing, Cautiously willing, Requires strong evidence, Reluctant / politically sensitive

Where Do Your Records Hide—and How Messy Are They?

• If I queried your environment for ‘applicant identity data’, how many distinct systems should I expect to find? Options: One centralized system, 2–3 systems, 4–6 systems, More than 6 / widespread
• Which systems store identity-related data today? (Select all that apply and add names in the next question.) Options: Legacy enrollment database, CRMs / case management, Biometric matcher / FIS, Document management system, Cloud storage buckets, Third-party vendor databases, Other
• List the system names, owners, and primary data formats (e.g., SQL, CSV exports, proprietary) for the top three sources of enrollment data.
• Estimate your current duplicate / potential-duplicate rate across the population. Options: <0.1%, 0.1%–0.5%, 0.5%–1%, 1%–5%, >5%, Unsure / no estimate
• Have you attempted deduplication or record merges before? If so, what tools or processes were used and why did they succeed or fail?
• Who owns ongoing data quality and the authority to resolve duplicates—describe roles and how conflicts are adjudicated.

Who’s Running the Show When It Matters?

• If enrollment slowed by 50% tomorrow, which role or team would be most exposed and why?
• Who makes operational decisions for enrollment sites (scheduling, staffing, escalation)? Options: Local site manager, Regional operations, Central program office, Third-party vendor, Hybrid/shared model
• Describe your operator training program: initial training length, refresher cadence, and how you verify ongoing competency.
• What is your operator turnover or vacancy rate over the last 12 months? Options: <5%, 5%–10%, 10%–20%, >20%, Unknown
• How do frontline staff feel about current tools and processes—what do they say is the most frustrating part?
• What escalation paths exist when an operator encounters a complex identity issue (e.g., mismatched biometrics, disputed identity)? Options: Immediate supervisor, Central adjudication team, Legal/privacy counsel, External vendors, No formal path

When the Line Gets Long: Bottlenecks, Delays, and Backlogs

• If you could snap your fingers and eliminate one bottleneck today, which one would free the most capacity?
• Which of these frequently cause bottlenecks at your sites? Select all that apply. Options: Document verification time, Biometric capture retries, Manual data entry, Network/system latency, Adjudication queue, Hardware availability, Other
• During peak periods, what average queue length or wait time do applicants experience? Options: <5 minutes, 5–15 minutes, 15–30 minutes, 30–60 minutes, >60 minutes, Unknown
• How often do enrollment sessions end without successful completion (applicant leaves, refusal, failed capture)? Options: Daily, Weekly, Monthly, Rarely, Never
• Describe how backlogs are cleared today: overtime, additional sites, manual rework, or other tactics.
• What KPI change would be most meaningful to you (pick one): shorter processing time, fewer duplicates, fewer adjudications, or improved customer satisfaction? Options: Shorter processing time, Fewer duplicates, Fewer adjudications, Higher customer satisfaction, Other

Regulatory, Legal, and Equity Landmines

• Which regulation, legal requirement, or public concern worries you most about modernizing enrollment?
• Which of the following compliance items apply to your program right now? Select all that apply. Options: Real ID deadlines, NIST 800-63 / IAL/AAL/IAL2/IAL3 requirements, Privacy Impact Assessment (PIA) required, Data residency/localization, Equity / anti-discrimination mandates, FedRAMP / FIPS 201 requirements, Other
• Have you completed any bias or demographic performance assessments for your existing biometric system? If yes, summarize the findings. Options: Yes — formal assessment with report, Yes — informal/internal review, No assessment done, Assessment in progress
• When a demographic disparity or privacy complaint has arisen, how was it handled and who led the response?
• Do you currently have contractual language or procurement constraints intended to minimize vendor lock-in? Options: Yes — strong portability clauses, Some clauses but limited, No specific provisions, Unsure
• What level of evidence would satisfy your legal or privacy teams to move forward with a pilot (e.g., test data results, third‑party audit, ATO documentation)? Options: Technical test results, Third-party audit/assessment, Pilot with non-production data, Formal legal review / contract amendments, Other

If We Could Reimagine Enrollment Tomorrow

• Imagine enrollment is faster, fairer, and auditable — what three things would change first for operators and citizens?
• Which target KPIs matter most for a successful pilot? (Select up to three.) Options: Average enrollment time, False rejection rate by demographic, Deduplication accuracy / reduction in duplicates, Operator error rate, Number of manual adjudications, Customer satisfaction / NPS
• What acceptance criteria would you require to consider a pilot successful? Please be specific (e.g., enrollment time < X minutes; dedupe rate > Y%).
• What data or sample workload are you willing to provide for a pilot (select all that apply)? Options: Synthetic/test data only, Anonymized historical records, Subset of live applicant flows, No data available for pilot, Undecided / need approvals
• How soon could your team start a small pilot if contractual and privacy questions were addressed? Options: Immediately, Within 1–3 months, 3–6 months, 6+ months, Unsure / dependent on approvals
• Who are the essential stakeholders you would involve in a pilot decision and their roles (names/titles preferred)?

What Would Make You Say Yes to a Pilot?

• What are the top three non-negotiables that would prevent you from approving a pilot?
• Which of these pilot risk mitigations would make you most comfortable? Select all that apply. Options: Data minimization & anonymization, Escrow / portability guarantees, Independent accuracy testing, Limited-scope timeboxed trial, Operator shadow mode (no citizen-facing changes), Other
• How should success be measured and who signs off—program director, CIO, legal, or another party? Options: Program director, CIO/CTO, Legal/privacy, Operations lead, A steering committee
• What internal approvals or documentation will we need to gather before a pilot (e.g., SOW, data sharing agreement, PIA, budget approval)? Options: Statement of Work (SOW), Data Sharing Agreement / MOU, Privacy Impact Assessment, Budget certification, Security / ATO paperwork, Other
• Would you be willing to designate a single point of contact to run pilot logistics and approval coordination? Options: Yes — we have someone in mind, Yes — will identify after internal discussion, Maybe — depends on workload, No

Starting Together: How Outcomes Feel Today

• How would you briefly describe your current experience setting measurable outcomes for identity programs (what’s worked, what hasn’t)?
• How often do you use quantified KPIs (not just anecdotes) to make go/no-go decisions on identity projects? Options: Never, Often, Sometimes, Rarely, Always
• Which outcome owners in your organization currently sign off on operational KPIs? Options: Program Director, CIO/CTO, Identity Division Chief, Contracting Officer, Operations Lead, Legal/Compliance, Other
• Can you share one recent example where a KPI (good or bad) changed project direction? What happened?

What Would Failure Actually Look Like — and Who Feels It First?

• If the new identity platform misses its targets, what concrete harms would your agency face in the next 6–12 months?
• Which stakeholder groups would raise the loudest alarms (e.g., front-line operators, public advocates, federal auditors)? Options: Front-line operators, Program leadership, Legal/Compliance, Public/policy advocates, Oversight bodies/auditors, Contracting office, Other
• How would public trust or political risk change if false rejections or demographic bias materialize at scale?
• What short-term operational impacts would you expect (e.g., backlog growth, manual adjudication hours, credential issuance delays)? Options: Backlog growth, Increased manual adjudication, Longer enrollment time, Higher per-citizen cost, Legal challenges, None of the above, Other

Which Numbers Will Decide This Project’s Fate?

• Which single metric would you say is most likely to determine whether leadership continues funding this program? Options: False rejection rate (FRR), False acceptance rate (FAR), Deduplication (duplicate record) reduction, Average enrollment time, Manual adjudication rate, Credential issuance time, Other
• From the list below, select all KPIs you expect to track during pilot and rollout. Options: False rejection rate (FRR), False acceptance rate (FAR), Deduplication reduction (%), Average time per enrollment (seconds/minutes), Throughput per operator per hour, Manual adjudication rate (%), Applicant drop-off rate at enrollment kiosk, Credential issuance lead time, System availability / uptime (%), Integration success rate with legacy DBs, Cost per enrollment, Demographic accuracy gaps
• For the top three KPIs you just selected, please list your current baseline and the target value you would accept at pilot completion (e.g., FRR: baseline 6% → target ≤2%).
• How soon do you expect to see measurable improvement against those targets after pilot launch? Options: Within pilot period (≤3 months), 3–6 months post-pilot, 6–12 months, 12+ months, Unsure

What Tradeoffs Are You Willing — or Not Willing — to Make?

• Which outcome(s) are absolutely non‑negotiable from a regulatory or public-trust perspective? Options: Specific FRR threshold, No demographic disparity >X%, Full audit traceability, No credential issuance delays, Full compliance with named regulation (e.g., Real ID), Other
• Where could you tolerate a short-term compromise to gain long-term benefit (choose all that apply)? Options: Higher manual adjudication during migration, Slightly longer enrollment times to improve accuracy, Limited initial geographic pilot scope, Temporary SLA reductions during integration, Phased feature rollout, None of the above
• What level of temporary manual adjudication (%) would you accept during pilot without triggering escalation? Options: 0–1%, 1–3%, 3–5%, 5–10%, >10%, Unsure
• Are there legal, equity, or contractual limits that would make any tradeoff unacceptable? Please describe.

If the Pilot Only Shows One Thing, It Must Be This

• What single signal from the pilot would convince leadership the platform is fit for scale? Options: Achievement of numeric KPI thresholds, Successful legacy DB deduplication at X scale, Demonstrated demographic parity, Operational throughput targets met, Positive user/operator feedback, Other
• Select the pilot success signals you want measured (these must be instrumented and reported). Options: KPI thresholds met for enrolment accuracy, Deduplication rate improvement, Operator enrollment time under target, Manual adjudication below threshold, No critical integration failures, Public feedback sentiment positive, Security penetration tests passed, Other
• For each selected pilot signal, please define the numeric acceptance criteria and how it will be measured (data source and cadence).
• How large a pilot sample do you need for results to be credible (approx. applicants/day or total participants)? Options: <100 total, 100–500, 500–2,000, 2,000–10,000, >10,000, Unsure
• Who must sign off that the pilot passed (list specific roles/titles)?

Trustworthy Measurement — Avoiding False Signals

• What’s your biggest worry about pilot data being misleading or biased?
• What minimum statistical confidence or power do you require before treating pilot results as valid? Options: 90% confidence, 95% confidence, 80% confidence, No formal requirement, Unsure
• Which monitoring cadence feels right for pilot reporting (how frequently do you want interim reports)? Options: Daily, Weekly, Biweekly, Monthly, Milestone-based
• Which tools or dashboards do you currently use or prefer for KPI reporting and analytics? Options: Splunk/ELK, Power BI/Tableau, SaaS analytics (vendor provided), Custom internal dashboards, Statistical analysis in R/Python, Other
• What escalation thresholds should trigger immediate remediation (give one or two examples with numbers)?

Bias, Equity, and the Public’s Trust — What Will You Tolerate?

• If specific demographic groups show worse outcomes, at what point would you pause or limit rollout? Options: Any measurable disparity, Disparity > 1%, Disparity > 3%, Disparity > 5%, Only if public complaints arise, Unsure
• Which fairness metrics must we report during pilot (select all that apply)? Options: False rejection rate by demographic, False acceptance rate by demographic, Adjudication frequency by demographic, Coverage/participation rates by demographic, Statistical parity difference, Other
• What mitigation strategies do you expect if we detect bias (select preferred responses)? Options: Adjust algorithm threshold, Operator retraining and quality control, Targeted additional data collection, Pause rollout in affected sites, Public transparency report, Legal review
• How should we communicate bias findings to stakeholders and the public (preferred channels and tone)? Options: Formal agency press release, Technical appendix for auditors, Community stakeholder briefings, Internal memo only, Other

Who Signs, Who Monitors, and Who Owns the Numbers?

• Who will be the executive sponsor accountable for outcome acceptance at pilot and handover? Options: Program Director, Agency CIO, Identity Division Chief, Operations Lead, Other
• Which team will own day-to-day measurement, reporting, and issue triage during pilot? Options: Vendor delivery team, Agency analytics team, Joint vendor-agency working group, Third-party auditor, Other
• What contractual or governance controls are required to make acceptance binding (e.g., SLA credits, exit triggers)?
• If stakeholders disagree on whether acceptance criteria were met, what arbitration mechanism do you prefer? Options: Independent third-party validation, Joint review board, Executive escalation to program sponsor, Contractual mediation/arbitration, Other

From Targets to Test Plans — Ready to Lock in Three Priorities?

• If you had to name the three outcome priorities we should instrument first for this pilot, what would they be and why?
• Are you able to provide a representative, anonymized dataset for pilot validation (helps reproduce baselines)? Options: Yes — full sample available, Yes — partial sample with limitations, Not yet, but we can prepare one, No, cannot share
• What date do you need an initial baseline report by (approximate week/month)?
• Who should be included on the weekly outcome review invite list (names or roles)?
• What would success look and feel like to you and your team at pilot close (one-paragraph description)?

• Solution Experience Kickoff — Confirm Context & Success Criteria
• Scenario Walkthrough — Nominal Enrollment (Agency Data)
• Scenario Walkthrough — Edge Cases, Fraud Detection & Bias Assessment
• Integration & Throughput Validation — Dedupe, Migration Tradeoffs, and Performance
• Validation Review & Pilot Sign‑off

• Produce a dedupe accuracy and performance report with recommended thresholds and indexing changes.
• Quantify false rejection and false match rates across targeted demographic cohorts and identify gaps relative to KPIs.
• Confirm operator guidance and adjudicator SLAs are sufficient to prevent backlog and political risk.
• Produce a prioritized mitigation plan for any scenario failing acceptance thresholds.
• Deliver a bias assessment report with measured error rates per demographic and recommended threshold adjustments.
• Implement tuned detection thresholds and document rationale for each change.
• Define an adjudication staffing and SLA plan to handle projected exception volumes.
• Schedule follow‑up tests after mitigations are applied to confirm effectiveness.
• Integration Topology & Data Mapping Review
• Confirm deduplication accuracy at the volumes required and agree tuning needed to meet KPIs.
• Verify integration approach will not break existing operations and understand latency impacts.
• Validate throughput targets and identify concrete actions to remove identified bottlenecks.
• Agree on migration strategy options and associated manual adjudication volume projections.
• Introductions & Objectives
• Deliver a proposed migration strategy with estimated FTE, timeline, and expected manual adjudication load.
• Create the performance tuning backlog with owners to resolve identified bottlenecks before pilot.
• Finalize rollback and incident response runbook and distribute to stakeholders.
• Executive Summary of Scenario Outcomes vs KPIs
• Obtain formal mutual agreement to proceed to pilot with clearly documented acceptance criteria.
• Confirm all high‑priority mitigations are assigned with delivery dates prior to pilot start.
• Secure legal/commercial preconditions that protect portability and limit vendor lock‑in risk.
• Establish the pilot kickoff timeline, owners, and reporting cadence.
• Publish and circulate the Pilot Charter including site list, acceptance tests, KPIs, and dates.
• Execute required legal and data access agreements needed for pilot (NDAs, SOW addendum, data sharing).
• Assign owners and schedule the pilot kickoff meeting and weekly status cadence.
• Close out any outstanding high‑priority mitigations or document residual risk acceptance before pilot starts.
• Record and lock a crystal‑clear current state sentence that all parties acknowledge.
• Agree quantified consequences (cost/time/risk) that create urgency.
• Define the future state in operational terms and set measurable KPIs.
• Finalize scenario list, required datasets, and environment access for live runs.
• Establish validation protocol and decision gates for the experience series.
• Document and circulate the agreed one‑sentence Current State, Consequence summary, and Future State with KPIs.
• Deliver sanitized data extracts and grant environment access to vendor test team.
• Publish the prioritized scenario list and assign owners for each scenario.
• Distribute the validation checklist and signoff template for use in walkthroughs.
• Recap Scope & Acceptance Criteria
• Demonstrate the platform meets the enrollment time and dedupe targets for a typical applicant.
• Verify end‑to‑end interoperability with the selected legacy system(s) used in the scenario.
• Surface operator or UX issues that could degrade enrollment quality and propose immediate mitigations.
• Collect SME confirmation at validation checkpoints to avoid interpretation drift.
• Create a defect ticket for each issue observed, include severity and suggested mitigations.
• Adjust capture configuration and retest parameter(s) shown to affect KPI (e.g., camera settings, threshold).
• Schedule targeted operator training adjustments addressing identified technique problems.
• Record and store logs and artifacts from the run for audit and compliance review.
• Edge Scenario Overview & Expected Outcomes
• Validate fraud detection logic and that flagged cases follow the agreed adjudication workflow.
• Synthetic Identity / Fraud Run
• Risk Register & Mitigation Commitments
• Dedupe Accuracy Tests (Sample & Scale)
• Environment & Data Verification
• Current State (One Sentence)
• Demographic & Bias Sensitivity Tests
• Consequence Quantification
• Pilot Scope, Sites, and Success Criteria
• Live Walkthrough — Enrollment Flow
• Throughput & Stress Test Results
• Commercial, Legal & Data Portability Preconditions
• Degraded Input & Partial Document Scenarios
• Data Migration Tradeoffs & Strategy
• Tie Steps Back to Consequences

• Biometric Enrollment and Capture
• Document Authentication and Tamper Detection
• Remote Identity Proofing with Liveness
• Biometric Deduplication (1:N Search)
• Credential Issuance and Card Personalization
• Enrollment Kiosk Deployment and Provisioning
• Legacy Database Connector and Synchronization
• Federated Identity Integration (SAML/OIDC)
• HSM Key Management and FIPS Crypto
• Operator Training and Certification
• Real-time Fraud Detection and Synthetic ID Flagging
• Credential Lifecycle Management and Revocation
• Mobile SDK for Remote Enrollment
• Audit Logging with Tamper-Evident Export

Biometric Enrollment and Capture

• Which enrollment locations do you plan to support? Options: Fixed office sites, Mobile teams/vehicles, Temporary pop-up sites, Remote (user device), Combination
• Which biometric modalities must be captured in scope? Options: Face (photo), Single finger (2D/optical), Rolled fingerprint (live-scan), Iris, Voice, Multimodal (combination)
• What is the expected average enrollments per site per day during pilot and scale phases? Options: <50, 50-250, 250-1,000, 1,000-5,000, 5,000+
• Which capture quality / compliance standards must be met? Options: FIPS 201, ISO/IEC 19794, NIST SP 500-288, Agency-specific spec, No formal standard
• What maximum end-to-end capture time per enrollee is acceptable (operator time)? Options: <2 minutes, 2-4 minutes, 4-8 minutes, 8+ minutes
• Are there environmental or accessibility constraints (e.g., outdoor, low light, wheelchair access)? Describe.

Document Authentication and Tamper Detection

• Which document intake modes are required? Options: On-site document scanner, Mobile camera capture (remote), Hybrid (on-site + mobile)
• What types of identity documents must be supported? Options: Driver's license, Passport, National ID card, Birth certificate, Utility bills / proofs of address, Other
• Is machine-readable zone (MRZ) / barcode / OCR extraction required? Options: Yes, No
• Do you require visual security-feature analysis (hologram, UV, microprint) and tamper detection? Options: Yes - advanced feature checks, Yes - basic authenticity check, No
• Which languages/scripts must OCR and template matching support?
• Are there regulatory thresholds or acceptance criteria for false accepts / false rejects for document checks?

Remote Identity Proofing with Liveness

• Is remote (self-service) identity proofing required for the program? Options: Yes - primary channel, Yes - optional channel, No
• What identity assurance level (IAL) or equivalent target is required? Options: IAL1 (low), IAL2 (substantial), IAL3 (high), Custom / agency-defined
• Which liveness detection approaches are acceptable? Options: Passive liveness, Active challenge (movement/pose), Audio challenge, Combination / adaptive
• Which device/platform constraints must the remote proofing SDK support? Options: iOS, Android, Modern desktop browsers, Older devices (specify), Agency-managed devices
• What is the acceptable remote proofing failure rate or user retry budget before manual adjudication?
• Are accessibility accommodations or alternative flows required for certain populations? Describe.

Biometric Deduplication (1:N Search)

• What is the size of the biometric repository(s) that require 1:N deduplication? Options: <100k records, 100k-1M, 1M-10M, 10M-100M, 100M+
• Do you need cross-database deduplication across multiple legacy systems? Options: Yes - realtime, Yes - periodic batch, No - single repository
• What search latency is acceptable for a 1:N query (ms/seconds)? Options: <100ms, 100-500ms, 500ms-2s, 2-10s, No strict requirement
• What match score thresholds should trigger automatic match, possible match (manual adjudication), or no-match?
• Should dedupe operate continuously in production or only during migration/pilot? Options: Continuous real-time dedupe, One-time migration dedupe, Scheduled periodic batch dedupe, Hybrid
• Are there data protection or privacy constraints impacting how template data or search indexes are stored/queried?

Credential Issuance and Card Personalization

• Will the program issue physical credentials (cards) or digital credentials or both? Options: Physical cards only, Digital credentials only, Both
• Which card personalization features are required? Options: Magstripe, Contact chip (ISO7816), Contactless (NFC), Printed visual features, PKI certificate provisioning
• Do you require on-site personalization (per site) or centralized bureau issuance? Options: On-site personalization, Centralized bureau, Hybrid
• What monthly issuance volume do you expect during pilot and full rollout? Options: <1k, 1k-10k, 10k-100k, 100k-1M, 1M+
• Are there cryptographic or certification requirements for credentials (e.g., FIPS, Common Criteria, PKI interoperability)? Options: FIPS, Common Criteria, PKI / PIV-compatible, None specified, Other
• What acceptance tests for issued credentials (e.g., chip read, visual inspection, durability) must be included?

Enrollment Kiosk Deployment and Provisioning

• What form factors are needed for enrollment hardware? Options: Fixed desk workstation, Self-service kiosk, Mobile tablet kit, Vehicle-mounted, Operator handheld
• How many pilot sites and devices per site are planned? Options: 1-3 sites, 4-10 sites, 11-50 sites, 50+ sites
• Which peripherals must be supported and provisioned (camera, fingerprint reader model, printer, card encoder)?
• Who will manage kiosk provisioning, OS updates, and remote monitoring? Options: Agency IT, Vendor-managed, Third-party integrator, Hybrid
• Are there site-network constraints (airgap, NAT, low bandwidth) or power/environmental limits?
• Is secure provisioning (tamper-resistant configuration, device attestation) required for kiosks? Options: Yes, No, Undecided

Legacy Database Connector and Synchronization

• Which legacy data sources must be connected? Options: SQL (e.g., MSSQL), Oracle, NoSQL, Flat files / CSV, Custom API, Other
• Do you require real-time change-data-capture (CDC) synchronization or scheduled batch imports? Options: Real-time CDC, Scheduled batch, One-time migration
• What is the expected total record count and average record size to be synchronized?
• Are there complex field transformations, schema mappings, or PII reformatting required? Options: Yes - extensive mapping, Yes - minor mapping, No
• How should conflicts and duplicates be handled during sync (auto-merge, flag for manual adjudication)? Options: Auto-merge rules, Flag for manual review, Custom merge rules
• Are retention, legal hold, or jurisdictional residency rules applicable to synchronized data?

Federated Identity Integration (SAML/OIDC)

• Which federation standards are required for integration? Options: SAML 2.0, OIDC / OAuth2, Both, Other
• Which external identity providers or partner systems must be federated?
• Are specific attribute mappings, claims, or transformations required for SSO? Options: Yes, No
• Do you require central session management and single logout across federated systems? Options: Yes, No, Conditional
• Is multi-factor authentication integration required as part of federation? Options: Yes - required, Optional, No
• Are certificate management and metadata exchange processes defined for trust establishment? Options: Yes, No, Need vendor guidance

HSM Key Management and FIPS Crypto

• Do you require on-prem HSMs, cloud HSMs, or HSM-as-a-service? Options: On-prem HSM, Cloud HSM (managed), HSM-as-a-service, No HSM required
• Which FIPS level or crypto certification is mandated (e.g., FIPS 140-2 Level 2/3)? Options: FIPS 140-2 Level 2, FIPS 140-2 Level 3, FIPS 140-3, No FIPS requirement, Other
• Are HSM key lifecycle policies defined (rotation frequency, backup, split-knowledge)? Options: Yes - defined, Partially defined, No
• Is separation of duties and multi-person authorization required for key operations? Options: Yes, No
• Which systems will integrate with the HSM (card issuance, PKI, tokenization)?
• What logging, audit, and export requirements exist for key events and crypto operations?

Operator Training and Certification

• How many operators and administrators require initial training and certification? Options: 1-10, 11-50, 51-200, 200+
• Which training delivery modes are preferred? Options: Onsite instructor-led, Virtual instructor-led, Self-paced eLearning, Train-the-trainer
• What certification levels or passing criteria should be enforced for operators? Options: Basic operator, Advanced operator, Supervisor/Adjudicator, No formal certification
• Should training include hands-on scenarios using representative agency data and workflows? Options: Yes - required, Optional, No
• What cadence is required for refresher training and re-certification? Options: Every 6 months, Annually, On major release only, Other
• Are compliance or background-check prerequisites required before operator certification? Options: Yes, No

• Statement of Work (SOW)
• Master Services Agreement (MSA)
• Service Level Agreement (SLA)
• Commercial Pricing & Payment Schedule
• Data Migration & Portability Plan
• Pilot Criteria & Acceptance Tests
• Security & Compliance Addendum
• Data Processing Agreement (DPA)
• IP Rights & Software Licensing Agreement
• Source Code Escrow / Escrow Agreement
• Exit, Transition & Portability Agreement
• Third-Party & Subcontractor Disclosure
• Change Control & Change Order Process
• Training, Knowledge Transfer & Certification Plan
• Insurance, Indemnity & Risk Allocation Schedule
• Governance, Reporting & Steering Committee Charter
• Privacy, Equity & Bias Mitigation Plan
• Regulatory & Audit Support Commitment

• Pilot Outcomes Diagnostic (Solution Experience)
• Rollout Acceptance & Scale Decision
• Lessons Learned & Continuous Improvement Workshop
• Issues & Enhancements Triage (Recurring)
• Executive Summary & Strategic Decision

• Keep the issues/enhancements tracker current and prioritized for engineering and ops work.
• Draft and circulate formal acceptance memo reflecting decision and any conditions for sign-off.
• Update project plan with phased rollout dates, owners, and gating KPIs.
• Legal/Procurement to prepare any required change orders or SLA amendments.
• Communications owner to prepare internal/external messaging for the rollout decision.
• Workshop Framing & Desired Outputs
• Produce a prioritized improvement backlog with measurable acceptance criteria for each item.
• Identify root causes for recurring failures and agree on corrective actions (technical, operational, training).
• Capture operator and equity feedback and encode required mitigations into the backlog.
• Assign owners and timelines so improvements are actionable and traceable.
• Populate the shared issues/enhancements tracker with prioritized backlog items and acceptance tests.
• Ops to schedule targeted operator retraining sessions and share materials within 10 business days.
• Engineering to estimate effort and provide timeline estimates for top 5 technical fixes.
• Equity lead to propose demographic bias mitigation experiments and measurement plan.
• Review Open Critical Issues
• Introductions & Meeting Objectives
• Commit critical fixes to the next available sprint with owners and clear acceptance criteria.
• Ensure timely stakeholder communications for high-impact items.
• Update tracker statuses and assign SLO-driven ETAs for all open critical issues.
• Engineering lead to add committed fixes to sprint board and notify QA of acceptance tests.
• Communications lead to send weekly status digest to executive and operational stakeholders.
• Concise Executive Summary
• Secure executive decision on whether to scale, conditionally scale, or extend the pilot.
• Obtain approval for required funding and procurement actions tied to the chosen option.
• Agree on executive communications and oversight cadence for the next phase.
• Prepare executive decision memo and circulate to signing authorities.
• If approved, allocate budget and instruct procurement to execute amendments/change orders.
• Publish executive-facing status summary and schedule oversight checkpoints for the rollout phase.
• Establish a single, agreed one-sentence current state describing what is breaking and who is affected.
• Quantify the operational and compliance consequences of KPI shortfalls in concrete terms (hours, $/case, complaint risk).
• Validate which aspects of the future state the platform proved and which require remediation, with stakeholder confirmation.
• Produce an agreed list of prioritized remediation items and data artifacts required for root-cause analysis.
• Customer to deliver anonymized pilot datasets and logs for flagged scenarios within 3 business days.
• Platform engineering to run targeted diagnostics on top 3 failure modes and deliver findings in 5 business days.
• Schedule technical deep-dive session with ops and vendor engineers to resolve top-priority items.
• Update shared KPI dashboard with final, validated numbers and mark items needing remediation.
• Executive Recap of Pilot Findings
• Reach a documented acceptance decision (full acceptance, conditional acceptance, or remediation required).
• Agree a phased rollout plan with timelines, owners, and go/no-go gates tied to KPIs.
• Identify contractual or funding actions required before scale and assign owners to complete them.
• Acceptance Criteria Mapping
• Timeline Walkthrough of Pilot Events
• One-sentence Current State
• New Issues & Customer Escalations
• ROI & Operational Impact
• Options & Recommended Path
• KPI Dashboard Walkthrough
• Facilitated Root-Cause Analysis
• Risk & Mitigation Review for Scale
• Prioritization & Sprint Commitments
• Quick Wins & Operational Adjustments
• Operator & Field Feedback
• Phased Rollout Plan & Timeline
• Consequence Quantification
• Funding & Procurement Implications
• Scenario Proofs (Diagnosis -> Proof)
• Equity, Bias & Public Feedback Review
• Status Communications & Stakeholder Updates
• Commercial/Contractual Implications
• Decision & Endorsement