Between March and August 2026, PEER shipped eleven release cycles focused on making everyday workflows in PTW, HSE Inspection, and project setup faster and more reliable. None of these releases required a migration or a reconfiguration project they rolled out as part of the normal update cycle and applied automatically once each company’s instance was upgraded. Here’s a summary of the PEER product updates that matter most for teams running the platform day to day.
Permit to Work (PTW)
PTW saw the most active development of any module in this period, which reflects how central the permit workflow is to daily HSE operations. The cycle opened with Day 0 pre-approval on the Master Plan, letting site teams submit and approve permits before work officially begins the next day, rather than scrambling through approvals at the start of a shift.
Workflow grouping followed shortly after, alongside a matching “Route-to” option added to both the PTW Plan list and the Plan form. This pairing matters because it lets approval routing mirror how teams actually assign work across supervisors and departments, instead of forcing every permit through a single fixed chain regardless of task type or risk level.
Later releases in the cycle refined the details that affect daily use: a maximum duration limit tied to the PTW Plan to prevent permits from running longer than intended, a confirmation prompt when reloading a form that’s still in progress (so half-completed submissions aren’t lost by accident), and an extended future-date range in the date picker to support permits planned further ahead. Together, these updates move PTW from a strictly linear approval tool toward something that adapts to how different sites and teams structure their permit process.
HSE Inspection
HSE Inspection improvements focused squarely on day-to-day usability rather than new modules. The most visible change was a mobile-optimised layout for creating Findings, which matters in practice because most Findings are logged from a phone or tablet on site, not from a desktop back at the office. A cluttered mobile layout is one of the fastest ways to make inspectors skip fields or rush documentation.
Support for multiple PICs per inspection followed, addressing a common real-world case: a single inspection round often spans more than one responsible area, and forcing a single PIC per inspection meant follow-up ownership got blurred. Finding numbers were also surfaced directly on both the Finding Detail and Corrective Action pages, so a finding can be referenced and tracked by number across reports without cross-checking spreadsheets.
Several bug fixes in this period also addressed missing company and PIC names appearing in reports generated from multi-project setups — a small issue on paper, but one that directly affects whether an inspection report is usable as audit evidence without manual correction.
Project Setup and My Tasks
Project Setup picked up a new Worker Assignment filter with page counters, making it faster to see how many workers are assigned across large, multi-site projects without paging through the full list manually. Timezone support was added at the project level, along with timezone selection inside the Project Wizard itself — a meaningful fix for companies running projects across different regions, where timestamps on inspections, permits, and reports previously defaulted to a single system timezone regardless of where the actual site was located.
On the My Tasks side, teams gained a dedicated RE/RTO menu so return-to-operation tasks no longer need to be tracked separately from other pending work, a start-and-end date range filter for narrowing down task lists by period, and a new Site Inspection card for faster access to pending inspection work directly from the task dashboard.
Language, Notifications, and Security
Thai language support was added during this period, alongside continued refinements to Indonesian and English translations across the platform. This kind of steady localisation work rarely makes headlines, but it directly affects adoption for frontline workers who are more comfortable working in their first language rather than translating HSE terminology on the fly.
A new email notification option was introduced for setup notifications, giving administrators more control over what triggers an email versus an in-app alert. Several releases across the six-month period also focused specifically on system stability and security hardening, including an update to worker registration that added support for email masking with prefixes useful for companies where multiple workers need to register under variations of a shared company email address without creating conflicts.
Why This Matters for Your Team
Taken individually, most of these changes look like small quality-of-life fixes. Taken together, they point in a consistent direction: PTW and HSE Inspection becoming more configurable to how teams actually work, project setup becoming more aware of multi-site and multi-timezone operations, and the platform quietly getting more secure and better localised in the background. For a team evaluating whether their current PEER setup is keeping pace with these changes, a useful exercise is to check whether workflow grouping and Route-to are configured for PTW, and whether project-level timezones have been set correctly for any site outside the default region.
For the full version-by-version changelog, including the exact release date and bug-fix list for each version mentioned here, visit the PEER Release Notes in the knowledge base. To see how PTW and HSE Inspection fit together as part of a complete digital HSE workflow, read our guide on the electronic permit to work system.
