Answer

How do you track overdue inspection items across a large site?

Stop tracking the inspection and track what it raised. In IssuesId every failed check on a checklist becomes a defect with one owner and a due date, an overdue workflow rule escalates it when the date passes, a digest rule sends the outstanding list on a schedule, and one page lists every running checklist across the organisation with a marker on any hold point still open. What IssuesId does not do is schedule the inspections themselves: nothing in it raises next Tuesday’s forklift check on its own. That calendar stays yours, and this page says so rather than implying otherwise.

ANSWERED FROM THE PRODUCT DOCS·UPDATED SEPTEMBER 2026
Before the tool

Two problems wearing one name

“Inspection schedules and overdue items” is two problems. The first is knowing which inspections are due: the monthly crane check, the quarterly racking walk, the daily pre-start. That is a calendar problem, and a good compliance calendar or a CMMS solves it. The second is knowing, across three sites and forty inspections, which of the things those inspections found are still open, whose they are, and how long they have been sitting. That is a register problem, and it is the one that hurts, because a finding nobody chased is what the incident report will be about. Most tools built for the first problem are bad at the second. IssuesId is built for the second and does not pretend to do the first.

How it runs in IssuesId

Five steps, one register

  1. 1Run the inspection as a checklist, so a finding is a record
    Build the machinery check, the racking walk or the plant-room inspection once as a reusable yes/no checklist and run it wherever it applies. Every No raises a tracked defect linked to the question, with the photo, at the moment it is answered. There is no “findings” document to type up afterwards; the findings are already in the register.
  2. 2Give every finding one owner and a due date
    Issue each one to a named person or contractor with a date. Issued is a state on the record, and the assignment email is logged, including whether it was opened. A finding without an owner is nobody’s; the register does not let it be nobody’s for long, because the next step chases it.
  3. 3Let the overdue rule do the chasing
    Workflow rules fire on an overdue trigger: a record passed its due date without progressing. Notify the owner, escalate to the safety manager, re-flag the item. A digest rule runs on a schedule instead, every Monday at seven, say, and sends the outstanding list to whoever should be uncomfortable about it.
  4. 4Read what is still open from one list
    The checklists page lists every checklist instance across the whole organisation, not one site at a time: filter by project, by location inside it, by status and by last activity, and each row carries an answered-of-total count and a marker when a hold point is still outstanding. For the findings themselves, the Issued To report groups open items by owner and the Quality Control report groups them by location, in PDF or Excel, and either can be scheduled.
  5. 5Close on evidence, verified by someone else
    The owner marks it fixed with a photo. It then goes to ready to inspect, not to closed, and a role that did not do the work closes it. When that defect closes, the checklist question flips back to Yes on its own, so the inspection and the register never disagree about what is still open.
The one list, and the Monday digest that reads it. The safety manager did not open anything to learn that Bay C has been sitting for twelve days.
What it does not do

Four limits, before you plan around them

If a compliance calendar is the thing you are missing, IssuesId is not it, and we would rather you found that out here than in week three. If the thing you are missing is knowing which findings from last week’s inspection are still open and whose they are, it is.

01
No recurring scheduler
Nothing in IssuesId raises next Tuesday’s forklift inspection on its own. A template can be run as often as you like, and attached to a day in the daily log, but the calendar that says it is due is yours.
02
No asset register
A machine is a location in the tree, or a checklist scoped to one. There is no plant list with service intervals, meter readings or manufacturer intervals behind it.
03
No PDF of the checklist itself
What you hand to an auditor comes from reports, which read the register the checks wrote to. The checklist is the input, not the document.
04
One list, but per organisation
The checklists page spans every project in your organisation. It does not span organisations, so a head contractor cannot see a subcontractor’s own internal inspections unless they were run in the head contractor’s workspace.
Related questions

Asked alongside this one

How do you track overdue inspection items across a large site?
Stop tracking the inspection and track what it raised. In IssuesId every failed check on a checklist becomes a defect with one owner and a due date, an overdue workflow rule escalates it when the date passes, a digest rule sends the outstanding count on a schedule, and the checklists page lists every running checklist across the organisation with a marker on any hold point still open. What IssuesId does not do is schedule the inspections themselves; that calendar stays yours, and this page says so rather than implying otherwise.
Does IssuesId schedule recurring inspections?
No. A checklist template can be run as often as you like and attached to a day in the daily log, and saved reports can run daily, weekly or monthly, but there is no scheduler that raises next week’s machinery inspection on its own. If a compliance calendar is the thing you are missing, IssuesId is not it. If the thing you are missing is knowing which findings from last week’s inspection are still open and whose they are, it is.
How do I see what is outstanding across every job?
The checklists page lists every checklist instance across the whole organisation, filtered by project, by location inside a project, by status and by last activity, with an answered-of-total count and an outstanding-hold-point marker on each row. For the defects those checks raised, the Issued To report groups open items by who owns them and the Quality Control report groups them by location; both export to PDF or Excel and can be scheduled.
Read on

Where this answer comes from

The docs behind this answer are inspections (templates, hold points, the organisation-wide checklists list), workflow rules (the overdue trigger and digests), reports (Issued To, Quality Control, scheduling) and the daily log, where a site walk usually belongs. The same loop on a factory line is how do you track non-conformities digitally in a factory?; in a warehouse or a depot it is the logistics page; in an office building it is the facilities condition walk. For the part of a checklist a subcontractor answers, read how does a subcontractor answer their part of an inspection checklist?