Attain OS for cleaning companies

Every building knows its scope, and every visit leaves a record of what was done.

The weekly schedule, who covers which building, the area-by-area checklist, the before-and-after photos, the supply list and the notes for the client's monthly review stop being seven WhatsApp groups and one supervisor's memory. They go into one workspace that stays put when someone quits on Friday.

14 days free · No card needed · Cancel anytime

Cleaning Business Software: Recurring Schedules, Crews, Checklists and Site Records

Who this is for

What this looks like today

Commercial and residential cleaning companies, janitorial contractors and building-services firms running crews across offices, condominiums, clinics, retail spaces and homes — anywhere from one route to dozens of contracted sites.

It is Sunday evening and you are rebuilding next week's coverage in a WhatsApp group because two people gave notice and one is out sick. Monday at 7:10 a building manager sends a photo of a lobby floor and asks who was there Friday night, and the honest answer is that you would have to ask three people. The new hire starting Tuesday will learn the site from whoever happens to be on that shift, because the scope of work exists as a PDF attached to a contract in your email. Supplies for the clinic ran out on Thursday and somebody bought disinfectant at retail price. And the report the condominium expects on the first is still a blank document.

  • Coverage gets rebuilt by hand every week because somebody quit, somebody is sick and somebody swapped
  • A new hire starts on a site nobody has written down, so quality depends on who trained them that morning
  • The client complains about a lobby and you have no photo of how it was left, only your word against theirs
  • Supplies run out at the site, not in the storeroom, and the crew buys at retail price on the way
  • The monthly client summary is assembled the night before from chat messages and memory

What changes

Each contracted site gets a record that holds what makes it that site: the address, the access and alarm instructions and the scope of work in the client's custom fields, a checklist form built from that scope, and the assigned crew on its calendar events. A large contract can have a project of its own. Nothing about the building has to sit in one supervisor's head.

The schedule repeats instead of being rebuilt. Daily, weekly or monthly service is set once as a recurring calendar event per site, with the crew as attendees and a reminder, and everyone opens the shared calendar in a phone browser. When someone is out, you change the attendee, and the person covering opens the same checklist, the same access notes and the same photos of how the site should be left.

The record is built while the visit happens. The crew completes the site's checklist form and posts before-and-after photos to the feed, and each route stop saves when it was marked done and by whom. At the end of the month you can ask Atty to draft the client summary as a note from the feed, the routes and the tasks, then edit it, approve it and share it by link. Photos are not stamped with a time or address, and nothing tracks where the crew is.

Coverage you adjust instead of rebuild

Recurring events per site mean the normal week already exists. Your Sunday work becomes changing the two visits that moved, not retyping forty, and the people on an event get its reminders. Crews open the access notes and the checklist on a phone, so a supervisor stops spending the morning telling people where to go.

Supplies and redo visits stop leaking money

Crews add what a site is running low on to one shared list the office buys from, before the storeroom is empty, so you buy on your terms instead of at retail on a Thursday night. And a visit that closes with a completed checklist and photos is easier to stand behind than one that closes with a text message.

The photo is already there when the client asks

Crews post before-and-after photos to the feed during the visit, and each post shows who posted it and when. Completed checklists are saved as form submissions. When a building manager questions Friday night, you open Friday night in the feed. Supervisors inspect against the same written checklist the crew uses.

Take the next building without another supervisor

Cleaning companies scale on supervision. When each site's scope, access notes and checklist are written down, a new hire can work a site they have never seen, and a supervisor checks against a standard instead of re-explaining it. Each new contract is still set up by hand: there are no site templates to copy.

The apps that carry the work

Every one of these is built in and already connected to the others. Nothing here is an integration you have to buy or wire up.

Calendar

Recurring schedules per site

Set daily, weekly, every-two-weeks or monthly service once per building as a recurring calendar event, with the crew as attendees, the site address as the location and a reminder. Deep cleans and floor care sit on the same calendar as routine visits. Attendees are members of your workspace, and the calendar does not sync with Google or Outlook.

  • Nightly office cleaning and weekend deep-clean cycles
  • Periodic floor care and window work booked ahead
  • A visit reassigned by changing its attendees when someone calls out
Calendar
Forms

Area-by-area checklists and inspections

Turn the scope of work into a checklist form with checkboxes, ratings and notes, and the crew completes it on a phone from its link with no login. Supervisor inspections use a rating form built the same way, so the standard is written down. Submissions are saved in a table. Forms have no photo, file or signature field, so photos go to the feed.

  • Per-area checklists that match the contract's scope
  • Supervisor inspections scored with rating fields
  • Damage and incident reports that open a Customer Care case for each submission
Forms
Routes

Crews rotating across buildings

Build the day as ordered stops for each crew, so a team covering five sites knows the sequence, and open it as Google Maps directions. Each stop carries a name and a description for keys, parking and access notes, and saves when it was marked done and by whom. You set the order; Attain OS does not optimize it.

  • Multi-site day routes for residential and light-commercial crews
  • Supply drop-offs placed in the order you set
  • Supervisor inspection runs across this week's sites
Routes
The Feed

Before-and-after photos and visit records

The crew posts before-and-after photos and anything unusual to the project feed as they work, naming the site in the post. You get one chronological record you can filter by person and date and search by text, instead of images scattered across personal phones. Posts show who posted and when; the photos themselves carry no stamped time or address.

  • Before-and-after photos for every visit
  • Damage or maintenance issues posted with the photo that shows them
  • A visit history you can search months later when a contract comes up for review
The Feed
Team

High turnover without losing the site

The Team app keeps your people directory, roles and org chart, so everyone knows who supervises whom. Because the site's scope, checklist and access notes are already in the workspace, onboarding is adding someone as a member rather than a week of shadowing, and removing them is just as quick when they leave.

  • A new hire opens the site's checklist and access notes on day one
  • Roles and reporting lines in one directory
  • Access removed the day someone leaves
Team
Shopping List

Supplies and chemicals on one list

Crews add what a site is running low on from the phone to a shared list the office buys from, and the list updates for everyone in the workspace as items are added or checked off. A list can repeat weekly and be linked to a client. It is a shopping list, not stock control: it does not count what is in the storeroom.

  • Supply requests raised before the storeroom is empty
  • One weekly purchase list the office works from
  • Equipment needs flagged from the field
Shopping List
Sharing Hub

Sharing a record with the client

Share a note, a document or a case with a building manager as a read-only public link, without making them a user of your system, and turn the link off when you are done. A monthly summary that Atty drafted as a note and you approved can go out this way. The Sharing Hub shows a total view count per link; there is no client portal.

  • Monthly service summary shared as a note link
  • The scope of work or an incident case shared by link
  • Links turned off after a contract review
Sharing Hub
WhatsApp + Atty

Atty on WhatsApp for crews

Where your organization has WhatsApp enabled, a cleaner or team lead can send Atty a voice note, a text or a photo. A photo is saved to the project's documents and Atty offers to attach it to the task or case it belongs to, once someone approves. Atty answers your team, not your clients.

  • A problem at a site reported by voice note and drafted as a case for approval
  • Ask which stops are on today's route without opening the app
  • A photo from a site attached to the right case once approved
WhatsApp + Atty
Appointments

Walkthroughs booked online

Share a booking page for walkthroughs and residential visits. Prospects pick an open slot without an account, get a confirmation email and reminders a day and an hour before, and can cancel or reschedule from the emailed link. The booking blocks your calendar and adds the prospect to your customer records.

  • Walkthrough for a new commercial contract
  • Residential visit booked from the website
  • Prospect reschedules from the reminder email
Appointments
Working guide

Cleaning business software should hold each site's scope, its recurring visits, the checklist a cleaner completes and a record of what was done on each visit. A good test is whether a cleaner who has never worked a building can start a shift there and know what to do. Check separately whether you need quoting, invoicing or payroll, because a workspace for schedules and visit records does not replace those tools.

In practice

Coverage, a complaint and a new hire's first shift

  1. Sunday evening · next week

    Two cleaners give notice and one is out sick, so the supervisor rebuilds next week's coverage. Each building's recurring visits already exist as calendar events with a crew assigned. The supervisor changes the attendee on the affected visits, then checks which sites still have no one covering them.

    Calendar
  2. Monday · a question about a lobby

    A building manager asks who was on site Friday night and whether the lobby was finished. The supervisor opens that site's route stop, which shows who marked it done and when, then looks up the checklist submission for that visit. The answer comes from the record instead of three phone calls.

    Routes
  3. Tuesday · a new hire starts

    A new cleaner starts at a building nobody has explained to them. They open the site's checklist on their phone and look at the photos from the last visit in the feed, then follow the same steps as everyone else. Adding them as a member does not transfer the site's knowledge, so the scope and access notes have to be written down first.

    Forms
  4. Wednesday · supplies run low

    The clinic's disinfectant runs low mid-shift. The cleaner adds it to the shared shopping list from a phone, so the office buys it from the usual supplier rather than paying retail on the way. The list can repeat weekly and can be linked to the client.

    Shopping List
  5. Thursday · the supervisor inspects

    The supervisor inspects a site with the same rating form the crew uses, so the standard is written down. Each low rating gets a note about what was seen and a task for the next visit. The note describes the area, not the person who cleaned it.

    Tasks
  6. Friday · the monthly summary

    The supervisor writes the condominium board's monthly summary from the visit records and open tasks, and a second person reviews it before it leaves the office. The supervisor shares the approved note with the building manager as a read-only link, then turns the link off when the review is finished.

    Sharing Hub
Workflow map

How each visit is planned and recorded

JobAppWhat it does here
Recurring site scheduleCalendarSet each building's daily, weekly or monthly visits once as a recurring event, with the crew as attendees and the address as the location. When coverage changes, change the attendee, and the covering cleaner opens the same visit.
Area checklistsFormsTurn each site's scope into a checklist form with checkboxes, ratings and notes, completed on a phone from its link with no login. Submissions save to a table. Forms have no photo or signature field, so photos go to the feed.
Crew routesRoutesBuild a crew's day as ordered stops, with access notes for keys, parking and alarms in each stop's description. Open the route as Google Maps directions. Each stop saves when it was marked done and by whom, and you set the order.
Before-and-after photosThe FeedCrews post before-and-after photos to the project feed and name the site in the post. You can filter the feed by person and date and search it by text. Photos carry no stamped time or address, so the post's author and time are the record.
Supply listsShopping ListCrews add what a site is running low on to a shared list the office buys from. A list can repeat weekly and be linked to a client. It is a shopping list rather than stock control, so it does not count what is in the storeroom.
Client summariesSharing HubShare a note, document or case with a building manager as a read-only link, without making them a user. Turn the link off when you are done. There is no client portal, and the hub shows how many times each link was viewed.
Start here

Forms and guides for a cleaning crew

Policy acknowledgement form

Show that a new cleaner received the current site rules and had a chance to ask questions before working alone.

Training playbook

Write the stages and sign-offs for one cleaning role, so a trainer checks the same steps for every new hire.

Mistakes to avoid

Three gaps that show up on the complaint call

A scope that says clean the office

A scope that says clean the office cannot be checked. Split each building into areas, such as the lobby, restrooms and kitchen, and give each task a frequency. A cleaner can then mark an area done, and a supervisor can see which area was skipped.

Coverage kept in a supervisor's head

Coverage that lives in one person's memory fails on the day that person is sick. Put each recurring visit on the calendar with an assigned crew, and keep access and alarm notes in the site record. A replacement should not need a phone call to learn the building.

Photos as the only evidence

Before-and-after photos help, but the workspace does not stamp them with a time or address, and forms have no signature field. Pair each photo with the visit record, which names who posted it and when. Keep the claim you make to a client no bigger than what that record shows.

Working checklist

Setup for a building and close-out for a visit

Setting up a building

  • Write the scope as areas, each with its frequency.
  • Put access and alarm notes in the site record, not in a message.
  • Assign the crew to the recurring visit before the first shift.

Closing a visit

  • Complete the checklist before leaving the site.
  • Post before-and-after photos with the site named in the post.
  • Mark the route stop done and open any follow-up as a task.
What this agreement means

What a cleaning company settles first

  • Decide how each building's scope is split into areas and how often each area is cleaned.
  • Decide who covers a site when someone is out, and how the covering cleaner learns the building.
  • Keep quoting, invoicing, payroll and hours in the tools you already use.

This describes a coordination routine for cleaning crews. It does not cover chemical safety training, regulatory requirements or the terms of your client contracts.

Frequently asked questions

Is cleaning business software the same as quoting and invoicing software?

No. Quoting, invoicing and payroll are separate jobs. Software for a cleaning company should cover the visit schedule, the scope, the checklists and the record of each visit. Keep the money side in the tools you use today.

How do I keep a cleaning schedule when crews rotate?

Set each recurring visit once, with the crew as attendees, and change the attendee when coverage changes. Give each crew an ordered list of stops for the day, and keep access notes in the site record so a covering crew has them. The schedule then stays the same when the people do not.

Can a client check what the crew did?

A client can see a note, document or case you share as a read-only link, without an account. Records show who marked each route stop done and when, and checklist submissions are saved. That is a record of what your team entered, not a legal proof of cleaning.

Does Attain OS handle time clocks or payroll?

No. There is no time clock, no shift-scheduling tool, no payroll and no invoicing. Attain OS keeps the schedule of visits, the scope and the record of each visit, and hours and billing stay in your current tools.

Who Attain OS Is For — One Operating System for the Team You Actually Run

Attain OS BETA