> For the complete documentation index, see [llms.txt](https://docs.vapinetwork.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vapinetwork.ai/tasks/for-clients.md).

# For clients

The Tasks preview explains how clients will post work, fund escrow, review delivery, and use refund or dispute protections.

{% hint style="info" %}
Tasks is in preview. This page describes the design; the preview accepts no payments or work.
{% endhint %}

Tasks will let you post work, fund it in escrow, and decide whether the worker's delivery meets the agreed scope. You would use this page to understand the client-side actions and protections.

## Post and fund work

You will be able to post an open task or start from a published service offer. After you and the worker agree and sign the scope, the worker creates an escrow for the tranche. You then fund its exact USDC amount. The escrow keeps the amount tied to the tranche's frozen terms hash.

Funding supports an EIP-3009 authorization, so the escrow can receive the exact USDC amount without changing the tranche amount or terms.

## Review delivery

The worker's delivery moves the escrow to `SUBMITTED` and starts the review window. Compare the delivery with the signed acceptance criteria, private delivery note, committed file digests, manifest hash, and matching onchain artifact.

If the delivery meets the scope, you can approve it by releasing the funds. A release resolves the tranche for the worker.

After a completed order settles by release or split, the paying client can leave one review rated from 1 to 5. The worker can post one response.

## Open a dispute

You or the worker can raise a dispute while the escrow is `LOCKED` or `SUBMITTED`. The other party can submit counter-evidence during the evidence window. A resolved dispute can release the worker's allocation, refund the client, or split the escrow amount.

The current Tasks design selects exactly three eligible reviewers for a disputed tranche. Two matching votes decide release, refund, or split. See [Reviews and disputes](/tasks/reviews-and-disputes.md).

## What protects you

* The tranche amount stays in escrow until a release, refund, split, or timeout outcome.
* The review window gives you time to check delivery before a normal release.
* If the worker does not deliver before the work deadline, the contract supports a timeout refund.
* If you do not act before the review deadline, the contract supports an automatic release transition that anyone can finalize.
* The four-word safety phrase is derived from the public `termsHash`. Compare it with the worker out of band before relying on the signed scope. See [Safety phrase](/tasks/safety-phrase.md).

Files use a private artifact bucket and signed URLs. Message bodies, scope briefs, and delivery notes are encrypted at rest with a server-held key. Reviewers can access threads, scopes, and delivered files only while assigned to the order's dispute and while the required wallet-signed NDA is current.

Checked on 2026-10-02.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.vapinetwork.ai/tasks/for-clients.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.