# A progress update ready to review, from the folder's point

> From the folder’s point, the composer opens on a progress update already written: where the folder stands, what is expected. You review it, then publish it.

## Writing where the folder stands takes time

The client wants to know where their folder stands, what is expected of them and what is being prepared. To say it, you reopen the folder, reread the milestones, find the open requests, then write it all by hand.

## A draft from the folder's point

In the "Folder point" drawer, the "Prepare a progress update" button opens the composer with a draft already written:

- **Where the folder stands**: the last milestone reached, with its date, and the next one, with its own.
- **What we need from you**: the open requests waiting on participants, with their due date and the person concerned.
- **What we are preparing**: the open points on your side.
- **Decided lately**: the decisions and approvals of the last thirty days.

Each request it cites links to its original card, in its own publication. The reader answers there: nothing is copied, and the answer stays where it will be followed.

## Read and published by a team member

The draft is addressed to the team and to the folder's contacts. It says only what the contacts can read: never a request addressed to a single contact, a confidential publication or an internal note.

It is never sent on its own. It opens in the composer: you read it, change what you want, and it goes out only when a team member publishes it. Once published, it is a publication like any other: the client reads it in the folder.

## In practice

**A folder moving along, a client asking where things stand.** You open the folder's point, prepare the progress update, check the dates, remove a paragraph and publish. The client sees the milestone reached, the next one, and what is expected of them, with a link to each request.

## What it does not do

- **It does not publish itself.** Nothing goes out until a team member has read and published it.
- **It is for the team.** Only members see the folder's point and its button.
- **It is not written in advance.** The draft reflects the folder at the moment you prepare it.
- **No separate plan**: the progress update is included in every plan.

## See also

The progress update starts from the folder's point, described under [Cockpit](/en/features/cockpit), and is written in the [composer](/en/features/writing-a-request). It relies on [milestones](/en/features/jalon).