Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.sensorup.com/llms.txt

Use this file to discover all available pages before exploring further.

​
What is Audit History?

Audit History is your complete audit trail for field operations and office workflows. Every action taken on an issue or task—from creation to resolution—is automatically logged with timestamps and user attribution. Whether you’re auditing a site inspection for compliance, resolving conflicting information in a leak report, or managing field teams and office staff working remotely, Audit History provides the permanent, unchangeable record you need to maintain accountability and operational visibility.

100% Accountability

See exactly who did what and when

Real-Time Visibility

Track mobile app actions instantly in web

Compliance Ready

Permanent audit trail for regulatory requirements

​
Why Use Audit History?

The Problem

Without issue & task history:Hours wasted manually reconstructing audit trailsNo visibility into asynchronous field operations and office workCan’t trace conflicting data changesDisputes about who did what and when

The Solution

With Issue & Task History:Automatic compliance documentationReal-time mobile-to-web visibilityComplete edit history with timestampsEliminates disputes with definitive records

​
Getting Started

Ready to use Audit History? The feature is automatically enabled for all issues and tasks. No setup required—just open any issue to view its complete history.
1

Open an Issue

Navigate to any issue in your Work Management dashboard and click to open the issue details blade.
2

Access the History Tab

Click the “History” tab in the issue details blade to view the complete audit log.
3

Review the Timeline

Scroll to the bottom to see the issue creation (oldest entry), then scroll up to follow the lifecycle to the current state (newest entries at top).Each entry shows:
  • What changed: Property, form field, or action
  • Who made it: User name or “System”
  • When it occurred: Exact timestamp
  • Before/After values: For property and form changes
Important: History displays in chronological order with oldest entries at the bottom. Scroll to the bottom to find when the issue was created, then read upward to follow its progression.

​
What Gets Tracked?

Audit History captures comprehensive details across three categories:

​
Issue Properties

Core issue attributes that change over time:
  • Title and Description: Updates to issue identification and details
  • Severity Level: Priority increases or decreases
  • Status: Opens, closes, reopens
  • Due Date: Deadline assignments, modifications, or removals
  • Assignment: Assignee additions, changes, or removals
  • Watchers: Team members added or removed from notifications
  • Resolution: Closure reasons and false alarm markings

​
Task Lifecycle and Data Collection

Work performed by field teams and office staff using Site Check-in and OGI Inspection tasks:
  • Task Creation: Initial creation timestamp and creator (e.g., “Site Check-in Task Created”)
  • Task Progress: Start, stop, complete, restart actions
  • Form Submissions: Data collected during inspections
    • Field-level tracking: See exactly which questions were answered (e.g., “Leak Observed = Yes”)
    • Initial vs. Update: Distinguish first data entry from corrections
    • Before/After values: Compare original and modified results
    • Human-readable labels: Form questions shown in plain language, not technical IDs

​
Comments and Annotations

Team collaboration and notes:
  • Comment additions: Who added what note and when
  • Comment modifications: Edits to existing annotations
  • Comment deletions: Removed annotations (action is logged, not comment content)
Cross-Platform Tracking: Actions performed in the Outpost mobile app by field operators appear instantly in the web control plane. Operations managers can track field progress in real-time without phone calls or status check-ins.

​
Understanding History Entries

​
Entry Components

Every history entry includes:
ComponentDescriptionExample
Event TimeExact timestamp of the action”2025-11-17 14:32:15 UTC”
Event TypeClassification of the action”Issue Assigned”, “Task Completed”
Trigger TypeUser or System initiated”user” or “system”
User InformationWho performed the action”John Smith” or “System”
Property ChangesWhat changed and how”Severity: 2 → 3”
Version NumberSequential version for tracking”Version 15”

​
Types of History Entries

​
Property Changes

Standard issue attributes changing: 
Event Type: Issue Severity Increased
Changed By: Sarah Johnson
Timestamp: 2025-11-17 10:15:23 UTC
Property: Severity
Old Value: 2 (Medium)
New Value: 3 (High)

​
Form Submissions

Data collected during field operations and office tasks: 
Event Type: Issue State Data Updated
Changed By: Mike Chen (via Outpost mobile app)
Timestamp: 2025-11-17 11:42:08 UTC

Form Fields Changed:
- Leak Observed: "Yes"
- H2S Detected: "No"
- Tag Number: "COMP-4421"
Initial Entry vs. Update:
  • First submission: Only new values are shown (no old value displayed)
  • Corrections/Updates: Both old and new values shown for comparison

​
Comments and Annotations

Team notes and collaboration: 
Event Type: Issue Annotated
Author: David Lee
Timestamp: 2025-11-17 13:20:45 UTC
Comment: "Spoke with site supervisor. Leak is accessible but requires scaffolding."

​
Task Completions

Field operations and office work milestones: 
Event Type: Issue Task Completed
Changed By: Mike Chen (via Outpost mobile app)
Timestamp: 2025-11-17 12:05:33 UTC
Task: Site Check-In
Status: Open → Complete

​
User vs. System Changes

History clearly distinguishes action sources:
  • User: Person performed the action (shows their name)
  • System: Automated action (shows “System”)
System actions include:
  • Automated integrations creating issues
  • Scheduled workflow triggers
  • Calculated field updates
  • Automated status changes based on rules

​
Common Use Cases

Compliance Auditing When your facility undergoes a regulatory audit, Audit History provides complete documentation showing when inspections were performed, which field operators and office staff completed them, and the full data collection process from start to finish. The permanent, unchangeable audit trail demonstrates accountability without requiring manual documentation. Resolving Data Discrepancies When you notice conflicting information in reports, Audit History lets you trace every edit back to the specific task and form submission. See when original data was entered versus when it was corrected, identify which field operator or office staff member made each entry, and use timestamped comments to understand the context and coach team members on proper procedures. Managing Asynchronous Field Operations and Office Work Track your field team’s and office staff’s progress in real-time as they work remotely using the Outpost mobile app or web interface. View updates as tasks are completed, see when specific tasks are marked “Complete,” and finalize issues in your triage process immediately when field operations and office work is done—all without making phone calls for status updates. Verifying Work Completion During daily triage, verify that high-priority issues have been properly addressed before closing them. Review the complete task history from creation to completion, verify all required form data was collected, check that proper procedures were followed, and confirm who performed the work and when. Dispute Resolution When there’s disagreement about when an issue was reported or what actions were taken, Audit History provides definitive timestamps for all actions, shows original issue details exactly as created, and documents every assignment change and status update. The permanent, unchangeable record eliminates disputes with factual evidence.

​
FAQ / Troubleshooting

No. Audit History is an immutable audit trail. Once logged, entries become permanent records that cannot be edited or deleted. This ensures data integrity for compliance audits and prevents tampering with historical records.
Some changes are triggered automatically by system processes rather than manual user actions. Examples include:
  • Issues created by automated integrations
  • Calculated field updates
  • Scheduled workflow triggers
The “System” label helps you distinguish automated actions from manual ones.
Some actions affect multiple properties simultaneously. For example, closing an issue updates:
  • Status (Open → Closed)
  • Closed timestamp
  • Closer user ID
  • Resolution reason
Each property change gets its own entry for complete transparency and granularity.
Scroll to the bottom of the history log. History displays chronologically with oldest entries at the bottom. The very first entry shows issue creation details including who created it and when.
Yes. Actions performed in the Outpost mobile app appear instantly in the web control plane. You can track:
  • Task starts and completions
  • Form data submissions
  • Comments added from the field
  • Status updates
This eliminates the need for status phone calls during field operations.
Form submission entries clearly show initial vs. update:
  • Initial entry: Only new values are displayed (no old values shown)
  • Update/Correction: Both old and new values are displayed side-by-side for comparison
This distinction helps you verify data accuracy and identify when corrections were made.
  • Property changes: Core issue attributes like title, severity, assignment, due date, status
  • Form submissions: Structured data collected during tasks (e.g., inspection checklists, observation details)
Both are tracked separately. Form submissions show field-level detail with human-readable labels like “Leak Observed” instead of technical field IDs.
Yes. Audit history is available through the GraphQL API for export and reporting. Contact your system administrator for:
  • API access credentials
  • Query examples
  • Export capabilities
  • Integration with compliance reporting tools
History captures every event from issue creation onward with no time limit. The complete audit trail is preserved for the entire lifecycle of the issue, ensuring permanent records for compliance and accountability.
Comments are treated as independent additions rather than updates to existing content. Each comment is a new contribution with no “old value” to compare against.However, if a comment is edited or deleted, that action is logged separately showing what changed.
If the form schema cannot be loaded, you’ll still see form data changes, but field labels may not be as descriptive. The system will display technical field identifiers instead of human-readable labels.This is rare and typically resolves automatically. Contact support if you consistently see technical IDs instead of field labels.
Currently, the history view shows all changes chronologically. For advanced filtering and analysis, use the GraphQL API to query specific event types or date ranges. Contact your system administrator for API access.

Issue Management

Learn how to create, manage, and resolve issues in Work Management.

Outpost Mobile App

Discover how field operators use the mobile app to complete tasks that generate history entries.

​
Feedback & Support

Found a bug or issue? If you notice discrepancies in the issue history or have questions about specific entries, contact your system administrator or support team with the issue ID and specific history entry details.
Have questions or suggestions about Audit History? We’re here to help improve your experience.