Fieldworker Activity Log

The Fieldworker Activity Log provides a clear audit trail of the key actions performed by a specific fieldworker (technician/contractor/subcontractor) inside OctopusPro. It helps you understand what changed, when it changed, and which job or invoice was affected—so you can resolve disputes faster, coach your team, and maintain operational accountability.
What you can track (past month): booking status updates, appointment start/end time changes, ETA (estimated time of arrival) updates, invoice additions/edits, and attendance status changes—based on the activity recorded for that fieldworker account.
Quick navigation
- What is the Fieldworker Activity Log?
- Why it matters (benefits)
- How to access the Activity Log
- How to read log entries
- Examples & common use cases
- Best practices
- Related logs & audit tools
What is the Fieldworker Activity Log?
The Fieldworker Activity Log is a dedicated activity feed found inside each fieldworker profile. It shows a chronological list of the most important changes and updates performed by that fieldworker, helping office staff and managers quickly verify job progress and data changes.
Important notes:
- Per-fieldworker: each log is tied to one fieldworker profile.
- Recent history: the Activity Log section focuses on changes made in the past month.
- Drill-down available: you can open a log entry to view more details and jump to the related booking or invoice.
Why it matters (benefits)
- Accountability & transparency: confirm what was changed and when—without relying on memory or manual notes.
- Faster issue resolution: quickly investigate schedule changes, disputes, missed appointments, and incorrect statuses.
- Operational control: identify patterns (late check-ins, frequent reschedules, repeated ETA updates) and improve processes.
- Better customer service: respond confidently to customers with accurate timelines and job updates.
- Compliance-friendly audit trail: support internal governance by keeping a clear record of job-related changes.
How to access the Activity Log
- Log in to your OctopusPro admin account.
- Go to Fieldworkers.
- Open the relevant fieldworker profile (click the fieldworker’s name).
- Open the Activity tab.
- Click Activity log.

Tip: If you don’t see the log or specific actions you expect to track, confirm your fieldworker setup and permissions (see Fieldworker Permissions).
How to read log entries
Each entry in the Fieldworker Activity Log is designed to answer three key questions:
- What happened? (e.g., booking status changed, appointment time updated, invoice edited)
- When did it happen? (timestamp of the action)
- What record did it impact? (the relevant booking or invoice)
To view more detail: click a log entry. You’ll be able to see additional context about the change and open the associated booking or invoice for deeper investigation.
Examples & common use cases
1) Verify job progress & status changes
A customer claims a job was completed late. You open the fieldworker’s Activity Log to confirm exactly when the booking status changed to Completed, and whether it was marked In Progress earlier that day.
2) Investigate schedule edits & time changes
A dispatcher notices a booking time changed unexpectedly. The Activity Log reveals when the fieldworker updated the appointment start/end times and helps you validate whether it was a legitimate on-site delay.
3) Confirm ETA updates in real time
If your team uses ETA updates, you can quickly confirm the timing and frequency of changes to the estimated time to arrive, which can help you reduce no-shows and improve customer communication.
4) Track invoice activity linked to fieldwork
A manager audits billing and finds a discrepancy. The Activity Log shows when an invoice was added or edited in relation to the booking timeline.
5) Review attendance and operational reliability
Use attendance-related changes to identify recurring issues (e.g., frequent attendance changes) and coach teams on process compliance.
Best practices
- Review logs regularly: check activity weekly for high-volume teams to catch issues early.
- Use role-based access control: limit who can change booking details and enforce approvals where needed (see Allow Fieldworkers to Edit Booking Details Anytime).
- Standardize workflow: ensure all fieldworkers follow the same status progression (e.g., To Do → In Progress → Completed) to keep logs meaningful.
- Use the right audit tool for the job:
- If you need a booking-wide timeline across everyone, use Booking History Audit or Booking Activity.
- If you need a system-wide log across all users, use User Activity Log.
Related logs & audit tools
Depending on what you’re investigating, these related tools may be helpful:
- View a Fieldworker Profile (where you can access Activity, communication logs, and more)
- Contacting Fieldworkers (email, SMS, call, chat options and workflows)
- Fieldworker SMS Log
- Fieldworker Email Log
- Fieldworker Call Log & Recordings
- Fieldworker Device Audit (device/app version visibility for troubleshooting)
- Fieldworker GPS Tracking
- Fieldworker Check-in / Check-out
- Fieldworker Permissions
To stay updated, please subscribe to our YouTube channel.
