Vendor Reporting Tools: What to Ask Before You Sign
Questions that show whether a vendor's reporting tools can prove the work was done, what to demand in monthly reports, and how to keep your own records.
Key takeaways
- Ask what vendor reporting tools a contractor uses for inspections, record-keeping and monthly reporting — then ask to see the last four weeks of records.
- Reporting tools are only useful to you if you can read the output: dated, per-area, with deficiencies and their closure.
- Verbal assurance that "the supervisor checks everything" is not a record. Ask for a sample report before award, not after the first complaint.
- Confirm in the contract who owns the inspection records and what happens to them when the contract ends.
- Keep your own inspection records regardless of what the vendor provides. The two sets together are what settle a dispute.
Why a vendor's reporting tools are your problem
They are your problem because the vendor's records are usually the only evidence that a task was performed, and you are the person who has to answer for the standard. When a tenant escalates a restroom complaint to the owner, "the contractor says it was done" is not an answer. A dated inspection with a photograph is.
This is not about preferring technology. A vendor with a disciplined paper system producing signed, dated, area-by-area inspection sheets can satisfy almost any requirement you set. What fails is the absence of records, or records that cannot be produced, read or trusted.
So the evaluation question is narrow: can this vendor show me, on demand, what was inspected, when, by whom, what was found, and what was done about it? The rest of their tooling is their business.
What four questions separate real vendor reporting tools from a spreadsheet?
Ask these before award, with evidence for each answer. A vendor who cannot answer them in one email has told you something about how they would handle your file.
| What to ask | Weak answer | Strong answer |
|---|---|---|
| How do supervisors record inspections? | "Paper forms, they stay in the van." | A named method, with records stored by site and date and retrievable on request |
| Can I see four weeks of records now? | "I'll dig some out." | Sent within a day, dated, area-specific, consistent across weeks |
| How does a deficiency get fixed? | "We tell the client." | Logged with a date, assigned to a person, re-inspected and closed |
| What proves a task was done on a given night? | "Our staff are reliable." | Timestamped records, photos per item, supervisor sign-off |
Judge the consistency of the samples, not their polish. Four weeks of immaculate scores with no deficiencies recorded anywhere usually means nobody is inspecting properly — real buildings produce real findings. A report showing three deficiencies, all closed with dates, is more credible than one showing nothing wrong for a month.
How do you check that inspection records are genuine?
Cross-check the record against the site's own logs and against what you can see. A four-week inspection sheet that reports every area perfect, in a building where you received six complaints in the same period, is not a record of the work — it is a record of a supervisor ticking boxes.
Three checks take about fifteen minutes each and are worth doing on every shortlisted vendor.
- Compare dates with access logs. If the inspection claims a night visit when the alarm was never disarmed, ask who inspected.
- Compare scope with the specification. Count how many areas and items appear in the sample report against the number of tasks in the contract. Ten lines for a 30-page specification is a summary, not an inspection.
- Compare findings with complaints. Deficiencies that never appear in the vendor's records but arrive as tenant complaints mean the inspection is not finding anything.
Ask whether the tool works offline. In a parking garage or basement mechanical room, a system that needs a live connection will not be used, and the crew reverts to paper you never see.
What should a monthly vendor report contain?
A monthly report should answer four questions on one page: what was inspected, what was found, what was fixed, and what is still open. A three-page narrative with no deficiency table is less useful than a one-page summary with dates.
Require these elements in writing, as a contract deliverable with a due date:
- Inspection coverage — inspections completed this month against those scheduled, by site and area.
- Scores or ratings — whatever scale the vendor uses, applied consistently, with the scale defined.
- Deficiencies raised, each with the date found, the location, the person assigned and the target date.
- Deficiencies closed, with the date of re-inspection. This is the column that tells you whether the system works.
- Open items carried forward, with an age in days. Anything older than the agreed closure window should be escalated automatically.
- Staffing exceptions — vacancies, new starters, agency cover and any night the site ran short.
A report with a closure column is a management tool. A report without one is a newsletter.
What if the vendor has no software at all?
That is acceptable, provided they produce a disciplined paper record and you can read it. Many competent contractors run signed checklists per area per night, filed by date, and can produce any week you ask for inside a day. The absence of an app is not the risk; the absence of a retrievable record is.
Set the same test for both. Ask for four weeks of records from two different sites, and check whether the format is the same at both, complete at both, and legible to someone who does not work there. If the answer is a shoebox, price the risk: your own inspection frequency has to rise to compensate.
If you want to raise the standard, ask for records in a defined format — a spreadsheet template works — as a contract deliverable with a monthly due date, which gives you comparability without dictating which product anyone buys.
Where do privacy and retention rules come in?
Inspection records often contain personal information: a photo with a tenant in the background, a note about a cleaner by name, a complaint from an identifiable employee. Under PIPEDA, organisations must limit what they collect to what the purpose requires, safeguard it, and retain it only as long as needed — the Office of the Privacy Commissioner's PIPEDA overview explains the principles in plain language.
In practice: photograph the area and the deficiency rather than people, keep records on the building file with controlled access rather than in personal inboxes, agree a retention period with your records team, and write into the contract what happens to the vendor's records at the end of the term — handover, format and deadline, with thirty days a workable window. Retention rules vary by province and site type, so set them in writing rather than assuming.
What tool do you use on your side?
Use your own inspection record, whatever the vendor supplies. The vendor's reports tell you what they believe happened; your inspections tell you what the building looks like when you walk it unannounced. You need both, and they should be comparable.
That is the role NeatScore plays. It is not a requirement you impose on a vendor, and no contractor needs to adopt it for your contract to work — it is the tool a property manager uses to inspect the service being paid for: area-specific checklists, APPA 1–5 scoring with critical items flagged, photos attached to each finding, offline inspections that sync, deficiency tracking, and a branded PDF report you can attach to the monthly owner pack. Where a vendor uses the same platform, comparison gets easier; where they do not, you inspect independently and compare in the meeting.
Two related decisions worth planning now: how deficiencies get tracked to closure on your side, and what a photograph has to show to be useful six months later. Deficiency tracking in cleaning covers the first, and inspection evidence and photo standards covers the second.
How do you make reporting a contract term?
Write reporting into the contract as a deliverable with a date, a format and a consequence. A reporting obligation with no consequence is optional in practice.
A workable clause set: monthly report due by the fifth business day; four weeks of inspection records available on request within two business days; deficiency closure within the agreed window by severity; records handed over within thirty days of termination; and a right for the owner's representative to inspect the vendor's records for the building.
Then test it in month one. Request the records on day three of mobilisation, before habits form, and again in month three. If they arrive complete and on time both times, you have a reporting system. If not, that is the first item for the next vendor quality audit.
Frequently asked questions
Should I require a vendor to use a specific inspection app?
No. Requiring a named product creates a barrier for competent contractors and does not guarantee usable records. Specify the output instead: dated, per-area, with deficiencies and closure dates, delivered monthly and on request. A well-run paper system that meets that standard is fine.
How many inspections should a vendor be doing each month?
Match the count to the site, not to a round number. A single building is usually served by weekly supervisor walks plus a monthly management inspection; a multi-building portfolio often needs one inspection per site per week. Ask what the vendor proposes, then compare it with the schedule in their price — the two should agree.
What if the vendor's reports show nothing wrong every month?
Treat it as a data quality problem and say so. Real buildings produce real deficiencies. Walk one inspection with the supervisor and compare their findings with yours. If the gap persists, rely less on their reports, inspect more often yourself, and record the reason.
Do photographs count as evidence on their own?
Only with context. A photo with no date, location or item reference proves very little. Insist on photos linked to a checklist item, an area and a date, stored with the inspection record. Before-and-after photos with dates are a strong record; a folder of loose images is not.
How long should we keep inspection records?
Keep them for at least the contract term, and longer if your records schedule, insurer or lease requires it. A common working rule is the term plus two years, because claims often surface after the contract ends. Agree the period in writing with the vendor and confirm it with your records team.
Ask for the record, then verify it yourself
The vendor's reporting tools tell you what they think is happening. Your own inspections tell you what is true. Both should be dated and easy to produce when an owner or insurer asks a hard question.
NeatScore gives property managers the second half of that pair: cleaning inspections scored on the APPA 1–5 scale, critical items flagged, photos on every finding, offline inspections that sync, deficiency tracking to closure, and branded PDF reports for the owner pack. Try it free for 14 days, or see pricing. For how this fits the rest of the vendor lifecycle, start with the vendor management framework.
