Scope of Work vs. Service Level Agreement: What Facility Managers Actually Need

Why the distinction matters

When a service contractor's performance begins to slip, repeated conversations may not be enough to correct it. The underlying problem is often not a lack of concern or communication. The contract documents may never have clearly defined what satisfactory performance looks like, how it will be measured, or what happens when the required level of service is not delivered.

Facility managers responsible for recurring services—such as janitorial, landscaping, pest control, security patrols, or preventive maintenance—often need both a clear Scope of Work and a clear Service Level Agreement.

What belongs in a Scope of Work?

The SOW should describe everything the facility manager expects the contractor to accomplish when the job is done properly. It establishes the locations, tasks, frequencies, responsibilities, exclusions, staffing expectations, supplies, reporting requirements, and other details contractors need to price and perform the service.

A task list alone can still leave room for disagreement. Two contractors may interpret ‘clean the floors’ very differently. One may believe a quick pass with a mop satisfies the requirement. The facility manager may expect the floor to be free of visible soil, streaks, residue, debris, and sticky spots after service. Unless the expected result is written down, both parties may believe their interpretation is reasonable.

• Clean floors in all identified areas at the required frequency
• Empty every designated waste receptacle and replace liners
• Remove fingerprints and visible marks from stainless-steel surfaces
• Clean and restock restrooms
• Dust horizontal surfaces and accessible fixtures
• Report damage, leaks, supply shortages, or other observed problems
• Complete periodic tasks such as floor refinishing, high dusting, or deep cleaning

What belongs in a Service Level Agreement?

The SLA turns general expectations into observable performance standards. It should explain how the facility manager will determine whether the service was delivered acceptably and what corrective process applies when it was not.

Depending on the contract and procurement rules, the corrective process might include documented deficiency notices, corrective-action plans, re-performance at no additional cost, escalation meetings, service credits, withholding payment for incomplete work, or termination rights for repeated failures.

The purpose is not to create a punishment system. It is to remove uncertainty. The contractor should know how performance will be assessed, how deficiencies can be corrected, and what repeated nonperformance means before the work begins.

• Floors are free of visible debris, soil, streaking, residue, and sticky areas following scheduled cleaning
• All designated waste receptacles are emptied during each scheduled service, with no overflowing containers remaining
• Stainless-steel doors, appliances, fixtures, and panels are free of visible fingerprints and smudges after cleaning
• Restroom consumables are replenished to the specified level before the contractor leaves the facility
• Reported deficiencies are acknowledged within an established period and corrected within an agreed timeframe

Why conversations alone may not improve service

In one real-world janitorial arrangement, cleaning quality steadily declined despite repeated conversations intended to produce improvement. Examples included floors that did not appear properly cleaned, waste containers that were not consistently emptied, and fingerprints left on stainless-steel surfaces.

Those issues expose a common contracting weakness. If the agreement only states that the contractor will ‘clean the floors,’ ‘remove trash,’ or ‘clean stainless steel,’ it identifies the activity without defining the required result. When the expected condition, inspection method, corrective timeframe, and consequences are missing, every performance discussion can become another subjective disagreement.

A stronger agreement establishes both the required tasks and the observable condition after the tasks are completed.

The facility manager still has an active role

Even a well-written SOW and SLA will not manage the contract by themselves. Facility managers should inspect service quality regularly and document deficiencies consistently.

Inspections should be consistent enough to identify trends, not limited to occasions when someone complains. Documentation gives the contractor specific information it can act on and gives the facility manager a defensible record if escalation becomes necessary.

• The date, time, and location of the inspection
• A description of the unmet requirement
• Photographs when appropriate
• The applicable SOW task or SLA standard
• When the contractor was notified
• The contractor's response and promised correction
• Whether the deficiency was corrected within the required timeframe
• Whether the same problem has occurred previously

Use the SOW and SLA together

A detailed SOW without performance standards may produce completed tasks with unacceptable results. An SLA without a detailed scope may measure performance against work that was never clearly assigned.

When developed together, the SOW and SLA give contractors a clearer basis for pricing, employees a clearer basis for performing the work, and facility managers a clearer basis for inspection and contract administration.

Before issuing the next recurring-services RFP, ask two questions: Have we clearly described everything the contractor must do for the job to be considered well done? Have we clearly defined how acceptable performance will be measured and what happens when the standard is not met? If either answer is no, the solicitation may need both a stronger Scope of Work and a stronger Service Level Agreement.

The SOW defines what a well-done job includes. The SLA defines the expected level of performance and the consequences when that level is not achieved.