Inspections

Inspections in IssuesId are reusable yes/no checklists. Build a template once, run it on every unit, level or plant room, and let every failed answer raise a tracked defect on its own.

Templates

A template is a reusable checklist definition, held at organisation level so every project can use it. Common categories:

→Safety inspections — daily / weekly site walks.
→Quality inspections — trade-specific pre-handover checks.
→Pre-completion (PC) inspections — full handover sweep.

A template is a list of questions in an order you set. Each question is answered Yes or No, and can be marked a hold point — the checks that shouldn't be waved through because someone was in a hurry.

Templates can be edited after they've been used. Adding, renaming, reordering, or deleting a question changes the template for future runs; checklists already running on a project keep their own copy of the questions, so a mid-job template edit never rewrites work already done.

Running an inspection

01From the project, add a checklist from a template — optionally scoped to a location.
02Walk the area, answering each question Yes or No as you go.
03Every answer records who gave it and when.
04A No raises a linked defect automatically.

Questions can also be added to, edited on, or removed from a running checklist if the job on the ground doesn't match the template.

Every checklist on every job, in one list

Templates live in one place; the checklists actually running live in another. The checklists page lists every checklist instance across the whole organisation, not one project at a time.

Filter the list by:

→Project, and then by a location inside that project's tree — including an explicit No location choice for checklists that were never scoped to one.
→Last activity, as a date range.
→Status — Not started, In progress, or Complete.

Each row carries the checklist name, its project and location path, a status chip, an answered-of-total count, and a marker when a hold point is still outstanding. Open a row for the full checklist: the same answer, hold-point and raised-defect behaviour as the inline view on the project, not a read-only copy of it.

The template library moved onto its own page when this list arrived, reachable from Manage templates at the top of it.

Failed answers become defects

This is the link that ties inspections to the defect register:

→Answer No on a question.
→A defect is created and linked back to that question.
→The defect runs the normal lifecycle — issued to a trade, evidenced, closed.
→When that defect closes, the question flips back to Yes on its own, and the record shows it was resolved that way rather than re-answered by hand.

No re-keying, and no drift between the checklist and the register in either direction.

Sending a segment to a subcontractor

A subcontractor can answer part of a checklist without an account, an invitation, or an app.

From the checklist, issue a share link against one contractor. It's emailed to that contractor's nominated contact, or to the company address if there isn't one. Set a due date when you issue it. The app shows you the raw link once, at the moment you issue it, in case the email doesn't land — after that panel closes it isn't retrievable, and the fix is to re-send.

What the recipient can reach. Not the whole checklist — only the stretch that's live right now: the questions after the last hold point answered Yes, up to and including the next hold point that hasn't been. That scope is recalculated every single time the link is opened and every time an answer is submitted. Reordering the questions, adding new ones, or editing the checklist after the link went out cannot widen what it reaches.

What comes back. Answers land through exactly the same path a signed-in inspector's answers do, so a No still raises its linked defect. The record shows the answer arrived through that share link rather than pretending a user gave it, and every attempt against the link — including refused ones — is logged.

Managing a link in flight.

→Each link carries a status: Active, Due soon, Overdue, Completed, or Revoked.
→Revoke kills it immediately. Extend moves the due date. Re-send issues a fresh link and retires the old one in the same step, so a forwarded copy stops working.
→Reminder emails go out before the due date and again once it has passed — to the subcontractor, and to the project's managers. The managers' copy never contains the link itself.
→A dead link says which kind of dead it is. Expired, revoked and already-completed each get their own wording, rather than one shrug of an error page.

Sign-off

Sign-off in IssuesId is a status, not a signature. The defect a failed check raised moves through its lifecycle and is signed off by a role permitted to sign it off — which is never the trade that did the work. Each transition is stamped with who made it and when, and the whole sequence stays on the record.

There is no signature pad. Nobody signs with a finger or a stylus, and there is no counter-signature step. What the record carries instead is the name, the role, the time, and the evidence — which is what a claim actually turns on.

The one place a real signature appears is the Defect Notification PDF, which carries your project coordinator's name, contact details and uploaded signature image. That's configured once per project, not drawn per inspection.

Getting an inspection out as a document

Checklists themselves do not export as a PDF. What you hand over comes from Reports instead — the Door Sheet for a per-location walk-through, the Purchaser Report for a per-defect pack with photos, Internal Detailed for the full evidence record. Because failed checks are defects, everything raised on an inspection is already in the register those reports read from.

Inspections on a day

An inspection can also be attached to a specific day in the Daily Log, which is usually where a site walk actually belongs. From an empty day you can start a QA checklist inspection on its own, without filling in the rest of the day, and it opens focused on that one checklist rather than the whole day form.

Answers lock when the day is submitted, along with everything else on it.