The Round That Runs on Memory Is the Round That Loses Money
A window cleaning round with sixty residential clients runs on three things: knowing where to go, knowing what to clean when you get there, and knowing who owes you money. Most sole traders manage this across a combination of a paper notebook, a phone calendar, and memory. When the notebook gets wet, when the phone syncs badly, or when memory fails on the Velux at number 47 that the customer specifically doesn't want touched anymore—the system breaks down, and the customer notices before you do.
This Window Cleaning Schedule template in Memento Database is a round management system designed for exactly that operation: small, owner-operated, route-dependent, and payment-sensitive.
Clean Includes: The Scope Field That Prevents the Argument
The "Clean includes" field is the most operationally important entry on the record. Nine options—Front, Left side, Right side, Rear, Conservatory, Loft conversion, Velux x1, Velux x2, Dormer Window/s—define the agreed scope of service per property.
Every residential customer has a slightly different agreement. The terraced house on the main road only wants the front done because the back yard is inaccessible. The detached on the corner includes the conservatory at a price that was negotiated separately eighteen months ago. The customer in the new build has two Velux windows in the loft conversion that add three minutes to the visit and were the reason the agreed price went from £8 to £11.
Without the scope record, those agreements exist only in the cleaner's memory. With it, they're retrievable when a customer says "I didn't agree to have you do the conservatory" six months after the conversation that they've forgotten and you haven't.
Area Codes, Week Rotation, and How the Route Actually Works
The Area code field uses a twelve-slot week/rotation system—week 1a through week 4c—that maps clients to their position in the four-week cleaning cycle. All clients on week 2b get cleaned together on their week 2b day. This is standard round management: geographic clustering by rotation week to minimize drive time and maximize cleans per day.
Filtering the Memento database by Area code gives you the day's route. Adding a secondary sort by Address gives you the cleaning order. This is the working view for the operational day, and it requires zero additional planning beyond the filter that's already built into the template.
The four "Dates of cleans" fields capture the actual scheduled dates across the year for each rotation slot—pre-populated options for each week of the cycle from June through March. Checking the applicable date for a client marks their visit in the record without requiring a separate calendar entry.
The Owes Calculation and the Conversation It Prevents
The Owes field is a calculated field: Cost Today minus Money Collected. It is, in most cases, zero. When it isn't, that record is the customer who paid £8 for a £10 job last visit and still hasn't settled the £2. Over a sixty-client round, those small balances accumulate to meaningful numbers that are invisible without systematic tracking. The calculated field surfaces them automatically.
Agreed Price, Money Collected, and Cost Today together handle the common scenario where a customer pays irregularly, tips occasionally, or short-pays due to a disputed visit. The Agreement date and agreed price establish the baseline. Any deviation from that baseline is visible in the record without requiring the cleaner to remember which customers are running a tab and which paid in full last visit.
A round with a payment problem looks normal visit by visit. It only looks like a problem in aggregate—when you filter by clients with a nonzero Owes balance and find that eight of them are carrying balances over three visits.