Can I Reject a Project?
Yes, but with professional responsibility.
Freelancers may reject a project assignment if they are unable to take it on due to availability, scope mismatch, or other valid professional reasons. Since GigBig follows a managed allocation model, rejections should be used responsibly.
Valid reasons include
- Unavailable within timeline
- Scope does not match expertise
- Scheduling conflict
- Conflict of interest
- Technical requirements exceed skill level
- Personal or emergency circumstances
How to reject a project
- Inform the Project Manager immediately
- Clearly state the reason
- Confirm non-acceptance before execution begins
Early communication prevents project disruption.
What happens after rejection
- Project Manager initiates replacement matching
- Availability and timeline reassessed
- Client is informed if required
- Project continues without penalty to client
Responsible rejection policy
- Frequent rejections may affect future assignment priority
- Unjustified last-minute withdrawal impacts evaluation
- Rejection after work begins may trigger review
Consistency and reliability are valued.
Can I reject after accepting?
- Immediate communication with the PM is required
- Timeline and impact are assessed
- Replacement may be considered if necessary
Repeated mid-project withdrawal may affect account standing.
Single vs Team Service
- Single Service: reject before execution begins
- Team Service: rejection affects cross-role coordination
- Early notification is critical
Team allocation stability is important.
What rejection does not mean
- Loss of payout for completed and approved work
- Automatic account suspension
- Permanent prevention of future assignments
Reliability influences future matching decisions.
Best practices for freelancers
- Keep availability updated
- Avoid overcommitting
- Review scope carefully before acceptance
- Communicate early if unsure
Professional consistency builds long-term opportunity.