SLA targets
- Targets for each stage, such as response and completion.
- Times set in days, hours and minutes.
- An at-risk point before each target.
Service level agreement software that keeps every contract on target
Response and completion clocks on every contract job, alerts before a target is missed, and contracts tied to the assets and plans they cover.
Book a demo
FieldEx is a field service and asset management (FSM+CMMS) application. As service level agreement software, it runs response and completion clocks on contract jobs in each client's business hours. FieldEx alerts your team before a target is missed. It ties each service contract to the assets and maintenance plans it covers.
SLA clocks on every job a contract covers.
Alerts when a job is at risk and when it breaches.
Contracts linked to their assets and maintenance plans.
What FieldEx does as service level agreement software
FieldEx puts each service contract's terms onto the jobs it covers. The office sees which promises are on track and which are at risk.
Contracts, assets and plans stay linked.
Business hours
- Working-hours calendars set day by day.
- Round-the-clock calendars for 24-hour contracts.
- Each SLA counted on its own calendar.
Clocks on jobs
- Clocks that start, pause and stop as the job moves.
- SLA status shown on each job.
- Completed, at risk or breached at a glance.
Alerts
- An alert when a job reaches its at-risk point.
- An alert when a job breaches its target.
- Alerts to a chosen person or role, plus their manager or the job owner.
Who an SLA covers
- One SLA for all clients, or chosen clients only.
- A start and end date for each client's SLA.
- An SLA tied to a specific asset.
Service contracts
- Client, contact, start and end dates and reference number.
- Your own contract types.
- The assets a contract covers, with quantities.
Contracts and maintenance
- Maintenance plans attached to a contract.
- Contracts listed on each asset's record.
Reminders and records
- Email notifications for contracts, such as a contract-ending reminder.
- SLA status in reports.
Commercial records
- Sales orders with products and pricing for each client.
- Sales orders linked to contracts and jobs.
Response and completion targets written into each SLA
Set targets for each stage of a job, such as response and completion, so every contract job carries the promise you made.
Service level agreements turn "as soon as possible" into numbers. In FieldEx, each SLA is built from stages, such as response and completion. Each stage has its own target in days, hours and minutes. It also has an earlier point at which the job counts as at risk.
When a job matches the SLA, its clock starts automatically, and its SLA status shows on the job.
SLA clocks that count business hours, not just the calendar
Give each SLA its own working-hours calendar, so a four-hour response target means four working hours where the contract says so.
In FieldEx, you set business-hours calendars day by day. Each day has start and end times or runs all day, and weekends switch on or off. Each SLA uses the calendar that matches its contract. A 24-hour hospital contract and an office-hours retail contract run side by side.
Clocks can also pause and restart as the job's status changes, for example while waiting for a client.
Some contracts run around the clock. Others don't, and a weekday contract's request logged at 6 pm on Friday shouldn't breach by Saturday.
Timers that follow the client's working hours
Each SLA uses its own calendar, so a four-hour response under an office-hours contract counts four working hours.
A fault logged at 7 pm on a Friday under a Monday-to-Friday contract shouldn't count as breached by Saturday. Timers that ignore working hours make reports nobody believes.
In FieldEx, calendars are built per weekday, each with its own hours or set to all day, and weekends included or not. A 24-hour hospital contract and an office-hours bank contract can run side by side, each on its own calendar.
Timers can also pause and resume as the job's status changes, for example while waiting for site access.
Alerts before a target is missed, and when it is
FieldEx alerts the people you choose when a job reaches its at-risk point and again if it breaches, so there is time to act.
Some deadlines are short, such as making an emergency safe within hours. In FieldEx, each SLA stage can alert a chosen person or role when a job becomes at risk and when it breaches. The alert can also copy their manager or the job's owner. It arrives while the job can still be saved, not in next month's report.
The job itself shows its SLA status, so a dispatcher looking at the schedule can see which jobs need moving up.
Different SLAs for different clients and assets
Apply an SLA to all clients or chosen ones, with its own dates, and tie it to one asset where the contract does.
Contracts rarely share one target. A hospital's critical systems may need a two-hour response, while the same contractor's office clients accept next-day visits.
In FieldEx, an SLA can apply to every client or be attached to chosen clients. Each client gets a start and end date that matches their contract. An SLA can also be tied to one asset. The chiller under a premium agreement then gets the faster clock, while other equipment on the same site does not.
Conditions decide which jobs an SLA applies to, such as the job type or fault type.
Service contracts tied to the assets and plans they cover
A service contract in FieldEx lists its client, dates, assets and maintenance plans, so the office knows exactly what is covered.
In FieldEx, a contract records the client and the client's contact, and its start and end dates. It also holds a reference number and your own contract type. Its assets are listed with quantities, and maintenance plans can be attached to it. The planned visits the contract promises are then scheduled from the same record.
Each asset's record also lists the contracts it falls under.
Each machine's record also shows the contracts it falls under.
Proving SLA performance at review and renewal time
SLA status is recorded on every contract job and available in reports, so reviews start from evidence rather than memory.
That gives both sides the same record at a quarterly review or a renewal discussion.
Late service has a price, often a discount or a penalty under the contract. In FieldEx, every job under an SLA records whether each stage was completed in time, became at risk or breached. Reports can group those results by client, site, job type or month, and can be emailed to the client on a schedule.
Contract start and end dates, with reminders before renewal
Every contract carries its start and end dates, and email notifications, such as a contract-ending reminder, can be set up, so renewals are planned.
Renewals slip when end dates live in a spreadsheet nobody opens. A lapsed maintenance contract can mean a client served for months without a valid agreement.
In FieldEx, each contract shows its start and end dates and its status. Email notifications can be set up for contracts, for example a reminder ahead of the end date, using your own message.
The contract list shows each contract's dates and status, so the office can see which contracts end this quarter.
Sales orders that connect contracts to the work
Record what a client bought on a sales order, with products and prices, and link it to the contract and the jobs that deliver it.
Contract terms often start as a commercial order: a number of service visits, a set of parts, an installation.
In FieldEx, each client can have sales orders with products, pricing and billing details. A sales order can be linked to the contract it created and to the jobs that fulfill it. The office can then trace work back to what was sold.
How sales orders reach your accounting system is covered in the FAQ below.
Settling SLA disputes with the job's own record
When a client questions a response time, the job shows when it was raised, when the technician arrived and every change made since.
SLA disputes usually come down to times: when the call came in, when someone arrived, when the fault was fixed. Memories and phone logs rarely agree.
In FieldEx, each job records when it was created, and each task records the technician's check-in and check-out. The job's change history logs every edit with the old and new value, who made it and when. Completed jobs can be locked so that only chosen roles can change them.
Put beside the SLA status on the same job, that gives both sides one timeline to discuss, rather than two competing accounts.
What each person gets from contracts and SLAs in FieldEx
Contract managers see which promises are at risk, dispatchers see which jobs to move up, and clients see the same record at review.
Contract manager
Each contract's assets, plans, dates and SLA results.
Dispatcher
SLA status on jobs in the schedule.
Supervisor
Alerts before and when a target is missed.
Service manager
SLA results by client, site and month.
Finance
Sales orders linked to contracts and jobs.
Client
Scheduled reports of SLA performance.
Contracts that cover both breakdowns and planned visits
FieldEx is field service management and a CMMS in one system, so one contract times breakdowns and schedules its planned maintenance.
Most service contracts promise two things: a fast response when something fails, and planned visits that stop it failing. In FieldEx, the SLA runs on the reactive jobs. The maintenance plans attached to the contract create the planned ones, all on the same assets.
The asset's history then shows both, under the contract that paid for them.
See how contracts connect to other parts of FieldEx:
Or read what to look for in Field Service Management Software.
Royal Facilities Management: client visibility that supports renewals
Royal Facilities Management (facilities management, Oman) needed property owners to follow the progress of a job and view completed work. That visibility was critical for assessing performance and supporting contract renewals.
With FieldEx, a dedicated portal lets property owners log issues, track technician progress and review completed service reports. Maintenance work orders are created automatically before a deadline is missed.
Read the Royal Facilities Management Story
Magnum: SLA tracking that keeps the team on target
Magnum, a Malaysian leisure and entertainment brand since 1968, moved its maintenance operations from paper to FieldEx.
FieldEx centralizes SLA management and notifies the team when deadlines approach, helping them stay on target. "With FieldEx's SLA feature, our team completes tasks more efficiently, keeping us on track with our key performance index."
Read the Magnum Story
Questions contract and service managers ask about SLAs in FieldEx
Is FieldEx good service level agreement software for field service and maintenance contracts?
Yes. FieldEx runs response and completion clocks on contract jobs in each client's business hours. It alerts your team before and when a target is missed, and links each contract to its assets and maintenance plans. Because it is also a CMMS, the planned visits a contract promises are scheduled from it.
Can FieldEx track response and resolution times?
Yes. Each SLA has stages, such as response and completion. Each stage has targets in days, hours and minutes, and each job shows whether it met them.
Can SLA clocks follow business hours?
Yes. Each SLA uses a working-hours calendar set day by day, or a round-the-clock calendar for 24-hour contracts.
Can the SLA clock pause?
Yes. Clocks can start, pause and stop as the job's status changes, for example while waiting for the client.
Will we be warned before an SLA is breached?
Yes. FieldEx alerts chosen people when a job reaches its at-risk point and again if it breaches. It can also copy their manager or the job owner.
Can different clients have different SLAs?
Yes. An SLA can apply to all clients or chosen ones, each with its own start and end dates. It can also be tied to a specific asset.
What does a 4-hour SLA mean in FieldEx?
It means four hours on the calendar that the SLA uses. On an office-hours contract, that is four working hours, so a call logged late on Friday can still be on time on Monday morning. On a 24-hour contract, it is four clock hours. Conditions such as job type decide which jobs the SLA covers.
Can we report SLA performance?
Yes. SLA status is recorded on each job and available in reports, which can be emailed to clients on a schedule.
Can a contract include specific assets?
Yes. A contract lists the assets it covers, with quantities, and each asset's record shows its contracts.
Can maintenance plans be linked to a contract?
Yes. Maintenance plans can be attached to a contract, so the planned visits it promises are scheduled from the same record.
Can FieldEx remind us before a contract ends?
Yes. Email notifications can be set up for contracts, such as a reminder before the end date.
Can we show a client exactly when we arrived?
Yes. Each task records the technician's check-in and check-out, and the job's change history shows every edit with who made it and when.
Can we classify contracts by type?
Yes. You can classify contracts by your own contract types.
Can contract billing flow to our accounting software?
FieldEx can connect to any open system through REST APIs and has connectors for QuickBooks and Xero.
Customers, sites, assets and past jobs can be uploaded. FieldEx helps with setup, and training is included. See Setup and Training.
Once we know your requirements and your data is ready, FieldEx can be implemented in as little as a week with standard features for small businesses. Larger setups and custom work take longer.
How long does it take to set up contracts and SLAs in FieldEx?
There's no setup fee. Customers, sites, assets and past jobs can be uploaded. FieldEx helps with setup, and training is included. See Setup and Training.
You can also set FieldEx up yourself with guides, videos and the in-app AI assistant, which answers questions as you go.
Once we know your requirements and your data is ready, FieldEx can be implemented in as little as a week with standard features for small businesses. Larger setups and custom work take longer.
