Short answer
Housekeeping and cleaning SOPs describe a service task as a sequence of areas, surfaces, chemicals, tools and inspection standards. They help a service humanoid with task order, scope and what "clean" means to the customer, but they say nothing about how a wipe, a bed-making fold or a vacuum pass is physically executed.
The buyer's problem
Cleaning is a plausible early workplace task for mobile manipulators: high volume, structured rooms, repetitive sub-tasks. It is also deceptively wide. Hotel room turnover, office janitorial rounds, restroom service and post-construction cleaning share verbs and differ in standards, chemicals, equipment and risk.
Cleaning contractors and hotel groups write procedures to make staff output uniform and to define inspection. Those two functions are valuable to a robotics buyer. A procedure supplies the sequence and scope; an inspection standard supplies the pass condition. Without the second, a team has to invent its own success criteria, often with weaker grounding.
What the documents contain
Typical document types include room-attendant standards, public-area checklists, restroom cleaning cards, chemical dilution and dwell instructions, equipment use guides and inspection forms. Within them, expect:
- Area and surface order, such as top to bottom, far to near, dry before wet.
- Task variants by room status (departure clean, stay-over, deep clean).
- Tool and chemical assignments for each surface type.
- Inspection standards, sometimes with photo references of an acceptable result.
- Time allowances per room type or per task.
- Special handling rules for biohazards, lost items and guest property.
Order rules can be encoded as precedence constraints; see task graphs from procedures. Chemical handling rules overlap with safety data sheets as handling constraints.
A public vocabulary to cross-check against
O*NET offers a public reference for the language of work. Its database includes task statements and Detailed Work Activities, with a file that maps tasks to the activities, and task statements are retained only if their relevance rating is 25% or higher (O*NET Resource Center). Buyers can use these as a neutral label set for what a cleaning role does, and to test whether a supplier's SOP corpus covers the activities of the occupation or only a slice of it.
Occupational statements are brief and generic. They cannot replace the supplier's own procedure, but they help map documents from different businesses to common categories; see occupational task taxonomies for the approach.
What cleaning SOPs can support, and what they cannot
| Use | What the SOP contributes | What it lacks |
|---|---|---|
| Task planning for a service robot | Order, scope and room-state variants | The robot's reachable skills and navigation constraints |
| Language grounding | Staff vocabulary: "strip", "make up", "detail" | Visual grounding of each term |
| Inspection and success detection | Standards for an acceptable result | Pass/fail examples as images |
| Resource planning | Chemicals, tools, and time allowances | Evidence that time allowances match actual work |
| Procedural question answering | Rules for exceptions and special items | Edge cases staff handle informally |
Cleaning is a contact-rich task. Wiping force, spray distance, scrubbing intensity and sheet handling vary with materials and are absent from SOPs. They need robot, teleoperated or instrumented capture, which procedures do not provide. See what SOPs can and cannot teach a humanoid.
Illustrative package: room-turnover procedure set
# Illustrative only - synthetic example, not an available dataset
package: room_turnover_sops_v0
source: housekeeping documentation from one hotel operator (several properties)
documents:
turnover_standard: step list by room zone (entry, bed, bath, desk)
variants: [departure, stay_over, deep_clean]
inspection_form: item list with pass/fail and photo reference id
chemical_card: product, dilution, dwell, surface compatibility
step_fields:
step_id: hk_012_s07
zone: bath
action: "wipe"
target: "mirror"
tool: microfiber_cloth_blue
agent: glass_cleaner_A # product names replaced with aliases
order_constraint: after hk_012_s05
inspection_item: insp_09
excluded: video, motion, force, guest information, property-specific brand standards
rights: internal training and evaluation; no redistribution; brand names removed
The tool and agent fields matter because tool-and-chemical assignments by surface are easy to lose if SOPs are summarized into general prose.
Quality and acceptance criteria
Set these as your own thresholds:
- Variant coverage. Each room or area type has all status variants, not only the standard case.
- Inspection linkage. Every cleaning step maps to at least one inspection item, or is flagged as uninspected.
- Alias coverage. Product and equipment names are replaced consistently so the same chemical does not appear under four labels.
- Revision control. The version in force on a given date is identifiable.
- Review by a domain reader. A person who has done the job reviews a sample for omissions; see tacit knowledge gaps in SOPs.
Limitations and extra preparation
Cleaning SOPs often assume a trained human who adapts: a stain that needs a second pass, a drawer jammed shut, a guest's belongings on a surface. The document may cover such cases in one line, or not at all. If your deployment concerns hospitals, the controls and terminology differ substantially; see hospital environmental services procedures.
Documents also vary by role. A supervisor's inspection guide and an attendant's card describe the same room differently; use role-based procedures to keep them separate.
The tool list inside a procedure can differ from what a robot can carry. Tools and materials lists covers how to extract and map it.
Commissioned recording of room turnover, by contrast, would show actual execution but involves guest-room access, privacy and consent. Those considerations appear in worker consent and identifiable people.
Questions to ask suppliers
- Are the SOPs company-wide standards, brand standards from a franchisor, or property-specific?
- Who controls the inspection standard, and does it include photo references?
- How many room or area types and status variants are documented?
- Which chemical, equipment and cloth rules are stated, and from whom?
- Do documents mention time allowances, and are they based on measured work?
- Is there content from product manufacturers (dilution charts, equipment manuals) mixed in?
- Are procedures translated, and which version is authoritative?
- Does any procedure mention guest data, lost-property logs or room numbers that must be removed?
Discuss your requirements
If you are scoping a cleaning or housekeeping task, describe the facility types, document formats and permitted uses to SourceX. SourceX looks for US businesses that hold suitable documents, checks the data and the supplier's licensing permissions, and coordinates the license and delivery. A request does not guarantee a match; SourceX follows up about potential sources.
Start at the humanoid training data guide or the procedural data hub, and see the checklists as success criteria page for the inspection side. The robotics and embodied AI use case shows the broader request categories.
Discuss your humanoid training-data requirements with SourceX
Sources
- ONET Database (ONET 29.1 per search snapshot): Task Statements and Detailed Work Activities — O*NET provides task statements and Detailed Work Activities with a mapping between them, offering a public vocabulary for occupations.