No verb matches. Aidepost has four: offer, post, add a date, export.
The order is the product, and every step of it is somebody’s deliberate action. A shift goes to the people who already work in the house before it goes anywhere near the outside, because they know the house.
This week and next, for your houses, one row per shift, soonest first — covered, with the person’s name, or open. Above one house they are grouped by house. That is the whole emotion.
One row per shift — covered, with a name, or open, in the accent.
Surfaced, not required. The eligible filter shows what the shift asks for; it does not exclude.
If two workers claim at once, the first stands and the second is told immediately. If nobody claims, the shift stays open, the escalation repeats, and the provider works the phone as she did before — but now with a record of having tried.
Two gates, and both are about who may act rather than about whether a rule was followed. Nothing else in this product stops anyone: where it knows a fact bearing on whether a person should work a shift, it marks it at the point of assignment and never removes her from the list or prevents the assignment.
It shows what is not covered.
Tap a cell: M. Okafor → J. Ruiz → T. Nguyen → Open. A pattern per house generates this; you only touch what changed. The roster shown is sample data.
Never a background check — the provider runs ORCHARDS and Aidepost records the status and the date.
Never a background check — the provider runs ORCHARDS and Aidepost records the status and the date.
Recorded with its dates and marked self-attested, because that is what it is. Nothing to say yet.
Nothing is blocked at any point on this line. Expired is marked on the roster and in the eligible list, naming the credential; the assignment still proceeds on a single action. Renewed is a new row; the old one stays as history.
Clock in at the house, clock out, a daily total, a weekly total, the overtime flag at forty hours. Approved, then exported. Never computed into pay.
Hours are exported, never calculated into pay. A correction is an addendum with a reason; the original stays.
Offline if she must — the event queues, marked pending, and is submitted exactly once on reconnection. A clock event is never edited or deleted; a correction is a new record beside the original.
Over forty by 2 h · weekly flag, never daily
One thing survives a failed payment. Rosters cannot be built, shifts cannot be assigned, postings cannot be published and applications cannot be advanced — and your workers can still clock in and out, because hours worked are a legal record that must not be lost over a billing failure. The notice says so.
A post is drafted, paid, published. An application arrives with self-attested credentials. Screened → offered → accepted → hired → a staff row, onboarding open.
A posting describes work, not a person. “One-to-one for a resident who…” raises a warning and is rewritten before it goes live.
A posting describes work, not a person. “One-to-one for a resident who…” raises a warning and is rewritten before it goes live.
recorded with its dates and marked self-attested, because that is what it is → a thirty-day notice → a seven-day notice → a notice on the day → expired, named on the roster and on the eligibility list, and the shift can still be assigned → renewed as a new record superseding the prior one, which stays with its dates. Credential history is never collapsed. An expiry before its issue date is refused; an expiry in the past is accepted, because that is a true and useful fact.
a post is drafted, invisible to everyone outside your organisation → the per-post charge is paid, because an unpaid posting stays a draft → published, and reachable without an account → an application arrives carrying her profile, her recorded credentials as self-attested and her answers, one per person per posting → screened → offered → accepted → a staff record is created and the invitation attaches the account she already has → the onboarding checklist opens for that house’s track. Applications are never ranked or scored, and hiring is never a bulk action.
clock in at the house, offline if she must, on an idempotency key of user, shift, action and client timestamp → clock out, or the entry is marked incomplete two hours after the shift ends and you both see it → hours by day → a week → an indication at forty hours, and none daily → approve one person at a time, which locks the week → export CSV. A clock event is never edited or deleted; a correction is a new record referencing the original, and both remain visible.
Binderkit produces the policy text and Aidepost never authors, edits or templates it → you register which version is current → each person signs by typing her name and confirming, and the signature records who, when, which version and the IP → a new version resets the outstanding signatures and keeps the ones made against prior versions, so it stays provable who agreed to what and when.
Leave an email and we will tell you when it opens, what it costs, and how to get in. One message when there is something to say — nothing else, ever.
No organisation. No card. Nothing to cancel.
One email address, one licence track, one house count. No card, no account, no newsletter.