UpKeep Automated Technician Workload Report
Every Monday, WebRun opens UpKeep, tallies each technician's open work orders and estimated hours, logs the split to a tracking sheet, and posts a Slack summary flagging anyone overloaded or underloaded so a supervisor can rebalance the week before it starts.
How do I balance technician workload before someone gets buried?
WebRun opens UpKeep every Monday, tallies each technician's open work orders and estimated hours, and logs the split to a tracking sheet. It posts a Slack summary flagging anyone more than 20 percent above or below the team average, with suggestions for which work orders could move, so a supervisor can rebalance before someone falls behind.
- Technicians more than 20 percent over the team average get flagged before Monday's shift
- Supervisors get concrete rebalancing suggestions instead of a raw work order count
- 8 weeks of workload trends are logged automatically for review
Built for maintenance supervisors · facilities managers · in-house maintenance teams · operations managers
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
app.onupkeep.comin a real browser with your saved login - no setup, no API keys. -
1
UpKeep - tally each technician's open workload
WebRun opens UpKeep to tally each technician's open workload. - Open UpKeep and list every open work order grouped by assigned technician
- Sum the estimated hours and count of work orders per technician
- Compare each technician's total against the team average
Done when Every technician has a work order count and hour total for the week.
-
2
Google Sheets - log the weekly workload split
WebRun logs this week's workload split to the tracker sheet. - Open the workload tracker sheet and add this week's row for each technician
- Fill in the work order count, hour total, and variance from the team average
- Keep the last 8 weeks so trends are visible
Done when The tracker sheet has this week's workload logged for every technician.
-
3
Slack - flag who needs rebalancing
WebRun posts the workload ranking to Slack and flags who needs rebalancing. - Post a Slack summary ranking technicians from most to least loaded
- Flag anyone more than 20 percent above or below the team average
- Suggest which open work orders could move from an overloaded to an underloaded technician
Done when A supervisor has this week's workload ranking and rebalancing suggestions in Slack.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does WebRun reassign work orders to rebalance the load?
No. It only reports the split and suggests which work orders could move. A supervisor decides on and makes any reassignment in UpKeep.
How is estimated hours calculated?
It reads the estimated hours you set on each work order in UpKeep. Work orders without an estimate are counted toward the total but flagged so you can add one.
What counts as overloaded?
Any technician more than 20 percent above the team's average open hours for the week. Ask WebRun to change that threshold and it will use your number instead.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.