Linear Project Updates
Stakeholders want answers to three questions: how is the project going, what worries the team, and what happens next. Project updates answer those questions in writing. A short post replaces many status meetings and keeps everyone informed.
What a Project Update Contains
Each update has a health marker and a written summary. The project lead posts it on the project page, and followers receive it in their inbox.
| Health | Meaning | Typical Signal |
|---|---|---|
| On track | Work moves as planned | Milestones hit their dates |
| At risk | A problem threatens the plan | A key issue stays blocked |
| Off track | The plan needs a change | The target date will pass without action |
Everyday Comparison
Think of a pilot's announcement during a flight. The pilot reports the current position, mentions weather ahead, and gives an arrival time. Passengers relax because they know the situation. Project updates give your stakeholders the same calm.
PROJECT UPDATE · Customer Portal · Week 6 Health: AT RISK Progress Login and invoices are complete (22 of 35 issues) Risk Payment provider approval takes longer than planned Next Prepare a fallback test mode; review on Friday
Post an Update
- Open the project page.
- Find the updates section and choose to write a new update.
- Select the health status.
- Write the summary.
- Publish the update.
Linear can send reminders to project leads on a schedule. Choose a rhythm that matches the project pace, such as weekly for fast projects and every two weeks for slower ones.
Write Updates People Read
Lead With the Headline
State the health and the main message in the first sentence. Busy readers stop after one line, and that line must carry the key point.
Use Facts and Numbers
Report completed issues, milestone dates, and open risks. Numbers like "22 of 35 issues complete" beat phrases like "good progress".
Name the Risks
Describe each risk in one sentence and name the person who owns the response. Early honesty gives leaders time to help.
End With Decisions Needed
List any question that needs an answer from readers. Specific requests lead to quick replies.
Read Updates as a Stakeholder
Follow the projects that matter to you. Open the initiative page to see updates from every project beneath it. Scan the health markers first, then read the summaries of any project marked At risk or Off track.
Team Habits
- Post on a fixed day so readers know when to expect news.
- Keep each update under 150 words.
- Update the health marker whenever the situation changes, even between scheduled posts.
- Reply to comments on updates to keep conversations in one place.
Common Mistakes
Some leads mark every update On track to avoid worry. This habit hides problems until they grow large. Other leads write long essays that nobody finishes. Honest, short updates build trust and speed up decisions.
Sample Update Library
On Track Example
"Milestone two finished two days early. The team starts payment work on Monday. No open risks."
At Risk Example
"Design approval slipped by one week. We pulled forward testing tasks to protect the launch date. We need a decision from the design lead by Thursday."
Off Track Example
"The vendor API changed and breaks our login flow. We propose to move launch by three weeks or cut the social login feature. Leadership input is needed this week."
Each example states the situation, the effect, and the request in a few sentences. Copy the pattern for your own posts.