> ## 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 Review Applicants for Your Fundwork Contract

> Learn how to evaluate applicants for your Fundwork Contract — what to look for in their profile, portfolio, and application message.

After you publish a Contract, workers can apply. Each application gives you a snapshot of who the person is, what they've done, and why they think they're the right fit for your specific project. Take time to review each application carefully — the person you hire will be your collaborator through every milestone.

<Steps>
  <Step title="Open your Contract dashboard">
    Navigate to your posted Contract and open the **Applicants** tab. You'll see everyone who has applied, listed with their name, Base identity, and the time they applied.
  </Step>

  <Step title="Review their Base identity and profile">
    Each applicant has a Base account, which may include a **.base.eth** name. Look at their Fundwork profile to understand:

    * Their display name and Base identity
    * Any linked work history or past completions on Fundwork
    * Their skills and the categories they've tagged themselves in

    <Tip>
      A .base.eth name signals a worker who's established on Base. While it's not a credential on its own, it's a useful signal of engagement with the ecosystem.
    </Tip>
  </Step>

  <Step title="Examine their portfolio">
    If the applicant has linked portfolio work, review it closely. Ask yourself:

    * Does the quality of their prior work match what you need?
    * Have they done work of similar scope or complexity?
    * Is their style or approach aligned with your project's requirements?

    For creative work (design, video, writing), look for samples that are close in format or audience to your project. For technical work (development, research), look for demonstrated familiarity with relevant tools or environments.
  </Step>

  <Step title="Read their application message">
    The application message is where applicants explain their fit for your specific opportunity. A strong application will:

    * Reference your deliverables by name — not just the title
    * Explain *how* they'd approach the work, not just *that* they can do it
    * Raise any relevant questions or flag constraints they noticed in your posting
    * Be written clearly and professionally

    A generic message ("I'm a great designer with 5 years of experience") tells you little. A specific message ("For milestone 1, I'd start with a mobile wireframe audit of your existing flow before designing the new structure") tells you how they think.

    <Tip>
      Prioritize applicants who engaged with the details of your posting over those with impressive-sounding but generic messages. Specificity is a proxy for care.
    </Tip>
  </Step>

  <Step title="Compare applicants side by side">
    Once you've reviewed all applicants, compare them across the dimensions that matter most for your project:

    * **Relevant experience** — have they done this type of work before?
    * **Communication quality** — did they write a thoughtful application?
    * **Milestone understanding** — do they seem to understand the scope and structure?
    * **Fit** — does their style, approach, or background align with your project's needs?

    You're hiring one person, so don't rush. Take the time to feel confident before you move to selection.
  </Step>
</Steps>

<Note>
  You're not obligated to hire anyone who applies. If no applicant is a strong fit, you can wait for more applications or revisit your posting to make the requirements clearer.
</Note>