Billed scope beyond contract in facilities and janitorial

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. In facilities and janitorial services, that gap often shows up as scope: work the invoice bills that the statement of work never priced.

A janitorial or facilities contract typically prices a defined set of tasks, a defined frequency, and a defined square footage. Anything outside those three boundaries is billed scope beyond contract, and it accumulates quietly because the invoice still looks routine.

Executive Summary

Facilities and janitorial contracts price scope narrowly: specific tasks, a stated frequency, a defined square footage or site list. The invoice, though, is generated by a site supervisor filling out a service ticket, not by someone checking that ticket against the SOW's task matrix. When a supervisor adds a task, a frequency bump, or a square footage change without a change order, the invoice carries it forward as if it were always in scope.

The mechanism that lets this persist is the disconnect between the person who authorizes work at the site and the person who reconciles the invoice against the contract. Facilities managers approve site-level requests for practical reasons, extra floor stripping before an audit, additional trash pickups during a busy season, without routing them through procurement or updating the master agreement. AP pays the invoice because it matches a purchase order for "facilities services," a category too broad to catch a task-level change.

What changes it is task-level matching: comparing each line on the invoice against the SOW's task matrix and frequency table, not just against the PO total. Once that check exists, scope additions have to be priced and approved before they bill, not discovered after months of accumulated invoices.

1. How does scope beyond contract get onto a facilities invoice in the first place?

A facilities or janitorial SOW lists specific tasks (floor care, restroom service, trash removal) at a specific frequency for a specific footprint. A site supervisor who needs extra work done, an added floor, a special event cleanup, a deep clean before an inspection, asks the vendor directly instead of routing the request through procurement. The vendor performs the work and adds it to the next invoice as a line item, often without a change order number, a new unit price.

The request usually starts as a reasonable, urgent ask. A plant manager wants the lobby stripped and waxed before a customer visit, or wants nightly trash pickup increased to twice daily during a production surge. The vendor's site team has the crew and the equipment on hand, so it says yes.

What does not happen next is the part that matters: nobody amends the SOW's task matrix, nobody issues a change order, and nobody tells AP that the new invoice will contain a line the contract does not price. The invoice arrives with a new task description, sometimes folded into an existing line so it does not even appear as a separate charge.

Because the request came from inside the building, it feels authorized. It was authorized, by the person who needed the work done, just not by the process that reprices the contract when scope changes. That distinction is the entire mechanism.

2. What contract language actually defines scope on a facilities agreement?

Three clauses do the defining: the task matrix, listing what is cleaned or maintained, the frequency schedule, stating how often, and the site or square footage schedule, stating where. A change to any one of the three is a scope change and requires a written amendment or change order with its own price, under the agreement's change-order clause. An invoice line that does not map to an existing row in the task matrix, at the contracted frequency, for a listed.

These three clauses together are what a facilities contract actually prices, more precisely than the monthly headline fee suggests. Reading only the fee schedule misses the boundary; reading the matrix and frequency table together shows exactly where a billed line falls outside it.

A. Task matrix and frequency table

Most janitorial and facilities SOWs attach a task matrix: a grid of tasks (vacuuming, restroom restocking, window washing, floor stripping) against a frequency (daily, weekly, quarterly). This grid is the actual price basis, more specific than the headline monthly fee suggests. A task performed more often than its listed frequency, or a task not listed at all, sits outside the priced scope even when the vendor treats it as a minor add.

B. Change order clause

The change-order clause is what is supposed to catch this. It typically requires written approval and an agreed unit price before out-of-scope work proceeds. In practice the clause exists on paper and gets bypassed at the site level because the people requesting extra work do not know the clause exists or find it slower than asking the crew directly.

3. Why does AP approve invoices that bill scope beyond the contract?

AP typically matches an invoice to a purchase order and a monthly not-to-exceed amount, not to the task matrix underneath the contract. If the invoice total falls within a reasonable range of the usual monthly bill, or under the PO ceiling, it passes review without anyone opening the SOW to check whether the specific tasks and frequencies billed are the ones actually priced. The task matrix is simply not part of the standard approval workflow.

Three-way matching checks the invoice against the purchase order and a receipt or confirmation of service. It does not test whether a line item labeled "additional floor care, main lobby" corresponds to a task the SOW ever priced. The PO for facilities services is usually written as a single category and a monthly cap, not a task-by-task budget.

A facilities invoice also tends to arrive as a lump sum with a task description in narrative form rather than a coded line item, which makes it harder for an AP reviewer with no facilities background to know what belongs and what does not. The reviewer's job is to confirm the invoice matches what was expected, and an added task blended into the usual monthly total does not look unexpected.

4. How do you find billed scope beyond contract once it has accumulated?

Pull the SOW's task matrix and frequency table, then line up every invoice line from the audit period against it. Any line that does not map to a listed task, at its listed frequency, for a listed site, is a candidate finding. Group the candidates by site and by requester where the invoice narrative names one, because scope additions cluster around specific site managers who habitually request extra work outside the change-order process.

Start from the contract, not the invoice. Build a reference table of every priced task, its frequency, and the sites it applies to before opening a single invoice. Reviewing invoices first, then trying to recall what the contract allows, is how additions get waved through as reasonable-sounding.

Once the reference table exists, the matching itself is mechanical: does this line exist in the matrix, at this frequency, for this site. Lines that fail the test go into a findings list with the invoice date, the site, and the dollar amount.

A pattern worth watching for separately: scope additions that repeat month over month become, in effect, a new permanent frequency that was never formally amended into the contract. That is a compounding version of the same drift, not a one-time exception.

5. How do you stop scope beyond contract from recurring?

Route every site-level request for added or more frequent facilities work through a change order with an agreed unit price before the work happens, not after it bills. Require AP or a facilities controller to match invoice line items against the task matrix and frequency table, not just against the monthly PO cap. Give site managers a fast, simple change-order path so the incentive to bypass the process on urgent requests goes away.

The fix has two halves, and both need to exist together. The first is procedural: a change order that takes minutes to issue for a small addition, so a site manager facing an urgent request has a legitimate path that is not slower than calling the vendor directly.

The second is a control: task-level matching built into the invoice review, so a line that was never routed through a change order gets caught before it pays, not discovered a year later in an audit. This is the same logic applied to maintenance work in scope drift on maintenance work orders, and to labor billing in labor rate deviations against master service agreements: the contract's specificity has to be carried into the approval workflow, not left in a filing cabinet.

• Task matrix reference: Keep the SOW's task and frequency table in the hands of whoever approves facilities invoices, not just in the contract file.
• Fast change-order path: Give site managers a same-day change-order option so urgent requests do not default to an unpriced verbal ask.
• Line-level invoice matching: Match each invoice line to a matrix row and frequency before approval, not just the total to the PO cap.
• Recurring-addition review: Flag any added task that repeats for two or more consecutive months as a candidate contract amendment, priced and signed, rather than an ongoing informal add.

6. Is billed scope beyond contract different from a rate error or a duplicate charge?

Yes. A rate error charges the wrong price for a task the contract already covers. A duplicate charge bills the same task twice. Scope beyond contract bills a task, frequency, or location the contract never priced at all, correctly or incorrectly, because no rate for it exists in the agreement. The fix differs too: a rate error is corrected against the existing rate card, while scope beyond contract has to be priced and approved before it can even be evaluated.

This distinction matters because the three drift types call for different review steps. A rate audit compares a billed unit price against the rate card, an exercise covered in labor rate deviations against master service agreements for staffing invoices. A duplicate-billing review compares invoices against each other for repeated charges.

Scope beyond contract requires a different reference point entirely: the task matrix and frequency table, not a price list. An auditor who only checks rates against the rate card will miss scope drift completely, because the added task may be billed at a rate that looks perfectly ordinary. The problem is that the task was never priced into the agreement in the first place, not that its price is wrong.

7. Where does this fit against ValueXPA's broader facilities and contract-compliance work?

Billed scope beyond contract is one of several drift types the Margin Drift Diagnostic checks within facilities and the broader maintenance category, alongside rate deviations, duplicate charges, and warranty misbilling. Facilities and janitorial spend sits within the maintenance and repair audit category, reviewed against the specific task matrix, frequency table, and change-order history for each site rather than against a generic facilities budget line.

The diagnostic treats scope beyond contract as one line of inquiry within a facilities or maintenance engagement, not the whole of it. The same engagement also checks whether billed rates match the master agreement and whether any billed work was actually covered under an existing warranty rather than chargeable as new work, covered in warranty work billed as new work.

For a reader auditing facilities spend directly, the starting reference points are the sub-hub for maintenance and MSA invoice audit and the walkthrough of how to audit maintenance and repair invoices, both of which cover the surrounding checks this page does not repeat: rate verification, duplicate detection, and warranty overlap.

For the wider pattern this sits inside, start with the margin drift guide.