01
Captured
Required inputs
The engagement keeps submitted onboarding details together.
For compliance and program operations
Make onboarding status easy to understand
Collect the inputs your onboarding policy requires, assign review work, and keep each status and reason with the engagement. Exceptions have an owner, and finance receives a deliberate handoff.
Required inputs capturedReview status recordedException owner assignedFinance handoff prepared
Onboarding record
Engagement ENG-9824
- Status
- In review
- Owner
- Program operations
- Inputs
- Needs attention
- Reason
- One item outstanding
One onboarding record
The state operations can act on
02
Visible
Review status
Teams can see what is ready or needs attention.
03
Assigned
Exception owner
Open issues have a responsible person.
04
Reasoned
Next action
A status includes the reason and expected follow-up.
What onboarding carries
A useful record for every handoff
Keep onboarding progress understandable without turning an open review into a promise that the engagement is ready.
Required input list
Define and capture the details your onboarding process expects for the engagement.
Submission status
Show which inputs were received and which still need attention.
Assigned review
Give a reviewer ownership of the record when your process requires a decision.
Reason and notes
Explain a pending or returned status so the next person understands the issue.
Exception owner
Route an incomplete record to a named owner with a visible next action.
Finance handoff
Share the reviewed onboarding status and open reasons when finance begins its readiness check.
Onboarding work with a clear next step
Your policy defines what is required. Gruv keeps the inputs, review, and handoff visible.
01
Collect
Capture the engagement and onboarding inputs your process requires.
02
Review
Assign the record and record its current status.
03
Resolve
Give exceptions a reason, an owner, and a next action.
04
Hand off
Provide finance with the reviewed status and remaining context.
Where onboarding status clarity helps
Use the record when inputs and decisions cross contractors, operations, compliance, and finance.
New contractor setup
Collect the required inputs and show the record's current state.
Missing information
Return a record with a reason and a named follow-up owner.
Review queue
Give operations a clear list of records awaiting a decision.
Finance readiness
Share the reviewed onboarding status before payout planning proceeds.
After onboarding review
Keep the engagement context with its agreement
Carry the onboarding status and any open reason into the agreement workflow so legal and operations share the same context.
Frequently Asked Questions
What can the onboarding record capture?+
It can capture the inputs your policy requires, their submission status, the assigned reviewer, a reason, notes, and an exception owner.
Who decides whether onboarding is complete?+
Your designated team makes that decision under your process. Gruv records the assignment, status, and reason.
How are incomplete records handled?+
They can remain open with the missing item, reason, responsible owner, and next action shown on the engagement.
What does finance see?+
Finance can see the reviewed onboarding status and any open reason when the engagement reaches the payout-readiness handoff.
Scope onboarding around your requirements
Bring your input list, review roles, statuses, exception reasons, and finance handoff needs. We will use them to map the workflow.
Many teams start with a narrow launch in weeks.