Frozen document. Dates and status refer to its original source. Private resources and unreviewed images are unavailable.

Atlas insurance intake research

Access date for every source: 2026-10-07. US workflows only. Six wizards: life application, evidence of insurability, death claim, Medicare supplement application including replacement, annuity withdrawal, and annuity servicing.

Boundaries

These are researched workflow patterns for a fictitious Atlas prototype using synthetic people, simulated evidence, payments, and legacy systems. They are not legal, financial, underwriting, or eligibility advice. The sources describe particular carriers, contracts, jurisdictions, and form editions. No source authorizes Atlas to determine real eligibility. All stages and rule examples labeled prototype are design choices. Numeric thresholds, rates, deadlines, exact diagnoses, state protections, and required notices need independent approval before any production use.

Keep Contentful forms declarative through approved SDUI components and bounded conditions. The Fastify BFF owns TypeBox validation and derives the active route; the browser uses the agreed tRPC interface. Camunda owns submitted case progress, evidence requests, review tasks, and simulated outcomes. Contentful must not execute arbitrary scripts or underwriting expressions. This architecture is the supplied project constraint, not a finding from the insurance sources.

1. Life application

Sources:

• Protective individual life application packet, New Jersey example. The viewed packet contains older form editions, including application 06/2016 and replacement 1/05. Pages 5-7 separate insured, owner, plan, beneficiaries, existing coverage, and replacement. Its replacement question triggers state forms. It also asks whether existing policy values will finance the purchase.
• Protective application process. Describes application, medical interview, paramedical exam, then underwriting review.
• Pacific Life underwriting. Describes accelerated and modified underwriting routes. The no-exam route has carrier-specific conditions; it is not a universal promise.

Prototype stages: applicant and state → insured and owner → requested coverage → beneficiaries → existing coverage and replacement → health and lifestyle disclosures → authorizations → review → simulated submission → underwriting tasks.

Answer branches:

• Owner differs from insured: collect owner identity, relationship, and authority. Trust owner: collect trust name/date and synthetic trustee evidence.
• Multiple primary or contingent beneficiaries: add repeatable beneficiaries and validate each populated class totals 100 percent. No contingent beneficiaries is an explicit choice.
• Existing policies or pending applications: show repeatable company/policy/amount entries.
• Replacement or financing from existing policy values: open replacement details, comparison acknowledgment, and simulated disclosure requirements. Do not issue a recommendation to replace.
• A disclosed medical condition, medication, tobacco use, or hazardous activity: open structured details, dates, treatment/provider, and follow-up questions. A positive answer does not mean denial.
• Choose simulated accelerated or full-review scenario through a server-owned fixture. Do not infer a real no-exam right from a browser rule.

Review and missing information: summarize every active answer and why extra evidence is requested; link edits to their originating stage. Missing owner authorization, incomplete beneficiary allocation, or incomplete positive-answer details prevents final attestation. After submission, a reviewer can request one specific item and resume the case when it arrives. Evidence examples are synthetic authority papers, medical authorization, replacement acknowledgment, and simulated exam/provider report.

2. Evidence of insurability

Sources:

• MetLife EOI explanation. Requested coverage above the plan's guaranteed-issue amount triggers EOI; dependents may need their own medical information. Additional records or exams may be required. Review and a coverage decision follow submission.
• MetLife Statement of Health common questions. Search-indexed first-party text also names late enrollment and previously waived coverage as possible triggers. Plan rules and effective dates vary. The page returned an open error, so use only these indexed facts and do not copy exact deadline/effective-date rules.
• Principal EOI integration announcement. First-party 2026 account of guided EOI collection and follow-up information detection. Supports embedding EOI in enrollment, not Atlas underwriting criteria.

Prototype stages: locate synthetic employer/plan request → person requiring EOI → verify requested and existing coverage → health screening → expanded disclosures → medical authorization → review and attest → review queue.

Branches: employee versus spouse/dependent creates separate subject records and signatures. Above fixture guaranteed-issue amount, late enrollment, or previously waived coverage opens EOI. If a fixture says EOI is unnecessary, show an explanation and return to the referring enrollment workflow without asserting actual coverage. Any positive screening answer opens a condition/treatment/provider detail group. Unknown answer offers save and return or a reviewer clarification request, not a forced negative answer.

Review and evidence: highlight missing disclosures or authorization. After submission, records-needed and exam-needed are separate tasks with named requirements and status. The prototype reviewer may record simulated approved, declined, or needs-more-information outcomes. Existing and requested coverage remain separate; an EOI draft never changes active coverage. Evidence is a synthetic signed authorization plus simulated provider records or exam completion when requested. Plan threshold and routing reason come from versioned server fixtures.

3. Death claim

Sources:

• New York Life start a claim. Initial reporting can use deceased identifying details and date/cause of death; the insurer follows up with the beneficiary when more information is needed.
• New York Life death benefit proceeds form, current proceeds page 03/2026 with older explanatory pages. Requests an original death certificate and separates individual from trust/estate/corporate beneficiaries. Each beneficiary completes their own form. Settlement choices depend on the contract.
• Prudential group beneficiary form. First-party indexed text names court-issued estate authority and minor-estate guardianship evidence. Full opening returned an error. Treat these as carrier-specific examples, not universal legal requirements.

Prototype stages: report deceased and locate policy → reporter role → claimant/beneficiary details → death circumstances → authority and documents → simulated settlement preference → review → claim received → claims review.

Branches: reporter who is not beneficiary can notify death without completing beneficiary payment elections. Unknown policy number uses identifying details and enters simulated policy-location review. Individual adult, minor, trust, estate, and corporation each open their own identity/authority fields. Accident opens incident details and a simulated supporting-report request; foreign death can request synthetic additional evidence as a prototype choice. Unknown cause is allowed for initial notification and flagged for review. Multiple claimants create separate claimant packets rather than sharing tax/settlement answers.

Missing information: allow initial notification with an unavailable death certificate, then show an outstanding evidence task. Full claimant attestation requires active identity and authority fields. Death certificate quality/mismatch or authority uncertainty becomes a review task, not automatic rejection. Synthetic evidence can include certificate, trust certification, estate appointment, guardianship order, and incident report. Submission records receipt; simulated adjudication and simulated payment are later states.

4. Medicare supplement application and replacement

Sources:

• Medicare get ready to buy. Federal Medigap open enrollment lasts six months starting the first month a person has Part B and is at least 65. It does not repeat annually. Outside it, underwriting may apply unless a protection applies. Under-65 access varies by state.
• Medicare changing Medigap policies. Identifies switching protections, evidence of coverage termination, and a 30-day free look. Consumers should not cancel old coverage before deciding to keep new coverage.
• California insurance department Medigap advisory. A 2020 jurisdiction example describes a birthday protection with same-or-lesser benefits. It proves jurisdiction changes the workflow; it is not a current nationwide rules table.
• Mutual of Omaha eApp guide. First-party indexed guide describes applicant, Medicare, payment, producer, review, then applicant signature. Full open returned an error; exact screens are not independently verified.

Prototype stages: identity and residence → Medicare A/B and requested effective date → current coverage → claimed enrollment/protection route → route-specific questions/evidence → fictional plan selection → premium/payment preference → replacement acknowledgments if applicable → review/attestation → enrollment review.

Branches: current Medicare Advantage opens planned return-to-Original-Medicare details and human coordination review. Existing Medigap plus replacement intent opens old insurer/plan/effective date and replacement acknowledgment. No Part B or unclear dates opens missing-information tasks and does not manufacture eligibility. Claimed initial OEP, claimed guaranteed issue, state-specific protection, and underwritten application are distinct route values. OEP candidate dates are computed server-side for a fixture and labeled pending verification. GI asks for reason, prior coverage, event/end date, and synthetic notices. State protection and under-65 applicants route to reviewer verification. Only the fixture underwritten route opens health disclosures; positive disclosures open detail groups and review, not automatic refusal.

Missing information: absent Medicare dates, loss-of-coverage notice, or replacement detail blocks the corresponding complete-application submission. Permit save/return and a reviewer evidence request. Do not suggest cancellation or claim that annual Medicare enrollment creates Medigap underwriting protection. Evidence examples are a synthetic Medicare card, coverage termination notice, prior coverage summary, and route acknowledgment. Fictional premium is labeled simulated. Selection/submission does not establish effective coverage.

5. Annuity withdrawal

Sources:

• Fidelity fixed deferred annuity systematic withdrawal form. Establish/change/delete are separate requests; deletion skips details. It separates amount calculation, schedule, delivery, withholding, and signatures. New EFT can need bank evidence; all contract owners sign. Some conditions need a Medallion guarantee, distinct from notarization. Limits are contract-specific; do not import them as Atlas defaults.
• Fidelity annuity FAQ. Directs users to the withdrawal form for their product when closing a Fidelity annuity and to the issuing carrier for other annuities.
• Nationwide Destination Future. Withdrawals can reduce benefits and incur charges/tax effects. These details depend on the contract and transaction.

Prototype stages: select synthetic contract → owner and authority → request type → amount/calculation → schedule if recurring → delivery details → withholding preference → impact acknowledgment → review/sign → servicing review.

Branches: one-time partial, full surrender, establish recurring, change recurring, and stop recurring. Stop skips amount/schedule/payment setup. Change starts from existing instructions and collects changed fields. Qualified-contract fixture exposes a requested RMD review option; Atlas does not calculate real tax obligations. New bank opens synthetic bank-owner/evidence fields. Joint owner or representative opens additional signatures/authority. Recent address change, larger simulated withdrawal, bank mismatch, and contract rider restrictions create review tasks from explicit fictional fixtures. Full surrender gets a separate confirmation of contract closure effects.

Missing information and evidence: amount must be positive and fit a synthetic available balance; recurring schedules require frequency/start date. Missing signature or new-bank evidence opens a repairable task. Evidence is synthetic bank proof, authority, and guarantee where the fixture requires it. Display simulated fees/net amount separately from the requested amount. Do not recommend withholding or assert penalty exemption. Submitted, accepted for processing, and simulated disbursed are separate states.

6. Annuity servicing

Sources:

• Fidelity beneficiary annuity form, viewed edition 06/26. Person/trust/entity, primary/contingent shares, and all-owner signatures differ. Trust owners need trustee signatures; representative authority must permit beneficiary changes. The NY Retirement Reserves variant addresses annuitant beneficiaries only. Search excerpts conflict with the viewed current PDF; use the current document, not old excerpt text.
• Fidelity annuity FAQ. Name/address and beneficiary changes use product-appropriate forms or account tools. Divorce division requests court-filed decree, settlement agreement, and signed instructions.
• Pacific Life online services guide. Shows contract information and separate financial/nonfinancial services; availability depends on contract features.

Prototype stages: select contract → change category → authority → before/after details → evidence → review/sign → service review → simulated recorded change.

Branches: address/contact, legal name, beneficiary, owner/trustee, and bank instruction change. Beneficiary change explicitly distinguishes replace-primary, retain-contingent, and replace-contingent. Populated beneficiary classes total 100 percent. Trust/entity beneficiary changes ask identifying details and authority; do not infer legal effects. Joint owner requires all fixture-required signers. Owner/trustee change and divorce-related request always go to reviewer authority assessment. A contract variant can make a category unsupported and offer a service-review task. Bank changes use the bank verification subflow; financial withdrawals use wizard 5.

Missing information and evidence: collect only evidence relevant to the chosen change, such as synthetic name-change document, trust certificate, authority record, bank proof, or divorce papers. Show exact before/after values and full resulting beneficiary list before signing. Removing or replacing a beneficiary is explicit. Post-submission reviewers can request corrected evidence without making the user restart. A recorded change is confirmed only after the simulated servicing system accepts it.

Shared interaction and validation contract

Prototype choices for all six:

• Save after every stage. Server derives active stages and requirement reasons from versioned forms, answers, and server-owned fixture data.
• Yes/no/unknown are distinct; unknown creates clarification where allowed. Avoid default negative health answers.
• Hide irrelevant groups, mark their answers inactive, and exclude them from submission. On a controlling answer change, warn before clearing affected visible answers. Review must show the final active packet.
• Review shows complete, missing, and needs-review separately. Completeness is not approval.
• Final attestation binds an answer snapshot and form/rule version. An edit after attestation requires renewed attestation.
• Evidence requirements have category, reason, subject, state, and due information if the fixture supplies it. Upload status is separate from reviewed/accepted status.
• BFF returns structured field/stage errors and routing reasons. Camunda waits for review/evidence events and preserves an audit trail. CMS controls copy and supported presentation, not unrestricted business decisions.

Research limits

These sources do not establish an Atlas production insurance ruleset. Carrier packets contain legacy editions, and three pages were usable only through first-party search-indexed text. They support workflow choices, not exact current forms. The California advisory is deliberately a jurisdiction example, not a 2026 legal determination. No copied carrier threshold, medical criterion, tax table, coverage price, approval timer, or guaranteed-issue determination should become an unlabeled prototype rule. Synthetic fixture choices should be documented alongside each journey before implementation.