> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fundwork.app/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Submit Work on Fundwork | All Opportunity Types

> Learn how to submit work for contracts, bounties, and campaigns on Fundwork — what to include, how each flow differs, and what makes a strong submission.

Submitting your work clearly and completely is one of the most important things you can do on Fundwork. A well-structured submission helps the client review your work accurately and speeds up approval and payment. The exact flow differs depending on whether you're on a contract, a bounty, or a campaign.

## What Every Strong Submission Includes

Regardless of opportunity type, a high-quality submission typically contains:

* **A link or attachment to your deliverable** — the actual work product the client can review or download
* **Notes on your approach** — a brief explanation of the decisions you made and why, especially if the deliverable isn't self-explanatory
* **Any files the listing specifically requests** — check the requirements section for formats, naming conventions, or supplementary materials
* **Context on anything incomplete or in progress** — for contract milestones, flag any blockers or questions before the client reviews

***

## Submission Flows by Opportunity Type

<Tabs>
  <Tab title="Contract">
    Contract work is broken into milestones. You submit once per milestone, not all at once at the end.

    <Steps>
      <Step title="Complete the milestone deliverable">
        Work through the scope defined for this milestone. Refer back to the listing's deliverables and milestone description to confirm you've met the requirements before submitting.
      </Step>

      <Step title="Open the milestone submission form">
        Navigate to your active contract and open the submission form for the current milestone.
      </Step>

      <Step title="Attach your work">
        Add a link or upload the files for this milestone. If your deliverable lives in an external tool (Figma, GitHub, Notion, etc.), paste a direct link with any necessary access permissions set.
      </Step>

      <Step title="Add your notes">
        Describe what you built or produced, any decisions you made, and anything the client should know before reviewing. Clear notes reduce back-and-forth and help the client approve faster.
      </Step>

      <Step title="Submit and wait for approval">
        Submit the milestone. The client reviews your work and either approves it — triggering the USDC payment for that milestone — or requests revisions.
      </Step>
    </Steps>

    <Note>
      Each milestone is reviewed independently. Don't move on to the next milestone until the client has approved the current one, unless your contract specifies otherwise.
    </Note>
  </Tab>

  <Tab title="Bounty">
    Bounty submissions are one-shot. You produce your completed work and submit it once before the deadline.

    <Steps>
      <Step title="Confirm the deadline">
        Check the bounty listing for the exact deadline before you start. The submission window closes at that time with no exceptions.
      </Step>

      <Step title="Complete your work">
        Produce your deliverable according to the listing's requirements and judging criteria. Your submission is competing against everyone else who enters, so give it your best effort.
      </Step>

      <Step title="Open the submission form on the listing page">
        Go to the bounty listing and open the submission form.
      </Step>

      <Step title="Attach your deliverable and notes">
        Add your link or files and include a clear description of your approach. Explain why your submission meets the judging criteria — don't make the client guess at your reasoning.
      </Step>

      <Step title="Submit before the deadline">
        Submit your entry. After the deadline, the client reviews all submissions and selects the winner(s). You'll be notified if your submission is selected.
      </Step>
    </Steps>

    <Tip>
      Address the judging criteria directly in your submission notes. If the listing says the client values originality and technical precision, call out specifically how your work demonstrates both.
    </Tip>
  </Tab>

  <Tab title="Campaign">
    Campaign submissions earn a fixed USDC reward per qualifying entry, until the pool runs out.

    <Steps>
      <Step title="Read the qualifying criteria">
        Before you produce anything, read the campaign requirements closely. Only submissions that meet the qualifying criteria receive a reward.
      </Step>

      <Step title="Complete your submission">
        Produce your work according to the requirements.
      </Step>

      <Step title="Submit through the campaign listing">
        Open the campaign listing and submit your work. Include all files, links, and information the campaign requests.
      </Step>

      <Step title="Receive your reward if you qualify">
        If your submission meets the criteria, the fixed USDC reward is sent to your payout address on Base. If the pool has already been exhausted, no further rewards are issued.
      </Step>
    </Steps>

    <Note>
      Campaigns are an alpha feature. Details around qualification and reward processing may change. Check the campaign listing for the most current requirements.
    </Note>
  </Tab>
</Tabs>

***

## Common Submission Mistakes to Avoid

<AccordionGroup>
  <Accordion title="Submitting a broken or permission-blocked link">
    Always test your links before submitting. A Figma file set to "only me" or a private GitHub repo gives the client nothing to review. Set sharing permissions to allow the client to view or access the work.
  </Accordion>

  <Accordion title="Leaving out submission notes">
    Deliverables without context force the client to make assumptions. A few sentences explaining your approach, your choices, and any trade-offs you made can prevent revision requests and accelerate approval.
  </Accordion>

  <Accordion title="Submitting incomplete work for a bounty">
    Bounty submissions must be complete at submission time. Unlike contracts, there's no revision loop built into the bounty format. Submit only when your work is finished.
  </Accordion>

  <Accordion title="Missing required files or formats">
    Check the listing's requirements section for specific file types, naming conventions, or supplementary materials. Missing a required element can disqualify your submission.
  </Accordion>
</AccordionGroup>