# How to write a checkable facilities and janitorial contract > A facilities and janitorial contract that survives an audit names every variable that can move the price and specifies the invoice format up front. Source: https://valuexpa.com/insights/how-do-you-write-a-facilities-and-janitorial-contract-that Publisher: ValueXPA (https://valuexpa.com) Updated: 2026-09-07 --- Margin drift is the gap between what a vendor contract says and what the invoice actually charges. In facilities and janitorial services, that gap opens quietly because the contract is written around a relationship and the invoice is generated by a billing system that only knows what fields it was given. A facilities contract that survives an audit names every variable that can move the price, states which document controls when two numbers disagree, and requires the invoice to show its work. This page covers what that document looks like. ## Executive Summary Facilities and janitorial contracts get written for the sales conversation, not the invoice. Square footage bands, frequency tables and consumable inclusions get handled as prose during negotiation, then the vendor bills against whatever their own system tracks, and nobody on the buyer's side has a document that says what the invoice should have said. The gap between the contract's intent and the invoice's arithmetic is margin drift, and facilities spend hides it easily because so much of the service is bundled per square foot or per site rather than itemized per task. The fix is structural, not procedural. A contract becomes auditable when every variable that can change the bill, square footage, frequency, site count, consumable allowance, has its own named field with a current value, and when the invoice format is specified in the contract itself rather than left to the vendor's template. An AP reviewer should be able to hold the contract next to the invoice and check the numbers without calling anyone. None of this requires new software. It requires writing the contract as a spec instead of an agreement, with the audit in mind before the first invoice arrives. ## 1. What makes a facilities and janitorial contract hard to audit? **Facilities and janitorial pricing is usually bundled: one rate per square foot or per site covers cleaning frequency, consumables and labor together. When the invoice arrives, it shows the bundled total, not the components. If square footage, headcount, or frequency changed mid-term, the buyer has no field to check it against, because the contract stated a single price rather than the inputs that produced it. The invoice becomes unverifiable by design, not by accident.** Most service contracts in this category are priced as a monthly flat fee tied to a site or a building. That number is easy to invoice and easy to pay, and it is also the reason a change goes unnoticed for a long stretch of the term. The underlying inputs, square footage serviced, cleaning frequency per area type, number of sites, consumable inclusions, are usually described once in an exhibit and never referenced again. When a site closes a wing, adds a shift, or drops a service line, the flat fee often does not move, because there is no mechanism in the contract that ties the fee to the inputs on an ongoing basis. An auditable contract separates the price from the inputs that justify it, so a change in one is visible without renegotiating the other. ## 2. How should scope of work be written so drift is visible? **Scope should be written as a table, not a paragraph: one row per service line, area, or site, each with its own frequency and unit of measure. A paragraph description lets a vendor argue that an activity was included or additional after the fact. A table forces both sides to agree on the unit before a dispute happens, and it gives AP a fixed structure to check a change order against instead of re-reading the whole agreement.** A scope written in narrative form invites interpretation later. "Daily cleaning of common areas" does not say which areas, what daily means for a three-shift site, or whether a deep clean counts as part of that frequency. A table format closes that gap by forcing each service to declare its own unit before the contract is signed, and it becomes the reference an AP reviewer checks an invoice line against months later. - **One row per service line:** Floor care, restroom service, waste removal and window cleaning each get a separate row with their own frequency, not a combined [janitorial services line](/guides/indirect-spend-audit-categories). - **A stated unit for each row:** Square footage, site count, or occurrence count, named explicitly so a change in any one has somewhere to be recorded. - **An exclusions row:** What the base scope does not cover, so a billed extra has to match something named as out of scope, not just something the vendor decided was extra. ## 3. What pricing structure survives an invoice-by-invoice check? **A rate per unit, applied to a current count of units, survives a check. A flat monthly fee does not, because it hides the arithmetic that produced it. The contract should state a rate per square foot or per site for the base scope, a separate rate for any add-on frequency, and a defined process for updating the unit count when the facility footprint changes. The invoice should then show rate multiplied by current count, not a single total.** Where a flat fee is unavoidable, commercially or contractually, the contract should still state the unit count it was calculated from and require that count to be reprinted on every invoice. That single line, based on a stated square footage across a stated number of sites, gives AP something to compare against the current facility roster without needing the original pricing model. A rate card structure, similar to what is used in freight and staffing contracts, works the same way here: the reference table lives in the contract, the invoice cites it, and a mismatch is visible on sight rather than after a manual recalculation. The same mechanism applied to labor is covered in the discussion of [rate card enforcement against approved timesheets](/guides/rate-card-enforcement-why-approved-timesheets-still-produce). ## 4. How do you handle square footage and frequency changes over the term? **The contract needs a change order mechanism that updates the unit count in writing before the next invoice, not a verbal agreement the vendor's billing team may or may not act on. Every change order should restate the new unit count, the effective date, and the resulting rate impact, and should be numbered and referenced on the invoice it first appears on. Without that trail, a facility expansion or contraction becomes invisible to anyone checking the bill later.** Facilities footprints change more often than the contract term implies: a mothballed area stops needing daily service, a new production line adds a shift, a leased annex gets added or dropped. Each of these should trigger a written change order, even when the commercial terms do not change the base rate. The change order becomes the audit trail. A reviewer checking twelve months of invoices against one contract exhibit will miss a mid-year change; a reviewer checking each invoice against its cited change order number will not. ## 5. What documentation should every invoice carry? **Every facilities invoice should carry the site or sites billed, the unit count used for the period, the rate applied, any change order number in effect, and an itemized list of add-on services beyond the base scope. A total with none of that context cannot be checked against the contract; it can only be paid or disputed on trust. Specifying this format in the contract itself removes the vendor's discretion over what the invoice discloses.** A common failure looks nothing like fraud: the vendor's invoicing system prints a total and a purchase order number, and the line-item detail exists somewhere in their internal records but never reaches the buyer. AP pays it because the purchase order matches and the amount looks roughly right. Requiring an itemized format in the contract, not as a request but as a term, changes what the vendor's system has to produce. This is the same discipline covered for maintenance work in the discussion of [scope drift on maintenance work orders](/guides/scope-drift-on-maintenance-work-orders), where the invoice format decides whether a change is visible at all. ## 6. How do you build in the right to audit itself? **A right-to-audit clause should state who can request supporting documentation, within what time window, and covering what records: timesheets, consumable delivery receipts, change orders, and the unit count history. Without a stated time window, a vendor can decline to produce records for a period that has aged out of their own retention policy. The clause should also state that withheld documentation is treated as an unsupported charge, not as a stalemate.** Facilities and janitorial vendors keep operational records, staffing rosters, consumable delivery logs, supervisor visit reports, that rarely reach the buyer unless the contract requires it. A right-to-audit clause exists to make that data producible on request rather than optional. The clause is weakest when it grants a right without a mechanism: no stated response time, no named record types, no consequence for non-production. Naming the records explicitly, and stating that an unsupported line item gets credited rather than argued about, turns the clause from a formality into something AP can actually use during a dispute. This is general information, not legal advice; the specific remedy language belongs in front of counsel before it goes into a signed agreement. For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. ## 7. Frequently Asked Questions (People Also Ask) ### Does a flat monthly facilities fee always hide drift? Not necessarily, but it hides the inputs that produced it unless the contract also states the unit count, such as square footage or site count, the fee was calculated from. Without that stated count, a change in the facility footprint has nowhere to register before the next invoice. ### Should square footage be verified independently or taken from the vendor? The contract should name a source of record for square footage, such as the buyer's facilities team or a lease document, rather than defaulting to whatever figure the vendor last used. That prevents a stale or rounded number from persisting across years of invoices. ### What is the difference between a change order and a contract amendment here? A change order updates an operational input, like unit count or frequency, within the existing rate structure and pricing terms. A contract amendment changes the commercial terms themselves, such as the rate or the scope definition. Facilities contracts need both mechanisms, used for the right kind of change. ### How do consumables get audited separately from labor? Consumables should have their own line in the scope table with either a stated allowance or a pass-through rate, and delivery receipts should be requested as supporting documentation. Bundling consumables into a per-square-foot labor rate makes their cost invisible to a later audit. ### Can this contract structure be applied retroactively to an existing agreement? Not to invoices already paid, but the itemization, unit count disclosure and change order requirements can be added at renewal or through an amendment, and applied going forward from that date. ### Who inside a company should own the audit of these invoices? Typically AP or a controller function reviews the invoice against the contract terms, with facilities or procurement providing the current unit counts and confirming any change orders. The review works best when it sits outside the relationship owner who negotiated the contract. ### Does this apply to single-site and multi-site contracts differently? The same structure applies to both, but multi-site contracts need a per-site breakdown on every invoice rather than a consolidated total, since a single blended number across sites hides which location actually changed. ### What happens if the vendor refuses to itemize going forward? That is worth weighing against the rest of the relationship. A vendor unwilling to itemize a facilities invoice against contract terms is choosing not to support its own billing, which is a reasonable basis to require it as a contract term at the next renewal. ### Is contract complexity quietly draining your operating margin? A small systematic drift between your negotiated contracts and your actual vendor billing compounds quietly across a year of invoices. Stop guessing at your exposure and run a targeted audit. **[Take the Free Screener → https://valuexpa.com/margin-drift-screener](https://valuexpa.com/margin-drift-screener)** ## Executive Summary Facilities and janitorial contracts get written for the sales conversation, not the invoice. Square footage bands, frequency tables and consumable inclusions get handled as prose during negotiation, then the vendor bills against whatever their own system tracks, and nobody on the buyer's side has a document that says what the invoice should have said. The gap between the contract's intent and the invoice's arithmetic is margin drift, and facilities spend hides it easily because so much of the service is bundled per square foot or per site rather than itemized per task. The fix is structural, not procedural. A contract becomes auditable when every variable that can change the bill, square footage, frequency, site count, consumable allowance, has its own named field with a current value, and when the invoice format is specified in the contract itself rather than left to the vendor's template. An AP reviewer should be able to hold the contract next to the invoice and check the numbers without calling anyone. None of this requires new software. It requires writing the contract as a spec instead of an agreement, with the audit in mind before the first invoice arrives. ## 1. What makes a facilities and janitorial contract hard to audit? Facilities and janitorial pricing is usually bundled: one rate per square foot or per site covers cleaning frequency, consumables and labor together. When the invoice arrives, it shows the bundled total, not the components. If square footage, headcount, or frequency changed mid-term, the buyer has no field to check it against, because the contract stated a single price rather than the inputs that produced it. The invoice becomes unverifiable by design, not by accident. Most service contracts in this category are priced as a monthly flat fee tied to a site or a building. That number is easy to invoice and easy to pay, and it is also the reason a change goes unnoticed for a long stretch of the term. The underlying inputs, square footage serviced, cleaning frequency per area type, number of sites, consumable inclusions, are usually described once in an exhibit and never referenced again. When a site closes a wing, adds a shift, or drops a service line, the flat fee often does not move, because there is no mechanism in the contract that ties the fee to the inputs on an ongoing basis. An auditable contract separates the price from the inputs that justify it, so a change in one is visible without renegotiating the other. ## 2. How should scope of work be written so drift is visible? Scope should be written as a table, not a paragraph: one row per service line, area, or site, each with its own frequency and unit of measure. A paragraph description lets a vendor argue that an activity was included or additional after the fact. A table forces both sides to agree on the unit before a dispute happens, and it gives AP a fixed structure to check a change order against instead of re-reading the whole agreement. A scope written in narrative form invites interpretation later. "Daily cleaning of common areas" does not say which areas, what daily means for a three-shift site, or whether a deep clean counts as part of that frequency. A table format closes that gap by forcing each service to declare its own unit before the contract is signed, and it becomes the reference an AP reviewer checks an invoice line against months later. - One row per service line: Floor care, restroom service, waste removal and window cleaning each get a separate row with their own frequency, not a combined [janitorial services line](/guides/indirect-spend-audit-categories). - A stated unit for each row: Square footage, site count, or occurrence count, named explicitly so a change in any one has somewhere to be recorded. - An exclusions row: What the base scope does not cover, so a billed extra has to match something named as out of scope, not just something the vendor decided was extra. ## 3. What pricing structure survives an invoice-by-invoice check? A rate per unit, applied to a current count of units, survives a check. A flat monthly fee does not, because it hides the arithmetic that produced it. The contract should state a rate per square foot or per site for the base scope, a separate rate for any add-on frequency, and a defined process for updating the unit count when the facility footprint changes. The invoice should then show rate multiplied by current count, not a single total. Where a flat fee is unavoidable, commercially or contractually, the contract should still state the unit count it was calculated from and require that count to be reprinted on every invoice. That single line, based on a stated square footage across a stated number of sites, gives AP something to compare against the current facility roster without needing the original pricing model. A rate card structure, similar to what is used in freight and staffing contracts, works the same way here: the reference table lives in the contract, the invoice cites it, and a mismatch is visible on sight rather than after a manual recalculation. The same mechanism applied to labor is covered in the discussion of [rate card enforcement against approved timesheets](/guides/rate-card-enforcement-why-approved-timesheets-still-produce). ## 4. How do you handle square footage and frequency changes over the term? The contract needs a change order mechanism that updates the unit count in writing before the next invoice, not a verbal agreement the vendor's billing team may or may not act on. Every change order should restate the new unit count, the effective date, and the resulting rate impact, and should be numbered and referenced on the invoice it first appears on. Without that trail, a facility expansion or contraction becomes invisible to anyone checking the bill later. Facilities footprints change more often than the contract term implies: a mothballed area stops needing daily service, a new production line adds a shift, a leased annex gets added or dropped. Each of these should trigger a written change order, even when the commercial terms do not change the base rate. The change order becomes the audit trail. A reviewer checking twelve months of invoices against one contract exhibit will miss a mid-year change; a reviewer checking each invoice against its cited change order number will not. ## 5. What documentation should every invoice carry? Every facilities invoice should carry the site or sites billed, the unit count used for the period, the rate applied, any change order number in effect, and an itemized list of add-on services beyond the base scope. A total with none of that context cannot be checked against the contract; it can only be paid or disputed on trust. Specifying this format in the contract itself removes the vendor's discretion over what the invoice discloses. A common failure looks nothing like fraud: the vendor's invoicing system prints a total and a purchase order number, and the line-item detail exists somewhere in their internal records but never reaches the buyer. AP pays it because the purchase order matches and the amount looks roughly right. Requiring an itemized format in the contract, not as a request but as a term, changes what the vendor's system has to produce. This is the same discipline covered for maintenance work in the discussion of [scope drift on maintenance work orders](/guides/scope-drift-on-maintenance-work-orders), where the invoice format decides whether a change is visible at all. ## 6. How do you build in the right to audit itself? A right-to-audit clause should state who can request supporting documentation, within what time window, and covering what records: timesheets, consumable delivery receipts, change orders, and the unit count history. Without a stated time window, a vendor can decline to produce records for a period that has aged out of their own retention policy. The clause should also state that withheld documentation is treated as an unsupported charge, not as a stalemate. Facilities and janitorial vendors keep operational records, staffing rosters, consumable delivery logs, supervisor visit reports, that rarely reach the buyer unless the contract requires it. A right-to-audit clause exists to make that data producible on request rather than optional. The clause is weakest when it grants a right without a mechanism: no stated response time, no named record types, no consequence for non-production. Naming the records explicitly, and stating that an unsupported line item gets credited rather than argued about, turns the clause from a formality into something AP can actually use during a dispute. This is general information, not legal advice; the specific remedy language belongs in front of counsel before it goes into a signed agreement. For the wider pattern this sits inside, start with the [margin drift](/guides/indirect-spend-audit-categories) guide. ## Common questions ### Does a flat monthly facilities fee always hide drift? Not necessarily, but it hides the inputs that produced it unless the contract also states the unit count, such as square footage or site count, the fee was calculated from. Without that stated count, a change in the facility footprint has nowhere to register before the next invoice. ### Should square footage be verified independently or taken from the vendor? The contract should name a source of record for square footage, such as the buyer's facilities team or a lease document, rather than defaulting to whatever figure the vendor last used. That prevents a stale or rounded number from persisting across years of invoices. ### What is the difference between a change order and a contract amendment here? A change order updates an operational input, like unit count or frequency, within the existing rate structure and pricing terms. A contract amendment changes the commercial terms themselves, such as the rate or the scope definition. Facilities contracts need both mechanisms, used for the right kind of change. ### How do consumables get audited separately from labor? Consumables should have their own line in the scope table with either a stated allowance or a pass-through rate, and delivery receipts should be requested as supporting documentation. Bundling consumables into a per-square-foot labor rate makes their cost invisible to a later audit. ### Can this contract structure be applied retroactively to an existing agreement? Not to invoices already paid, but the itemization, unit count disclosure and change order requirements can be added at renewal or through an amendment, and applied going forward from that date. --- ValueXPA runs a fixed-scope Margin Drift Diagnostic that validates every service vendor invoice against contract terms, for $100M+ US industrial manufacturers and distributors. Two to four weeks. The client retains 100% of recoveries. https://valuexpa.com/contact-us