Nightly task board
Each building shows its routine tasks, special requests and overdue items for the shift.
SIZ Group would build a janitorial manager app that shows the general manager every building on the route, which crew is assigned, which tasks are overdue and which client requests are still open. It gives one screen for the nightly shift, the weekend deep clean and the spill that cannot wait until Monday.
A commercial janitorial company may run dozens of buildings on a single night shift. Each building has a checklist of routine tasks, a few special requests and a supervisor who walks it at the end of the night. The general manager often hears about a missed restroom or a late lobby only from a client the next morning.
Information lives in too many places. The contract sets the scope, a shared spreadsheet holds the schedule, a group chat carries the night's changes and sign-off sheets sit in each building's binder. When a crew lead texts that a floor was skipped, nobody can confirm whether the supervisor checked it.
Quality problems pile up quietly. A floor that was never finished, a trash room nobody emptied or a supply order that never went through all surface later as complaints, when the cause is hard to trace.
Facility managers choose cleaning partners through referrals, procurement lists and renewal reviews. They want a company that reports problems before a tenant calls, can prove the work was done and answers within the day. Those expectations are set in the first months of a contract, so the manager's view of the company forms early.
At renewal, the manager compares monthly reports, the number of complaints and how quickly each one was closed. A general manager who can show that every building was walked, every request logged and every missed task fixed gives the account owner a clear story to take to the client.
That is why the oversight app matters to the sale as well as to operations. The record that helps the general manager assign crews can also give a facility manager proof of service at renewal time.
Before design starts, the company provides the building list with floor plans, the contracted task list for each site and the schedule each crew follows. Photos of janitor closets and supply rooms help us describe the work accurately, since storage layout shapes how crews restock.
Access needs care. Supervisors see the buildings they run, and the general manager sees the whole portfolio. Crew members see tonight's task list and nothing about pricing. Building access codes and alarm instructions stay on the site record, and each one has a named owner who can change it.
Some clients also require background checks, sign-in logs or key control. Confirm those requirements in each contract before building, since they affect how crew profiles and building records are stored.
Each building shows its routine tasks, special requests and overdue items for the shift.
Supervisors confirm each area with a tick, plus a photo where the standard calls for one.
Tasks not completed by their set time rise to the top of the general manager's list.
Client requests arrive once, get assigned and show their status until the client accepts the fix.
Each crew sees its buildings for the shift, and the general manager can move work between crews in one change.
A summary for each client lists completed tasks, closed requests and average closing time.
The biggest mistake is building a checklist app that looks finished in the office but fails in a dark lobby at midnight. Crew leads will go back to paper if logging a restroom check takes three taps. Test each task flow in a real building before the design is locked.
Another is making the client view too complicated. A facility manager who only needs open issues and recent completions does not need a dashboard full of charts. Keep the first client view to a short status list with photos.
Avoid letting the app replace supervisor judgment. A tick box says the lobby was done, but it does not show a scuff on the glass. Prompt for a photo on items where judgment matters, and leave the inspection itself to a person.
Cost follows the number of user roles, the number of buildings the app holds and any connection to payroll or invoicing. A manager view across a few sites is much smaller than a portfolio tool for dozens of properties. The written scope lists the roles and screens behind each price.
Timeline depends on the task lists. A contract with clear, numbered tasks per building moves quickly, while a contract written as paragraphs needs translating into checklists first. Supply that translation before the build begins, not during it.
Scope stays honest when the first release is split from the wish list. Anything not needed for the nightly shift or the client status view goes onto a numbered list for later, each with its own estimate.
Begin with the supervisors, since they set the tone for the crews. Walk one building with each supervisor and have them mark up the task list until it matches the real night. A list that matches the contract on paper but not the floor will be ignored.
Crews need a short training session on their own phones, followed by a supervisor check on the first few shifts. Retire the binder for each building only after the crew has logged two full shifts with no gaps.
Clients receive a simple link showing completed tasks and open requests for their buildings, with no login. Post-launch support then adjusts the status page and reminder timing once the first renewal review has passed.
Yes, if supervisors actually log the walk. Overdue alerts appear during the shift, not the next morning, so you can send a crew back while the client is still in the building. The app is only as good as the nightly sign-off habit behind it.
They can, once they exist as numbered tasks for each building. We would help turn paragraph-style scope into checklists, then check them with the supervisors before the crews see them.
They sit on the building record, visible only to the supervisor on that site and to managers. Changes are logged with the name of whoever made them, and exports leave them out. Confirm your client's own requirements in writing before the design is set.
Our starting price for a mobile app is $4,500. The total depends on how many buildings the app holds, the number of roles and whether it connects to payroll or invoicing. The written scope from the free call sets out each choice.
Post-launch support covers fixes, operating system updates and changes to task lists when a client adds a service. We would review the overdue alerts with you each month so the thresholds reflect how crews actually work.
Book a free scoping call and bring a sample task list. We will show, building by building, what the app would display and what is still behind.