Skip to content
WorkWing Docs

Auto-assignment

Auto-assignment puts someone on a job the moment it’s created, so straightforward work never waits for a dispatcher. You tell WorkWing what rules a person has to meet and what you care about most, and it picks from whoever is left.

Go to Settings > Auto-Assignment. You need the Tenant Admin role, and auto-assignment is on the Professional plan. On other plans the page says so and the controls are greyed out.

Turning it on

Section titled “Turning it on”

There are two switches, and work is only assigned when both are on.

  1. Enable auto-assignment on this page, which is the master switch for your organisation.
  2. Auto-Assign Jobs in each brand’s job settings, which starts off. That’s how you run it for one brand and not another. See Job settings.

Click Save in the top right when you’ve finished changing anything on this page.

What it will and won’t touch

Section titled “What it will and won’t touch”

Auto-assignment covers jobs scheduled within the next 30 days, and jobs with no time on them yet. Anything dated further out, or in the past, is left for a dispatcher. Assigning work months ahead against today’s availability produces assignments that are wrong by the time they matter.

Someone is only a candidate if they’re in the job’s brand, marked available, and free of any time off covering the job. WorkWing also needs a recent position for them and an address on the job, so it has something to measure the journey against. When nobody qualifies, the job stays unassigned and a dispatcher picks it up.

Hard constraints

Section titled “Hard constraints”

These rule a person out entirely. Someone who fails one is never considered, however well they’d score on everything else.

  • Max Daily Jobs: the most work one person can be given in a day.
  • Max Travel Distance (km): how far you’ll send someone.
  • Max Travel Time (min): how long you’ll have them travelling.

The two travel limits are read one way when a single job is being placed and another when a whole day is rebuilt.

Placing one job, they cap that one journey: the trip from where the person is to the site. Rebuilding a day, they cap the day’s driving in total, and the trips someone is already booked for are added to their allowance rather than counted against it, so work already on the calendar can never push them over on its own.

Because the day’s reading is a total, a limit that comfortably covers one journey can still be tight across six of them. Max Travel Time defaults to 3 hours for that reason: it is a day’s driving, not a trip. If jobs start coming back unassigned when a day is rebuilt, these are the first two settings to raise.

Travel is measured on the road network. When a job is placed, WorkWing looks up the driving distance and time from each candidate to the site, buying any it has not measured before and keeping them for thirty days. When a whole day is rebuilt it uses the distances already measured; any pair it has not seen is estimated from the straight-line distance for that run.

A skill the job type marks mandatory is a hard constraint too. Someone without it is never considered.

Priority weights

Section titled “Priority weights”

Among the people who pass the hard constraints, four sliders decide who wins. Each shows as a percentage, and raising one lowers the others, so the four always share 100% between them.

  • Proximity: the nearest person to the site.
  • Skill Match: the best qualified.
  • Customer Familiarity: someone who has been to this customer before.
  • Workload Balance: spreading work evenly across the team.

Skill match ranks on the job type’s optional skills only, because the mandatory ones have already been settled as a hard constraint. On a job whose required skills are all mandatory, that slider has nothing left to rank on and makes no difference.

Defaults

Section titled “Defaults”

WorkWing uses these when the job or the person doesn’t supply a value of their own.

  • Default Job Duration (min), used when the job has no duration.
  • Default Shift Start and Default Shift End, used for anyone with no working hours set. The end has to be after the start. The dispatch console also uses them when it checks whether a job fits an engineer’s day.

Location staleness threshold

Section titled “Location staleness threshold”

This sets how old someone’s last known position can be before proximity scoring ignores it. A phone that has been off since this morning shouldn’t make its owner look like the nearest engineer.

Seeing why someone was picked

Section titled “Seeing why someone was picked”

A job assigned this way carries an Auto-assigned badge. Open it and the assignment shows its reasoning: how the chosen person scored on proximity, skill match, customer familiarity and workload balance, and how many candidates were weighed up.

If the answer looks wrong, that panel usually tells you which slider to move.

What’s next

Section titled “What’s next”