Turn a package into one PDF pack, with nothing quietly left out

Last release put inspections on site. This one is about the pack you hand over, and what the review actually read.

What's new

• Hand over a package as one document. Export a whole package to a single PDF, rendered in the background so a large pack doesn't tie up your screen while it builds. Continuous page numbering and a document control sheet mean it reads as a controlled document rather than a stack of files stapled together.
• Know what the pack doesn't contain. Choose what goes in, and anything left out, whether too large to embed or a file type that won't render, is listed on an exclusions page with the reason. A missing drawing is stated at the front rather than found by the client.
• See which subcontractor owns each package. Packages now name their installing contractor, editable in place, and you can assign or clear the contractor across many packages at once instead of opening each one. The ITPs under a package follow the contractor automatically, so a firm's inspection record stays attributed correctly when a package changes hands.
• RAMS reviews that read the tables. Method statements keep their substance in tables: risk assessments, COSHH entries, plant lists. Those are now pulled out of Word documents and assessed in place, anchored to the heading they sit under. Where the tables couldn't be read, the review declines to give a score rather than marking a document it only half read.
• Resubmissions read against the last one. When a subcontractor sends a revised RAMS, the review resolves the previous assessment and reads the new one against it, so you see what changed instead of a fresh score with no history. An unchanged resubmission returns the stored assessment rather than spending IU credits reviewing the same document twice.
• Approve a run of suggested actions together. Where an agent proposes several actions, they now arrive as a batch you can confirm in one step, and each card keeps its own state, so approving one no longer clears the rest. Anything still waiting on you is restored when you come back to the thread.
• Review incoming information with the concerns first. The information schedule now has a review queue that puts flagged deliverables at the top, grouped by the party who sent them, and lets you decide in place. Each line shows its assessment, what has arrived before and the decisions taken, and whoever is supplying can record an outcome per deliverable, add a note and re-upload against the same line.
• Emails that say which project they're about. Invitations, permit notices, form returns and public review emails now carry the project name in the subject, so a full inbox sorts itself.
• See where your IU credits go. Usage is now broken down by the tier of work, so heavy document analysis reads separately from routine drafting.
• Smaller things. A handover surface with no upload page raised says so plainly instead of showing an empty list, AI-drafted form content renders as formatted text with locked fields still legible, and disclaimers in generated documents appear as a callout rather than buried in the prose.

Why it matters

The pack and the review are the two places a project gets judged after the fact. A pack that states what it doesn't contain is easier to defend than one that omits it quietly, and a review that admits it couldn't read the tables is worth more than a score that only looks complete. Both come down to the same thing: say what you know, and say what you don't.