A maintenance company signed an attractive annual contract with a mall. Six months later technicians were visiting twice as often as agreed, spare parts were absorbed because nobody checked what the contract covered, and two urgent tickets missed their agreed response time. A contract that looked profitable was losing money every month.

In maintenance services, the contract is the product. Beyond the single work order, this article covers contract and SLA management and profitability per contract.

Contract types

TypeCoversSystem must track
PreventiveScheduled visitsSchedule, execution, reports
ComprehensivePreventive, breakdowns, partsParts and labour vs contract value
Labour onlyVisits and repairsParts billed separately
Visit bankFixed visits or hoursConsumed and remaining
SLABinding response and resolution timesActual vs agreed

SLAs: promises that must be measured

An SLA defines response time, resolution time and working hours for each priority. ERPNext supports Service Level Agreements on tickets with priorities, response and resolution times and working hours, showing each ticket's deadline and whether it was met. Times should be written per contract; any figures you quote to customers must come from what you can deliver.

Contract lifecycle

  1. Quote from equipment survey and expected visits and parts.
  2. Contract with type, term, value, billing, SLA and covered serial numbers.
  3. Preventive schedule generated per asset.
  4. Every visit and ticket is a work order linked to the contract.
  5. Periodic billing plus out-of-scope work.
  6. Monthly profitability and SLA review.
  7. Renewal repriced on actual cost.

Profitability per contract

ItemSource
RevenueContract and extra invoices
LabourTechnician timesheets
PartsStock issued to work orders
TravelLinked expenses
SubcontractSupplier invoices on the contract

With the contract as a cost centre or project, everything is charged automatically and contracts can be ranked from most to least profitable.

Covered equipment and the customer view

Linking tickets and visits to serial numbers stops unbilled work on uncovered assets, reveals failure-prone equipment (see recurring failures) and builds asset history. A customer portal or Frappe Helpdesk lets customers log tickets, see priority and SLA deadlines and follow them; see ticket vs request vs work order.

Pricing contracts from data

ComponentEstimate
Preventive visitsVisits × hours × technician cost
BreakdownsAverage tickets for this equipment from past contracts
PartsConsumption rate per asset in comprehensive contracts
TravelDistance and visits
SLA riskCost of readiness for critical times

After a year of work orders, parts and hours on contracts, pricing rests on your own experience, so you can compete confidently or decline contracts that do not cover cost.

Scheduling technicians

Group visits by area, reserve capacity for SLA-critical tickets and assign by qualification. Technicians see their schedule on mobile and record start, finish and parts on site.

Periodic customer reports

Visits done, tickets and SLA times vs agreed, and equipment needing attention turn the contract into a visible service and a renewal tool.

KPIs and common mistakes

  • SLA compliance per contract.
  • Preventive visits on time.
  • Margin per contract, type and customer.
  • Parts cost vs comprehensive contract value.
  • Most failure-prone assets.
  • Renewal rate.

Avoid pricing comprehensive contracts without failure data, accepting SLAs you cannot measure, doing out-of-scope work without a billable order, and renewing at the same price without reviewing last year's cost.

Frequently asked questions

Preventive vs comprehensive contract?

Comprehensive adds breakdowns and parts, so cost tracking matters more.

Does ERPNext support SLAs?

Yes, with priorities, response and resolution times and working hours.

How do I see profitability per contract?

Charge labour, parts, travel and subcontract to the contract and compare with billed revenue.

Can out-of-scope work be billed?

Yes, through a separate work order.