Skip to main content

​
Expert Delivery Review & Client Acceptance

​
Overview

When your expert completes development work, you need a clear process to review deliverables, verify quality, and release payment. This feature gives you structured review workflows with evidence-based acceptance or rejection, automatic escrow release, and dispute resolution if requirements aren’t met. You stay in control of quality without micromanaging the technical details.

​
Step-by-Step Guide

​
For Experts Submitting Work

  1. Mark work complete - Navigate to your allocated job in the Expert Dashboard (/developerdashboard) and click “Mark Ready for Review” when your work is finished.
  2. Upload deliverables - Upload your code files, README documentation, and any deployment instructions. The system requires at least these core files and supports packages up to 100MB total size. You’ll see a progress indicator during upload.
  3. Confirm submission - Review your uploaded files in the deliverable manifest. Once you confirm submission, you cannot modify these files. The system logs your submission timestamp for SLA tracking and notifies the client immediately.
  4. Automatic quality checks run - The platform scans all files for viruses, validates that required files are present (README, LICENSE if applicable), and checks code syntax for common languages. If issues are found, you’ll be notified before the client sees anything and can fix problems and resubmit.

​
For Clients Reviewing Work

  1. Receive notification - You’ll get an immediate notification when your expert submits deliverables, with a download link to review all files.
  2. Download and inspect - Visit the Client Review page (/review/clientreview) to download the complete deliverable package as a ZIP archive. The system displays your original specification side-by-side with the deliverables for easy comparison.
  3. Work through the checklist - Mark each specification requirement as pass or fail using the provided checklist. You can save partial progress and resume your review later. The system enforces a 7-day review SLA with automatic escalation if you don’t complete the review in time.
  4. Make your decision:
    • Accept - Click “Accept Delivery” to release escrow funds to the expert within 60 seconds. Both parties can then rate each other, and the job moves to COMPLETED status.
    • Reject - Select specific unmet requirements from the predefined list (incomplete, non-functional, poor quality, wrong scope). Attach evidence files like screenshots, error logs, or test results to document problems. The expert receives detailed feedback within 5 minutes.

​
If Work is Rejected

  1. Expert reviews feedback - The expert sees highlighted unmet requirements with your attached evidence on the Expert Rework View page (/expert/expertreworkview).
  2. Expert chooses a path:
    • Rework - Expert fixes issues and resubmits with change notes explaining what changed. This resets your 7-day review SLA and increments the version number (v1, v2, v3). The system tracks revision history across all attempts.
    • Dispute - If the expert believes requirements were actually met, they can initiate a dispute with supporting evidence. The job moves to the dispute resolution workflow.
  3. Review reworked submission - You follow the same review process for resubmissions. The system limits rework cycles to 3 attempts before forcing a dispute resolution path.

​
Common Questions

What happens if I don’t review deliverables within 7 days?
The system auto-escalates after 7 days. You’ll receive escalation notifications, and platform supervisors may intervene to prevent delays. Your review SLA resets each time an expert resubmits reworked deliverables. Can I reject deliverables with vague feedback like “not what I wanted”?
No. The system requires you to select specific unmet requirements from your original specification. You must choose from predefined rejection reasons (incomplete, non-functional, poor quality, wrong scope) and attach evidence files. This prevents vague rejections and gives experts clear direction for rework. What if I accept deliverables but later find critical bugs?
Once you accept delivery, escrow releases immediately and the job closes. The acceptance creates a permanent audit trail with timestamp and acceptance terms. If you discover issues after acceptance, you cannot reopen the original review. Contact support to discuss options, which may include creating a new job for bug fixes. How many times can I reject and request rework?
The system limits rework cycles to 3 attempts. After the third rejection, the platform forces both parties into formal dispute resolution. This prevents endless rework loops while giving reasonable opportunity to meet requirements. What happens to deliverable files that are too large to download?
The system enforces a 100MB total package size limit. Experts cannot submit packages larger than this. If you need access to larger assets (like video files or databases), work with your expert to use external file sharing services and include access instructions in the README.

​
Troubleshooting

Problem: Upload shows “processing” but never completes
Check your internet connection and file sizes. The 100MB limit applies to the total package. If individual files are corrupt or extremely large, the upload may hang. Try uploading files in smaller batches or compress files before upload. Problem: Expert disappeared after submission but I need changes
If an expert doesn’t respond to rejection feedback within the platform’s expected timeframe, escalate through the dispute resolution workflow. Platform supervisors will intervene, potentially reassigning work or mediating the situation. Problem: I clicked “Accept” by mistake
Acceptance triggers immediate escrow release and cannot be reversed. Contact support immediately if this happens. The platform may be able to assist depending on how quickly you report the error, but there’s no guarantee of fund recovery once escrow releases. Problem: Quality checks failed but I think the code is fine
Quality checks flag common issues like virus signatures, missing required files, or syntax errors. Review the specific failures in the quality report. If you believe the checks are wrong, experts can fix flagged issues and resubmit before your review even begins. This prevents you from reviewing broken code. Dispute Resolution - If you and your expert cannot agree on whether requirements were met, the formal dispute resolution workflow provides AI-assisted analysis, assigned adjudicators, and executive appeals. This feature connects directly when either party initiates a dispute from a rejection. Expert Allocation & Matching - Before delivery review happens, you need the right expert assigned to your job. This feature handles skill matching, expert selection, and allocation - setting up the relationship that leads to deliverables you’ll review. Escrow Management - The escrow system holds your funds securely during development and releases them automatically when you accept deliverables. Understanding escrow status, funding, and release timing helps you manage cash flow and expert expectations during the review process.