House Cleaning Schedule Planner

Introduction to workload-based cleaning schedules for a home

Most cleaning schedules on the internet are lists of chores with folk intervals attached: vacuum weekly, mop fortnightly, change the sheets on Sunday. They fail for a boring reason. They tell you what to do and how often, but never how many minutes the plan actually costs, so there is no way to know whether the week you have drawn up fits inside the evenings you have. This planner is built the other way round. It starts from measured task times, multiplies them by the frequencies you choose, adds them into a total weekly workload, and only then tries to fit that workload into the cleaning sessions you say you can realistically run.

The task times are not invented. They come from cleaning production rates published by ISSA, the worldwide cleaning industry association, whose Cleaning Times reference is the standard benchmark that contract cleaners use to bid work and to staff buildings. A production rate is simply how much area one person services in an hour for one specific task with one specific tool: 2,239 square feet per hour for a 12-inch upright vacuum on carpet, 4,545 square feet per hour for damp mopping with a 16-ounce mop head and a double bucket. Those numbers are measured with stopwatches on real floors. They transfer to a house far better than a guess, because a vacuum head does not know whether the carpet it is crossing is in an office or a living room.

What ISSA does not publish, and what nobody credible publishes, is how often a home should be cleaned. That is a preference, a health judgement, and a household negotiation rolled together. CDC advises cleaning high-touch surfaces regularly and after you have visitors, and states that in most situations cleaning regularly is enough to prevent the spread of germs, but it deliberately sets no interval for vacuuming, dusting, mopping or bedding. This planner therefore treats every frequency as a stated assumption that you own and can edit, and labels it as such. The arithmetic downstream of that assumption is rigorous; the assumption itself is yours.

How to use the planner without feeding it garbage

Start with the geometry. Home floor area is the interior area you actually maintain, not the figure on the deed: leave out the garage, the unfinished basement and any room you clean twice a year. Set the unit selector first, because it governs both the home area and the kitchen worktop area, and the planner converts everything to square feet internally at 10.7639104 square feet per square metre. Carpeted share splits that area between the vacuum task and the mop task; at 100 percent the mop task disappears from the plan entirely, and at 0 percent the vacuum task does. Nothing is double-counted, because the two floor tasks partition one area rather than each claiming all of it.

Bathroom fixtures means countable fixtures, not rooms: a bathroom with a toilet, a basin and a shower is three fixtures. ISSA prices restroom service per fixture rather than per square foot because that is what the work actually scales with, and the planner follows that convention. Beds is the number of beds whose linen you change. Kitchen worktop area is the wipeable run of counter, which is usually a much smaller number than people expect; 25 to 40 square feet is typical for a domestic kitchen.

Then set your capacity honestly. Sessions per week is how many times you sit down to clean, and minutes per session is how long a session lasts before you stop. These two numbers are what make the output falsifiable: if the plan does not fit inside them, the planner tells you in plain language instead of quietly rounding the problem away. The disinfectant contact time field exists because EPA-registered disinfectant labels specify a dwell during which the surface must stay visibly wet; if you stand and wait for it, that is real time, so enter it, and if you move on to another task while it dwells, enter zero.

Finally, the frequency table. Press Suggest frequencies to fill it from your occupant and pet counts, then override anything you disagree with. Each row has its own unit, so you can mix per-week and per-month cadences freely: the planner normalises everything to times per week before it adds a single minute.

The ISSA production-rate formula behind every task time

ISSA's guidance How to Calculate Cleaning Times gives three methods, and this planner uses two of them. For any task measured by area, the cleaning time in minutes is the area to be cleaned divided by the production rate in square feet per hour, multiplied by 60:

ISSA's own worked example is mopping 1,000 square feet with a 14-inch flat mop and a dual-chamber bucket at 5,355 square feet per hour, which gives 1,000 ÷ 5,355 × 60 = 11.2 minutes. For tasks that scale with fittings rather than floor, ISSA uses the fixture method instead, where the time is the number of fixtures multiplied by the minutes allowed per fixture:

The dwell term is the EPA contact time. If the area was entered in square metres it is converted before anything else happens, using the exact international definition of the foot:

Here are the published rates the planner uses, taken from the ISSA 540 Cleaning Times schedule of production rates. Each row shows the rate exactly as ISSA prints it, together with the basis area or fixture count that the printed minutes refer to, so you can check the arithmetic yourself.

The last row is the only one that is not fully sourced. ISSA publishes 5.00 minutes to strip a bed but does not publish a make-up time, so the planner doubles it and says so here rather than presenting an invented figure as a standard.

Turning task times into a weekly workload

A task time on its own is not a schedule. What matters is the time multiplied by how often the task happens, and for that every frequency has to be expressed in the same unit. The planner normalises everything to times per week. A per-month frequency is divided by the average number of weeks in a Gregorian month, which follows from the 365.2425-day mean year:

Getting this conversion wrong is the classic failure mode of chore planners: a task set to twice a month is not half a week's worth of work, it is 0.46 times per week, and mixing the two units without normalising inflates a monthly task by about nine percent. Once every frequency is in the same unit, each task contributes a weekly load, and the household's total weekly load is the sum over all tasks:

Against that sits your capacity. If you clean s times a week for d minutes each time, the weekly capacity and the utilisation of that capacity are:

Utilisation is the single most useful number the planner produces. A schedule at 40 percent utilisation has slack for the odd spill and the odd skipped week. A schedule at 95 percent has none, and will collapse the first time somebody is ill. A schedule above 100 percent is not a schedule at all; it is a wish, and the planner refuses to present it as anything else.

How the four-week rotation is packed and reconciled

Days are discrete, so the planner works on a four-week cycle containing S = 4s sessions. Each task gets a whole number of occurrences in that cycle, rounded from its weekly frequency, and never fewer than one if the task is switched on at all:

Those occurrences are then spread across the sessions as evenly as the arithmetic allows. Every session receives the floor of n_i divided by S occurrences of task i, and the remainder is distributed at evenly spaced session indices. Each task is given a phase offset chosen to minimise the busiest session, so the heavy jobs do not all pile onto the same evening. That is a balancing heuristic rather than an optimal bin-packing, and the planner says so, but it reliably beats the alternative of starting every task on day one.

The load-bearing property of the rotation is that it reconciles. If c_ji is the number of occurrences of task i placed in session j, then the minutes scattered across the calendar must add back up to the cycle workload exactly:

The planner computes both sides and prints the check with the result. It is there because scheduling code is exactly where work quietly disappears: a task gets dropped when a session is full, or an occurrence gets counted twice when a frequency rounds up, and the summary total no longer describes the calendar underneath it. If the two sides ever disagree by more than a rounding whisker, the page tells you rather than showing you a plan it cannot justify.

A worked example: 1,400 sq ft, two bathrooms and two cleaning evenings

Take a 1,400 square-foot home that is 55 percent carpeted, so 770 square feet of carpet and 630 square feet of hard floor. It has two bathrooms with six fixtures between them, three beds, and about 30 square feet of kitchen worktop. The household uses a disinfectant with a one-minute contact time and stands and waits for it. Two people clean, twice a week, for 90 minutes a session.

Applying the ISSA rates gives the per-occurrence times: vacuuming is 770 ÷ 2,239 × 60 = 20.6 minutes; damp-mopping is 630 ÷ 4,545 × 60 = 8.3 minutes; dusting the whole 1,400 square feet is 1,400 ÷ 5,000 × 60 = 16.8 minutes; the kitchen worktops are 30 ÷ 3,125 × 60 = 0.6 minutes plus the 1-minute dwell, so 1.6 minutes; the bathrooms are 6 × 3.0 = 18 minutes plus 1 minute of dwell, so 19 minutes; and the beds are 3 × 10 = 30 minutes.

Now the frequencies: vacuum twice a week, mop weekly, dust twice a month, wipe worktops daily, bathrooms weekly, linen weekly. Over the four-week cycle that is 8, 4, 2, 28, 4 and 4 occurrences respectively — note that dusting twice a month becomes 0.46 per week and therefore 2 occurrences in the cycle, not 4. Multiplying out gives 165.1, 33.3, 33.6, 44.1, 76.0 and 120.0 minutes, for a cycle workload of 472.1 minutes, or about 118 minutes a week — one hour and 58 minutes.

Capacity is 2 sessions × 90 minutes × 4 weeks = 720 minutes, so utilisation is 472.1 ÷ 720 = 66 percent. The plan fits, with real slack. The eight sessions average 59 minutes each, and the rotation puts the 30-minute bed change and the 20-minute vacuum on different evenings. Change one thing — drop to a single 60-minute session a week — and capacity falls to 240 minutes per cycle against the same 472.1 minutes of work. The planner then reports a shortfall of 232 minutes per cycle, roughly 58 minutes a week, and names the sessions that overflow instead of pretending the calendar absorbed it.

Reading the utilisation figure and the overload warning

Treat utilisation as a design target rather than a score. Under about 60 percent, the plan is robust: you can miss a session and catch up without a backlog. Between 60 and 85 percent, the plan works but has little tolerance, and it is worth checking that the longest single occurrence still fits inside one session — a 45-minute bathroom deep-clean cannot be squeezed into a 30-minute slot no matter what the weekly totals say, which is why the planner flags that case separately. Above 85 percent you are effectively running at capacity, and above 100 percent the honest options are to lengthen the sessions, add a session, stretch a frequency, or hand a task to somebody else.

The per-task breakdown is where you find the lever, and it is rarely the task you expect. In the worked example the largest line is vacuuming at 165 minutes per cycle, but only because it runs eight times; a single pass costs 20.6 minutes. Changing bed linen runs four times and still costs 120 minutes, because one occurrence is 30 minutes — the most expensive single occurrence in the plan. The obvious win is therefore not always the big one: switching the daily worktop wipe off entirely saves 44 minutes a cycle, while stretching bed linen from weekly to every ten days saves 30. Reading the minutes-per-occurrence column next to the minutes-per-week column turns an argument about who is doing their share into an arithmetic problem with an answer.

Assumptions and limitations of a production-rate cleaning schedule

The most important limitation is the one stated at the top: the frequencies are assumptions, not standards. No public health body publishes an interval for vacuuming a living room. CDC's household guidance is qualitative — clean high-touch surfaces regularly and after visitors, and disinfect mainly when somebody is sick — and the one hard frequency in the neighbourhood, the FDA Food Code requirement that food-contact surfaces used with time and temperature control for safety food be cleaned at least every four hours, governs food businesses, not kitchens at home. It is quoted on this page as a reference point for how seriously regulators treat food-contact surfaces, not as a rule you are breaking.

The second limitation is that ISSA production rates are measured in commercial buildings by trained cleaners with commercial equipment. A home has more furniture per square foot, more cords, more obstacles and more places a vacuum has to be lifted over, and a domestic vacuum is usually narrower and slower than the 12-inch upright the rate assumes. Expect real times to run longer than the model, particularly for vacuuming and dusting in cluttered rooms; a useful correction is to time yourself once on a single room and scale. The rates also assume routine maintenance cleaning. Deep cleans, move-out cleans, post-renovation dust, mould remediation and anything involving a machine are outside their scope entirely.

Third, the planner deliberately makes occupants and pets affect only the suggested frequencies, not the task times or the model itself. The suggestion rule — add 15 percent per occupant beyond two and 25 percent per pet — is a stated assumption with no published basis, offered as a starting point and nothing more. Nothing downstream depends on it once you have edited the frequency table. Finally, the rotation balances load, not preference: it does not know that you would rather not mop on a Monday, that some tasks are pleasant to pair, or that laundry has to start before you can strip the beds. Use it to find out whether the work fits, then rearrange the calendar to taste.

Sources and how each number was checked