Every routine has a sign-off. Initials on the restroom sheet every hour, green ticks in a checklist app, a "done" in the team chat. And almost every manager has stood in front of a fully signed sheet and an empty soap dispenser at the same time.
The sheet isn't exactly lying. It records that someone made a mark, which is all it was ever able to record. Knowing the work was done takes a different kind of record: one that is easier to produce by doing the work than by skipping it.
Key takeaways
- A tick or a set of initials proves that someone made a mark, not that the work happened. Good proof is a by-product of doing the work: a photo of the result, a reading, a count.
- Strong proof of task completion answers four questions: who did it (a named person), when (a time the system records), where (the place) and what (the result).
- Match the proof to the risk. Photos and readings for the few tasks where a miss is costly, a simple named tick for the rest.
- Check a small random sample, look for missing records as hard as for bad ones, and treat a miss as information about the routine before treating it as a problem with a person.
This guide is about recurring work: cleaning rounds, opening and closing, equipment checks, inspections, temperature logs. If you are building one of these routines from scratch, start with our office cleaning checklist or opening and closing checklist.
Why sign-off sheets and "done" ticks drift
Paper sheets and checkbox apps fail in the same predictable ways:
- Filled in later. The hourly restroom row gets filled in at 5 p.m. for the whole afternoon. In safety and maintenance work this has a name, pencil whipping: completing a checklist without doing the checks.
- Batched. Six items ticked within the same minute were not inspected one by one.
- Copied. Everyone signs because the row above is signed. A sheet where every day looks identical is less believable than one with the occasional "not done, no supplies".
- Anonymous. Initials nobody can read, a shared login, a team name instead of a person.
- Unread. If nobody looks at the sheet until something goes wrong, there is no reason to fill it in carefully.
- Silent when missing. A day with no record looks like a blank row, and blank rows don't raise alarms. The worst failure, a routine that never started, leaves the least trace.
None of this requires bad people. It is what happens when the record is cheaper than the work, and nobody reads it.
What counts as good proof of task completion
Good proof has four parts. The strong version of each is rarely more work for the person doing the task.
| Weak | Strong | |
|---|---|---|
| Who | Initials, a shared account, "night team" | A named person, signed in under their own account |
| When | A time written by hand | A time recorded by the system on submission, and stamped on any photo |
| Where | "Building B" typed in a box | Location stamped on the photo, or a form opened from a code posted at the spot |
| What | A tick | A photo of the result, a reading, a count, or a note of what was wrong |
The kinds of evidence, roughly from strongest to lightest:
- Readings and counts. A cooler temperature, a meter reading, a cash count. A number can be wrong in ways you can see: out of range, identical every day, impossible. "OK" can't.
- Photos of the result. Taken after the work, from the same angle each time, so a month of them can be compared quickly.
- A named person and a system time. Not proof of the work by itself, but it turns "someone" into a person you can ask.
- A signature. It records that a specific person stated the work was done, which matters when the record is questioned later.
- A second person's confirmation. The opener confirming the close, a supervisor confirming a repair. Now two people would both have to be wrong.
Know the limits, too:
- A photo's file date is not proof. Phone clocks can be wrong, files can be edited, and last week's picture can be uploaded today. Proof is stronger when the app takes the photo and stamps the date, time and place at that moment.
- Phone location is approximate, especially indoors. Use it to confirm the site, not the exact room.
- A code on the wall proves less than it seems. A QR code at the location opens the right form in the right place, but a photo of the code works from anywhere. Pair it with a photo of the result.
- Tell people what you record. If photos carry location, say so and say why, and require it only where the place is the point.
Match the proof to the risk
Asking for maximum evidence on every task makes routines slow, and people start photographing instead of working. Sort recurring tasks by what a miss would cost:
| Cost of a miss | Examples | Proof to ask for |
|---|---|---|
| Low | Restock printer paper, erase whiteboards | A named tick |
| Medium | Restroom rounds, meeting room resets, opening the store | A named tick and a photo of the result |
| High | Locking up and cash, food temperatures, safety, equipment and vehicle checks | Readings or counts, photos, a named person, and a second person's check on a sample |
Some checks have a frequency set by regulation. Under OSHA's portable fire extinguisher standard, extinguishers must be visually inspected monthly, and the employer must record the annual maintenance date and keep that record for one year after the last entry or the life of the shell, whichever is less (29 CFR 1910.157(e)). The standard asks for a record of the annual maintenance, not of each monthly look, but a record is the only way to show the monthly checks happened. OSHA's guidance on hazard identification says the same of inspections in general: document them so you can later verify that hazardous conditions were corrected, and photograph problem areas. This is general information, not legal advice.
Sampling and spot checks
You don't need to verify every task. You need to know whether the records can be trusted, and a small random sample answers that.
- Spot check in person. A few times a week, someone other than the doer looks at the result soon after the record says it was done. Vary days, times and areas.
- Use the same standard. Check against the written "done when", not personal taste. If checker and doer disagree on what "clean" means, rewrite the standard, as in our guide on how to document a business process.
- Review a handful of records. Open a few completed checklists each week and look for photos of the wrong place, the same photo twice, readings that never move, six tasks submitted in one minute.
- Track agreement. How often did the spot check agree with the record this month? High agreement means you can check less often. A gap means the records aren't telling you what you think.
- Announce the program, not the visits. The point is accurate records, not a trap.
Look for what is missing
Most reviews read the records that exist. The bigger risk is the record that doesn't: the cleaning round that never started, the Sunday close nobody logged, the monthly check that slid into next month.
To see absences, you need a list of what was supposed to happen: for each routine, when it is due (every weekday by 9:00 a.m., every night at close, the first Monday of the month). Compare that with what was recorded, and each expected occurrence lands in one of four buckets:
- Done on time
- Done late
- Still open: started, not finished
- Missed: never done
A weekly look at those four counts per routine tells you more than reading every completed checklist. Often late usually means a timing problem; often missed may mean no owner on certain days.
Turn misses into fixes, not blame
When a spot check fails or a record is missing, ask "what made this hard to do?" before "who didn't do it?". Repeated misses usually point at the routine:
| Pattern | Likely cause | Fix |
|---|---|---|
| Missed on the same day every week | Nobody owns that day, or the shift is short | Name an owner for that day, or move the task |
| Late every afternoon | The deadline lands in the busiest hour | Move the time, or split the task |
| Same item fails spot checks | The standard is unclear, or impossible in the time | Rewrite the "done when", or allow more time |
| Ticked but not done | The list is too long and nobody reads it | Cut the list, review records weekly |
| "Not done, no supplies" | Reordering depends on memory | Add a supply count with a reorder point |
Once the routine is fixed, a miss that keeps repeating with the same person is a management conversation, and good records make it a fair one: specific dates and items, no guesswork.
Be careful about what you reward. OSHA's guidance on worker participation says workers should not experience retaliation for raising safety and health concerns, and that incentive programs should not discourage injury and illness reporting. The same logic applies to routine work: if writing "couldn't do it, the cooler was broken" gets someone in trouble, the next record will be a tick. An honest "not done" with a reason is worth more than a perfect sheet, because you can fix it.
Frequently asked questions
How do you verify that a task was completed?
Ask for evidence that comes from doing the work (a photo of the result, a reading, a count), recorded under a named person with a time the system sets. Then spot check a small random sample in person, and look for routines with no record at all.
Are photos enough proof of work?
Photos are strong proof when taken on the spot, stamped by the device with the date, time and location at that moment, and showing the result from a consistent angle. A picture uploaded from the camera roll proves much less, because it could have been taken at another time or place.
What is pencil whipping?
Filling in a checklist or inspection form without actually doing the checks, usually by ticking every box at once or copying the previous entry. It is a symptom of lists that are too long, records nobody reads, or pressure to show a perfect sheet.
How do you hold employees accountable for checklists?
Give each task one named owner and a deadline, look at completion every day, follow up on missing records quickly and spot check the results. When misses repeat, fix the routine first.
Running it in Easyflow
In Easyflow, a recurring routine is a short, linear process. The step that does the work can carry a Checklist field, number fields for readings and counts, a signature and a Photo evidence field. On a phone, each photo is stamped with the date, the time and, with Require location on, the GPS position, and a field that requires location only offers the camera, not the photo gallery. The request's timeline shows who completed each step and when, and a follow-up step with a Run condition only runs when someone reports a problem, so a miss becomes a step with an owner.
Schedules start each routine daily, weekly or monthly, steps can go to the people on duty with Take turns or to the Least busy person, and deadlines, reminders and escalation handle the ones running late. Each schedule's History shows, day by day, whether the routine was Done on time, Done late, Still open or Missed: the missing-record check above, without a spreadsheet. Any process can also start from a printed QR code where the work happens, and people outside the company, like a cleaning contractor, can fill public forms and guest steps without an account.
The gallery has routines ready to adapt: Restroom check, Daily vehicle check, Fire extinguisher and first-aid check, Food temperature log and Safety inspection.