Revision Process

Refine outcomes without redefining scope.

GigBig follows a structured revision process to keep deliverables aligned with scope while maintaining fairness and efficiency for clients and freelancers.

What is a revision?
  • Refines output within the agreed scope
  • Adjusts minor elements or clarity
  • Corrects misunderstandings within scope
  • Does not introduce new requirements

Step 1: Deliverable submission

  • Expert submits the completed milestone
  • Project Manager performs internal quality check
  • Deliverable is made available in the dashboard

Step 2: Client review

  • Approve the deliverable
  • Request revisions (within scope)
  • Provide structured feedback

Feedback should reference the original scope for clarity.

Step 3: Revision implementation

  • Expert reviews feedback
  • Project Manager ensures alignment with scope
  • Necessary adjustments are made
  • Updated files are re-submitted
  • All revisions are documented in the dashboard

Revision policy in Single Service

  • Applies only to defined deliverables
  • Revision rounds may be predefined in scope
  • Major structural changes require scope review
  • PM keeps revisions controlled and efficient

Revision policy in Team Service

  • Revisions may involve multiple specialists
  • Project Manager coordinates updates across roles
  • Cross-functional alignment is maintained
  • Timeline impact assessed before implementation

What is considered within scope?

  • Minor design adjustments
  • Text corrections
  • Alignment changes
  • Formatting improvements
  • Feature tweaks already agreed upon

What is considered out of scope?

  • Adding new pages or features
  • Introducing new technical requirements
  • Changing core project direction
  • Increasing quantity of deliverables
  • Major redesign after approval

Out-of-scope requests require scope re-evaluation, timeline adjustments, and client confirmation.

Timeline impact of revisions

  • Minor revisions typically stay within milestone timeline
  • Extensive revisions may extend deadlines
  • Timeline changes are documented transparently

The Project Manager ensures revisions do not disrupt overall structure.

How revisions protect both parties

For clients:

  • Ensures final output meets expectations
  • Provides a structured feedback system
  • Prevents miscommunication

For freelancers:

  • Prevents unlimited change requests
  • Protects against scope creep
  • Ensures fairness in execution

Revision limits & fair use

  • Revision limits are stated before execution
  • Additional rounds may require scope adjustment
  • Maintains balance and professional boundaries

Transparency & documentation

  • All revision requests are logged in the dashboard
  • Linked to specific milestones
  • Accessible for future reference
  • Supports dispute resolution if required

No informal or undocumented changes are encouraged.