PEA-555 · Discovery v10 (corrects Mike's role: CEO and owner of Safe Life) · Evidence as of Jul 28, 2026 · Doc dated Jul 29, 2026

New Agent Onboarding: Signed to Ready for Calls

For Aaron and Mike. Evidence: the agent's 25-email archive, an every-word sweep of his live SureLC portal (40+ views across 20 numbered files), and fact-checked research on SureLC, NIPR, and LIMRA (sources indexed in the appendix). Every load-bearing claim in the tables is tagged V verified, H hypothesis, U unknown; prose repeats table claims or cites the appendix. Unknowns are named blockers, never guessed.

Pre-review discovery: the Mike + Aaron review has not happened. Tyler owns scheduling it this week and folding answers into the next version.
A real agent, fully "onboarded" by every email he received, can sell exactly two carriers of fixed life today (pending per-state appointment confirmation). Annuities are blocked in all eleven of his states, three contracts show an uninterpretable status, his CE looks unreported, one license already lapsed, and no person or system owns telling him any of it. That silence is the product.
0 Sign + intro1 Licenses2 SureLC account3 Profile complete4 Request per carrier5 Anna's desk6 Carrier approval7 Training gates8 Call readiness (proposed)9 Declared ready (provisional)

The answer in ten lines

  1. The real sequence has ten steps; contracting is only the middle of it.
  2. Every step has one accountable owner today and a proposed product owner.
  3. State differences: licenses, CE clocks, product training, carrier state lists, and appointment timing all vary per state; all eleven appointment rules are statute-verified (table below); the single open cell is Indiana's filing window.
  4. IMO differences: branded SureLC per agency, agency-set contract type (LOA here), agency-enabled carrier lists, transfers driven by prior NIPR appointments.
  5. The checklist lives in Peach Pilot as a readiness engine reading trustworthy signals; SureLC stays the contracting system of record, read, never duplicated.
  6. Checklist versus bot: checklist owns determinable state; bot owns explanation and may never declare readiness or reveal disclosures.
  7. Uplines see track-level progress and blockers, never background answers or documents.
  8. Six tickets, dependency-ordered: T1 and T6 start now, T2 and T4 unlock when T1 lands, T3 and T5 stay drafts until the interviews answer their inputs.
  9. Metric: signed-to-first-writable days and signed-to-declared-ready days, instrumented from day one, baseline from the next cohort.
  10. Riskiest unknown: what At Carrier dwell means. Nothing may interpret it until Anna answers.

The story first

A new agent signed with Safe Life in early summer 2026. His intro call with Mike, Safe Life's owner, covered comp and training out loud, never in writing V. He activated SureLC through Safe Life's branded link V. On Jul 6 at 11:02 AM he created his first contracting request, American Amicable. Anna Collins at the Safe Life desk packaged and delivered it that evening at 5:30 PM V. The carrier made the contract effective Jul 11, marked Completed Jul 14 V. Occidental, a related carrier, appeared as a second active contract with no request ever filed V; why is a hypothesis H.

On Jul 11 he created three more requests in one 30-minute sitting: Americo, Banner, Mutual of Omaha. Anna processed all three the evening of Jul 13: two emailed to carriers, Banner delivered electronically through its transfer channel V. As of Jul 28 all three still show At Carrier, and nothing anywhere says whether carriers are still reviewing or nobody updated the record U.

Meanwhile the portal quietly says he cannot sell annuities in any licensed state until he takes a state course, his Georgia CE shows zero credits reported although his course history shows the hours done, his training sync has been failing since Jul 11, and a nonresident license expired unnoticed in April V. Nobody owns telling him. His honest position today: fixed life with American Amicable and Occidental, subject to per-state appointment confirmation, and nothing else.

Who's who, and six words you need

Aaron: Peach Pilot, assigned this issue, owns build priority. Mike: CEO and owner of Safe Life Policy LLC, the agency this agent signed with; he owns the readiness bar, and Anna's desk reports up to him. Anna Collins: Safe Life's contracting desk. Tyler: Peach Pilot, owns this discovery and the interviews. Safe Life Policy LLC: the IMO; Mike's agency. Peach Pilot: us.

IMO: the marketing organization an agent signs with. Holds carrier relationships and a share of comp.
BGA desk: the agency's contracting staff (Anna). SureLC has a literal At BGA review stage.
NIPR: the national registry of who is licensed where. SureLC imports identity and licenses from it, read-only to the agent.
Appointment: a carrier telling a state "this agent may sell for us here." Per state, after licensing.
Writing number: the agent ID a carrier issues at approval. Normally required before submitting business; in just-in-time (JIT) states the carrier may file the appointment after the first application.
LOA: Licensed Only Agent, this agent's type. Comp flows through the upline, so SureLC never asked him for banking.

The one-page sequence

One accountable owner per step; steps 8 and 9 have no owner today, so the owner shown there is our proposal, flagged as such. At a glance, by owner lane: Agent owns 1 licenses, 3 profile, 4 requests, 7 training. Agency (Anna's desk) owns 2 invite, 5 review and delivery. Carrier owns 6 approval and writing number. Upline owns 0 intro, 8 call readiness (proposed), 9 declared ready (proposed).

#StepAccountable todayProduct ownerTrustworthy signalWeak or missing todaySource
0Sign + intro call (comp, expectations)UplineUpline; product writes the comp sheetCall held (calendar)Comp only verbalV: email 01
1State licenses (resident + nonresident)AgentAgent; product monitorsLicense active in NIPRRenewals lapse silently (NM, 4/30)V: portal 04, 05
2SureLC account activationAgency (owns the invite)Product nudges agentActivation emailNothing if invite missedV: email 02
3Profile completion (contact, 19 questions, signature auth, E&O)AgentAgent; product tracksRed notices cleared; Create Request unlocksYellow items bite later at carrierV: portal 02, 09, 10, 13, 14; research 6, 7
4Contracting request per carrierAgent (creates and signs)Agent; product recommends orderRequest notes: created + reviewedSigning feels like "submitted," is notV: portal 16, 17; research 2
5BGA desk review + deliveryAnna (agency desk)Anna; product mirrors her queueDelivery notes, timestampedAgent never told packet left the deskV: portal 16, 17
6Carrier review to approval + writing numberCarrierProduct watches signalsWelcome email; Contracts page recordAt Carrier dwell uninterpretableV: emails 04, 05; portal 18; research 3, 5
7Product training gates (AML done; Best Interest, annuity, LTC, Medicare unmet)AgentAgent; product computes per stateCertificate on fileState CE reporting lags (GA 0 of 24 shown, hours done)V: portal 11, 11a, 12; research 8, 9
8Call readiness setup (proposed inventory below)Upline (proposed; unowned today, decision 1)Upline works a visible checklistEach item checkableAbsent from every captured systemU
9Declared ready to take calls (provisional bar below)Upline (proposed; decision 1)Upline clicks it against evidenceThe product's readiness gateNo definition exists todayU

Step 8, proposed inventory for Mike to correct: CRM access, dialer or phone setup, a lead source assigned, script or presentation reviewed with the upline, compliance and call-recording rules covered, carrier e-app access confirmed, first calls shadowed, and an explicit first-call authorization. Built from what the evidence shows is missing; Mike's version replaces it (T6).

Step 9, provisional readiness bar until Mike defines the real one: licensed in the target state, at least one carrier contract active with a writing number or confirmed JIT path, product training satisfied for what he will pitch, E&O current, step 8 complete, and the upline's explicit go. Ships in no product until T6 replaces or confirms it.

The status model: what At Carrier actually means

Three requests show At Carrier since Jul 13 V. Two readings compete: carriers genuinely still reviewing (both transfers could involve release handling), or already resolved with nobody updating SureLC. Vendor docs: only a few carriers send automated feeds; agencies update most requests by hand V. The evidence cannot separate the readings U. What decides it, strongest first: a welcome email or writing number (decisive), Anna's per-carrier update habits (strong), a carrier feed record (strong), dwell time alone (worthless). Until Anna answers, no product logic may interpret At Carrier dwell. Highest-risk misread in the domain, in both directions.

Reconciling an apparent contradiction: SureLC is the system of record for the contracting pipeline, and still not a source of truth for readiness. Both are true: the stages and red/yellow gates are real and enforced; late-pipeline statuses depend on manual upkeep; readiness spans licensing, training, and call access SureLC does not model.

Claim-to-evidence matrix

ClaimTagSource and date
Red notices block creating requests; yellow allowed but bites at carrier reviewVPortal 02 welcome banner (Jul 28); research 6, 7
Producer signature is not carrier submission; BGA review sits betweenVResearch 2; notes: reviewed Jul 11, delivered Jul 13 (portal 16)
Anna's desk packages, delivers (email or electronic), copies producer, timestamps everythingV19 request notes (portal 16, 17; Jul 6 to 13)
Writing numbers issued at approval; recorded on Contracts pageVResearch 5; portal 18 (both codes present)
Writing codes in the portal but hidden by responsive layout at narrow widthVPortal 18 capture note (a11y tree, Jul 28)
Cause of the At Carrier dwell for Americo, Banner, MoO (carrier review versus bookkeeping)UUndecidable; see status model
Occidental contract with no request = sister-company bundlingHPortal 17, 18; mechanism unverified (research open q1)
Agent's only active contracts today: American Amicable + Occidental, fixed lifeVPortal 18 (Jul 28)
Whether he may submit business per licensed state today (appointment or JIT)UNeeds NIPR per-state check or Anna; research open q2
Annuities blocked in all licensed states until state training doneVPortal 11, 11a (per-state detail, Jul 28)
AML satisfied once via LIMRA reciprocity (MoO course, Jun 15)VPortal 11, 12; research 9
GA CE hours complete but state-reported count shows 0, PendingVPortal 11 vs 12 (Jul 28)
LIMRA training sync failing since Jul 11VPortal 11 error banner
Transfers caused by prior IMO appointments visible in NIPRVPortal 18 NIPR tab; research 13
Comp verbal only; changed mid-onboarding (Americo cut)VEmails 01, 10
Release and contracting-debt norms on transfersUResearch open q3; needs Anna

Readiness snapshot for this agent (evidence as of Jul 28, 2026)

Sellability is a computation, not a status; each component shows separately, and the columns mirror the step 9 bar exactly so the two cannot drift. Net stays conservative where a component is unknown. Absence is honest: "none found" means no gate appeared in the captured views, weaker than verified clearance, so carrier-specific requirements stay U until checked.

CarrierContract + writing numberDelivery channelAppointment per stateTraining (fixed life)E&OE-app accessUpline goNetSource
American AmicableV active 7/11, code on Contracts pageElectronic packet, 7/6U not verified per stateNone found; carrier courses unchecked UPolicy active V; per-carrier sufficiency UU not capturedAbsent today USellable pending per-state appointment confirmationPortal 17, 18, 13
OccidentalV active, code present; no request filed HNone visible (bundled H)USameSameUAbsent USame, plus origin for AnnaPortal 18, 13
AmericoNo: At Carrier since 7/13Emailed 7/13n/a yetSameSamen/an/aBlocked (U on cause)Portal 16 notes
BannerNo: At Carrier 7/13, transferElectronic, transfer channel, 7/13n/a yetSameSamen/an/aBlocked (U, possible release handling)Portal 16 notes
Mutual of OmahaNo: At Carrier 7/13, transfer, no TXEmailed 7/13n/a yetSameSamen/an/aBlocked (U on cause)Portal 16 notes
Any carrier, annuitiesn/aUnmet, all 11 states VSameBlocked by state trainingPortal 11, 11a
Any carrier, LTC or Medicaren/aUnmet or absent VSameBlocked by state training or AHIPPortal 11a

Anna's desk, as evidenced (a strawman for her to correct)

Built only from the 19 timestamped request notes (portal 16, 17); unmarked steps are V, gaps are U. Anna corrects this in the review, and her corrections replace it.

  1. Invite and account setup: not evidenced from the desk side U; the agent received the branded activation link (email 02)
  2. Agent creates and signs; the desk sees it after producer review (created 11:02 AM, reviewed 11:08 AM, Jul 6)
  3. Desk review and packaging: observed turnaround same-day (American Amicable, Jul 6) and two days (wave two: reviewed Jul 11, delivered evening Jul 13). What she checks, and how not-in-good-order items are handled, unknown U; this case was clean
  4. Delivery per carrier, as observed: American Amicable electronic packet; Americo emailed; Mutual of Omaha emailed; Banner electronic through its transfer channel. A producer copy sent every time
  5. Carrier follow-up and chase cadence: not evidenced U
  6. Writing-number intake: numbers exist on the Contracts page, but where they arrive first and who enters them is unknown U; research 5 says manual agency entry is the norm for most carriers
  7. Marking Completed: American Amicable went Completed Jul 14, three days after the carrier's Jul 11 effective date, consistent with manual after-the-fact marking H
  8. What the desk does not own, per the evidence: licensing, product training, CE, call readiness (V by absence)

Where each readiness field comes from

The snapshot's columns are only buildable if every field has a source and an acquisition path; this is that map, and T1 to T5 scope against it.

FieldSource of truthHow the product gets itTicket
Licensed statesNIPR, via the SureLC profileRead from SureLC; later, NIPR PDB alerts for renewals and lapsesT1, monitor later
Contract + writing numberCarrier welcome email; SureLC Contracts pageT2 parses the welcome email (decisive signal); SureLC record as corroborationT2
Appointment per stateNIPR per-state appointment recordsPer-state PDB lookup keyed to the verified rule table; interim answer from AnnaT3, interim T6
Product training per stateCE & Training certificatesRead certificate records; state rule table maps training to product linesT1, T3
E&O currentE&O policy record and declaration pageRead policy dates; per-carrier sufficiency needs carrier minimums (open)T1
E-app accessCarrier portalsAgent self-check with upline verification in the step 8 checklistT4
Upline goThe uplineAn explicit click against the evidence panelT4, T5
At Carrier meaningAnna's deskBlocked on her SOP; until then the field renders as unknown, never inferredT6 gate on T3

The concept: a readiness engine, not a checklist page

Licensing (agent, NIPR) Contracting (Anna, carrier) Training (agent, per state) Call readiness (upline) Readiness enginetrustworthy signals only What can you sell,where, and whatis blocking you?

The agent runs on four tracks at once: licensing, contracting, product training, call readiness. Different owners, different failure modes, no connecting system. SureLC models one track, email carries the decisive signals for another, training lives in a third place, call readiness lives nowhere. The product reads the trustworthy signals from each track (NIPR license state, welcome emails with writing numbers, training certificates, the upline's explicit go) and answers one question per agent: what can you sell, where, and what exactly is blocking you. SureLC and the inbox cannot do this by design. That gap, not a prettier checklist page, is the ownable thing.

Checklist versus the Q&A bot

The rule: the checklist owns anything with a determinable state, an owner, and evidence. The bot owns explanation, reads checklist state for status questions, and carries hard prohibitions.

QuestionBelongs toWhy
"Is my Americo contract done?"Checklist (bot may read it aloud)Determinable state with evidence
"Why is my Americo still pending?"Bot, reading checklist stateExplanation over live status
"What do I need to sell annuities in Georgia?"Checklist computes; bot explainsState rule + training records = determinable
"What is a writing number?"BotGlossary explanation
"What's my comp on Eagle Select?"Neither yet: comp sheet is step 0's fixComp is contractual, needs a written source first
"Am I ready to take calls?"Checklist gate onlyThe bot may never declare readiness
"What did I answer on background question 7?"Neither surfaces it to anyone but the agentDisclosure privacy

Bot prohibitions, explicit: it may not declare readiness, may not interpret At Carrier dwell, may not expose background disclosures or documents, and may not state carrier or state rules it cannot source. These become acceptance criteria in T4/T5 and the bot's system prompt.

State and IMO differences

Appointment timing, the eleven states

Operative statutory text checked Jul 29, 2026; official state sites where reachable, two rows via legal republishers (flagged, small currency risk). A 2009 carrier guide misclassified Florida, so it is treated as known-unreliable and carries no weight here. Rules are normalized: Pre-appointment (appointment must exist before acting), Appointment on filing (effective the moment the carrier submits), Explicit just-in-time (statute expressly permits the producer to act before appointment), Insurer-side acceptance window (statute permits the insurer to accept a first application from a non-appointed producer, not the same as permitting the producer to solicit), Model-act filing window (notice due within N days of contract or first application; producer solicitation permission not spelled out the way Texas and Virginia spell it out).

StateRuleWindow and citationSourceTag
Georgia (home)Appointment on filingDeemed obtained immediately upon submission; O.C.G.A. 33-23-26(a)findlaw (republisher)V
FloridaPre-appointmentLicensed AND appointed before acting, no grace window; Fla. Stat. 626.112(1)(a), (2)flsenate.gov (official)V
TexasExplicit just-in-timeMay act before the department receives the notice (4001.204); notice 30 days after effective date (4001.202(b))texas.public.law (republisher)V
VirginiaExplicit just-in-timeUnappointed licensed agent may sell; insurer appoints or rejects within 30 days of first application; 38.2-1833(A)law.lis.virginia.gov (official)V
MarylandInsurer-side acceptance window (life, health, annuity)Producer may not act without written appointment documentation; insurer may accept a first life/health/annuity application from a non-appointed producer if within 30 days it rejects or appoints; Md. Ins. 10-118findlaw (republisher)V
WashingtonModel-act filing windowNotice within 15 days of contract or first application; RCW 48.17.160leg.wa.gov (official)V
WisconsinModel-act filing windowRequest within 15 days of contract or first application; Ins 6.57(1)docs.legis.wisconsin.gov (official)V
South CarolinaModel-act filing windowNotice within 15 days; S.C. Code 38-43-50(B), (C)scstatehouse.gov (official)V
TennesseeModel-act filing windowNotice within 15 days; Tenn. Code 56-6-115findlaw (republisher)V
District of ColumbiaModel-act filing windowNotice within 30 days; D.C. Code 31-1131.14code.dccouncil.gov (official)V
IndianaAppointment required before actingProducer shall not act as agent unless appointed; IC 27-1-15.6-14 (full section text read)Indiana Code chapter textV
Indiana (filing window)No window provision in the producer licensing chapter2015 chapter text contains no appointment filing deadline (section 15 covers only termination notice); current-code and department-rule confirmation openSameU

What this changes, with one hard boundary: these rows are the statutory tier, what the law permits. A second tier, carrier practice, sits on top and is unknown (U): carriers commonly require their own onboarding confirmation before accepting business regardless of what the state allows, so the readiness engine must AND the two tiers and never tell an agent he can write from statute alone. Within the statutory tier: in Georgia an appointment is effective the moment the carrier files it; in Florida nothing may be written until the appointment exists; Texas and Virginia expressly let the producer act before appointment; Maryland lets the insurer accept a first life application from a non-appointed producer. Whether the carriers actually filed his American Amicable and Occidental appointments is still the U in the snapshot. T3's config table now starts with all eleven rules resolved (one filing-window cell open) instead of zero.

The metric

Two numbers the product exists to move: signed-to-first-writable days and signed-to-declared-ready days. n=1 supplies no baseline because the one missing datum is the signed date itself: the archive starts after signing and the intro-call email is undated in the export. Mike or the agent can supply it in the review; either way T2 instruments both timestamps from day one and the next cohort establishes the real baseline. Target direction: down, with silent windows like this agent's Jul 13 to 28 eliminated as a side effect of surfacing blockers.

Decisions we need in the review

Decision 1: who declares an agent ready to take calls? Options: upline (recommended), agency desk, or rule-based. Recommendation: the upline clicks it against a visible evidence panel, with the bar itself set agency-wide by Mike. If Mike's bar differs from the provisional one here, his bar wins; that is the point of the interview.
Decision 2: upline visibility scope. Options: track-level only (recommended) or full detail. Uplines see progress, days stuck, blockers; never background answers, documents, or personal identifiers.
Decision 3: where the checklist lives. Options: Peach Pilot (recommended), Notion, or pushing SureLC. Peach Pilot, because the decisive signals arrive in email and the unifying computation is ours to own; SureLC stays the contracting system of record.
Conflict rule. Mike's field judgment wins on the readiness definition; Aaron's wins on build order. Anything still contested goes on the review agenda and gets decided in the meeting, not by default.

Review agenda (the exact questions)

Anna: (1) Which carriers update SureLC automatically versus by your hand, and how often do you update the rest? (2) What does At Carrier mean for Americo, Banner, and Mutual of Omaha right now? (3) How did Occidental appear with no request? (4) How do releases and contracting debt work on transfers in? (5) Your desk flow from invite to Completed, including NIGO fixes and carrier chasing. (6) Who is supposed to tell an agent about training, CE, and license blockers today?

Mike (who, as Safe Life's owner, can also answer or arbitrate any of Anna's desk items above): (1) Your actual bar before an agent takes a live call. (2) Correct the step 8 inventory. (3) Who should click "ready," and would you use the evidence panel? As agency owner you may already have agency-side SureLC visibility the producing uplines lack (U, confirm); the T5 upline view targets those producing uplines. (4) What does sales training completion mean? No attendance or completion record for the Weekly Edge calls appears anywhere in the archive or portal (V by absence, emails 11 to 25).

Aaron: (1) Accept or reorder ticket priority and dependencies. (2) Confirm the metric pair. (3) Confirm the bot prohibitions as acceptance criteria.

Build-ready tickets for next cycle

Owners: Aaron assigns T1 to T5 at planning; Tyler owns T6 now. Start now: T1 and T6. Unlock when T1's model lands (same cycle): T2 and T4. Discovery-dependent drafts until T6 answers land: T3 and T5.

T1. Readiness data model
P0 · no dependencies · ~1 wk
The model must hold a state like this agent's Jul 28 reality without flattening it: two sellable-pending contracts, three uninterpretable ones, training gates split by state, one lapsed license. Four tracks, per-state and per-carrier branching, evidence-tagged statuses (V, H, U), one owner per step. Non-goals: no UI, no SureLC integration.
Acceptance: this real case representable end to end (a transfer, the TX exclusion, an unexplained contract, an unknown-status request) without forcing false certainty.
T2. Email signal ingestion v1
P0 · depends on T1 · ~1 to 2 wks
Parse activation, request submitted, carrier welcome with writing number; emit both metric timestamps. Privacy: raw emails never leave our store; only extracted statuses; no credentials or personal identifiers in derived records.
Acceptance: replaying the real 25-email archive auto-completes exactly the right steps, zero false completes.
T3. Readiness engine v1
P1 · depends on T1 + T2 · blocked on Anna's status answers for At Carrier logic · ~1 wk
Can-sell per product, state, carrier; JIT states as config, unknowns default conservative.
Acceptance: reports this agent as American Amicable + Occidental fixed life pending appointment confirmation, annuities blocked everywhere, and refuses to interpret bare At Carrier dwell.
T4. Agent-facing checklist UI
P1 · depends on T1 · ~1 wk
The sequence as a live view: one owner per step, signal state, plain-language blockers, bot integration honoring the prohibitions. Non-goals: no upline view yet.
Acceptance: an agent in this exact Jul 28 position sees his two active contracts marked sellable pending per-state appointment confirmation, his annuity block, his lapsed license, and his silent At Carrier window, in the snapshot's conservative language, without asking anyone.
T5. Upline progress view
P2 · depends on T3 + decision 2 · ~1 wk · discovery-dependent draft
Whether an upline can see any of this in SureLC today is unknown (the sweep covered only the producer portal, U); what is verified is that no blocker notification reached the agent on any captured surface (his inbox and his producer portal) during the Jul 13 to 28 window (V by absence); whether Anna or Mike received anything is outside the capture (U). This view gives the upline a track-level window with the privacy boundary of decision 2.
Acceptance: personal data absent from the API response, not merely hidden; background answers and documents unreachable by the upline role.
T6. Discovery interviews and validation
P0 · parallel · Tyler owns · this cycle
Run the review agenda with Anna and Mike, fold answers into the next version, validate against a second real agent, ideally one who got stuck.
Acceptance: every U in this doc becomes V with a source or a numbered follow-up ticket.

Open blockers, named

Appendix: the assignment, as received

Linear issue PEA-555, as relayed by Tyler; the Linear connector was down when this pack was assembled, so this is the relayed brief, not a verbatim copy of the issue body. Paste the verbatim body here at review. Aaron's ask: define how a new agent gets from signed to ready to take calls. Deliverables: a one-page onboarding sequence; who owns every step; state and IMO differences; where the checklist should live; what belongs in the checklist versus the Q&A bot; whether uplines can see progress; build-ready Linear tickets for the next planning cycle. Base it on Safe Life's real process, then review it with Mike and Aaron. Discovery, not a build.

Appendix: source index

Note: drafted with AI assistance from real onboarding evidence; pre-review, Anna's and Mike's answers pending (T6). Tyler owns this doc; send questions and corrections to him.