01
Captured
Engagement inputs
Scope and working details stay with the review.
For compliance, legal, and operations teams
Give every classification decision a clear record
Collect the engagement details your reviewers need, assign the decision, and keep the outcome and reason with the engagement. Onboarding and finance can then work from the same reviewed record.
Engagement inputs in one placeAssigned review ownershipOutcome and reason historyClear downstream handoff
Classification review
Engagement ENG-9824
- Status
- Assigned
- Owner
- Compliance review
- Inputs
- Captured
- Reason
- Awaiting decision
A shared review record
The context each team needs to move forward
02
Assigned
Review owner
The team can see who owns the next decision.
03
Reasoned
Recorded outcome
The result includes the reviewer's reason.
04
Shared
Downstream context
Onboarding and finance read the reviewed status.
What the record carries
Classification context without the thread hunting
Keep the information used for a decision beside the decision itself, so a handoff does not depend on email or chat history.
Engagement details
Capture the worker, client, scope, and other inputs your policy requires for review.
Review ownership
Assign a reviewer and show the team where the assessment is waiting.
Outcome and reason
Record the decision and its reason so downstream teams understand what was reviewed.
Decision history
Keep prior statuses and reviewer notes available when the engagement needs another look.
Exception ownership
Give incomplete or disputed cases an owner and a visible next step.
Team handoff
Pass the reviewed status and reason to onboarding and finance without re-keying the decision.
A review flow teams can follow
Your policy defines the questions and the decision. Gruv keeps the work and its handoff organized.
01
Capture
Add the engagement inputs required by your classification policy.
02
Assign
Send the record to the reviewer responsible for the decision.
03
Record
Save the outcome, reason, and reviewer notes with the engagement.
04
Hand off
Share the reviewed status with onboarding and finance.
Where a shared classification record helps
Use the workflow when several teams need to understand the same engagement decision.
New engagement review
Collect inputs and assign the initial classification decision.
Incomplete submissions
Return a record with a reason and a named owner for follow-up.
Changed engagement terms
Open another review while keeping the earlier decision available for context.
Finance handoff
Give finance the reviewed status and reason before payout planning continues.
After classification review
Carry the reviewed context into onboarding
Keep the classification status and reason with the engagement as onboarding collects its own required inputs.
Frequently Asked Questions
What information can a classification record capture?+
Teams can capture the engagement details their policy calls for, then keep the assigned reviewer, status, outcome, reason, and notes with that engagement.
Who makes the classification decision?+
Your designated reviewer makes the decision under your policy. Gruv organizes the inputs, assignment, and resulting record.
What happens when information is missing?+
The record can remain in review with a reason, an owner, and a next step for the person gathering the missing context.
Can a team revisit an earlier decision?+
Yes. A team can start another review and retain the earlier status and notes as decision context.
Map the classification record your teams need
Bring your required inputs, reviewer roles, decision statuses, and finance handoff needs. We will use them to scope the workflow.
Many teams start with a narrow launch in weeks.