Afforrd

This report is password protected

Ask David for the password.

Afforrd · End-to-end verification

E-signing verified live, across 5 real customer scenarios

Every scenario below was run for real: a browser walked through the actual product end to end — getting a quote, picking a plan, filling out the application, and signing it. Nothing here is mocked, faked, or edited after the fact.

5 / 5scenarios completed
7real signatures across all runs
5completed applications, one per scenario
Investigated live, not assumed

How a spouse's signature actually gets completed

When an application includes a spouse, they sign separately from the main applicant. Once the applicant finishes, the spouse gets their own signing link and completes their own signature independently — this is normal for e-signature software, not a workaround.

Both VUMI and IMG's with-spouse runs completed a real, independent spouse signature this way — visible in the screenshot walkthroughs below.

Technical detail: submissions with more than one signer do not continue in the same embed once the first person finishes. Each submitter (Applicant, Spouse) gets a distinct slug and its own /s/{slug} signing URL — confirmed directly in the app's own DocuSeal client code. The app's UI never surfaces a second signing session on its own.

1 · Applicant embed

The app's normal <docuseal-form> embed, submitter slug A. Recorded and confirmed complete on every run.

2 · Spouse embed (built for this test)

A standalone HTML page replicating the same embed pattern, pointed at submitter slug B, driven in a second browser page/tab — because the app has no built-in way to reach it.

Results

Status matrix

Each row is one test, each column a step in the process. A dash means that step doesn’t apply to that scenario (for example, there’s no spouse to sign) — it’s not a failure.

ScenarioEligibility CheckPlan SelectedApplication DetailsHealth QuestionsApplicant SignedSpouse SignedApplication Finalized
VUMI — Main Application
no spouse
VUMI — Main Application
with spouse
IMG — Application
no spouse
IMG — Application
with spouse
Best Doctors — Application
standard test
VUMI · No spouse

VUMI No spouse

Jordan Rivera · age 35 · Jamaica · spouse_included = No

Verified · real signature
Signing system reference ID docuseal_03dfde30-66c6-4d04-a845-d84ffe7e1a56
RoleNameEmailSlugNote
Applicant david.bain+e2e-test@incrementic.com the only signer — this application has no spouse

Recording (578 KB)

Completed Application (PDF) (211 KB)

First page of VUMI Application (Full) VUMI Application (Full)
↓ Download PDF

Step-by-Step Screenshots

Age: 35
Age: 35Qualification: age set to 35
No spouse on this application
No spouse on this applicationQualification: spouse included — No
Comparing available plans
Comparing available plansPlan results — comparing available plans
Contact details submitted
Contact details submittedEnrollment: contact submitted — thank you screen
Application details completed
Application details completedApplication: provider-specific details filled
Signature in progress
Signature in progressDocuSeal: signature drawn, signing in progress
Signed — complete
Signed — completeDocuSeal: documents signed — complete
VUMI · With spouse

VUMI With spouse

Jordan Rivera · age 35 · Jamaica · spouse_included = Yes · spouse Casey Rivera, age 33

Verified · real signatures
Signing system reference ID docuseal_68ef812a-c1c1-4286-95d9-4bae3f8044b4
How the spouse's signature was collected

The applicant signs first. Once they're done, the spouse gets their own separate signing link and completes their signature independently — a standard part of how e-signature works when more than one person needs to sign.

Technical detail: the signing tool does not continue in the same embedded window after the Applicant finishes — each signer gets their own unique slug and /s/{slug} URL. The app itself has no built-in UI for a second signer, so the test script builds a standalone page replicating the app's own embed pattern, points it at the Spouse's own signing URL, and drives it in a second browser tab. Both signatures below are real, independently completed sessions.

RoleNameEmailSlugNote
Applicant david.bain+e2e-test@incrementic.com DahheWnpNm35J2
Spouse Casey Rivera david.bain+e2e-test-spouse@incrementic.com zKwaKM4k5NNL2L

Recording (569 KB)

Step-by-Step Screenshots

Spouse included on this application
Spouse included on this applicationQualification: spouse included — Yes
Application details completed
Application details completedApplication: provider-specific details filled
Applicant signed — spouse signs next
Applicant signed — spouse signs nextDocuSeal: primary applicant signed — spouse signature next
Spouse's turn to sign begins
Spouse's turn to sign beginsDocuSeal: spouse's separate signing session opened
Spouse signed — complete
Spouse signed — completeDocuSeal: spouse signed — complete
IMG · No spouse

IMG No spouse

Jordan Rivera · age 35 · Jamaica · spouse_included = No

Verified · real signature
Signing system reference ID docuseal_0f0f1c98-df2c-483d-bcca-8b64478f5947
RoleNameEmailSlugNote
Applicant david.bain+e2e-test@incrementic.com the only signer — this application has no spouse

Recording (532 KB)

Step-by-Step Screenshots

Plan selected — starting the application
Plan selected — starting the applicationSelected the IMG plan — landed on enrollment
Contact details submitted
Contact details submittedEnrollment: contact submitted — thank you screen
Application details completed
Application details completedApplication: provider-specific details filled
Signature in progress
Signature in progressDocuSeal: signature drawn, signing in progress
Signed — complete
Signed — completeDocuSeal: documents signed — complete
IMG · With spouse

IMG With spouse

Jordan Rivera · age 35 · Jamaica · spouse_included = Yes · spouse Casey Rivera, age 33

Verified · real signatures
Signing system reference ID docuseal_abe44dd9-05e2-48e7-9961-6f493f6938c5
How the spouse's signature was collected

The applicant signs first. Once they're done, the spouse gets their own separate signing link and completes their signature independently — a standard part of how e-signature works when more than one person needs to sign.

Technical detail: the signing tool does not continue in the same embedded window after the Applicant finishes — each signer gets their own unique slug and /s/{slug} URL. The app itself has no built-in UI for a second signer, so the test script builds a standalone page replicating the app's own embed pattern, points it at the Spouse's own signing URL, and drives it in a second browser tab. Both signatures below are real, independently completed sessions.

RoleNameEmailSlugNote
Applicant david.bain+e2e-test@incrementic.com
Spouse Casey Rivera david.bain+e2e-test-spouse@incrementic.com

Recording (537 KB)

Step-by-Step Screenshots

Spouse included on this application
Spouse included on this applicationQualification: spouse included — Yes
Application details completed
Application details completedApplication: provider-specific details filled
Applicant signed — spouse signs next
Applicant signed — spouse signs nextDocuSeal: primary applicant signed — spouse signature next
Spouse's turn to sign begins
Spouse's turn to sign beginsDocuSeal: spouse's separate signing session opened
Spouse signed — complete
Spouse signed — completeDocuSeal: spouse signed — complete
Best Doctors · Single scenario

Best Doctors Single scenario

Jordan Rivera · age 35 · Jamaica

Verified · real signatures

Best Doctors has the applicant sign twice on the same form — not a separate co-signer — so there's no spouse scenario to show for this provider.

Signing system reference ID docuseal_90913604-77ca-4b28-b886-65c4c8d10f09
RoleNameEmailSlugNote
Applicant david.bain+e2e-test@incrementic.com signs the application
Applicant david.bain+e2e-test@incrementic.com signs again later in the same document — same person, not a second signer

Recording (566 KB)

Completed Application (PDF) (4.9 MB)

First page of Best Doctors Application Best Doctors Application
↓ Download PDF

Step-by-Step Screenshots

Occupation: Software Developer
Occupation: Software DeveloperQualification: profession search — Software Developer
Age: 35
Age: 35Qualification: age set to 35