When to use the Activity tab
Open the Activity tab on a Work Package whenever you want to know who has done what and when. It's the place to look when:
- You've come back to a Work Package after a few days off and want to catch up on what's changed
- A client asks who allocated a particular operative and you need a clear answer
- Someone has changed the status without telling you and you want to confirm
- You're chasing the trail of a re-allocation, a dependency change, or a progress update
- You want to drop a comment on the Work Package without picking up the phone
The Activity tab keeps a permanent timeline of every change, so you don't have to rely on memory or hunt through messages.
What gets recorded automatically
Project Commander writes activity entries whenever something meaningful changes on the Work Package. The events you'll see in the feed are:
- Created — when the Work Package was first added
- Updated — when any field is edited
- Status Changed — when the status dropdown is changed
- Allocated — when an operative is allocated to a sub-package
- Deallocated — when an operative allocation is removed
- Dependency Added — when a dependency link is added
- Dependency Removed — when a dependency link is removed
- Progress Changed — when progress is updated, either by hand or by sub-package completion
- Comment Added — when someone leaves a comment
- Duplicated — when the Work Package is duplicated
You don't have to do anything to write these entries — they appear in the feed as they happen.
Opening the Activity tab
- 1
Open the Work Package you want to check.
- 2
Click the Activity tab in the sidebar.
- 3
The most recent entries appear at the top. Scroll down for older ones.
Filtering the log
The activity tab has a filter at the top that lets you narrow the feed to a single type of entry — useful when there's a long history and you only care about, say, status changes.
- Pick a specific type (for example, Status Changed) to see only those entries
- Pick All to see the full feed again
The filter only changes what you see — nothing is deleted from the underlying record.
Loading older entries
The activity log loads in pages of 20 entries at a time. Scroll to the bottom and the next 20 will load automatically. This keeps the page fast even on a Work Package with hundreds of entries — older history only loads when you actually need it.
Adding a comment
The comment box sits at the bottom of the Activity tab. Type your comment and click Post to add it to the feed. It appears in the timeline alongside the automatic entries, with your name and avatar against it.
Public versus internal comments
Every comment has an Internal toggle that controls who can see it.
- Public comments — visible to everyone with access to the Work Package, including any external users (subcontractors or clients) you've shared it with
- Internal comments — visible only to staff users at your company. Use these for notes that shouldn't be shared outside the business
Internal comments are highlighted with an Internal badge in the feed so they're easy to spot at a glance and you don't accidentally read them out to a client.
Attaching files to a comment
You can include file attachments with a comment — they appear inline in the feed entry. This is handy for sharing site photos, documents, or marked-up drawings without needing them to live on their own card somewhere.
Use internal comments for handover notes, cost implications, or concerns that need tracking but shouldn't reach the client. Use public comments for anything that forms part of the legitimate project record everyone should see.
How activity sits alongside sign-off
Sign-off keeps its own card on the Work Package sidebar with its own permanent record. Sign-off events also show up on the Activity tab as a status change to Complete, so the activity feed remains the single source of truth for who-did-what-when. The sign-off card is a focused subset for quick reference.
Real-world examples
- Catching up after annual leave — open the Activity tab, scroll back to your last day in, and read upwards through everything that's happened
- Settling a query about who closed it — filter to Status Changed and find the entry that moved the Work Package to
Complete - Sharing a site photo with the team — drop it into a comment so it sits on the timeline next to the events it relates to
- Logging an internal concern — write an internal comment so it's recorded against the job without the client seeing it
Next steps
- Sign-off — for the permanent record of completed work.
- Getting started with Work Packages — for the Work Package status workflow.
- Allocating operatives — for the allocation events that show up in the activity feed.