Build the board from the workload limits configured for that property, compute the reductions the local rules prescribe, and hold anything that moves a shift or reaches a limit for the supervisor.
4Controls appliedSquare-footage checks, prescribed reductions, hour-cap and notice checks, and confidence threshold
No human action required
Stages 1 to 4 run unaided, and no work is assigned at any of them — the agent is proposing, and the housekeeper's lane opens at the confidence gate.
5DecisionBranches at the confidence threshold
High confidence
Goes to the executive housekeeper to release.
Low confidence
Adds a floor-supervisor read first.
Housekeeper releases
The board is held with its limits, its flagged rooms and the confidence.
Release · Adjust · Send to supervisor review
Released — the board goes out▼
6Property systems updatedOnly where write access and approval policy allow it
7Outcome evaluatedWorkload against limit, consent outcomes, shift changes and rooms reassigned during the day
Adjustments
Every housekeeper adjustment is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Assigning work past a property's workload limit.
Re-assigning, moving or cancelling a posted shift.
Extending a day beyond the configured hour cap.
Entering a room a guest is currently occupying.
Automation boundaryAgent acts unaided
✓Build the board from configured limits and room square.
✓Compute the reductions the local rules prescribe, floor.
✓Show which rooms a written consent would be needed to cover.
✓Flag what a supervisor must weigh, and hold the board there.
Any write happens inside the boundaries agreed at implementation, never ahead of release.
Clearing or overriding a do-not-disturb notice.
Acting on a housekeeping observation about a guest.
Filling a shift gap from an outside agency roster.
Changes to workload limits, notice or consent rules.
Example output
One attendant's board, annotated
Everything the agent proposes is attached to the limit it was computed against.
Assignment output · single attendantIllustrative example
Attendant
Proposed board
Workload computed
Limit applied
Confidence
Standing
Floors three and four
Fourteen rooms across two floors, with the special-attention reductions already taken
3,450 sq ft
Configured for this property
93%
Within the day's cap
As receivedTaken from the room record and the limits configured for this property — nothing here is assumed by the agent.
Limits appliedConfigured area capPrescribed reductionsHour cap and notice
Why this boardIt sits inside the day's cap once the reductions are taken — the line the supervisor weighs.
ActionReleaseAdjustSend to supervisor review
What the score decidesBelow the configured threshold the board picks up a floor-supervisor read before it.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every boardFrom the property's own limits
03Proposing
Propose against the limits
Draw on the property's own configured workload, hour and notice rules, and on the room record itself.
01Approved path
Assigning rooms assigns work
Routine boards reach the housekeeper already computed and already carrying the limit behind them.
02Human review
Send review to what moves a shift
The figures differ between neighbouring jurisdictions, so limits are configured per property and never assumed, and a stored consent is re-checked because a worker may withdraw it at any time.
04Build an evidence trail
The assignment, the limits it was made under and the supervisor who released it stay on the board.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
Boards that land within a hair of the area cap are the ones an aggregate figure buries: a small share of days The cohorts that carry it are named, not averaged away..
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Boards near the area cap
8.5%
3.8×
Review
Shifts moved after posting
5.6%
2.5×
Review
Multi-building properties
3.8%
1.7×
Watch
Steady single-floor boards
1.3%
0.6×
Normal
Bar: housekeeper-adjustment-rate lift vs. single-floor baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
A cycle ends in one more case
The loop shuts when the miss is a case in the suite, not when it has been explained. That suite is what the next board put out is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Housekeeper-adjustment rate rises in a board slice.
02Diagnose
Take the boards from that slice, put the square footage and the limits back beside them, and keep reading until the cause narrows to one.
03Improve
Whatever changes ships against a version, with the boards that prompted it attached.
04Verify
Nothing ships until the affected cases pass a second time.
05Learn
The suite grows by one case; so does the workload rule set.
Learn → DetectThe return edge. Next time detection starts one case further along.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, assignment workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Housekeeping workflow discovery and boundary definition.
02Property and labour source assessment.
03Workload limit, hour-cap and notice-rule configuration.
04Room-record ingestion and normalisation.
05Assignment logic and limit binding.
06Confidence scoring and exception routing.
07Housekeeper release workflow.
08Property and labour-system integration.
09Workload and notice cases.
10Guardrails and scheduling controls.
11Board-trail instrumentation.
12Deployment, documentation and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne property, one teamProductionProduction property systemsAdvancedMultiple properties / brands
Introduced at Pilot
Proposing against your limits✓✓✓
Housekeeper release✓✓✓
Assignment-quality baseline✓✓✓
Introduced at Production
Reporting by floor and shift—✓✓
Approval workflow in your systems—✓✓
Approved write-back—✓✓
Property-ops integration—✓✓
Introduced at Advanced
Multi-jurisdiction limit sets——✓
Multi-stage ops approvals——✓
High room volume——✓
Multi-property board controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your room records and square footage→Room-record ingestion and limit mappingWeek 1
02Boards you have already worked→Assignment baseline, pattern extraction and limit bindingWeek 2
03Your local limits and who releases a board→Workload limit, hour-cap and notice-rule configurationWeek 1
04Access to relevant APIs, feeds or exports→Property, housekeeping and labour assessment, then integration setupWeek 2
05Boards you would not want worked→Workload cases and the evaluation suiteWeek 4
06What must reach a supervisor before a shift moves→Confidence scoring, exception routing, guardrails and release controlsWeek 3
07Named housekeepers to release boards→Release workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
The bands follow real work rather than a plan, so evaluation and pilot genuinely share the fifth week.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Housekeeping workflow discovery, limit mapping and the automation boundaryW2Property-system integration and the assignment baselineW3Assignment workflow, confidence logic and release controlsW4Workload cases, notice guardrails and failure-mode testingW5Labour-system integration, pilot boards and targeted correctionsW6One operating period run under the executive housekeeper, then handover
Reading the bandPhases occupy the weeks they really need, so evaluation and launch share the fifth rather than pad it.
At the end of W6Once the period validates, Agent Care owns the running agent.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Travel & Hospitality AI agent
Build a housekeeping agent that proposes, and never assigns.
In several cities and counties a housekeeper's day is capped by floor area, with prescribed reductions, an hour priced differently once a threshold is crossed, and written consent required in advance for a long day — and the figures differ between neighbouring jurisdictions. So the question comes back: for each of your properties, who knows which set applies, and where is that written down? Show us your room records and who releases a board.
