Skip to content

Creating a job type

Creating a job type takes a minute. Getting the forms right takes longer, and you can come back to them whenever you like.

You need the Brand Administrator or Tenant Admin role.

  1. Open Settings, pick the brand in the Scope selector, then click Job types.
  2. Click Create Job Type.
  3. Give it a Job Type Name, such as “Boiler service”. Names have to be unique within the brand.
  4. Add a Description if it helps your team pick the right one.
  5. Set the Estimated Duration in minutes. This fills in the duration when someone creates a job, so put in how long the work usually takes.
  6. Leave Active on unless you’re building it ahead of time.
  7. Click Create.

WorkWing saves it and drops you straight into the form builder.

The builder has four tabs. The first two are the forms: the Operator Form your office fills in, and the Resource Form the person on site fills in on their phone. The form builder walks through both.

The other two tabs are settings that sit alongside the forms.

QuickView Fields decides what a dispatcher sees in the side panel when they click a job on the dispatch console. Pick from your custom fields and from the fields on either form, then drag them into the order you want. Three to eight is about right for something meant to be read at a glance.

Required Skills lists what somebody needs before auto-assignment will put them on this kind of job. Add a skill, set the minimum proficiency to Beginner, Intermediate, Expert or Certified, and mark it Mandatory if a resource without it should never be picked. Skills themselves are set up under Teams and skills.

Required skills feed the automatic picker. A dispatcher assigning by hand still sees everybody.

Click Save Job Type when you’re done. The builder also saves a draft as you work, and offers it back if you close the tab by accident.

Open the job type from the list and you get its own page: how many jobs use it, how many are running and how many are finished, plus the settings below. Change anything and a Save button appears at the bottom.

The same duration you set when you created it. Change it here whenever the work turns out to take longer than you thought.

Default Priority is where a job of this type starts: Low, Normal, High or Urgent. Pick the job type on the create form and the priority follows it. Recurring schedules built from that job type get the same. Whoever creates the job can still change it before saving.

Every job type starts at Normal until you change it, and a job created without a job type at all starts there too.

Off by default. Turn it on and jobs of this type gain a Parts section, on the job page in the web app and on the engineer’s phone, for recording the parts and materials used from your parts catalogue.

Turn on Enable SLA Tracking and set two numbers in minutes: Response Time, for how quickly the job should be picked up, and Resolution Time, for how quickly it should be finished. WorkWing starts them at 60 and 480 minutes.

Deadlines are counted from the job’s scheduled start, or from the moment it’s created if there’s no schedule yet. They’re worked out again if the job is rescheduled.

Use Business Hours stops the clock overnight and at weekends. Leave it off and a four-hour target set at four on Friday afternoon is due at eight that evening. Turn it on and the clock only runs while the brand is open, so with nine-to-five weekdays the same job is due at noon on Monday. The hours come from the brand, so set them under Business hours first: a brand with business hours switched off gives the job type nothing to count in, and the deadline stays calendar time.

Priority Overrides opens a panel where you can give Urgent, High and Low work their own response and resolution times. Leave a box empty and that priority uses the times above. Normal priority always uses them.

Once a job passes a target, WorkWing flags it and sends a webhook, so your own systems can pick it up. See Webhooks.

Open it and click Delete Job Type. WorkWing stops you if any job has been created from it, which is nearly always the case for a job type that’s been in use. Switch it to inactive instead: it disappears from the create-job list and every existing job carries on as before.