# Recipe: Upload against a brief
A page for one person who sends files to the team: their name, the week and the due date, the brief, and one card per task. Each card has its own upload; a file shows at once with its progress, then waits for review. When the team asks for a redo, the card turns orange with the team's note, and a button always points at the next thing to do. Light and dark themes follow the visitor's system, with a toggle.
## When to use it[](#when-to-use-it "Direct link to When to use it")
* Someone outside the team sends files for a list of tasks: a creator filming scripts, a photographer delivering a shot list, a supplier sending product images.
* One board per person. Give each their own app, or point one app at each person's board.
* Not for showing a board (use the [gallery](/docs/guides/hosted_apps_recipe_gallery.md)) or for the team deciding on work (use [review](/docs/guides/hosted_apps_recipe_review.md)).
## How the board drives it[](#how-the-board-drives-it "Direct link to How the board drives it")
Everything the person reads comes from their board, so the team changes the brief in Playbook and the page follows within five minutes, with no redeploy.
* **The board's title** is the person's name.
* **The board's description** is the brief, one item per line. Every line is optional; lines the page does not recognise become the introduction.
```
Week 12
Due: Friday, 20 March
Hi Sam! Four short pieces about the coast this week. Film vertical and keep each under 30 seconds.
Scripts: https://example.com/scripts/week-12
Script 1: Morning swim, in one take
Script 2: What the tide left behind
Script 3: Three spots I'd show a friend
Notes:
Daylight only, no ring light.
Leave two seconds of quiet at the start and the end.
```
* **Uploads** are titled `Script 2 – take-1.mp4` by the page. The prefix is how a file finds its task, so the team should keep it when renaming. Files sent under Extras keep their own names.
* **Review happens in Playbook.** The status `Changes requested`, with the reason in the asset's description, turns the task into a redo and shows the reason as a note. `Approved` marks it done. Both statuses must exist in the workspace.
* **Uploads must be allowed**: the board's share link has Allow uploads (no password, no email form), or the visitor signs in as someone who may upload. See [uploads from visitors](/docs/guides/hosted_apps.md#uploads-from-visitors).
Use `password` access for one person, and tell them the password apart from the link.
## The files[](#the-files "Direct link to The files")
`index.html`:
```
Your tasks