Stacked eForms let you send several related eForms as one ordered set. Your client receives one invitation for the first form, then continues through the remaining forms in order.
What is a form stack?
A form stack (also called stacked eForms) is a group of eForms that belong together:
Each form in the stack is still a normal eForm (its own name, sections, questions, and status).
The forms share a stack and a fixed completion order.
The first form in the order is the Entry form. This is the only form that is emailed or SMS'd when you send the stack.
Later forms wait with status In Stack until the client reaches them after submitting the previous form.
Use a stack when you want a guided multi-form journey (for example onboarding pack, tax questionnaire then document checklist) without sending separate invites for every form.
When to use a stack vs a single eForm
Single eForm: one questionnaire, one invite, one status lifecycle.
Form stack: several questionnaires that must be completed in a set order, under one client journey.
Bulk eForms: the same (or similar) form sent to many clients. Stacking is about multiple forms for one recipient, not bulk sending.
How forms in a stack work together
You build or select the forms and set the Stack order (form 1, form 2, form 3, and so on).
You send from the Entry form only. OnboardMe bills one request per form in the stack, then:
Marks the entry form as Sent and sends the usual invite (email and optional SMS).
Marks every other form as In Stack (queued, not invited separately).
The client opens the entry form, completes it, and submits.
OnboardMe moves them to the next form automatically (or they can use Continue to next form).
They repeat until the last form is submitted.
While filling out a stacked form, clients see a banner such as Form 2 of 3 with the note that this is part of a multi-form set and each form should be completed in order.
Statuses that matter for stacks
Stacked forms use the usual eForm statuses, plus one stack-specific status:
Draft: entry form before send (or a standalone form).
In Stack: a non-entry form waiting in the stack. These forms are not sent their own invite and are not chased by automated reminders while they remain In Stack.
Sent / Opened: the client has been invited to (or opened) the active form, typically the entry after send.
Submitted / Completed: finished forms. Submitted or completed earlier forms are left alone if you later cancel remaining forms.
Cancelled: cancelled by your practice.
Pending Proposal: forms attached to a proposal / engagement that are waiting for acceptance (where that workflow applies).
Each stacked form appears as its own row in the eForms list, so you can track progress form by form (including rows with status In Stack).
Requests and billing
Each form in a stack uses 1 request (subscription allowance first, then wallet), the same unit as a normal eForm.
When you send an unsent stack, OnboardMe reserves / charges for the full stack size up front.
If you Add next form after the stack has already been sent, that extra form is charged immediately (1 request) and is created as In Stack.
If funding is short, you will see a message that there are not enough subscription requests or wallet balance to stack another form, with guidance to top up or enable auto top-up under Settings / Account.
Key rules at a glance
Only the Entry (first) form can be sent.
Clients complete forms in stack order.
Reminders apply to Sent / Opened forms, not to forms that are still In Stack.
Cancelling a form in a stack can cancel that form and any later unfinished forms (submitted / completed forms stay as they are). See the sending and cancelling article for details.
If you remove forms until only one remains, that form is no longer treated as a stack.
Related
Still need help?
Contact us