One link and one chase for everything a subcontractor owes

Most of this release is about collecting documents from subcontractors, with a new examination check for hired pressure plant.

What's new

• Give each subcontractor one link for everything they owe. Every line a company owes on a project, across information schedules and inbound handover packs, now sits on one collection page, grouped by schedule or pack with its due date and status. If a company already had several links, the oldest becomes its page and the others point to it, so you don't have to send anything new.
• Chase a company once, not once per schedule. Chase from the handover board or the company's page and PlanOps lists every open line, whether awaited, overdue or sent back for changes, with the ones you were looking at already ticked. The email lists exactly what you ticked, and each line shows when it was last chased and by whom.
• Let the right people at the subcontractor upload. Add the email domains a company uses, and anyone with an address on those domains can verify and upload on its page, as can the company's named contacts on the project. Public webmail addresses still have to match exactly.
• Stop asking for the same document twice. When a line is waiting on a company, its page offers documents you've already accepted from that company elsewhere on the project. They choose "Use this" and it arrives as a normal submission, which someone on your side still accepts.
• Ask for a new revision of something you've already accepted. If an RFI or a drawing change makes an accepted document out of date, request a new revision with a reason and link the cause. The accepted version stays in the handover while the new one is reviewed, so the pack isn't left with a gap.
• Decide each document on its own. Inbound handover packs are now reviewed line by line, like information schedules, and a new upload reopens review on that line only. Your decision applies to the upload you actually read, so a file that lands while you're reviewing isn't accepted by mistake.
• Keep the schedule accurate when things arrive another way. Log a document that came by email or by hand against its line, waive a line that no longer applies (with a reason, and reinstate it later if needed) or change its due date. The record shows who did it and why, instead of a status someone changed by hand.
• Start the handover pack when the package starts. When a package is approved or gets an installer, PlanOps drafts its inbound handover pack from the template for that package type, or adds it to the company's existing pack. Nothing goes to the subcontractor until you issue it.
• Show that a hired compressor's pressure examination is in date. A new PSSR examination check records the competent person's report and takes the next due date from it, rather than a guessed interval. The project team is reminded 14 days before it's due.
• See which plant checks are due without reading a timeline. A plant's Upcoming checks tab now opens with a summary (overdue, due in the next 7 days, next inspection) and a list grouped into Overdue, Next 7 days and Later. Due dates count UK calendar days, so a check due tomorrow no longer reads "today" and an overdue one says so.
• Smaller things. Information schedule lines now name a company on the project rather than typed text, so two contacts at the same firm no longer show up as two parties. Automatic RAMS and RFI reviews can be switched on or off from project settings or the board's More menu, so you decide when IU credits are spent. The RAMS wizard now asks what the work is and who's doing it before the risk step, so suggested hazards have something to go on. Saved views on Tasks survive a reload, and the programme timeline shows adjusted dates against the baseline.

Why it matters

Handover information usually goes missing because the asks are scattered: a schedule link here, a handover link there, a separate chase for each. One page and one chase per company makes it obvious to them what's left. It also leaves a record of what was asked for, when and how often, which is what you need when the O&M pack is late and someone wants to know why.