At Doully.io, our arbitration is based strictly on verifiable data. Whether you are an Expert or an Employer, providing organized and granular evidence is the only way to ensure a favorable ruling. Use this expanded checklist to prepare your case.
1. Contractual & Scope Evidence (The Foundation)
- The Original Brief: A copy of the initial project requirements or the specific “Service Description” (Gig) at the time of purchase.
- Mutual Agreement Logs: Screenshots of the exact moment both parties agreed on the price, deadline, and specific deliverables.
- Modification History: If the project scope changed mid-way, you must provide the chat logs where these changes were discussed and confirmed.
- Deadline Extensions: Proof of any agreed-upon extensions to the original timeline.
2. Technical Execution Evidence (For AI & Automation Experts)
- Functional Video Walkthrough: A high-definition screen recording (Loom/MP4) showing the automation logic (n8n, Make, Zapier) and a successful “Test Run” with live data.
- System Architecture/Logic: Screenshots of the workflow canvas to prove the complexity and completion of the logic requested.
- Execution Success Logs: Exported logs or screenshots showing “Success” status for recent runs, proving the system is operational.
- Environment Setup: Proof that all necessary API connections, Webhooks, and Environment Variables were correctly configured.
- Third-Party Screenshots: If the project involved a CRM, Database (Airtable/SQL), or AI model (OpenAI/Anthropic), show proof that the data is correctly flowing into those platforms.
3. Communication & Cooperation Evidence
- The “Unresponsiveness” Log: A chronological record of your attempts to contact the other party, showing timestamps where your messages or requests for information went ignored for more than 24-48 hours.
- Provision of Access: (For Experts) Proof of when you requested credentials and (For Employers) proof of when you provided them.
- Professional Conduct: Documentation of any unprofessional behavior, harassment, or attempts to take the transaction outside of Doully.io (Circumvention).
4. Delivery & Handover Evidence
- Formal Delivery Timestamp: A screenshot of the final “Submit Work” action or the message containing the final assets.
- Asset Accessibility: Proof that all links provided (GitHub repos, Google Drive, Shared Workflows) are active and the other party has the correct permissions to access them.
- Instructional Handover: A copy of the “User Guide” or “Handover Document” you provided to help the Employer manage the system after completion.
5. Conflict-Specific Evidence
- The “Bug” vs. “Feature Request” Debate: If an Employer claims a bug, the Expert should provide proof that the system functions as per the original agreement, and that the “bug” is actually a new feature request.
- Partial Completion: If the project was 80% done before the dispute, provide a breakdown of the completed milestones to justify a partial payment.
Mandatory Submission Standards:
- Chronological Order: Organize your screenshots in the order the events happened.
- No Alterations: Any evidence found to be edited, photoshopped, or tampered with will lead to an automatic loss and permanent account ban.
- Doully System Primacy: We strictly prioritize logs within the Doully.io dashboard. External files are only considered secondary support.