Short answer

Filter the Inspections list down to that one site, that one date range, and completed statuses only, add the columns that say who did each check and when, then print it or export it to CSV. Save the view so you can produce the same pack next week without rebuilding the filter.

Detail

Plenty of councils maintain land they don't own: a play area held by the county or unitary authority, a green space under a management agreement, a recreation ground on a lease. The landowner usually wants regular proof the checks are happening. If you're scanning paper sheets today, this replaces that.

Build the view once:

  1. Open the Inspections list.
  2. Add the Location Tag column, then open the advanced filter and set Location Tagis any of → the site.
  3. Add a second condition: Statusis any ofPassed, Failed and Cancelled. This is the step that turns the list into evidence rather than a work plan, because it shows only checks that were actually closed out. Remember lists hide completed tasks by default, so without this you'll be looking at what's still outstanding.
  4. Add a third condition: Due Dateis between → the two dates you're reporting on.
  5. Add the columns that make it evidence: Assignees (who the check was given to) and Updated By (who actually closed it). On a round shared between several people those differ, and the landowner's question is nearly always who did this one. Add Description too if your team writes notes.

Then get it out:

  • Print the grid view straight to PDF for something that reads like a report.
  • Export to CSV for a spreadsheet they can file or audit.
  • Copy the page URL — it carries your filter, so you can send the live view to a colleague.
  • Bookmark the URL in your browser and name it after the site. Next month you open the bookmark, change the two dates, and the pack is ready.

Watch-outs

  • A cancelled check is not a completed check. Including Cancelled shows the landowner you accounted for that week rather than silently skipping it, but if they're expecting an inspection every week, a run of cancellations is a conversation, not evidence. Be ready to explain why.
  • Exports carry the record, not the photos. The CSV holds what was checked, when, by whom and the result. If the landowner wants the images, keep them in Civic.ly and send the link, or attach them separately.
  • Nothing shows if nothing's been completed. The filter can only report what your team has actually closed out on the app. If checks are being done but left as To Do, see the entry on work done but the task still showing To Do.
  • The location tag has to be on the assets. If the site's equipment was added without a location tag, the filter won't find it. Tag the assets first, or draw the site as an area and work from that.
  • Retention. Playground inspection records carry a 21-year expectation. Producing the pack for the landowner is not the same as archiving it. Export once a year and keep your own copy.