Submitting Work

How to submit your completed work and what to expect during the review process.

Submitting your work is the final step in the development phase. Once submitted, your code goes through a review process before being merged to production.

Before submitting, verify that you've completed all these items:

  • ✓ All PRD features implemented – Every feature in the requirements is built and working
  • ✓ Client has approved – The client has reviewed the preview and given the go-ahead
  • ✓ No console errors – Open DevTools and check for JavaScript errors
  • ✓ Responsive design works – Test on mobile, tablet, and desktop
  • ✓ Cross-browser tested – Check Chrome, Firefox, Safari, and Edge
  • ✓ Authentication works – If applicable, test sign-in/sign-up flows
  • ✓ Data persistence works – Verify Firestore reads/writes function correctly
  • ✓ Environment variables are set – All required env vars are configured in Vercel
  • ✓ No hardcoded test data – Remove any placeholder content or test credentials
  • ✓ Code is clean – Remove console.logs, commented code, and unused files
Don't Rush Submission

Take time to verify everything works. Submitting incomplete or buggy work creates more work for everyone and delays the project.

  1. Push All Changes

    Make sure all your code is pushed to your worker branch on GitHub.

  2. Update Project Status

    On the project page, use the Status Update dropdown to change the status. Progress through: In Progress → Review → Completed.

  3. Notify Customer

    In the Workers section, click Notify Customer to send the client your preview URL with an email notification.

  4. Wait for Approval

    The client reviews your work. Once approved, the project moves to the promotion process.

Status Progression

Use the status dropdown on the project page to track progress:
• Pending → Just claimed, not started
• In Progress → Actively developing
• Review → Ready for client review
• Completed → Client approved
• Delivered → Promoted to production

After submission, your work goes through review:

  1. Automated Checks

    The build process runs to ensure the code compiles and deploys correctly.

  2. Code Review

    If applicable, the code may be reviewed for quality and security issues.

  3. Merge to Staging

    Approved code is merged to the staging branch for final testing.

  4. Production Deployment

    After staging verification, code is merged to main and deployed to production.

Review Timeline

Most submissions are processed within 24-48 hours. You'll receive notification when your work is live in production.

Issues that may cause submission rejection:

  • Build failures – Code that doesn't compile or build properly
  • Missing features – PRD requirements that weren't implemented
  • Security issues – Exposed API keys, insecure database rules
  • Client not satisfied – Outstanding feedback that wasn't addressed
  • Broken functionality – Features that don't work as expected

If your submission is rejected, you'll receive feedback on what needs to be fixed. Address the issues and resubmit.

Ask for Help

If you're unsure whether your work is ready for submission, ask in the Discord #help channel before submitting.