Funds Released Only After Approval
Client approval controls every payment release.
At GigBig, payments are held in escrow and released only after formal client approval of milestone deliverables. No approval means no payment release.
Approval-based release workflow
- Client funds escrow
- Freelancer submits deliverables
- Client reviews submission
- Client requests revisions or approves
- Funds release only after approval
Why this protects clients
- You pay only for completed work
- Deliverables can be checked against scope
- Revisions can be requested before payment
- Funds stay secure during review
- Disputes can be raised before release
You retain full budget control.
Approval in Single Service
- Scope and timeline are predefined
- Deliverables are submitted against scope
- Client reviews output and approves
- Payment releases only after approval
If revisions are needed, funds remain in escrow.
Approval in Team Service
- Execution follows fixed package duration
- Milestones are submitted in stages
- Client reviews each stage
- Approval triggers release per stage
Multi-role delivery does not override approval rights.
If you do not approve
- Request revisions within scope
- Project Manager may review alignment
- Funds remain locked in escrow
- Dispute process can be initiated if required
No automatic payout occurs without formal confirmation.
What approval does not mean
- It does not prevent future collaboration
- It does not block new-scope revisions
- It does not remove dispute rights before approval
After approval and release, ownership and settlement are finalized.
Transparency in approval
- Submission timestamps
- Revision requests
- Approval confirmation
- Payment release confirmation
All actions are documented in dashboard logs.
Why this policy matters
- Financial control
- Risk reduction
- Quality accountability
- Structured workflow
- Professional payment governance
It protects your investment.