The office prepares the week and publishes it. Everyone sees their shifts on the phone, with times and place, and requests holidays and time off from there. If someone is missing, their shifts stay marked until you cover them.
Book 30 minutesWhile there are few people a sheet is enough. Then the sites multiply, shifts change every week and information goes through the chats, where nobody knows which version is the latest.
The week starts from a sheet and goes through a group. Who has read the latest version?
The shift changes on Thursday evening. The person finds out on Friday morning, at the wrong site.
Whoever was there when they were requested knows. At the end of the year the sums are redone from memory.
That someone is missing comes out when the customer calls.
People in rows, days in columns. Tap a cell and write time, place and customer.
Last week is copied in one click. A regular shift repeats until the date you choose.
While it is a draft nobody sees it. On publication everyone gets their week by email.
On the phone or in the browser, with time, place and note. And they confirm they have seen them.
Each shift is a real row that changes on its own. A replacement is just another person on that shift.
All people and all days on one page, with absences and shifts. On the phone it becomes one box per day.
If you change a published shift, or move it to a colleague, those involved get an email straight away with before and after.
If the end time is before the start, the shift ends the next day.
Everyone confirms they have seen their shifts. If a shift changes, the confirmation starts over.
An address or a site, the customer chosen from the companies you already have, and a note for whoever goes.
You can let everyone see colleagues' shifts. For someone away they see only Away, never the reason.
The request starts from the phone. The office gets an email and sees in the menu how many requests are waiting for an answer.
Holidays from one day to another, or time off by the hour on a single day. It can be withdrawn until it is answered.
The office sees the person's shifts on those days and who else is away. It answers with a note, and the person gets the email.
The shifts of someone on holiday do not vanish. They stay in red, with the count at the top of the week, until you change the person.
If you give a shift to someone away a warning appears. You decide: you can save anyway.
For each person and type, the absences approved in the year, with days and hours.
A file with person, type, dates and hours, to send to whoever does the payroll.
Nobody, everyone or only some. Anyone without access does not see the module, and the rule holds in the database too.
You start from Holiday and Time off, and add the ones you need.
They go out from a mailbox of your company. Everyone can turn them off in their profile, and the office sees the outcome of each one.
On the phone the week, shifts, requests and answers. In the browser settings and export too.
People see their published shifts and their requests. Notes stay between them and the office.
As with all modules on the platform, one company's data is not visible to any other. The database guarantees it.
Thirty minutes, no commitment. You come away with an honest technical opinion on what is worth automating.
Book 30 minutes
Terra di App
Custom cloud business software, built on a base that already works. Source code and infrastructure stay with the client.
2026 Dino Solano · VAT 10312320962 · Milano · All rights reserved