Sign off inspections on site, and get RFI answers on the record

Last release gave ITPs their own place in the workspace. This one lets you actually run one on site.

What's new

• Get an ITP signed where the work is. Issue an ITP to site and it becomes a QR code the inspector scans on their own phone, no app and no account. Items are completed one at a time, with a signature captured against each one, and the office sees the status change as it happens rather than waiting for a marked-up sheet to come back.
• Invite a witness in time for them to attend. Witness and approval parties are now contactable people with a real notice period, so the client's engineer gets told before the hold point is reached instead of after the concrete has gone in.
• An inspection record that stands up later. Every entry carries who made it and when, and the trail is append-only, so a completed ITP can be produced as evidence months on. Inspectors who sign repeatedly can save their signature once rather than redrawing it on every item.
• Ask for an RFI answer and have it come back written down. An RFI can be sent to the person who holds the answer, in or outside your organisation, and their response writes back onto the item. The question, the answer and the date all sit in one place, which is what you need when a claim turns on when you were told something.
• RFI deadlines that mean something. The date a response is required by now drives the item's due date, and the person answering sees that deadline on the page they're answering on, so an overdue RFI reads as overdue to both sides.
• See who has actually accepted a RAMS. RAMS now carry an operative acceptance register, so you can tell at a glance which operatives have been briefed and signed up to the method, rather than assuming the briefing happened because the RAMS was approved.
• Incidents tracked as incidents. Site events, including H&S incidents, are now their own category in the workspace with severity and RIDDOR status recorded against them, and they appear in filters and registers alongside everything else. A reportable incident stops depending on someone remembering to flag it.
• Information schedules you can keep current. Schedule lines can be edited in place, and you can raise a request against a single line and track whether the information came back. Importing a schedule now uses the standard document picker, so you can start from a document already in PlanOps instead of uploading it again.
• Names instead of ids. Task boards, form submissions and notification emails now show who assigned, created or submitted something, and what type of document it relates to. Long generated documents also keep their finished output when they run big, so a large pack no longer needs regenerating.

Why it matters

Inspections and RFIs are the two places where a project's memory goes missing. The inspection got done but the signed sheet is in a van, or the answer was given on a call and nobody wrote it down. Both changes here put the record where the work happens, at the moment it happens, so the evidence exists before anyone needs to argue about it.