Columns
Availability
Availability is never computed on this screen. Shifts, working windows and leave have a precedence between them, and one place owns it — a screen that re-derived availability would be a second roster, and the first person to notice would be whoever got sent to a job on their day off. So what you see here, on the dispatch board, and in routing is always the same answer.Teams
Crews are managed here, beside the people in them, rather than filed under configuration — a team is people, not a setting.Adding somebody
New on this screen. A worker record needs a number, a name, a type and a site.A worker and a user are different records. A worker is somebody who does maintenance; a
user is somebody who signs in. Most technicians are both, and the two are linked so the app knows
whose work “my work” means — but a contractor might be a worker who never signs in, and a
storekeeper a user who is not a worker.Users and their roles live under people and access.
Inside a technician
Skills, certifications, schedule, availability, current work, history and performance.