What an Audit Log Is (and Why Agencies Should Look at Theirs)
A deadline moved. A task was reassigned without explanation. A client disputes the scope of what was agreed. In each case, the answer exists somewhere in the project history, if the tool captured it. An audit log is that capture.
Contents
One flat fee for the whole team
Tasks, timers, CRM and invoices in one workspace. From $29 a month, no seat tax.
Start free demo14 days · no credit card
01. What an Audit Log Records
An audit log is a time-stamped record of changes to a system, specifically who changed what, when, and from what value to what value. In a project management context, an audit log records every field change on every task: status moved from In Progress to Done by [person] at [time], deadline changed from October 15 to October 8 by [person] at [time], assignee changed from [person A] to [person B] by [person C] at [time]. This article covers project change-history audit logs. It's distinct from billing audits, which are about finding unbilled hours, not about software change records. Two genuinely different topics that share the word "audit."
"A log that says "deadline updated on October 3" tells you nothing. "Changed from October 15 to October 8 by [person] at 11:22 AM" tells you everything."
02. Why Agencies Need It: Three Real Scenarios
Scenario 1: the deadline that moved A project manager looks at a task and sees a deadline of October 8. She remembers agreeing on October 15. The developer assigned to the task says he didn't change it. Without an audit log, the conversation is a three-way reconstruction from memory. With an audit log: open the task history, see that the deadline changed from October 15 to October 8 on September 25 at 2:47 PM by the account manager. The conversation is now specific and resolvable. Scenario 2: the scope that expanded without a change order A client project closes and the PM reconciles the work delivered against the original scope. Several tasks exist on the board that weren't in the original brief. When were they created? Who added them? An audit log shows task-creation events alongside field changes: the PM can see that three tasks were added in week six by the account manager, on the same day as a client call, providing the attribution needed to determine whether a change order was issued or an ad-hoc scope addition was absorbed. Scenario 3: the access question after a team change A team member leaves the agency. A client calls three months later to say that project files have been accessed from an unfamiliar account. Who had access to what, and when did they last touch the project? An audit log provides contributor-level activity history that answers this question without requiring a conversation with the former employee.
03. What Melororium's History Tab Shows
The History tab is available on Agency and Studio plans. It's not included in the Starter plan. This is stated directly because it matters for the decision about which plan to use. The History tab appears on each project and shows a complete log of all field changes across all tasks in that project. The log is filterable by contributor (show only changes made by [person]), by field type (show only deadline changes), and by date range (show everything from September 1 to September 30). Each log entry shows: the field that changed, the previous value, the new value, the contributor, and the exact timestamp. This is the before/after diff format: you see what the value was before the change and what it became, not a note that something changed.
04. The Before/After Diff and Contributor Filter
The before/after diff is what makes an audit log operationally useful rather than merely present. A log that says "deadline updated on October 3" doesn't tell you whether the deadline moved earlier or later, or by how much. A log that says "deadline changed from October 15 to October 8 by [person] on October 3 at 11:22 AM" tells you everything you need to know. The contributor filter narrows the history to a specific person's changes. For the scenario where someone questions what a particular team member changed on a project, the contributor filter produces a complete list of that person's actions without requiring a manual scan of the full log.
Flat fee · no seat tax
Who changed this deadline? Answer it in ten seconds.
Melororium's History tab shows every project change with before/after diffs, a contributor filter, and a 14-week activity heatmap. Available on Agency and Studio plans.
$29/mo
Starter · 4 users
$59/mo
Agency · 15 users
$119/mo
Studio · 25 users
05. The 14-Week Heatmap
The 14-week activity heatmap at the top of the History tab shows project activity intensity by week, similar to a GitHub contribution graph. Each cell represents one week; darker cells indicate higher activity (more changes, more time logged, more task movements). The heatmap answers a different question than the detailed log: not "what happened," but "when was this project active." A project with a bright band of activity in weeks 3-6 and nothing since looks different from a project with consistent weekly activity for twelve weeks. The heatmap makes this visible without scrolling through the full log. Practical uses: identifying projects that have gone quiet unexpectedly, spotting unusual activity spikes that warrant investigation, and demonstrating to a client that consistent work was happening throughout the engagement.
06. The Client Dispute Use Case
The highest-stakes use case for an audit log is a client dispute about what was agreed, delivered, or changed. Client disputes are often not about the final outcome; they're about the process: who authorized what, when the brief changed, who approved the final direction. An agency with a complete audit log has an objective record for each of these questions. The account manager authorized the scope change on September 12 by adding three tasks to the board. The client approved the concept direction on October 2, the status change from Client Review to Approved at 3:15 PM is in the log. The brief was updated on September 28 by the PM, the before/after diff shows what changed. This record doesn't guarantee winning a dispute. It does prevent disputes from becoming purely he-said-she-said, which is the situation where agencies are most vulnerable regardless of what happened.
07. What Audit Logs Do Not Replace
An audit log records what happened in the project management tool. It doesn't record what was said in a phone call, what was agreed in a client meeting, or what was implied in an email thread. A well-maintained audit log combined with a habit of recording verbal decisions as task comments or Canvas notes produces a more complete project record than either alone. The audit log also doesn't substitute for a change order process. An audit log can show that a task was added in week six without a change order, but the audit log itself doesn't prevent that addition from happening or automatically trigger the change order. Operational discipline and audit log visibility work together; neither replaces the other.
Melororium
Try it in Melororium
Melororium's History tab shows every project change with before/after diffs and contributor filter. Available on Agency ($59/mo, 15 users) and Studio ($119/mo, 25 users) plans.
08. Frequently Asked Questions
What does a project audit log record? A project audit log records every field change on every task in the project: who changed it, from what value, to what value, and at what exact time. In Melororium's History tab, this includes status changes, deadline changes, assignee changes, priority changes, and task creation events. The log is filterable by contributor, field type, and date range. Each entry shows the before value and after value (the before/after diff), not a note that a change occurred. Is the audit log included on every Melororium plan? No. The History tab (audit log) is included on the Agency plan ($59/mo, up to 15 users) and the Studio plan ($119/mo, up to 25 users). It's not included in the Starter plan ($29/mo, up to 4 users). If project history tracking and the before/after diff are requirements for your team, Agency is the minimum plan tier that provides them.
Boards that run themselves
Kanban with subtasks, priorities and a timer on every card
Demo request from Bloom Cosmetics
Website redesign · due Oct 14
