Adam Martelletti
Employee • Assigned to this job
Not eligible
Missing Western Power Induction (1 required, 0 valid)
White CardFirst AidWestern Power Induction
Run jobs with more than a status update.
Plan work, assign crews, record what actually happened on site, and keep every run, event, delay, and decision attached to the job.
Plan the work
Keep scope, scheduling, crews, assets, and field conditions connected from the start.
Record each run
Track real attendances, not just whether the job moved to another status.
Keep the history
Attach events, delays, overrides, and follow-up actions to the same operational record.
Supporting intro
Most systems tell you whether a job is scheduled, in progress, or complete. That is not enough.
It may be enough for administration. It is not enough to understand what actually happened in the field.
A crew might attend but be blocked from access. Work might be partially completed. A hazard might change the method. Weather might delay the run. Additional work might be identified on site.
If all of that gets compressed into a single status, the job record loses the truth.
Oplerra is built to run jobs with proper execution context, not just status labels.
Why traditional job tracking breaks down
A status does not explain the day.
In the real world, jobs are not clean state changes. They are made up of attendances, decisions, delays, risks, partial completions, and follow-up actions.
A status like Completed does not explain what the crew encountered, what changed on site, or what still needs to happen next.
What a single status does not tell you
whether the crew actually reached site
whether all work was performed
whether conditions changed
whether scope was deferred
whether follow-up work was raised
whether something was overridden to proceed
How Oplerra runs jobs
Jobs organise the work. Runs record the execution.
A job is the overall piece of work to be delivered. A run is a real unit of execution: a specific attendance, on a specific day, by a specific crew, with specific assets, under specific conditions.
One job may require more than one attendance. Instead of forcing that into one flat record, Oplerra keeps the job intact while allowing each run to carry its own execution history.
an initial attendance
a return visit
a follow-up action
a final inspection
Planner View
Crew & asset scheduling
Replaced the fragile mock week columns with a real product screenshot so the page shows an actual scheduler instead of a broken illustration.
Scheduler
Teams visible
Crew, assets, and jobs on one board
Planned + reactive
Unscheduled work stays in the same flow
Asset context
Vehicles and plant remain visible while booking
Job Details
Operational job record
Rebuilt as a simpler static example that shows scope, release checks, and evidence without the broken card nesting from the old mockup.
Scope
Scenic Park tree grinding and clean-up
Job W0170522 linked to the same site history, attachments, and follow-up decisions.
Contact
Jonathan Holder
Work type
Tree grinding and clean-up
Priority
Medium / public-facing site
Location
54 Church St, Wanneroo
Assigned crew
Crew A with chipper support
Release checks linked before dispatch
SWMS ready, competency confirmed, and evidence attachments kept on the same record so later review does not depend on memory or separate folders.
Job pack.pdf
Site map.png
Before-after photos
Record timeline
Inspection recorded
Defect notes and photos attached to the same tree record.
Safety released
SWMS, permits, and competency checks linked before scheduling.
Field work planned
Crew, date, and plant assignment saved on the operational record.
Proof retained
Outcome notes, attachments, and follow-up remain visible years later.
Why it matters
This example is deliberately flat and readable: one operational record, one evidence chain, and one timeline of decisions that still holds together after the job is done.
Events, not just outcomes
Work is captured as events, not just a final label.
A job does not jump from scheduled to complete. Real execution unfolds through events, and the job record should reflect what happened instead of being rewritten afterward.
crew dispatched
crew arrived
access unavailable
hazard identified
work paused
partial work completed
additional work recommended
run completed
follow-up required
Checked before work begins
Readiness is verified before a crew is already on the road.
Oplerra can check whether the work is ready to proceed before the run starts, so supervisors catch issues before the day unravels.
crew competencies and expiry status
asset readiness and inspection status
permits or documents required for the work
location-specific conditions or requirements
other operational rules tied to the run
When an exception is needed
The decision can be explicitly recorded with context, justification, and accountability instead of being hidden in a call or comment trail.
Bob Williams
Employee • Assigned to this job
Eligible
Meets all requirements
White CardWestern Power Induction
Job status
Blocked until all assigned crew meet competency requirements.
Reason: Missing induction
Execution timeline
The full sequence stays attached to the job.
Execution is not just one timestamp. It is the chain around the work: what was planned, what was expected, what actually happened, and what changed.
when it was planned
when it was expected to occur
when it actually happened
what changed along the way
This matters when runs are delayed, rescheduled, split across days, or affected by field conditions. Instead of losing that detail in comments, calls, or memory, the timeline stays attached to the operational record.
Calendar View
Daily clarity for crews
Switch between crews, assets, jobs, and unscheduled work.
Timeline · Week
Crews
06:00Jobs
07:00Jobs
08:00Jobs
09:00Jobs
10:00Jobs
11:00Jobs
12:00Jobs
13:00Jobs
14:00Jobs
15:00Jobs
16:00Jobs
17:00Jobs
18:00Jobs
Crew A
Crew view
Crew A
Early site prep
07:30—09:30
Crew B
Crew view
Crew B
Utility inspection
08:00—13:00
Crew C
Crew view
Crew C
All-day outage response
06:00—18:00
What this gives your team
Clearer supervision, stronger records, and better answers later.
When someone asks what happened on a job, the answer should be in the record.
Supervisors
Better visibility for supervisors
- which runs are active
- which jobs are blocked
- where work changed in the field
- what still needs follow-up
- what was completed, partially completed, or deferred
Operations
Better records for operations
- jobs
- runs
- crews
- assets
- sites
- issues
- follow-up actions
Evidence
Better evidence when questions come later
- who attended
- when they attended
- what happened
- what changed
- what was completed
- what still needs action
Designed for real field work
Built for work that is routine, reactive, staged, interrupted, or condition-dependent.
Execution rarely follows a perfect script. Oplerra keeps the job connected to the runs and events that actually moved it forward, which makes it easier to coordinate the day, manage exceptions, and keep a record that holds up later.
Coordinate the day with a clearer picture of active runs, blocked work, and follow-up requirements.
Manage exceptions without losing the reason, the decision, or the person who approved it.
Maintain a record that is usable later for clients, councils, managers, and internal review.
Run jobs with real execution history.
Move beyond status-only job tracking and give your team a clearer record of what actually happened in the field.