> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.cloudraker.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.cloudraker.com/_mcp/server.

# Complete a task

This page covers the two task types **you** do by hand: a **Form** task, where you fill in fields, and a **File upload** task, where you provide documents. The other task types run on their own or are handled by Florent — see [Task types](/playbooks/task-types) for what each one is.

To find the tasks waiting on you, start from [My work](/work/my-work). Click any task to open it inside its run.

## Claim the task first

Most tasks are shared with a group, so you take ownership before you start. Until you claim a task, its fields are greyed out and you'll see **Claim this task to fill it out.** Click **Claim task** and the task becomes yours: its status moves to **In progress**, your avatar appears on it, and the fields become editable.

Claiming is covered in full — including first-to-claim-wins and what you can't claim — on [My work](/work/my-work).

Tasks already assigned to you specifically don't need claiming. For how assignment decides who can claim, see [Assignments and approvals](/playbooks/assignments-and-approvals).

## Do the task

Once the task is **In progress**, the work surface depends on its type. Pick the tab that matches.

A **Form** task asks you to fill in a set of fields — intake details, a decision, or data that becomes a record.

Under the **Fields** panel, complete each field. The helper line reads **Complete the fields below to submit this task.** Required fields are marked, and you can't submit until they're filled.

If Florent pre-filled some fields, they're marked **Suggested by AI**. Check each one — accept it as-is, edit it, or clear it. Suggestions are a starting point; you still submit the form yourself.

The button reads **Submitting…** while it saves. If a required field is empty, you'll see a message like **\{field} is required** — fill it in and submit again.

Some Form tasks create or update a [record](/projects/data) when you submit; others just save their values for later steps. Either way, your job is the same: fill the fields and submit.

A **File upload** task asks you to provide one or more documents — a signed agreement, invoice PDFs, an insurance card.

Each upload field (for example, **Insurance card (front)**) has an **Upload** button. Click it and choose your file. The field shows **Uploading…**, then **Uploaded \{date}** when it's done.

Some fields accept multiple files; others take just one. A field may limit the file types or show a size cap. The largest a single file can be is 50 MiB.

The button reads **Completing…** while it saves. If a required field has no file, you'll see **Upload at least one file to complete this task** — add the file and complete again.

Files you upload belong to the whole project, not just this task. Every later step in the run — and other runs in the same project — can reuse them. See [Project files](/projects/files).

Once you submit, your form becomes read-only. You'll see **Submitted by \{name}** at the top, and you can't edit the fields afterward. Double-check your values before you submit.

## What happens after you submit

What you see next depends on whether the task needs a sign-off.

* **No approval needed** — the task moves to **Completed** and the run continues. Anything downstream that was waiting on this task can now start.
* **Approval needed** — the task moves to **Pending approval** and the approver is notified. You're done; the work counts once they approve it.

You can leave the page either way — the run keeps going. Track the task's status from [My work](/work/my-work).

If your task is sent back, it returns to you marked **Rejected** with the reviewer's reason at the top, and your earlier work is kept as a starting point. Make the fix and submit again. The rules for who approves and what rejection means live in [Assignments and approvals](/playbooks/assignments-and-approvals).

## Where to go next

Find and claim the tasks waiting on you across every project.

See all five task types and which ones a person versus Florent handles.

Approve, correct, or reject what Florent drafted, with citations to the source.

Understand who owns a task and who has to sign it off.