Close out RAMS reviews and registers are easier to use

Last release made RAMS requests easier to send. This one sorts out what happens when the answer comes back.

What's new

• A RAMS review ends with a decision, not a status. Reviewers can approve or reject a submission with comments and attach files to the response - a marked-up copy, a photo, whatever makes the point. A rejection moves the item back to the sub-contractor and sends them an email explaining what needs to change, and the decision itself is recorded on the item's timeline so there's an answer to "who signed this off, and when?"
• Approved RAMS file themselves. When a submission passes review it becomes a project document automatically, so the current version sits in your document register rather than in someone's inbox.
• Scores you can defend. RAMS assessment scores now display against their actual scale, with the rubric breakdown behind them, so a 7 comes with what it was marked out of and why.
• Charts from your registers. Any register can now feed a chart, on a dashboard or embedded in a generated document, so the monthly report can show the trend rather than just the table. Built-in presets get a register started, and saved registers open as full pages you can sort and page through.
• Dashboards you can shape. Create named dashboard pages and build your own widgets from project data. Programme activities and form submissions join the list of register sources, so progress and returns can sit on the same page.
• Connect Autodesk Construction Cloud. Alongside SharePoint, you can now connect an Autodesk Construction Cloud environment, test the connection and browse project files, under the same governance controls as your other document sources.
• Share links that behave. Email-gated share links now send the invitation themselves and verify the recipient before opening, documents inside a shared page are resolved at the moment of download so a link doesn't quietly expire mid-review, and public submission pages show exactly what's still outstanding before someone presses submit.
• A more honest interface. Actions you don't have permission for no longer appear as buttons that fail when pressed, viewer access is properly read-only, and when something does go wrong you get plain English where you're looking, not an error code in the corner of the screen.

Why it matters

A RAMS that's been reviewed but not answered is a liability in both directions: the sub-contractor doesn't know what to fix, and you can't evidence the decision if it's questioned later. Closing that loop, and putting register data where people actually look (a chart on a dashboard, a page in the monthly report), means less chasing and fewer surprises at audit.