Structure a janitorial service agreement / SLA between a BSC and a client
domain: issa.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Define scope of work precisely by area, task, and frequency (daily, weekly, periodic/project) to avoid ambiguity that leads to disputes.
Set measurable service levels (e.g., inspection scoring thresholds, response times for spot requests, restroom-check frequency) rather than vague 'clean and sanitary' language alone.
Include specific compliance references relevant to the account (e.g., which EPA-registered disinfectants are used, applicable OSHA programs, any green-cleaning/CIMS-GB or Green Seal commitments) so obligations are auditable.
Address staffing terms: minimum training requirements, background-check expectations, supervision ratios, and successor-employer/transition provisions where required by local law (e.g., California's Property Service Workers Protection Act successor-liability provisions).
Specify pricing structure, invoicing terms, escalation/termination clauses, and insurance/indemnification requirements.
Build in a periodic review/audit mechanism (quality inspections, scorecards) tied to remedies (credits, corrective action plans) for missed service levels.
Known gotchas
Vague scope language ('clean as needed') is the single most common source of janitorial contract disputes; every recurring task should have an explicit frequency.
Where the jurisdiction has a property-service-worker successor-liability law (as in California), a change of contractor can carry legal wage/hour liability exposure that should be addressed in the agreement, not assumed away.
SLA compliance references (e.g., 'CIMS certified,' 'EPA-registered disinfectants only') should be checked against the BSC's actual current certifications/product list at signing and periodically thereafter, not just taken on faith from a proposal.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?