Skip to main content

​
Expert Delivery Review & Client Acceptance

​
Overview

When your expert ships code, this feature lets you review the deliverables against your spec and decide whether to accept or reject. Acceptance releases payment from escrow to the expert. Rejection sends specific feedback so the expert can fix issues and resubmit. This builds accountability into every delivery and protects your payment until the work meets your requirements.

​
Step-by-Step Guide

​
For Experts: Submit Your Work

  1. Navigate to your allocated job in the Expert Dashboard (/developerdashboard)
  2. Click “Mark Ready for Review” when your work is complete
  3. Upload your deliverables - you must include code files and a README (up to 100MB total)
  4. Add deployment instructions and test results if your spec requires them
  5. Confirm submission - the system runs automated quality checks (virus scan, syntax validation, required files check)
  6. Once checks pass, the client receives a notification with a download link
  7. You cannot modify deliverables after submission

​
For Clients: Review and Decide

  1. You receive a notification when the expert submits deliverables
  2. Open the Client Review page (/review/clientreview) to see the submission
  3. Download the complete deliverable package as a ZIP file
  4. Review code side-by-side with the original specification requirements
  5. Check off each requirement in the provided checklist as pass or fail
  6. Test locally and document any issues with screenshots or error logs
  7. You have 7 days to complete your review (save partial progress anytime)
  8. Make your decision:
    • Accept: Click “Accept Delivery” to release escrow funds to the expert within 60 seconds
    • Reject: Select specific unmet requirements from your spec, attach evidence (screenshots, logs), and submit feedback

​
After Acceptance

  1. Both you and the expert can rate each other
  2. The job status updates to COMPLETED
  3. The expert receives immediate notification of payment
  4. An audit trail records the acceptance timestamp and terms

​
After Rejection

  1. The expert receives detailed feedback within 5 minutes
  2. The expert can either resubmit revised work with change notes or initiate a dispute
  3. If resubmitting, you enter a new review cycle with full revision history visible
  4. The system allows up to 3 rework attempts before forcing dispute resolution
  5. Your 7-day review SLA resets with each resubmission

​
Common Questions

What happens if I don’t review within 7 days?
The system auto-escalates overdue reviews. You’ll receive reminders as the deadline approaches. Extended delays may trigger intervention from a Fiftyknots supervisor to prevent project stalls. Can the expert see my rejection feedback?
Yes. The expert receives the exact requirements you marked as unmet, your written feedback, and any evidence files you attached. Transparency helps experts fix issues faster. What if I accept the work but find critical bugs later?
Acceptance is final for escrow release. Test thoroughly before accepting. If you discover issues after acceptance, you’ll need to negotiate separately with the expert or open a support ticket for guidance. How many times can I reject the same deliverable?
The expert gets 3 resubmission attempts. After the third rejection, the system forces both parties into formal dispute resolution to prevent endless rework loops. What quality checks run automatically before I see the deliverables?
The system scans all files for viruses, validates that required files are present (README, LICENSE if specified), and checks code syntax for common languages like JavaScript, Python, and Java. The expert sees flagged issues before you start your review.

​
Troubleshooting

Download link not working or files too large
If the deliverable package exceeds 100MB, contact the expert through Project Messaging (/project-messaging) to arrange alternative transfer. Large files may time out during ZIP generation. Expert disappeared after I rejected the work
If the expert doesn’t respond within the expected timeframe after rejection, escalate through the Dispute Dashboard (/escrowdashboard). Fiftyknots will assign a supervisor to investigate and resolve. I can’t find specific requirements to select when rejecting
The rejection form pulls requirements directly from your confirmed specification. If requirements are missing or unclear, you may need to document the issue in free-form feedback. Consider escalating to dispute if the spec itself was ambiguous. Automated quality checks keep failing
The expert needs to fix flagged issues before resubmitting. Common failures: missing README, syntax errors in code, or files that trigger virus scans. The expert sees detailed error messages explaining what to fix. Expert Allocation & Matching - Before delivery happens, you need the right expert assigned to your job. This feature matches experts to your requirements based on skills and availability. Dispute Resolution & Adjudication (Feature 008) - If you and the expert can’t agree on whether work meets requirements, this formal process assigns a neutral adjudicator to review evidence and make a binding decision. Escrow Funding & Management - Understand how your payment is held in escrow during the project and released upon acceptance. This feature protects both parties during delivery and review.