Your team and their phones
Adding people, what they see, documents that expire, background checks, and the visit report they send the family.
What they see
Everyone you add gets a login to their own app, which is not your app. They see their own shifts, the details of the client they are going to, and what they are owed. They never see your other clients, your other staff, or any of your money.
It installs on their phone from the browser. There is no app store, nothing to download, and no update to approve. On an iPhone it has to be installed before notifications work at all, which is an Apple rule rather than ours, so the prompt to add it to the home screen is worth them actually doing.
Documents that expire
Their profile → Documents. Upload a DBS, a first aid certificate, insurance, right to work, and give each one its real expiry date.
The date is the point. You get an email before anything lapses, and the status is visible on the screen where you assign work, so an expired certificate cannot be scheduled by accident.
Background checks
If Checkr is connected you can request a check from the worker's profile and the result lands back on it. If it is not, record the status by hand; the expiry alerts work either way.
References
Request one and the referee gets a link. They fill in a short form, no account needed, and the answer lands on the worker's profile and emails you.
When they are free
They set their own available hours in their app. You can see it when you assign work, and the system uses it when it works out who to offer an open shift to.
This is better than you keeping it, because they are the only person who knows when their circumstances change.
The report they send the family
After a completed visit, their app asks them to tell the family how it went: a few lines, and photos if they took any. It appears in the family's account.
Photos stay between you and that family unless you ask. If you want to use one in your own marketing, open the booking and ask to use it for that specific photo. The family says yes or no in their account and the answer is stored against the photo.
Until they say yes, the answer is no. We do not treat an unanswered request as permission, and neither should you: a photograph of somebody's child used without a recorded yes is a data protection problem, not an oversight.
Photos only at the moment, not video.