Cleaning Schedule & Audit Log

What this tool does

CM8-97 is a working cleaning log. You record each clean as it is done, each periodic audit with its score, and each issue reported between cleans; the tool shows which tasks are overdue, how the audit scores are trending against your target, which areas fell below the target on their most recent audit, and prints a report you can hand to a landlord, a client, a franchisor or an inspector.

Everything runs inside this single file. There is no account, no upload and no network request of any kind, so your premises details, contractor names and audit findings never leave the computer you are using.

What one record is

One row is one event on one date: a routine clean done, a deep clean done, an audit carried out, or an issue reported. It is not a task definition — the schedule emerges from the log, because each record can carry a next due date that says when that task should happen again.

Name areas consistently. The per-area summary and the audit chart group on the area name exactly as typed, so "Ground floor washrooms" and "GF washroom" become two different areas. Pick one form of each name and keep to it; the area category then lets you roll areas up into washrooms, food areas, offices and so on.

The four record types

• Routine clean — the scheduled clean at its normal frequency.
• Deep clean — the periodic full clean: carpets extracted, kitchens degreased, high-level surfaces done. Logging these separately matters because they are the ones that slip.
• Audit — somebody checked the standard of cleaning against a checklist and gave it a score out of 100. Only audit rows carry scores.
• Issue reported — a problem noticed between cleans: a spill, a blocked drain, a stained carpet. An issue stays open until it is signed off.

The tool refuses the two entries that would quietly corrupt the figures: a score on a row that is not an audit (it would silently change the average), and an audit with no score (it would silently vanish from it).

Frequency and next due

The frequency field records how often the task is meant to happen; the next due date records when it is actually next expected. The tool deliberately does not generate the next-due date from the frequency, because real schedules bend — a quarterly deep clean booked around a shutdown, a daily washroom check that skips a closure day. Enter the date the task is genuinely next due.

A record whose next-due date has passed is overdue and shows red. One falling within the warning window from the Settings tab (2 days unless you change it) shows amber as due soon. The "Overdue and upcoming" table on the Reports tab lists every record carrying a next-due date, soonest first, so the morning check is one glance.

If a newer record already carries the forward date — today's washroom clean says the next one is tomorrow — leave older rows' next-due blank rather than letting a superseded date sit in the log counting as overdue.

Audits and scoring

An audit is a check of the result, done by someone other than whoever cleaned if you can manage it. Walk the area with a fixed checklist — floors, touch points, sanitary fittings, consumables, high and low surfaces — and score against the same checklist every time. The number only means anything if the marking scheme stays constant: an 80 scored generously and an 80 scored hard are not the same 80, and a change of auditor can move the trend more than a change of cleaner.

Set your target on the Settings tab (85 unless you change it). Each audit row shows whether it met the target, and anything more than 10 points below it is flagged red rather than amber. Record what you found in Issues found even when the score is good — "extract grille still dusty" on two consecutive audits is exactly the evidence you need for the contractor conversation.

How the averages are worked out

Every average in this tool is taken over audit rows that carry a score — never over cleans, never over issue reports, and never over audits accidentally left unscored (the entry form prevents those).

The headline tile states the count it averaged over, and the monthly trend chart states how many audits sit behind each point. Read those counts before reading the line: a month with one audit is one audit, not a trend, and a "falling" average that is really one bad washroom audit in an otherwise quiet month should be read as exactly that. Where there are no scored audits at all, the tool shows "—" rather than inventing a number.

Filters apply to every figure. Filter the log to washrooms and the average, the trend and the target comparison are all washrooms only — the scope line on the printed report says so.

Areas and the latest-audit rule

The "Latest audit score by area" chart and the "Areas below target" tile use one deliberate rule:

Only the most recent audit of each area counts — earlier audits of the same area are not averaged in. This is intentional: an area that scored 60 in spring and 90 last week is currently at 90, and averaging in the old failure would hide the improvement, just as averaging a recent failure with old successes would hide the decline. The area's history is still there in the register and in the monthly trend; the per-area view is a statement of current standing.

The per-area summary table pulls the threads together for each area: how many records it has, the date of its last clean, its latest audit score against target, and the earliest next-due date it is carrying — with an overdue marker where that date has passed.

Issues and sign-off

The sign-off box means someone checked the work or the record — a supervisor countersigning a clean, or confirming an issue was dealt with. On issue rows it does the heavy lifting: an issue is open until it is signed off, and the Open issues tile counts exactly those rows. Ticking the box on an issue is a statement that the problem was fixed, so do not tick it when the issue is merely acknowledged.

Cleans and audits can be signed off too, and the "Signed off" tile shows how much of the log carries a counter-signature — useful where a contract requires supervised sign-off, and a quiet indicator of record quality where it does not.

Reading the charts

Records by type shows the shape of the log. All cleans and no audits means effort is recorded but the standard is never checked; all audits and no cleans means the schedule exists only on paper. Average audit score by month is the trend against your target line — read the audit counts in the labels before reading the slope. Records by area category shows where the effort is going; the categories that can hurt you — washrooms, food areas — should not be the quiet bars. Latest audit score by area is current standing, one bar per area, coloured against the target.

Printing and sharing

Print Report produces a report from whatever the current filter shows: header, headline tiles, the four charts, the overdue list, the per-area summary, the full register and your closing notes. Print to PDF to circulate it. The scope line under the title states the filter in force — clear the filters before issuing anything described as covering the whole premises or the whole period.

Saving your work

Records, settings and the report header are written to this browser's local storage as you type, and the toolbar shows the time of the last save. That storage belongs to one browser on one computer: another browser, a private window, a second machine or a clean-up tool that clears site data will not have it.

Treat Export .json as the real save — one file containing everything, which Import .json restores anywhere. Export CSV gives you the register for spreadsheet work and includes every filtered record, not only those drawn on screen. Reset asks twice, then erases everything this tool has stored. There is no undo.

Accuracy & disclaimer

This tool records what you enter and calculates from it. It cannot verify that a clean happened, judge whether an audit was scored fairly, or know that an area name typed two ways is the same room. The audit score measures performance against your own checklist and your own marking scheme — it is not a certification, and a high score does not by itself demonstrate compliance with anything.

What must be cleaned, how often, to what standard and with what records differs by country and by industry — food premises, healthcare settings and public buildings all carry their own regimes. This is an internal record-keeping and calculation aid, not hygiene advice and not a substitute for the inspections your sector requires.