What does companion readiness look like before someone is bookable?
A practical checklist for the scope, consent, room protocol, and reporting basics Humanly Held should see before a companion ever looks available.
Answer first
Before someone is bookable, Humanly Held companion readiness should cover scope understanding, allowed touch types, pause and stop language, trusted-space protocol, reporting readiness, and the confidence to decline.
2026-06-14 · 5 min read
Audience: Companion candidates, operators, and reviewers evaluating what readiness should mean before listing.
This checklist describes a future approval threshold. It does not claim active companion certification, completed background checks, or live readiness decisions.
Companion candidates who want a concrete standard rather than vague culture language.
Operators who need a repeatable readiness threshold.
Clients who care whether the service protects the companion as much as the buyer.
Reviewers who want to see readiness translated into visible operational checkpoints.
Not a fit
Listing people before they understand the category and their right to refuse.
Treating availability as a substitute for readiness.
Public profiles that imply approval without room protocol and reporting paths.
Systems that make declining feel risky or disloyal.
What should readiness cover first?
The first layer is category understanding: what the service is, what it is not, and what language should trigger a stop or escalation.
Without that clarity, every other safety control becomes harder to apply consistently.
Why do touch menus and pause language matter?
Allowed touch types, pause language, and stop language turn boundaries into something visible and repeatable. They reduce guesswork for both the companion and the client.
They also make operator review easier because the expectations are concrete before anyone enters the room.
What should room protocol include?
A companion should know how arrival works, who to contact, how to exit, what happens if the client pushes boundaries, and how incident reporting would work in a managed room.
That room protocol is part of readiness, not an extra detail after someone is listed.
Why should readiness come before availability?
Availability creates pressure. If the product advertises supply before readiness, the companion ends up carrying the cost of a system that moved too fast.
Humanly Held should make readiness the gate that earns availability, not the other way around.