Project Updates
Project updates let team leads and members share structured status reports directly within SetGet. Instead of relying on external channels for progress communication, you can post updates inside the project where the work lives. Updates are visible to all project members and provide a timestamped record of how the project is progressing.
Posting an update
- Open the project.
- Navigate to the Updates section in the project sidebar (or click Updates in the project header).
- Click New Update.
- Write your update using the rich text editor.
- Click Post Update.
The update is published immediately and visible to all project members.
Update format
Each update consists of:
| Field | Description |
|---|---|
| Title | Optional headline summarizing the update |
| Body | Rich text content with the same formatting as the page editor |
| Status indicator | Traffic light status: On Track, At Risk, or Off Track |
| Posted by | The member who created the update (set automatically) |
| Posted at | Timestamp (set automatically) |
Rich text body
The update body supports full rich text formatting:
- Headings and paragraphs
- Bold, italic, and inline code
- Bullet and numbered lists
- Checklists
- Code blocks
- Images and file attachments
- Links and @mentions
- Tables
Status indicator
The status indicator provides a quick visual summary of project health:
| Status | Color | Meaning |
|---|---|---|
| On Track | Green | The project is progressing as planned |
| At Risk | Yellow | There are concerns that may affect the timeline or scope |
| Off Track | Red | The project is behind schedule or facing significant blockers |
Select the status when creating the update. The latest update's status is displayed on the project card and in the project list.
Who can post updates
| Role | Can post | Can edit own | Can delete own | Can delete others |
|---|---|---|---|---|
| Project lead | Yes | Yes | Yes | Yes |
| Project admin | Yes | Yes | Yes | Yes |
| Project member | Yes | Yes | Yes | No |
| Workspace guest | No | N/A | N/A | N/A |
Any project member can post an update. Typically, project leads or designated owners post regular status updates, but the feature is available to the entire team.
Update visibility
Project updates are visible to:
| Audience | Access |
|---|---|
| Project members | Full access — can view, react, and comment on updates |
| Workspace members (non-project members) | No access — updates are scoped to the project |
| External users | No access — updates are not published externally |
TIP
To share an update with stakeholders who do not have access to the project, consider writing the content as a page and publishing it. See Publish Pages.
Viewing and browsing updates
The Updates section displays all updates in reverse chronological order (most recent first). Each entry shows the title, status indicator, author, date, and a preview of the body text.
Click an update to open the full content view.
Filtering updates
Filter the update list by:
| Filter | Description |
|---|---|
| Status | Show only On Track, At Risk, or Off Track updates |
| Author | Show updates by a specific team member |
| Date range | Show updates from a specific time period |
Commenting on updates
Project members can comment on updates to ask questions, provide feedback, or acknowledge the status.
- Open the update.
- Scroll to the comment area.
- Type your comment and submit.
Comments on updates follow the same rules as work item comments — they support rich text, @mentions, and reactions.
Reacting to updates
Add emoji reactions to updates to express acknowledgment without adding a comment. See Reactions.
Use cases
Weekly status report
Post a weekly update summarizing what was completed, what is in progress, and what is planned for the next week. Use the status indicator to flag any risks.
Milestone communication
When the team reaches a significant milestone, post an update celebrating the achievement and outlining next steps.
Blocker escalation
When the project hits a blocker, post an At Risk or Off Track update describing the issue, its impact, and what is needed to resolve it.
Sprint summary
At the end of each sprint, post an update summarizing completed work, carried-over items, and velocity metrics.
Stakeholder briefing
For projects with external stakeholders, post regular updates that can be referenced during review meetings or shared via published pages.
Best practices
- Post regularly — establish a cadence (weekly or bi-weekly) and stick to it. Consistency builds trust with stakeholders.
- Be honest about status — use At Risk and Off Track indicators when appropriate. Hiding problems delays resolution.
- Keep updates concise — focus on the key points: progress, blockers, and next steps. Link to relevant work items or pages for detail.
- Use @mentions for action items — if an update contains an action for a specific person, mention them to ensure they see it.
- Review past updates — before writing a new update, check the previous one to ensure continuity and track progress on previously mentioned items.
Related pages
- Comments and Activity — Commenting on work items
- Reactions — Emoji reactions
- Notification Center — Notification inbox
- Publish Pages — Share content publicly