3
Applicants, two policies issued, one decline
8
Chapters in this walkthrough
2
Real reviewer approvals, live
1
Shared workflow, three paths (plus an applicant chase)
Daniel Okoye
A new applicant with a clean health profile. His case moves through the fast track and reaches an issued policy ($88.00 a month), approved by a reviewer before it's finalized.
Applicant — Fast Track, Issued
Patricia Doyle
Applies twice in this walkthrough — once with an incomplete application that the case chases her to finish, then a more involved but insurable profile (standard review, issued at $265.50 a month), and once with a serious cardiac history that leads to a decline and a notice on record.
Applicant — Standard Review + Decline
Fast track — issued
Clean lab and physician evidence — the system classifies and routes automatically, a reviewer signs off, and the policy is issued.
Standard review — issued
An incomplete application is chased and completed, then a more complex profile takes extra review steps on the same workflow, then the same reviewer sign-off before it's issued.
Declined — notice on record
A serious medical history leads to a decline and a notice to the applicant. The decline path has no human approval step.
About this walkthrough
Every screen below is a real screenshot from an automated, end-to-end run of Regisseur on 2026-10-05, captured live — not a mock-up. The people are fictional and the data is illustrative. Three applicants, two policies issued and one decline: Daniel Okoye takes the fast track, Patricia Doyle's application arrives incomplete, so the case asks her for what is missing before taking the closer standard review and issuing a rated policy, and a second Patricia Doyle application is declined with a notice on record. Each ran on the same workflow. The underwriting review steps and the decline notice are completed by the system; the human sign-off sits at policy issuance. Every policy that was issued passed a named reviewer's approval — two real approvals in this run, one per issued policy. A decline does not pass a human approval. How much sign-off is required at each step is a setting your team controls per step.
About the applicant exchange (Part 4B). The reminder is set to go out after one day. So the demo did not have to wait a day, the real reminder process was run once as if 25 hours had passed; nothing in the case was edited by hand. Every answer in that exchange was typed into the secure form by the test applicant, not pre-loaded.
What stands in for the outside world. To keep the run repeatable we used test stand-ins in a few places, and we want to be plain about them: the secure upload links and access codes were read by the test harness rather than opened from an email; the lab and physician documents are generated sample files (for Daniel Okoye's, the clinical values were borrowed from another sample applicant under his name); the signed receipt is a stand-in file uploaded through the same secure page, because e-signature credentials are not configured in this environment; the records system, underwriting engine, document system and product catalog are simulated services; and the physician email was delivered to a test inbox. The summary line at the top of each case is written automatically by the system and can lag or contain odd details while a case is still moving — for example a submission date that does not match this run. Two items are visible and still open: a "1 warning" marker on a generated document in one scene.
The lab order and the physician request are complete. Lab Results Received and APS Document Received show "Awaiting Document" — they are waiting on the people who must upload them.
The physician request step lists one generated document, the APS Request Letter, with Download and Preview.
What the exam vendor sees when they click the secure link: a no-login upload request for Daniel Okoye with a file drop zone. The Upload button stays disabled until a file is chosen.
After the lab results file is uploaded through the page, it confirms "Received — thank you. Nothing further is needed for this request."
Lab Results Received and APS Document Received now show Complete, and the Lab Analysis and APS Medical Review steps after them are complete too.
The lab analysis step completes and lists two generated documents — a Lab Analysis Summary and a Lab Results Report — for the underwriting steps that follow.
The medical review step shows "Medical Review Prep Agent — Complete" with one completed task and no approval prompt. In this workflow the medical review runs on its own; the human sign-off sits at policy issuance, two screens ahead. (The summary at the top of the case was generated mid-run and describes the case as still in risk classification.)
Risk classification and routing are complete. The decline branch and the standard-review branch are skipped, and the Preferred Plus policy step is waiting for review.
A Policy Schedule has been generated, and the policy step shows "Awaiting Review" with a "needs attention" flag on the case. Woodgrove Life requires a person to approve the policy before it is issued.
A reviewer opened the case's Review tab and approved the policy — a real click in the real interface. The step now shows Complete and the "needs attention" flag has cleared.
Policy Issued shows Complete and the case header reads Complete with a premium of $88.00 a month. The case summary reads that the policy was issued with a Preferred Plus health class, an annual premium of $1,056 and an effective date of 2026-10-05.
Close-up of the last stages of Daniel's workflow — Policy Delivery, Applicant Signature, Policy Receipt Confirmed, First Premium Collection and Policy Issued — all shown complete.
The record shows the policy details — $1,000,000 coverage, a 20-year term, $88.00 monthly and $1,056.00 annual premium — Daniel's profile and health data, and the underwriting decision: Preferred Plus.
The history of the policy step: one completed task, the generated Policy Schedule (which carries a "1 warning" marker, left visible), and the values written — policy number WL-2026-NTABST9P3X, coverage $1,000,000, health class Preferred Plus, effective 2026-10-05 through 2046-10-05. The approval click itself is shown two scenes earlier.
When an application arrives with answers missing, the case no longer carries on regardless. It asks the applicant through a protected link, sends one reminder, checks the answers again, and asks again for only what is still missing. Once the application is complete it moves on to underwriting. Patricia Doyle's case is opened in the first scene of Part 5; this part shows how its gaps were closed. One thing to know: the reminder is set to go out after one day. To avoid waiting a day, the demo ran the real reminder process once as if 25 hours had passed. No records were edited by hand.
The exchange, from the case's message records (times are UTC, 2026-10-05)
| Time | Direction | Step | What was sent or received |
|---|
| 19:33:47 |
Sent by the case |
First request for missing answers |
We need a few more answers to continue your Woodgrove Life application — Dear Patricia, Thank you for applying. To keep your application moving we still need the f… |
| 19:34:07 |
Sent by the case |
Reminder, then reply to the first request |
Reminder: your Woodgrove Life application is waiting on your answers — We emailed you a personal secure link, with a verification code, for the application quest… |
| 19:34:23 |
Received from the applicant |
Reminder, then reply to the first request |
15 answers from the secure form |
| 19:34:25 |
Sent by the case |
Reminder, then reply to the first request |
Received — thank you. Nothing further is needed for this request. (automatic acknowledgement) |
| 19:34:30 |
Sent by the case |
Second request (still missing) |
Still needed: answers for your Woodgrove Life application — Dear Patricia, Thank you for your reply. We still need the following before we can continu… |
| 19:34:44 |
Received from the applicant |
Reply to the second request |
5 answers from the secure form |
| 19:34:46 |
Sent by the case |
Reply to the second request |
Received — thank you. Nothing further is needed for this request. (automatic acknowledgement) |
| 19:35:19 |
Sent by the case |
Physician statement request |
Attending Physician Statement — Patricia Doyle — Dear Dr. Laura Bennett, MD, We are writing on behalf of Woodgrove Life Insurance Company r… |
Source: the run's recorded message log (8 messages for this case at capture; the log keeps the first part of each message, and the verification code is masked here). Every answer was entered by the applicant in the secure form; none was seeded.
Patricia Doyle's application arrived with answers missing. The workflow map shows the case has already asked her for them and is now waiting for her reply. Ahead of it are a re-check, a second request if anything is still missing, and a hand-off to an underwriter if it is not resolved.
The Communications tab records the request: a secure link to a short form, delivered to Patricia. (The verification code she must enter travels in the email itself and is not shown on this tab.) The case header summarises what is being asked for and when a reply is due.
A reminder email appears on the thread, above the original request. The reminder is set to go out after one day. So that the demo did not have to wait a day, the real reminder process was run once as if 25 hours had passed. Nothing in the case was edited by hand.
Patricia opens her link, enters the verification code, and starts answering. The questions are in plain language. In this screen some answers are filled in and the last few are still empty. She answers only part of the form on purpose, to show what happens next.
The page confirms: "Received — thank you. Nothing further is needed for this request." It is a generic confirmation page, the same one shown earlier for the lab upload; the next scene shows the reply on the thread.
The thread now shows Patricia's reply arriving and, right above it, a new request. The case read her answers, found questions still unanswered, and sent a second secure link. (From the case's records: it asks for exactly the five that were left.) The summary at the top now says the applicant is being asked again, with a new due date.
On the new link Patricia answers the last five questions (the five filled answers at the bottom of the form are the ones the second request asked for) and presses Submit.
Patricia's second reply is on the thread. Immediately above it the case has ordered the paramedical exam, the next step in underwriting. The case summary now says the intake is complete and there are no open requests.
The workflow map shows the re-check and routing steps finished, the exam ordered, and the "underwriter reviews an incomplete application" path skipped, because the application is now complete.
Opening Patricia's first reply from the thread shows the 15 answers she gave, with the sender masked and the time received.
The second reply, opened from the thread, contains five answers, the five that the second request asked for.
Everything the case sent and received sits in one thread, newest first: policy issued at the top, then policy delivery and signature, the lab and physician requests, and at the bottom the two requests and replies from this chapter.
A second, independent application arrives for Patricia Doyle, on the same workflow. Her application is incomplete: the map shows Application Received, Application Intake, the completeness check and the first request to the applicant already complete, with her reply and everything after it still to come. Part 4B above shows how that request played out.
Risk classification and routing are complete. The decline branch and the Preferred Plus policy step are skipped, and the standard-review steps (Medical Director Review onward) are next — the same workflow adapting to what the evidence shows.
Medical Director Review, Underwriting Decision and Approval & Rating are all complete, and the standard policy step is "Awaiting Review". No person approves the three review steps; the human sign-off is at issuance.
Patricia's Policy Schedule is generated and the standard policy step is "Awaiting Review" at a premium of $265.50 a month. The case summary describes her underwriting package as complete, with Standard risk class and no table rating.
A reviewer approved Patricia's policy in the same Review tab. The step shows Complete and the "needs attention" flag has cleared — the same sign-off applies on both paths.
The last stages of Patricia's workflow — delivery, signature, receipt, first premium and Policy Issued — all complete, reached by a different route through the same template.
A third application arrives for Patricia Doyle with a different medical history. Application Received is complete, Application Intake is running, and the following steps are pending.
Risk classification routing is complete and sends this case down the denial path: the Adverse Action Notice step is active, and the Medical Director Review step on the standard path shows Skipped.
The Adverse Action Delivered step shows Complete, with one completed task and a recorded delivery of the notice by email. The case shows Premium: Declined, and the summary reads that an adverse action notice was sent to the applicant.
The Application Closed (Declined) step is recorded and the case reads Complete with Premium: Declined.
The routing section for the declined case: risk routing, the adverse action notice, its delivery and the closing step are complete; the standard-review steps are skipped.
The case record shows "Declined — no premium", Health class decline and tobacco use Yes. The case summary above it cites a prior heart attack requiring a stent, active coronary artery disease and active tobacco use as the basis for the decision.
The history of the Adverse Action Notice step: one completed task and one generated Underwriting Decision Letter, plus the decision recorded as "declined". This step completed without a human approval — only policy issuance is held for a person.
