The History tab on a task's page shows everything that happened to that task in one timeline: who it was allocated to and how, when a Vendor accepted or rejected it, every status change, budget changes, due date and instruction edits, and invoicing. Each entry shows who made the change, when, and the value before and after it. Use it to answer questions like "who moved this deadline?", "why did this budget go up?", or "was this task assigned by hand or by Auto Task Placement?" without asking around.
Who is this for? Account Admins and Project Managers who manage tasks, and Vendors who want to check the history of a task assigned to them. See All about wxrks roles for what each role can do.
Permissions:
Task Retrieve opens the task's page, and with it the History tab. Account Admins, Project Managers, and Vendors have it by default. Clients don't.
Payables List shows the budget and billing entries. Account Admins and Vendors have it by default. Project Managers don't, so a Project Manager sees every other entry but no budget amounts until an Account Admin grants it. See Who sees what.
Both permissions are on the user's Permissions page, under People > Users > [User] > Permissions. For what each one controls, see the wxrks Permissions Reference.
Table of contents
What the History tab records
wxrks writes an entry every time one of these things changes on a task. The Filter column is the option you pick in the type filter to show only that group.
Filter | Entry | Written when |
Allocation | Allocated to [name] | A Project Manager or Account Admin assigns the task, alone or in bulk, applies it to related tasks, a Vendor claims it through Auto Task Placement, or the task is sent to another account through a Work Package. |
Allocation revoked from [name] | The assignee is removed, for example with Clear Assignment. | |
Accepted | The Vendor accepts a task that requires acceptance. | |
Acceptance rejected | The Vendor rejects a task that requires acceptance. The entry shows the reason the Vendor gave. | |
Status | Status changed | The task moves to a new status, including when it's cancelled. |
Delivered | The task is delivered, or reverted to Delivered. | |
Budget & billing | Budget changed | The task's payable amount, currency, or net word count changes, for example after Recalculate Budget or when a logfile (the word-count analysis behind the budget) is completed. |
Invoiced / Not invoiced | A payable is created for the task. | |
Due Date | Due date changed | Someone edits the due date, for one task or in bulk. |
Instructions | Instructions changed | Someone edits the instructions, for one task or in bulk. |
ℹ️ Note: History starts from the day the feature was released. Changes made to a task before then aren't in the timeline.
ℹ️ Note: wxrks only writes an entry when a value actually changes. A budget recalculation that lands on the same amount, or an instructions edit that only changes formatting (bold, lists, line breaks), adds nothing to the timeline.
Open a task's History
From a project (Account Admins and Project Managers)
Open the project and go to its Tasks tab.
Click the ⋮ menu at the end of the task's row and choose History.
The task's page opens on the History tab. If you're already on the task's page (for example, after choosing Details in the same menu), click the History tab between Logfiles and Custom Fields.
💡 Tip: The address bar ends in #history while the tab is open. Copy the link to send a colleague straight to this task's timeline.
As a Vendor
On your Home page, click the My Projects tab.
Click the project's row to expand it and list its tasks.
Click the Details icon (ⓘ) on the task.
On the task's page, click the History tab.
ℹ️ Note: A Vendor sees the History only of tasks currently assigned to them. If the assignment is revoked, the Vendor can no longer open that task's History.
Read an entry
Entries are grouped by day, newest first, with the time of each change on the left.
Each entry starts with what happened (for example Budget changed or Accepted), next to an icon whose color matches its filter group. Removals and rejections are shown in red, deliveries in green. After that, an entry can show:
The change itself, as the old value → the new value. A status shows as a status badge, an amount with its currency, and a date with its time. When a field had no value before, only the new value appears. When a value was cleared, the new value reads removed.
One line per field when a change touches several fields at once. In the screenshot, the budget change (1) lists both Payable amount and Net words.
The full old and new text for Instructions changed (2). If the new text only adds to the end of the old one, the added part is highlighted.
The status change caused by an allocation or acceptance (3). Accepting the task moved it from Pending acceptance to Assigned.
Who did it (the byline) and how it was done (the origin badge, such as Manual). Both are explained below.
A reason, when a Vendor rejects a task, or when one was given for revoking an assignment.
Who did it
Byline | Meaning |
by [name] | A person made the change in wxrks. Hover over the name to see their email. |
by [name] with an API badge | A person's API integration made the change, using that person's API token. |
by wxrks (with the wxrks logo) | The platform made the change on its own. Work that wxrks finishes in the background shows up this way, for example the new amount after someone clicks Recalculate Budget. |
by an automation | A pipeline or an automatic review skip made the change. |
No byline | The person in the entry made the change themselves, for example a Vendor who claimed a task through Auto Task Placement. |
How it was done
Entries that come from an assignment action (allocations, acceptances, rejections, and the budget set up when a task is allocated) carry an origin badge:
Badge | Meaning |
Manual | Assigned, accepted, or rejected one task at a time. |
Bulk | Part of an action applied to several tasks at once. |
Related tasks | Applied with Assign to Related Tasks from another task's ⋮ menu. |
Autopilot | Placed by Auto Task Placement (its internal name is Autopilot), on a single task. |
Autopilot (bulk) | Placed by Auto Task Placement as part of a batch of tasks. |
Work Package | Allocated when the task was sent to another account through a Work Package. |
Example
A Vendor says the budget on their task dropped and asks why. Open the task's History and choose Budget & billing in the filter:
10:42 — Budget changed — Payable amount USD 120.00 → USD 96.00, Net words 1,500 → 1,200 — by wxrks
Both lines belong to the same entry, so the amount went down because the net word count went down, not because the Vendor's rate changed. The byline reads by wxrks because the recalculation ran in the background. To see what changed the word count, switch back to All types and check the entries just before it, then the task's Logfiles tab.
Filter and browse the timeline
Type filter: The dropdown in the top-right corner of the tab starts on All types. Choose Allocation, Status, Budget & billing, Due Date, or Instructions to show only that group (see What the History tab records).
Record count: The number next to the History heading, such as 12 records, counts the entries that match the current filter.
Day headings: Entries from the last 30 days are grouped under Today, Yesterday, or N days ago, each followed by the date (for example Today 2026-10-02). Older entries are grouped by date only.
Show more: The tab loads 20 entries at a time. The footer shows how many you're seeing, for example Showing 20 of 45. Click Show more to load the next 20.
Who sees what
Two things decide what a user sees in the History tab: whether they can open the task at all, and whether they can see money.
Opening the task. Account Admins can open any task's History. Other users with Task Retrieve can open it for tasks in the Organizational Units where they have that permission. Vendors can open it only for tasks currently assigned to them.
Seeing money. Users without Payables List don't see Budget changed, Invoiced, or Not invoiced entries at all, and amounts are removed from any other entry that carries one. The record count leaves them out too, so the same task can show 7 records to an Account Admin and 5 records to a Project Manager. Account Admins and the Vendor assigned to the task always see them.
User | Opens History of | Sees Budget & billing entries |
Account Admin | Any task | Yes |
Project Manager (default permissions) | Tasks in their Organizational Units | No — needs Payables List |
Project Manager with Payables List | Tasks in their Organizational Units | Yes |
Vendor | Tasks currently assigned to them | Yes, for those tasks |
Client (default permissions) | None — needs Task Retrieve | — |
⚠️ Common misconfiguration: A Project Manager reports that the Budget & billing filter is always empty, or that budget changes are "missing" from History. The entries exist; the Project Manager can't see them. If they need them, an Account Admin grants Payables List on People > Users > [User] > Permissions. Keep in mind that Payables List also opens the payables list for that user, not just the History entries.
Troubleshooting
What you see | Why | What to do |
Nothing recorded for this task yet | Nothing has changed on the task since History was introduced, or nothing in the selected filter has. | Switch the filter back to All types. Entries appear as soon as the task is allocated, edited, or changes status. |
The Budget & billing filter is empty, but the budget did change | You don't have Payables List. | Ask an Account Admin to grant it. See Who sees what. |
A Vendor can't open the History of a task they worked on | The task is no longer assigned to them. | This is expected. A Project Manager or Account Admin can check the History for them. |
A recalculation isn't in the timeline | The recalculation produced the same amount. | Nothing to fix. wxrks only records changes. |
Related articles




