Progress reports
Writing an update, pulling in the work, and getting it out as PDF, Word or CSV.
Reports in the Management group is for the update you send outward — to a client, a manager, a stakeholder.
Writing one
Click New report, give it a title, and write. The title is editable at any time.
Pulling in the work
Insert from tasks opens a picker over the project's real tasks, so you are not retyping what the board already knows.
- Filter by who created it, who it is assigned to, or both. Both exist because people often create a task without assigning it to themselves.
- Select all, with the checkbox reflecting a partial selection.
- Tasks already in the draft are marked, so a second pass does not duplicate them.
- Descriptions are included by default — turn them off for a terser update.
Inserted tasks are grouped by their board list, with completed ones marked ✓ Done.
Grouping by list rather than status is deliberate: plenty of teams use lists as areas of
work, and grouping by status would put the whole report under one heading.
You can include internal tasks in a report — sometimes you need to. Nalaras warns you on each internal task you select rather than silently blocking it. Read the warning; the report may be going to a client.
Sending and exporting
| Format | Good for |
|---|---|
| Sending as a document — opens a clean print view | |
| Word | When the recipient will edit it |
| CSV | Sorting, filtering, or pasting into a tracker |
The CSV unpacks the report rather than dumping it into one cell: each task becomes a row with its section, status and details.
On Pro, reports can also be shared to the client portal, and scheduled digests send progress automatically on the cadence set per member.
Drafts are never saved by accident
Opening the editor and closing it again does not create a blank report. Only an explicit save keeps it.