This article explains how field service trades businesses can decide whether Deputy is the right fit, plan their set-up, trial key workflows, and prepare for rollout across technicians, jobs, clients, payroll, and operations.

Before you read

• Target audience: This article is for users with System Administrator access.
• Plan restrictions: To check whether your plan includes this feature, see our plan guide.

This article covers:

• Who this guide is for
• What Deputy can help field service trades manage
• Choosing a starting model
• Structuring Locations, Areas, access, and integrations
• Reviewing Location settings before rollout
• Setting access and approval responsibilities
• Preparing payroll, costing, and reporting workflows
• Running day-to-day field service workflows
• Quick add-on and plan check
• Trial and rollout checklist
• Common mistakes to avoid

Who this guide is for

This guide is for electricians, plumbers, HVAC teams, fire services, pest control, security installers, maintenance teams, mobile technicians, and trade service businesses.

It is especially useful for businesses that manage multiple jobs per day, mobile technicians, travel time, job costing, call-outs, allowances, apprentices, licences, site requirements, or external job management systems.

What Deputy can help field service trades manage

Field service trades businesses often need to manage mobile teams, changing jobs, client sites, travel time, allowances, and payroll-ready time records. Technicians need clear rosters, managers need attendance visibility, payroll teams need approved timesheets, and operations teams need labour visibility without duplicating a job management system.

Deputy can help field service trades manage technician rosters, mobile clock-in, GPS attendance, timesheet approvals, job or client Areas, travel visibility, payroll preparation, Training Tags, communication with mobile teams, task workflows, and labour reporting.

Many field service trades businesses adopt Deputy because it can reduce manual admin, improve mobile workforce visibility, and simplify day-to-day coordination across technicians, supervisors, jobs, clients, payroll, and operations.

• Technicians can clock in and out using mobile workflows.
• Managers can review GPS, travel, overtime, and exceptions before payroll cut-off.
• Payroll teams can work from cleaner approved timesheets.
• Managers can review labour activity by job, client, Area, technician, or work type.
• Businesses can identify travel time, call-outs, and allowance-related work more clearly.
• Task workflows can help support operational consistency across mobile teams.
• Communication workflows can help managers coordinate job changes, call-outs, site access changes, and safety notices.

Deputy is usually used alongside quoting, dispatch, job management, asset management, invoicing, work orders, and customer record systems. Keep those workflows in your specialist systems if they already sit outside Deputy.

Many field service trades businesses start with attendance, approvals, and payroll-ready timesheets first, then expand into reporting, communication, onboarding, analytics, or broader workforce workflows over time.

What good looks like

• Technicians know which job, client, or work type they are rostered to.
• Managers can review GPS, travel, overtime, and exceptions before payroll cut-off.
• Payroll teams receive approved timesheets with the right job, Area, allowance, or export code detail.
• Licence-sensitive work is visible before shifts are published.
• Deputy does not duplicate job management unnecessarily.
• Mobile workers are not blocked by unrealistic geofences.

Choose your starting model

Start by choosing the model that best matches how your field service trades business works today. You can add more reporting detail later once your team is using Deputy consistently.

Use these models as a starting point only. Your final set-up should reflect your payroll rules, reporting needs, integrations, approval process, and how your team manages jobs, clients, travel, and mobile work.

Structure Locations, Areas, and integrations

In Deputy, a Location does not always need to represent a physical office. Many field service trades businesses use Locations to represent depots, regions, major clients, long-term job sites, service hubs, or major contracts.

Areas are usually used to represent the work being performed or the reporting detail needed. For field service trades, this might include jobs, clients, technician roles, apprentice work, installation, maintenance, call-outs, admin, or travel.

Some integrations can create or update team members, payroll data, job details, or reporting information in Deputy. Review your integration requirements before you finalise your structure so your Deputy set-up matches your payroll, job management, accounting, or operational workflows.

Option 1 — Region or depot as a Location

This structure works well for most field service trades businesses with mobile technicians working across multiple jobs or clients.

Trades businesses commonly use this model because it keeps the set-up scalable while still allowing job, client, work type, or travel reporting through Areas.

Option 2 — Major job site as a Location

This structure works well for long-term, high-value, or fixed-site projects where site-level reporting and approvals matter.

Use this model selectively for projects that need separate permissions, settings, clock-in rules, or reporting.

Option 3 — Job numbers through notes or integrations

This structure works well when another system already owns jobs, work orders, customer records, or project detail.

Deputy is mainly used for scheduling, attendance tracking, payroll preparation, and workforce visibility rather than detailed job management.

Option 4 — Client as a Location

This structure works well for major client contracts where client-specific reporting, permissions, approvals, or settings matter.

Use this model selectively when a client contract needs stronger separation than an Area can provide.

Review Location settings before rollout

Location settings control many of the defaults that affect scheduling, clocking in, timesheets, approvals, and reporting. Review these settings before go-live so each depot, region, site, client, or project works the way your team expects.

This section is not a full set-up guide. Use it as a quick reminder of the settings to review, then refer to the detailed Location, Area, scheduling, and timesheet settings articles for step-by-step guidance.

General Location settings to review: depot, region, site, or client name, address and map pin, operating days and hours, Location code, notes, and attachments.

For field service trades:

• Clear Location names can help managers distinguish between depots, regions, major job sites, major clients, or service hubs.
• For mobile work, remember that one Location address may not represent every job site.
• This is also where you can add site instructions, access details, safety reminders, or supervisor contact details.

Area settings to review: job, client, or work type names, Area export codes, Area addresses where useful, preferred technicians, and Training Tags.

For field service trades:

• Areas are where you can set up jobs, clients, technician roles, apprentices, installation, maintenance, call-outs, admin, or travel.
• Area export codes can support payroll, job management, accounting, or labour reporting workflows.
• Training Tags can help manage licences, apprentices, site inductions, specialist work, and role suitability.

Scheduling settings to review: default shift settings, default break settings, shift offers, open shifts, notifications, and shift locking.

For field service trades:

• Open shifts may be useful for call-outs, but licence or skill requirements should be controlled.
• Schedules may change due to urgent jobs, client changes, parts availability, weather, call-outs, or access issues.
• Shift locking can help reduce retrospective schedule changes after work has already happened.

Timesheet settings to review: mobile clock-in, GPS capture, geofencing, employee timesheet edits, break settings, rounding, timesheet auto-approval, and custom questions where useful.

For field service trades:

• This is where you can control important attendance and payroll behaviours.
• Mobile clock-in with GPS capture is usually more practical for mobile technicians.
• Hard geofencing should usually be reserved for fixed job sites, depots, or long-term projects.
• Custom questions may be useful where technicians need to record job number, travel, call-out reason, or work completed.

Set access and approval responsibilities

Access decisions should be made during set-up. The right access model helps managers control scheduling, timesheet approvals, payroll visibility, labour cost access, job visibility, and reporting.

Most field service trades businesses allow technicians and apprentices to clock in, clock out, and submit leave requests. Leading hands usually review daily attendance and exceptions. Service managers usually manage rosters, approvals, labour visibility, and job reporting. Payroll and admin teams usually review payroll outputs and final exceptions.

Supervisor or Location Manager?

Most field service trades businesses use Supervisor access for leading hands who approve time but should not see wage costs.

Use Location Manager access for service or operations managers who need labour cost visibility, roster cost visibility, or job reporting.

Prepare payroll, costing, and reporting workflows

Payroll systems and payroll workflows

Field service trades may need to manage overtime, travel time, site allowances, tool allowances, vehicle allowances, call-outs, on-call work, public holidays, RDOs, apprentice rates, and higher duties.

Many field service trades businesses want payroll workflows that sit close to scheduling, attendance, and approved timesheets. Deputy Payroll (AU) and Deputy Payroll (US) can help support that approach where available.

Businesses with established payroll, accounting, job management, dispatch, or invoicing systems may still choose to connect Deputy to a third-party payroll integration. This usually works best when another system already owns job detail, work orders, quoting, dispatch, invoicing, or customer records.

Before rollout, decide which system should own:

• Employee records
• Payroll calculations
• Travel time handling
• Allowance and call-out handling
• Export codes and job, client, or work type structures
• Job, client, technician, or labour reporting

Compare payroll approaches

Start by reviewing whether Deputy Payroll is available and suitable for your region and business needs. If your business already has a payroll, accounting, job management, dispatch, or invoicing system that needs to stay in place, review how Deputy should connect to that system.

Field service trades commonly test payroll exports and approval workflows before rollout so supervisors, payroll teams, and operations managers can confirm that attendance, travel, call-out, allowance, and job reporting workflows behave as expected.

Payroll testing

Test payroll before your first live pay run using real field service examples so payroll, operations, and service managers can confirm the outputs match your business workflows.

• Multiple jobs in one day
• Travel time
• Call-out
• On-call
• Overtime
• Apprentice shift
• Site allowance
• Public holiday
• Missed clock-in
• Job export code
• Technician moving between clients or jobs

Job costing and reporting

If labour reporting by job, client, technician, Area, or work type matters, use Areas, Area export codes, consistent naming conventions, notes, or integrations. This keeps reporting cleaner and helps avoid duplicating your job management system.

Field service trades commonly review reporting by:

• Technician
• Job
• Client
• Work type
• Travel
• Call-out
• Rostered versus actual hours
• Overtime
• Labour by client, Area, or work type

Qualifications, licences, and Training Tags

Training Tags help prevent technicians from being scheduled into Areas where they are not licensed, trained, or approved to work. This is useful for apprentices, licence-sensitive work, site inductions, specialist work, safety requirements, and customer-specific requirements.

Common field service trades Training Tags include Licensed Technician, Apprentice, White Card, Working at Heights, Confined Space, First Aid, Site Induction, Fire Licence, Equipment-specific Training, and Working with Children Check where relevant.

If your business needs to collect onboarding documents, store employee records, manage policy acknowledgements, or track licence and certification expiry dates, Deputy HR can help support those workflows. Deputy HR requires an add-on.

Run day-to-day field service workflows

Clocking in and attendance

Most field service trades businesses should use mobile clock-in with GPS capture. This provides attendance visibility while still supporting mobile work across changing jobs, clients, and sites.

Avoid hard geofencing unless technicians always start from a fixed site, depot, or long-term project.

For most mobile technicians, GPS capture without hard geofencing is more practical.

Scheduling and shift changes

Field service schedules may change due to urgent jobs, client changes, parts availability, weather, call-outs, or access issues.

Keep job detail in the right system so Deputy does not become a duplicate job management platform. Use Deputy for workforce scheduling, time capture, approvals, payroll-ready timesheets, and labour visibility.

Travel time

Decide before rollout how travel time should be recorded and reviewed.

Options may include:

• Travel as an Area
• Travel in notes
• Travel as a custom timesheet question
• Travel tracked in another system
• Travel handled through payroll rules

Task management

Task management can help field service trades standardise daily technician, job, safety, and close-out routines so important work is not missed.

Field service trades commonly use Task management for pre-start checks, job completion checks, safety checks, equipment checks, handover tasks, close-out reminders, and supervisor review tasks before payroll approval.

Communication

News Feed and Messaging can help managers share job changes, urgent call-outs, client instructions, site access changes, start-time changes, safety notices, and operational updates.

Messaging Plus can support field service trades that need larger groups, more message history, team-based conversations, or role-based communication. This can be useful when managers need groups for technicians, regions, job teams, call-out teams, or specialist teams.

Labour visibility and analytics

Field service trades commonly review technician utilisation, job labour, overtime, travel, attendance trends, rostered versus actual hours, and labour by client, Area, or work type.

Analytics can help businesses review workforce activity inside Deputy. Analytics Plus can support deeper reporting needs, including custom reports, scheduled emailed reports, and labour reports for managers or directors who need visibility without logging in every day.

Quick add-on and plan check

Some field service trades businesses need more than scheduling, attendance, and payroll preparation. Use this section as a quick guide to what may be useful as your rollout becomes more complex.

To check what is included in each plan or add-on, see our pricing plans.

Trial and rollout checklist

You do not have to build your full field service business in Deputy during a trial or first rollout. A focused rollout can help you test one real depot, region, technician workflow, job reporting workflow, payroll scenario, and approval process before expanding the set-up.

The timeline is up to your business. Some businesses move quickly, and others need more time to validate payroll, train supervisors, and review integrations. Use these stages as a guide, not a fixed timeline.

Avoid common field service trades set-up mistakes

Final recommendation

If you are unsure where to start, begin with the structure your supervisors already use to plan technician coverage.

For most field service trades, use Locations for regions or depots, Areas for jobs, clients, work types, or travel, mobile GPS clock-in, and hard geofencing turned off unless work happens at a fixed site.

Use Employee access for technicians and apprentices, Supervisor access for leading hands, and Location Manager access for service or operations managers who need labour visibility.

Choose one starting model, build one pilot Location, test mobile clock-in, review Location settings, review approval workflows, test payroll, and decide whether add-ons are needed before expanding your set-up.

Review attendance workflows, payroll testing, reporting requirements, integrations, add-ons, Training Tags, and supervisor adoption before rolling Deputy out across the business.

The goal is accurate mobile work tracking without unnecessary admin.

Need help? Use the help menu in your Deputy account to access support, online training, and guidance.