Scope day-porter service separately from project/periodic deep-clean work in a client proposal

domain: day-porter-vs-deep-clean-scoping · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Define day-porter scope as recurring, daytime, on-site presence tasks: restroom checks, spot-cleaning, trash/recycling monitoring, lobby/common-area upkeep, and responding to ad hoc spills or incidents during business hours
  2. Define deep-clean/project scope separately: tasks like carpet extraction, hard-floor stripping/refinishing, high-dusting, window washing, and other periodic or after-hours work not part of daily routine service
  3. Set distinct frequencies for each category (day-porter = daily/continuous presence; project work = weekly/monthly/quarterly/annual as scoped)
  4. Price and staff each category separately, since day-porter roles typically require a dedicated on-site FTE while project work can be scheduled with specialized crews or equipment
  5. Clarify in the contract which category picks up ambiguous requests (e.g., a large spill during business hours vs. a scheduled carpet extraction) to avoid scope disputes
  6. Build a reporting cadence that separately tracks day-porter task completion and project-work completion against the SLA

Known gotchas

Related routes

Scope day-porter services versus project/periodic work in a janitorial proposal
issa.com · 5 steps · unrated

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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans