Change History is a built-in audit trail feature in PartnerHQ that automatically tracks and records changes made to important records in your project.
This feature provides transparency and accountability by showing: who made a change, when the change occurred, and what values existed before and after the update.
Think of Change History as a detailed activity log that captures a complete before and after snapshot of every edit, giving you full visibility into how your project data evolves over time.
What Gets Tracked
Change History automatically monitors changes across the following record types:
| Record Type | What’s Tracked |
| Organizations | Name, status, contact information, and organization details |
| Individual Partners | Partner profile information and status changes |
| Tasks (To-Dos) | Task settings, labels, due dates, instructions, and configurations |
| Resources | Resource content, links, and visibility settings |
| Internal Tasks | Internal task settings and assignments |
| Tags | Tag names, colors, and associations |
| Custom Fields | Field configurations and settings |
| Task Submissions | Partner responses and form field values |
| Task Completion Rules | Automation rule configurations |
| Messages | Communication record changes |
How to Access Change History
Change History is available on the detail page of any supported record.
To view it:
- Navigate to the record you want to inspect (for example, an Organization, Task, Tag, or Resource)
- Scroll to the bottom of the detail page
- Locate the Change History section
The Change History section appears on:
- Organization detail pages
- Task detail pages
- Resource detail pages
- Internal Task detail pages
- Tag detail pages
- Partner profile pages
Understanding the Timeline
Timeline Layout
Changes are displayed in a chronological timeline and grouped by date for easy scanning. Each entry includes:
- Event Type: Indicates whether the action was a Create, Update, or Destroy
- Author: The name and avatar of the user who made the change
- Time: How long ago the change occurred (for example, “3 hours ago”)
- Change Count: The number of fields modified in that update
Viewing Change Details
To view the exact changes made in an entry:
- Click the event name (such as Update or Create)
- A detailed view opens showing:
- A unique Version ID
- Who made the change and when
- A field-by-field breakdown of all modifications
Reading the Difference View
The difference view uses a visual format similar to code comparison tools.
| Indicator | Color | Meaning |
| Minus (–) | Red background | Previous value that was removed or changed |
| Plus (+) | Green background | New value that replaced the old one |
| “Addition” badge | Green | Field was empty and now has a value |
| “Modification” badge | Yellow | Field changed from one value to another |
| “Deletion” badge | Red | Field previously had a value and is now empty |
Example
If a task due date changed from January 15 to January 20:
- Red row shows January 15, 2026 (old value)
- Green row shows January 20, 2026 (new value)
Key Features
Automatic Tracking
All changes are recorded automatically. No setup or configuration is required. Every edit is captured in real time as users work within the platform.
User Attribution
Every change is linked to the user who made it, including: user name, profile avatar, and exact timestamp
System Changes
Some changes may be attributed to System instead of a user. This typically occurs when:
- Automated processes update records
- Background jobs make changes
- Bulk operations are performed
Long Text Handling
For fields containing large amounts of text (such as instructions or descriptions), Change History intelligently truncates the display while preserving the full record.
An indicator such as “(500 characters total)” appears when content is abbreviated.
Common Use Cases
Troubleshooting Issues
If a partner reports unexpected behavior:
- Open the relevant record
- Review the Change History
- Identify when and by whom the change occurred
- Decide whether to revert or investigate further
Accountability and Compliance
For audit and compliance needs:
- All modifications are permanently logged
- History entries cannot be deleted or altered
- A complete record is always available for review
Team Coordination
When multiple team members manage a project:
- See recent updates made by others
- Avoid overlapping or duplicate edits
- Understand the context behind changes
Reviewing Partner Submissions
For task completions and form submissions:
- Track when partners submitted responses
- See if and when submissions were modified
- Maintain a complete audit trail of partner activity
Best Practices
- Review regularly: Periodically check Change History on important records to stay informed
- Use it for communication: Reference Change History when discussing updates with teammates
- Review before major changes: Understand the record’s evolution before making significant edits
- Investigate anomalies: Use Change History to identify what changed and when if data appears incorrect