Most of the delay in RAMS is waiting: for the document to arrive, then for it to come back right. This release shortens both.
What's new
- Chase a late RAMS without leaving the board. Pick the RAMS on the readiness board, check the reminder before it goes, and confirm. The subcontractor gets a clear email, and the board keeps a record of who was chased and when, so nobody chases twice or assumes someone else did.
- Send the reviewer's findings back with the rejection. When you agree with the findings raised on a RAMS, tick the ones to send. The subcontractor sees exactly those under "What needs fixing", on the email and on the resubmission page, instead of a rejection they have to interpret.
- Ask for the right document when the wrong one arrives. If an upload isn't a RAMS, the board says so as "Wrong document" and asks the subcontractor for the correct one, rather than showing an assessment that failed for no obvious reason.
- Resubmit without losing the files that were fine. A resubmission that keeps files from the earlier attempt no longer fails with an error about a malformed record.
- Set and change RAMS due dates on the board. Due dates show on each package and can be edited in place. The board also refreshes itself as assessments finish, and a package that doesn't need a RAMS can be closed as not required so it stops showing as outstanding.
- Open PlanOps where you left off. It returns you to the last project you opened in each organisation. The search box at the top now finds things, starts actions and answers questions in the one place, and a project overview can show readiness by area.
Why it matters
A RAMS that is chased late, rejected vaguely, or resubmitted unchanged is how a start on site slips by a week. Chasing from the board and sending back specific findings means the next version is more likely to be the right one.
New featureImprovementRAMSPublic pages