> ## 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.

# Safe Hiring Practices on Fundwork | Trust & Safety

> Learn how to hire safely on Fundwork — review profiles, use milestones, set clear deliverables, and keep all work on-platform for full protection.

Before you post an opportunity or accept a proposal, take a moment to set yourself up for a smooth engagement. Fundwork's on-chain identity layer gives you real, verifiable signal about the people you work with — but a few extra habits go a long way toward protecting your time and money.

## Review Profiles Carefully

Every Fundwork user is identified by their **.base.eth name**, which anchors their reputation to a persistent on-chain identity. Before you hire, dig into what their profile tells you.

<AccordionGroup>
  <Accordion title="Check completed work history">
    Navigate to a worker's profile and review their completed opportunities on Fundwork. Each completed engagement generates an on-chain payment receipt, so you can verify real, paid work — not just self-reported experience. Look for a pattern of successful completions in your relevant domain before extending an offer.
  </Accordion>

  <Accordion title="Evaluate their .base.eth identity">
    A well-established .base.eth name with a history of on-chain activity is a stronger trust signal than a brand-new identity. While new accounts can still be excellent workers, treat an account with no on-chain history as you would any unknown counterparty — start small and build trust incrementally.
  </Accordion>

  <Accordion title="Read any public feedback">
    Where available, review any public feedback or ratings left by previous clients. Pay attention to comments about communication, deadline adherence, and quality of deliverables — these are often more revealing than star ratings alone.
  </Accordion>
</AccordionGroup>

## Structure Work to Manage Risk

<AccordionGroup>
  <Accordion title="Use milestones on large contracts">
    Break larger projects into milestones with clearly defined deliverables and payment amounts attached to each. Releasing payment incrementally as work is approved — rather than upfront in one lump sum — keeps both parties accountable and limits your exposure if expectations diverge mid-project.
  </Accordion>

  <Accordion title="Define deliverables before you hire">
    Ambiguity is the most common root cause of disputes. Before you finalize a hire, write out exactly what you expect: scope, format, deadline, acceptance criteria, and revision policy. Share this in your opportunity description and confirm that the worker agrees before work begins. The clearer your brief, the smoother the engagement.
  </Accordion>

  <Accordion title="Start with a small paid test task">
    If you're unsure about a new worker, consider posting a small, well-scoped test task first. A modest paid task lets you evaluate quality, communication, and reliability with limited risk before committing to a larger contract.
  </Accordion>
</AccordionGroup>

## Keep Work On-Platform

<Warning>
  Do not move work or payments off Fundwork. Paying workers through external channels — or accepting off-platform payment as a worker — removes you from Fundwork's payment receipt system and eliminates any ability to seek support in a dispute.
</Warning>

Fundwork's built-in opportunity structure exists to protect both clients and workers. Every on-platform payment creates a transparent, on-chain receipt that serves as an immutable record of the engagement. When you work outside the platform:

* You lose access to Fundwork's trust infrastructure
* Payment receipts are no longer generated
* You have no recourse through Fundwork support if something goes wrong

Always use Fundwork's opportunity and payment flow from start to finish.

## Communication Best Practices

<Tip>
  Keep all substantive communication about deliverables, timelines, and scope changes inside Fundwork's messaging system. This creates a clear, timestamped record you can reference if a question arises later.
</Tip>

<Tip>
  Confirm scope changes in writing before any additional work begins. A quick written confirmation protects both you and the worker if expectations need to be revisited.
</Tip>

<Tip>
  Respond promptly to worker questions. Delays in answering blockers are one of the most common reasons projects run over deadline — staying responsive keeps projects on track.
</Tip>

<Tip>
  Before approving final payment, review deliverables against your original acceptance criteria rather than a general impression of quality. This keeps the review objective and fair for both parties.
</Tip>