Revision Handling Process

Structured, scope-aligned revision workflow.

At GigBig, revisions are managed inside the dashboard with full documentation and scope control. Revisions are not informal change requests and must align with approved deliverables.

What is a revision?
  • Adjustments within approved scope
  • Corrections based on client feedback
  • Improvements aligned with requirements
  • Minor refinements to submissions

Revisions do not include new features or expanded scope.

In This Section
How the Dashboard WorksCommunication with ClientRevision Handling ProcessDispute ProcessHandling Inappropriate Client Behavior

Step-by-step revision process

1. Deliverable Submission
  • Freelancer uploads files under the milestone
  • Submission is timestamped
  • Client is notified for review
2. Client Feedback
  • Client submits feedback in dashboard
  • Feedback is documented and milestone-linked
  • Revision points are clearly outlined
3. Scope Alignment Review
  • Project Manager reviews scope alignment
  • Within-scope requests are confirmed
  • Potential scope expansion is flagged

Out-of-scope requests follow a separate scope change process.

4. Revision Execution
  • Freelancer implements agreed revisions
  • Updated files are uploaded
  • Version history is maintained
5. Final Review and Approval
  • Client reviews revised submission
  • Formal approval triggers payment release
  • Revisions close once milestone is approved

Revisions in Single Service

  • Timeline is predefined
  • Revisions must fit agreed schedule
  • Multiple rounds may be allowed per service structure
  • Excessive revisions may require structured review

Revisions in Team Service

  • Feedback flows through the Project Manager
  • Revision points are routed to relevant roles
  • Package duration must accommodate revision cycles
  • Team coordination remains structured

What is not considered a revision

  • Adding new deliverables
  • Expanding functionality
  • Changing original project direction
  • Increasing content volume significantly

These are new requirements or scope expansion.

Timeline and revision discipline

  • Revisions must align with milestone deadlines
  • Team Service revisions must respect package duration
  • Turnaround time should remain reasonable

Delayed cycles may impact overall delivery schedule.

If revisions become excessive

  • Scope documentation is reviewed
  • Project Manager may intervene
  • Additional scope approval may be required

Structured control prevents endless change cycles.

Protection for freelancers

  • Protection from unapproved scope expansion
  • No informal additional tasks
  • No unlimited revision demands
  • No off-platform feedback requirements

Only documented, scope-aligned revisions are mandatory.