New upload · ENG-731
Government photo ID
Upload received. The document requirement still waits for a review decision.
Pending review
Document gate: Review
Contractor document onboarding
Know why a file is waiting and what moves it forward
Collect the documents configured for the contractor's country, keep each review decision with the file, and show the correction needed before the document gate can clear.
One document, two uploads
Uploaded is a starting state, not an approval
Follow a fictional Government photo ID through a concrete review. The first file is rejected with a reason. Its corrected replacement starts pending and receives a separate decision.
Example assumptions
This US document path is assumed enabled for the program. Proof of address is already approved, and no earlier approved photo ID is available. Confirm availability with Gruv.
ENG-731 · US document path
Government photo ID
First upload
Pending review
The new file is stored as pending. Uploading it does not clear the Government photo ID requirement.
Authorized review
Rejected
Reason recorded: “Photo and name are not legible. Upload a clearer image.” The uploader cannot make this decision on the same file.
Corrected replacement
Pending, then approved
The corrected file creates a new pending record. An authorized approval then lets this requirement clear.
What does each decision preserve?
The record keeps the reviewer identity, prior and new status, decision time, optional notes and the required rejection reason when a file is rejected.
The wider onboarding path
Document approval clears one gate
The engagement begins with worker and jurisdiction context, then carries separate classification, document, agreement and operational readiness checks. Approved documents do not activate the engagement by themselves.
Worker setup and jurisdiction
Establish the path
Engagement identity and worker country provide the context for the onboarding steps that follow.
Classification
Separate decision
The engagement carries the latest classification result and its own readiness state.
Required documents
Approved in this example
Government photo ID and Proof of address each have an approved, unexpired document.
Agreement
Next stage
The agreement gate separately checks its signed record and related requirements.
Remaining readiness checks
Separate gates
Tax, screening, payout and insurance each return their own status and reasons before active-ready.
Next stage
Prepare the agreement
Agreement status stays separate from document approval and has its own readiness checks.
When a requirement stays open
Preserve the reason, then take the next action
Readiness reflects the usable document available for each required kind. The correction path depends on whether a file was rejected, remains pending, is missing or has expired.
An authorized reviewer with access to the client's workspace or record may decide a pending file. The uploader cannot review that same document.
Returned file
The reason drives the correction
A rejected document does not satisfy its requirement. The recorded rejection reason explains what the next file needs to fix.
What happens to the rejected upload?
It remains part of the document history with its status and decision. A corrected file with new content becomes a new pending record and must be reviewed before the requirement can clear.
Readiness check
Pending, missing and expired stay open
Every blocking requirement needs an approved, unexpired document before the document gate returns ready.
What if a newer upload exists beside an approved file?
Readiness can use a valid approved document for the required kind. A newer upload does not replace a still-valid approved item simply because it was uploaded later.
Contractor onboarding questions
Does an uploaded document count as approved?+
No. A new document upload starts in Pending review. An authorized reviewer with access to the client’s workspace or record must approve the pending document before it can satisfy that requirement, and the uploader cannot review the same file.
What happens when a document is rejected?+
The rejection records a required reason. The contractor can use that reason to submit a corrected file, which starts as a new pending document and needs its own review decision.
Which documents are required?+
The software resolves its document checklist from the contractor country. The worked US example uses the configured Government photo ID and Proof of address items. Confirm the countries and document paths enabled for your program with Gruv.
Who can approve or reject a document?+
An authorized reviewer with access to the client’s workspace or record can review a pending document. The uploader cannot review that same document. The decision record keeps the reviewer identity, prior and new status, decision time, and the rejection reason when a file is rejected.
Do approved documents mean the engagement is ready to activate?+
Approved required documents clear the document gate. Classification, agreement, tax, screening, payout and insurance checks remain separate, and the engagement reaches its active-ready state only after every required gate clears.
Plan the onboarding path
Map the next review
Review enabled countries, configured documents, reviewer access and the agreement handoff for your contractor program.