How Project Tracking Is Used in a Logistics Company
Project tracking in logistics is rarely “nice to have.” It’s how teams keep customer promises, coordinate across departments, and spot risks early, especially when work depends on many moving parts.
In this story, Radiant’s corporate team uses Confluence with the help of Handy Macros as the hub for tracking projects. Their approach is simple, fast to maintain, and built for day-to-day accountability, not just for reporting.
The real-life setup: one Confluence table used every day
Radiant Logistics operates a global network of more than 100 locations, providing technology-enabled freight forwarding, brokerage, and value-added logistics services across a broad range of industries.
Over 50 people across Radiant’s Corporate Team are involved in multiple projects and rely on a project tracking table in Confluence daily. The same table also supports a weekly, high-level overview, therefore, leadership and delivery teams can align without switching tools.
A key pattern: each project has its own Confluence page with a table, and selected fields “roll up” into a weekly overview page showing all projects.
This creates a lightweight operating rhythm:
- Team members update project information every day as work progresses.
- The weekly high-level overview gives project stakeholders a single place to review priorities and bottlenecks.
- If something appears to be stuck, the project management teams follow up and update the record.
What they track and why: visibility and accountability first
The team tracks project statuses and a couple of dates, including an estimated UAT (User Acceptance Testing) date, using Handy Statuses and Handy Dates. But the purpose isn’t to build perfect project plans inside Confluence. On the contrary, it’s to make it easy to answer practical questions during cross-team calls using real-time data:
- Are we on track?
- If not, what target was missed?
- What is blocked, by who and why?
- What needs attention right now?
When business stakeholders and developers are on the same call, having these fields visible makes it easier to “call it out” when targets aren’t met and to keep commitments clear.
One important Radiant requirement is the ability to leave date fields blank. When users don’t yet know an estimated UAT date, requiring a date can lead them to enter placeholder information before they can make a realistic estimate. Leaving the field blank allows the project team to add a reliable estimate when one becomes available.
In logistics, this kind of detail matters. Inaccurate dates can flow into dashboards, status emails and other reporting tools, affecting decision-making across teams.
Why they moved away from native Confluence elements
A critical insight from this workflow is the team’s prioritization: speed of use.
Radiant updates the table constantly, which means every extra click or workaround increases the chance that someone won’t update it at all. And if the table isn’t current, people stop trusting it. Because of that, they don’t treat those manual date fields as the ultimate source of truth. Instead, they plan to rely more on Handy Status History for querying and analysis, because it’s easier to manage consistently over time.
The team previously tried using Confluence’s built-in inputs and task tracking tools as/date and /status. In practice, they found those hard to track at scale. Confluence collaboration hub or a knowledge base is easier to maintain, but robust project tracking requires patterns that stay usable as the number of projects grows.
That’s why they moved to a table-based structure using Handy Macros: it’s more controllable, easier to scan, and better suited to an operational cadence for team collaboration. In addition, most of the macros work without switching to editing mode.
A simple project tracking Confluence workflow map with the help of Handy Macros
Here’s a compact view of how this logistics team’s Confluence tracking behaves in day-to-day work:
| Project moment | What triggers an update | What gets updated | Why it matters |
|---|---|---|---|
|
Work starts |
Project becomes “In progress” |
Start date (once known) with Handy Date |
Creates clarity on when delivery actually began |
|
UAT planning |
Dev team can estimate realistically |
Estimated UAT date (kept blank until then) with Handy Date |
Avoids fake dates that break metrics |
|
A delay happens |
Weekly call or daily review shows mismatch |
Delay reason (in a comment or a textbox) |
Replaces guessing with visible context |
|
Ongoing progress |
Document moves through stages |
Status changes + history with Handy Status |
Helps keep stakeholders aligned |
At Stiltsoft, we build apps that extend Atlassian tools without forcing teams to stitch together a dozen add-ons. If your teams already live in Confluence, the goal is organizing seamless project management to make tracking feel natural. It should be fast to update, easy to review, and reliable enough to drive decisions. Handy Macros for Confluence helps teams structure dynamic pages for operational work where “weekly overview” and “daily updates” need to work without friction.
More Confluence use cases with Handy Macros:
