# ERP for Facility Management and Cleaning Services: Schedules, Checklists, and SLAs > A system guide for facility management and cleaning providers: contracts and service scope per site, recurring schedules, work checklists, issue reports, SLAs, repair requests, consumable and equipment costs, and billing and margin per contract. Source: https://www.agsora.tech/en/blog/erp-untuk-facility-management-dan-jasa-kebersihan-jadwal-checklist-dan-sla Category: Industry Guides · Published: 2026-11-10 · Updated: 2026-11-10 · By PT Agsora Teknologi Indonesia Facility management and cleaning providers sell something that is hard to see: clean rooms, working elevators, tidy gardens, and generators that are ready when needed. Clients only notice the value when something fails. That makes this business a game of consistency and proof. Consistency means the same work happens at the same time across dozens of sites. Proof means you can show, whenever asked, that the work was actually done as the contract requires. Many companies in this field still manage schedules in chat groups, checklists on paper that get photographed, and client complaints through phone calls to a supervisor. While there are few sites, this works. As contracts multiply, the same problems appear: tasks are missed without anyone knowing, SLA penalties arrive with no data to defend against them, and the margin of a contract is only known after it ends. This article covers the system functions you need, how to design the flow from contract to billing, and a realistic rollout. It is general guidance; labor and service-licensing rules differ, so confirm details with your legal adviser. ## Summary - The value of this business lies in proof of work, so every schedule must produce an execution record - A contract per site defines scope, frequency, working hours, headcount, and the SLAs to be measured - Digital checklists with time, location, and photos replace paper reports that are hard to trace - Client complaints should enter as tickets with response deadlines, not as scattered messages - Costs for consumables, equipment, and labor must be calculated per contract so margin is visible from month one *Documented work per site becomes the basis for billing and for defense in SLA disputes* ## What makes facility management different A manufacturer produces goods that can be counted. A facility management company produces a condition: a building that is clean, safe, and comfortable. That condition is measured through a mix of work execution, inspection results, and occupant satisfaction. Three traits shape the system requirements. First, the work is scattered and repetitive. One contract may cover an office building with a dozen staff across three shifts, while another is a single worker in a shop house. Daily, weekly, monthly, and annual tasks mix together: sweeping every morning, cleaning windows every two weeks, servicing air conditioners every quarter. Second, the client relationship is governed by contracts and SLAs. Clients demand response times, cleanliness levels, and staff attendance. Violations can lead to invoice deductions. Without data, all you can do is argue. Third, labor is the largest and hardest cost to control. Attendance, replacement of absent staff, overtime, and turnover affect both quality and margin. If you also supply outsourced workers, the related material is in [ERP for manpower outsourcing companies](https://www.agsora.tech/en/blog/erp-untuk-perusahaan-alih-daya-outsourcing-tenaga-kerja-penagihan-per-kepala-dan-payroll). ## Contracts and service scope per site The starting point of the system is a structured contract, not just a PDF file. For each site, record the following in a searchable, calculable form: - The client, address, responsible contact, and contract validity period - A list of areas and types of work, such as lobby, restrooms, production area, garden, or pool - Frequency per task and the time window for execution - Number of staff and the promised working hours - Pricing: fixed monthly, per hour, per head, or a mix - SLA terms, including deductions if targets are missed - Materials and equipment supplied by the provider or by the client From this data the system can generate schedules, materials requirements, and the basis for invoices. Renewals are also easier to monitor; general coverage is in [contract management and customer renewals](https://www.agsora.tech/en/blog/manajemen-kontrak-dan-perpanjangan-pelanggan). ## Recurring schedules and staff assignment With a clear scope, the system creates recurring work schedules. The rules are simple but numerous: daily tasks appear every day at a set time, weekly tasks on specified days, and periodic tasks follow the calendar. Each occurrence becomes a task that can be assigned to a worker or team. Things the system should support: - Assigning staff to sites and shifts, including substitutes when someone is on leave or sick - A daily schedule view for supervisors so sites with no assigned worker are visible before the day runs - Shift swaps with supervisor approval and a change trail - Working-hour and overtime rules so internal policy and regulation are not violated General shift-scheduling principles are covered in [shift scheduling and workforce management](https://www.agsora.tech/en/blog/penjadwalan-shift-dan-manajemen-tenaga-kerja), and attendance across dispersed sites in [managing field employee attendance](https://www.agsora.tech/en/blog/mengelola-absensi-karyawan-lapangan). In facility management the two connect: a scheduled worker who has not arrived immediately triggers an alert to the supervisor. ## Digital checklists as proof of work Paper checklists are often filled in at the end of the week from memory. Digital checklists turn this into a reliable execution record. Each task has a list of work items, and the worker ticks them through a mobile app on site. An effective design includes: - Short, specific items, such as "refill soap in all second-floor restrooms", rather than "clean restrooms" - Automatic timestamps and location, with QR code scans at areas as proof of presence - Before-and-after photos for work that is often disputed - A notes field for findings, such as a leaking tap or a broken light - Offline mode, because many basements and warehouses have no signal; how this works is explained in [when an app needs to work offline](https://www.agsora.tech/en/blog/kapan-aplikasi-perlu-bekerja-offline) These records are not only supervision of workers. They also protect workers who do the job properly when a client claims otherwise. ## Inspections, findings, and repair requests Besides routine work, supervisors perform periodic inspections. The system provides inspection forms with a score per area, for example on a one-to-five scale, plus photos of findings. Consistent scores over time become evidence of quality, and a declining trend is an early warning before the client complains. Findings that need repair must not stop as notes. They should become work requests with an owner and a deadline. If the repair is the client's responsibility, such as a leaking roof, the request is forwarded to the client with photo evidence so there is a record that you reported it. For assets the provider maintains, such as pumps or generators, link to preventive maintenance schedules as in [asset management and equipment maintenance with ERP](https://www.agsora.tech/en/blog/manajemen-aset-dan-perawatan-peralatan-dengan-erp). ## Client complaints and SLAs Clients rarely wait for the monthly report. They contact a supervisor, receptionist, or manager when something feels wrong. A good system gives clients one channel, such as a portal or dedicated number, and every complaint enters as a ticket with a number, category, priority, and response and resolution deadlines. Practices that help: - Clear categories and priorities: a spill in the lobby during an important event is not the same urgency as a routine cleaning request - An SLA timer that runs automatically and warns before the deadline passes - Escalation to a supervisor or manager when a ticket is not handled - Ticket history per site, usable in monthly review meetings with the client The principle is the same as a general support ticket system, covered in [customer support tickets and SLAs](https://www.agsora.tech/en/blog/sistem-tiket-dukungan-pelanggan-dan-sla). The difference is that every ticket here ties directly to a site, a contract, and the worker on duty at that moment, so root causes are easier to trace. ## Consumables, equipment, and costs Consumables such as cleaning liquids, trash bags, and tissue, and equipment such as polishers and vacuum cleaners, must be linked to contracts. The reason is simple: without records, overuse at one site is hidden by other sites, and contract margin is never accurate. Required functions: - Material stock in the central warehouse and on site, with requests and issues per site - Usage standards per area so deviations are visible - An equipment list with current location, condition, and service schedule - Purchasing connected to approvals and suppliers, following the pattern in [purchase approval flows](https://www.agsora.tech/en/blog/alur-approval-pembelian) With this data, the direct cost per contract consists of labor, materials, equipment depreciation, transport, and supplies such as uniforms. At company level, fixed costs such as head office and supervisors are allocated with a consistent rule. ## Billing and margin per contract Billing follows the contract's pricing structure. A fixed monthly contract produces recurring invoices. A per-hour or per-head contract pulls approved attendance data. Extra work outside scope, such as cleaning after renovation, is recorded as additional work with client approval and billed separately. Without this mechanism, extra work is often done for free. SLA deductions are calculated from ticket and inspection data, not end-of-month negotiation. You still accept legitimate deductions, but you also have a basis to reject unjustified ones. Invoice automation and receivables follow-up are covered in [invoice automation and B2B receivables collection](https://www.agsora.tech/en/blog/otomatisasi-faktur-dan-penagihan-piutang-b2b). The most important report for the business owner is margin per contract: revenue minus direct cost, compared with the plan at quotation. A contract whose actual margin stays below plan needs renegotiation or non-renewal. ## Bringing it all together in one system These functions can be spread over five applications, but the value appears when data flows between them. The ideal flow: contracts produce schedules, schedules produce tasks, tasks produce execution records, records and tickets produce SLA data, and that data becomes the basis for invoices and margin reports. If each step uses a separate app, people go back to copying data manually and errors return. Consider integration with the HRIS for attendance and payroll, with accounting for invoices and costs, and with a client portal for tickets. Integration patterns follow [webhooks and real-time integration for business](https://www.agsora.tech/en/blog/webhook-dan-integrasi-real-time-untuk-bisnis). ## A realistic phased rollout A system like this should not launch across all sites at once. A sensible order: - Month one: contract, site, and worker data; recurring schedules for two or three pilot sites - Month two: digital checklists and QR codes at pilot sites, with short training for workers and supervisors - Month three: complaint tickets and the SLA timer, then expansion to other sites - Month four onward: material costs, automatic billing, and margin reports Choose pilot sites that are cooperative and reasonably representative. Involve supervisors from the start, because they use the system every day. If the app feels like a reporting burden with no benefit, workers will fill it in carelessly and the proof value disappears. Show concrete benefits: clearer schedules, faster complaint resolution, and protection in disputes. ## Common mistakes - Checklists so long that workers tick everything without looking; start with the most important items - No rule about who closes a ticket, so complaints hang - Material costs not linked to contracts, so margin is only an estimate - Contract data not updated when scope changes, so schedules and invoices drift apart - Ignoring field conditions such as weak signal and basic phones when choosing an app ## Frequently asked questions ### Does a business with ten sites need a system? Usually yes, at least for schedules, checklists, and tickets. At that scale supervisors can no longer remember everything, and one SLA dispute without proof can wipe out several months of margin. ### Can workers with basic phones use digital checklists? Yes, if the app is lightweight, the interface is simple, and it supports offline mode. Some companies also provide a shared phone at each site. ### What about privacy when tracking worker locations? Collect only what is needed, such as QR scans at work points rather than continuous tracking. Tell workers what data is recorded and why, in line with personal data protection principles. ## Conclusion Facility management and cleaning is a business of proof: work that is consistent, recorded, and accountable to the client. A system that connects contracts, schedules, checklists, tickets, costs, and billing turns the business from relying on supervisors' memory to being data-driven. The result is fewer disputes, more profitable contracts, and a solid base for growth. If you want to design a system for a service business like this, the Agsora team can help map the flow and choose the most impactful first step. **Design an operations system for your facility management business** Discuss contracts, schedules, checklists, SLAs, and billing with the Agsora team to decide the most impactful first step. [Free consultation](https://www.agsora.tech/en/services/erp)