Porter and janitorial work is easy to under-deliver on, because it happens when nobody is watching and, done well, it is invisible. Nobody notices a clean entrance. A skipped visit here and a rushed loop there add up quietly until the board is asking what exactly it has been paying for. So ask for four things on every visit: a completed checklist, dated photos, a note on anything the team found, and the time in and out. Write them into the job description before you sign, and read them once a month.
The answer is proof of work: an agreed way for the company to show what it did and when. It protects both sides, defending a good company against an unfair complaint and catching a slipping one early. Here is how to set it up without becoming a micromanager.
Why "trust me, I was there" is not enough
Wanting proof is ordinary practice in this trade. Recurring cleaning is hard to check after the fact, because the evidence disappears. An emptied trash can looks the same as one that was never full. Without a record, every dispute is one person's word against another's, and the board has nothing to show a resident who asks what the porter line pays for. Proof of work turns a subjective argument into a matter of record.
A professional cleaning company will welcome it, because the record is also theirs. When a resident says "the porter never comes," a photo log showing every visit settles it in the company's favor as often as the board's.
What good proof of work looks like
A few simple habits cover it. No cameras, no GPS trackers:
- A completed checklist per visit. The company checks off the scoped tasks each visit. Trash emptied, stations restocked, restrooms cleaned, litter cleared. Tied to your written scope, that list is the backbone of accountability.
- Dated, time-stamped photos of the same key areas each visit. The entrance, the pool deck, the mail center, and a few dog stations. A handful of consistent shots tells the story fast.
- Before-and-after photos for anything one-off: event cleanups, deep cleans, storm debris.
- An issue log. Part of a porter's value is spotting problems. A burned-out light, graffiti, a broken gate. A running log of what they reported shows the service doing more than cleaning.
- A simple visit record. Date, time in, time out, and who was on site. Nothing elaborate, just a consistent trail.
The key word is consistent. Proof of work only helps if it happens every visit, not just when there is a complaint.
A photo log only works if it is consistent. The same key areas get photographed every visit, not just when somebody complains.
Build it into the scope, not as an afterthought
The mistake boards make is asking for documentation only after a problem appears. By then it feels accusatory, and the company has no habit of producing it. Make proof of work part of the arrangement from day one:
- Put the documentation expectation in the scope of work. State that each visit includes a completed checklist and photos of named key areas.
- Agree on the format and where it lives. A shared folder, an app, or a dashboard. Somewhere the board or the manager can read it without chasing anyone.
- Set a review date each month. A board member or manager reviews the records monthly against the scope. This is where slippage gets caught early.
- Do a periodic walk-through. A quarterly in-person walk against the scope validates that the records match reality.
Set up this way, proof of work is simply how the service runs, and by the time anybody is unhappy the record is already sitting there to be read.
Reading the record: what to look for
When you review the documentation, you are watching for patterns, not nitpicking a single dusty ledge:
- Missed or short visits. Gaps in the log, or times in and times out that do not add up to the scoped work.
- Tasks left unchecked. If "clean restrooms" is blank three visits running, that is a conversation about the scope.
- Photos that never change. The same debris in the same corner across visits means nobody is touching it.
- Reported issues that never get fixed. The porter did their job by flagging it. Someone else is dropping the follow-up.
The goal is to catch drift while it is small. A company that knows the record is read every month rarely drifts in the first place.
Keep it a record, not a leash
There is a balance here. The record exists so you can check at a sensible interval. Read it monthly, walk the property quarterly, and otherwise let a performing team get on with the work. Save the close scrutiny for when the record shows a problem. A good company will walk away from minute-by-minute justification, and it will be right to.
Where the record lives
Proof of work only earns its keep if it has one home the board can open. A folder of emailed PDFs somebody has to go hunting for is where documentation goes to be forgotten.
Proof of work is a contract term before it is a habit, so write it into the scope you post. Local janitorial and porter companies propose on that scope, with the documentation expectation already written into it, so nobody has to negotiate it later. Your board reads the proposals side by side and picks one. The contract is yours and that company's. The completed checklist, the dated photos, the issue log, and the times in and out are recorded as each visit is finished, and the company's own invoice arrives in the same view. A company gets to propose once three documents are current: general liability, workers' compensation, and its trade's own credential. A person here verifies each certificate against the limits your community set, and a lapse closes proposing until it is current. Agree the proof of work up front, read it once a month, and the porter line in your budget always has an answer attached.