Skip to main content

Disputes

Sometimes disagreements arise. FlexDuty has a structured dispute resolution process to ensure fair outcomes for both experts and clients.

What Is a Dispute?

A dispute is a formal disagreement about:
  • Payment: Client won’t release funds for completed work
  • Quality: Disagreement about whether work meets requirements
  • Scope: Disagreement about what was agreed upon
  • Timeline: Issues with deadlines or delays
  • Communication: Serious breakdowns in communication

Before Filing a Dispute

Disputes should be a last resort. Try to resolve issues directly first.

Steps Before Disputing

  1. Communicate clearly in project chat about the issue
  2. Reference the original scope and agreements
  3. Propose solutions and be willing to compromise
  4. Allow time for the other party to respond (48-72 hours)
  5. Involve platform ops for mediation before formal dispute

Filing a Dispute

If direct resolution fails:
1

Go to Project

Navigate to the project with the issue
2

Click 'Report Issue'

Find this in the project menu or settings
3

Select Dispute Type

Choose the category that best describes your issue
4

Provide Details

Explain the issue thoroughly with evidence
5

Submit

Your dispute enters the resolution queue

Dispute Types

TypeDescriptionCommon Resolution
PaymentClient won’t release approved workPlatform review of deliverables
QualityWork quality disagreementIndependent review, partial refund
Scope”That wasn’t in the scope”Review original agreements
DeadlineMissed deadlines causing problemsTimeline adjustment, penalties
CommunicationExpert or client unresponsiveMediation, project restructuring

The Resolution Process

Timeline

Day 0: Dispute filed
Day 1-2: Platform ops reviews initial claim
Day 3-5: Both parties provide evidence
Day 6-10: Platform ops investigates
Day 10-14: Resolution decision made

What Platform Ops Reviews

  • Original project scope
  • All chat communications
  • Submitted deliverables
  • File history
  • Time tracking data
  • Any supporting evidence provided

Providing Evidence

Strong evidence includes:
Chat messages documenting agreements
Original scope document
Submitted deliverables
Time tracking records
Screenshots of issues
Email confirmations (if any)

Presenting Your Case

Do:
  • Be factual and specific
  • Provide dates and references
  • Include all relevant evidence
  • Stay professional
Don’t:
  • Be emotional or accusatory
  • Omit relevant facts
  • Make personal attacks
  • Exaggerate claims

Possible Outcomes

OutcomeDescription
Full PaymentExpert receives full agreed amount
Partial PaymentCompromise based on work completed
Full RefundClient receives refund (rare, for serious issues)
Project RestructuredScope/timeline adjusted, work continues
Project CancelledEnded with fair settlement
No ChangeDispute not substantiated

Expert-Specific Concerns

Not Getting Paid

If work was delivered but payment not released:
  1. Document that deliverables meet requirements
  2. Request specific feedback on what’s lacking
  3. If client unresponsive, escalate to platform ops
  4. Platform ops may force-release after review

Scope Creep

If client is requesting more than originally agreed:
  1. Reference the original scope document
  2. Politely decline out-of-scope requests
  3. Offer to handle additional work as a scope change
  4. Document all requests in project chat
  5. Escalate if client insists

Client Disputes Quality

If client claims work is poor quality:
  1. Request specific, actionable feedback
  2. Review against original requirements
  3. Offer reasonable revisions
  4. If feedback is unreasonable, escalate

During the Dispute

Do

Continue communicating professionally
Respond promptly to platform ops requests
Provide requested evidence quickly
Remain open to compromise

Don’t

  • Stop all communication
  • Make threats
  • Discuss dispute publicly
  • Destroy evidence
  • Take retaliatory actions

Appeal Process

If you disagree with the resolution:
  1. You have 7 days to file an appeal
  2. Provide new evidence or arguments
  3. A senior team member reviews the appeal
  4. Final decision is made within 14 days
  5. Appeal decisions are final

Preventing Disputes

Best Practices

  1. Clear Scope: Ensure scope is detailed and agreed upon
  2. Regular Updates: Keep client informed of progress
  3. Document Everything: Keep all agreements in writing
  4. Address Issues Early: Don’t let small problems grow
  5. Professional Communication: Stay courteous always

Warning Signs

Watch for these red flags:
  • Client becoming unresponsive
  • Scope changing without documentation
  • Vague or contradictory feedback
  • Delays in approving work
  • Communication moving outside platform

Impact on Your Profile

Dispute Outcomes

ResultProfile Impact
Resolved in your favorNo negative impact
Mutual compromiseMinimal impact
Resolved against youMay affect standing
Pattern of disputesSerious concern, review required
One dispute won’t ruin your profile, but patterns of disputes will trigger a review of your account.