Protection Against Unfair Rejection
Scope-aligned work cannot be arbitrarily denied.
GigBig operates with a structured Protection Against Unfair Rejection policy to ensure freelancers are not denied payment when deliverables meet the approved scope and defined requirements.
What qualifies as unfair rejection
- Deliverables match approved scope
- Funded milestones are fulfilled
- Requirements are objectively met
- Rejection is based on preference rather than specification
- Scope is expanded without added funding
Work cannot be rejected solely due to subjective dissatisfaction.
How GigBig prevents unfair rejection
- Milestone-linked deliverables
- Escrow-secured funding
- Defined scope documentation
- Structured approval workflow
- Evidence-based evaluation during disputes
Rejection must be justified within scope boundaries.
If rejection occurs
- Funds remain secured in escrow
- The reason for rejection must be documented
- Scope vs. delivery is formally reviewed
- Both parties may submit clarification
- Structured mediation may be initiated
Approved completed portions remain payable.
Evaluation criteria
- Original project scope
- Funded milestone definitions
- Agreed deliverable standards
- Communication history
- Revision limits
Personal taste does not override contractual agreement.
What freelancers must follow
- Deliver according to defined scope
- Submit work within platform systems
- Avoid off-platform agreements
- Do not execute unfunded changes
- Respect revision limits
Policy compliance activates protection safeguards.
What this protection does not cover
- Incomplete deliverables
- Missed agreed requirements
- Late submissions without justification
- Work delivered outside platform
- Scope misunderstandings not clarified during execution
Protection applies to scope-aligned work.
Why this matters
- Financial fairness
- Reduced payment manipulation
- Professional accountability
- Structured approval standards
- Balanced client-freelancer relationships
Rejection must be justified, not arbitrary.