Onboarding on Vome starts after someone submits an application form. From there they are placed into a sequence, which is the step-by-step process that carries them from applicant to ready to work.
There are three ways someone lands in a sequence:
Which one you use depends on how much screening you do before letting someone through.
Please note: because the application already happened, the first step of a sequence is normally not the application. Start the sequence at whatever comes next.
Four questions:
These four answers determine your steps, your notifications and your automation settings. Deciding them first saves rebuilding later.
Every step either gives information, collects information, or both. Vome offers twelve types:
| Step type | Use it to |
|---|---|
| File Upload | Collect a document: a signed agreement, a certification, proof of eligibility. |
| Interview | Explain an interview, or let someone book one. |
| Orientation | Deliver orientation information or track an orientation requirement. |
| Training | Deliver training content, often with guides or handouts attached. |
| Fillable PDF | Have someone complete a PDF in Vome. You upload a blank PDF and design the fields. |
| Fillable Form | Run an existing Vome form inside the sequence. |
| Video | Share a welcome video, policy overview or recording. Vome can track whether it was watched. |
| Checklist | Group several smaller items as sub-steps, each with its own status plus a master status. |
| Course | Run a published course from the Courses module, with progress, results, pass or fail, certificates and credential expiry tracked automatically. Requires Enterprise or Ultimate. |
| Custom | Anything the other types do not fit. |
| Background Check | Screen through the Sterling Volunteers integration. |
| E-Learning | Connect your LMS through SCORM Cloud and sync completion back to Vome. |
For the detail on configuring any of these, see How do Sequences work on Vome?
Each step is separately visible or hidden, and using both kinds well is the difference between a tidy sequence and a confusing one.
Visible steps are for anything the person has to do: read something, watch something, upload a document, complete a form, book an interview.
Internal steps are for your team: reviewing a submission, confirming eligibility, verifying a document, or any manual checkpoint before someone moves on.
When somebody is sitting on an internal step, they do not see its contents. They see a placeholder telling them there is nothing to do and that they will be notified when the next step is ready. So you can add as many internal checkpoints as your process needs without cluttering their view.
Both, depending on the step. That is the point of configuring them individually.
Per step you can allow someone to complete the task themselves, have the step mark itself complete, and have the sequence move them to the next step automatically. Or you can require an administrator to review and advance it by hand.
The practical gain is fewer emails. A typical loop looks like this:
Nobody had to write a message.
Most organizations start with one and grow into several.
| Use one sequence when | Use several when |
|---|---|
| Everyone follows the same path, the same steps apply to all, and the process is simple. | Different groups need different steps: adults and minors, different regions or locations, different roles or programs. |
A common shape is one sequence for adults, one for minors, and one per location where the requirements genuinely differ.
Yes, and this is where sequences earn their keep beyond onboarding.
Somebody might complete general onboarding, then later be assigned a second sequence for a specific opportunity, then later again a third for an extra qualification or a renewal.
A sequence is really a process management tool. It is not limited to the start of someone's time with you. Assign one whenever you need to walk a person through a defined set of steps: qualification for an opportunity, post-approval requirements, role-specific training, annual renewals.