Account Warning System

Corrective, structured, and evidence-based enforcement.

GigBig's warning system helps maintain professional standards, protect ecosystem integrity, and address repeated policy or performance concerns through guided correction.

Why this system exists
  • Maintain service quality
  • Protect clients and freelancers
  • Prevent repeated violations
  • Encourage accountability
  • Reduce platform risk

Warnings are intended to guide improvement.

In This Section
Performance evaluation systemClient feedback processRating calculation methodAccount warning systemSuspension policyDispute against unfair ratings

When a warning may be issued

1. Repeated missed deadlines

Consistent failure to submit milestones on time.

2. Frequent last-minute project rejections

Rejecting projects after acceptance without valid reason.

3. Scope violations

Executing out-of-scope work without approval or ignoring structured process.

4. Unprofessional communication

Disrespectful language, harassment, or policy violations.

5. Attempting off-platform transactions

Requesting direct payment or sharing contact details to bypass escrow.

6. Non-compliance with availability management

Repeated unavailability after accepting assignments.

Types of warnings

  • Informal performance notice
  • Formal warning
  • Final warning

Warnings are recorded internally.

How the warning process works

  1. Issue identified through review or report
  2. Logs and documentation reviewed
  3. Freelancer notified of concern
  4. Explanation may be requested
  5. Corrective guidance provided
  6. Monitoring period may follow

The process is evidence-based.

Can a warning be disputed?

  • Freelancer may provide clarification
  • Supporting documentation may be reviewed
  • PM or internal team may reassess the case

Fair evaluation is prioritized.

Impact of warnings

  • Assignment priority
  • Eligibility for complex projects
  • Performance rating trends
  • Platform standing

Repeated unresolved warnings may lead to suspension review.

What does not trigger a warning

  • Isolated minor delays
  • Single revision disagreement
  • Legitimate dispute resolved professionally
  • Occasional availability conflict if properly communicated

Patterns matter more than isolated incidents.

How to avoid warnings

  • Maintain clear communication
  • Respect milestone deadlines
  • Keep availability updated
  • Follow structured workflow
  • Avoid off-platform agreements
  • Cooperate with PM oversight

Professional consistency prevents risk.