The paperwork a nursery runs on, doing itself
Onboarding, supervisions, probation reviews, return-to-work. Build each one once and it starts on its own, asks the right person, produces the document, collects the signatures and files it where it belongs.
Processes that run themselves
Draw a process once - a form, a review, a document, an approval - and it runs. Start it when somebody submits a form, on a date from a team member's record, or on a date written into a form: three weeks before a probation ends, a fortnight after somebody returns.
Documents, signed in order
Templates fill themselves from answers given earlier in the process. Signature blocks go to named people in the order you set, one waiting on the one before, and only the people who actually signed get the finished copy.
Filed where you would have filed it
Connect a Google account and finished documents land in Drive - under the site, or under the person - decided by what kind of document it is. Mail goes out from your own address, not ours.
Access that follows the job role
Nine areas, each at none, view or edit, set per job role rather than per person. Somebody becoming a room leader gets what room leaders get, and stops getting it when the role ends.
And follows the dates
Access can open and close against somebody's own start and end dates. AI chat a fortnight before they start so they can read up; the team list a month in, once they have settled; their records for a fortnight after they finish.
How the rooms are going
Four states rather than a score, because a loud room deep in a construction game is going well and a quiet one where nobody is engaged is the problem. Note what was tried and whether it helped, so the log becomes something to act on.
A tablet on the wall, signed in to the building
Sign it in once with the site's own username and password and it stays signed in. Anybody working there can log how a room is going without stopping to identify themselves, which is the point of having it by the door.
Staff tap their own photograph and enter a short code to reach their own tasks, the policies they may read and the chat - for a few minutes, then it returns to the wall of faces on its own. The code is not their password, because the screen is shared and somebody is usually standing next to them.
- Each site decides what its tablet offers
- A job role decides whose face appears on it
- Signed out automatically after a few minutes
- A lost tablet can be revoked without changing the password
Ask your own policies
Put your policies in the library and staff can ask about them in their own words. Answers quote the document they came from, so the answer can be checked rather than taken on trust. A policy written for one site is only shown at that site.
A quality framework you can change
A short survey on a cycle you choose, built from a starting bank of statements that is yours to reword, retire or add to. What comes back is grouped by the things it is actually about, with the drivers that move most.
Start with one process
Set up an organisation, add your sites and job roles, and build the first flow. Nothing else has to be in place for it to run.