What It Is
When an assignee finishes a Gig and submits their work, the Gig moves into review.
The reviewer checks the submitted work and decides whether it is complete or needs another revision.
Who Can Review
Gig review depends on the reviewer assigned to the Gig and the user's permissions.
Authorized reviewers can open submitted work and perform the review actions available for the current Gig state.
Being able to view a Gig does not automatically mean a user can review it.
Review Options
Approve
Approve the Gig when the submitted work meets the requirement.
Approval completes the Gig.
Request Changes
Request changes when the work needs another revision before it can be completed.
Add clear feedback explaining what needs to change.
The Gig returns to the assignee so they can update the work and submit it again.
Review Flow
A typical Gig moves through:
Assigned → Work Completed → Submitted → Review → Approved → Completed
If changes are required:
Submitted → Changes Requested → Assignee → Resubmitted → Review
This keeps responsibility clear throughout the revision cycle.
Good Feedback
Feedback should explain exactly what needs to change before the work can be approved.
Instead of:
> Needs improvement.
Prefer:
> Shorten the opening section and replace the second product shot with the approved version.
Keeping review feedback inside AGENCIE gives the assignee a clear requirement and reduces follow-up conversations outside the platform.
What Happens Next
When the reviewer approves the submission, the Gig is completed.
When changes are requested, responsibility returns to the assignee until they submit the revised work for review again.
The available actions depend on the current Gig state and the user's permissions.
Compare the submission with the Gig instructions before approving it. If the requirement changed during production, include that context in the review instead of making the assignee reconstruct it from chat history.