Additional/Restricted User Dashboard for 'My Projects'

Product Suggestion Introduce a dedicated “My Projects” dashboard view for additional/restricted users which automatically filters and displays only the projects they are directly linked to, assigned against, or responsible for within the system. This dashboard would provide users with a clearer and more focused workspace by removing visibility of unrelated projects and allowing quicker access to the projects relevant to their role. The feature could potentially include project status visibility, upcoming actions, expiry indicators, and quick navigation links to associated permits, bookings, or documentation. This would be particularly beneficial for organisations managing large numbers of concurrent projects where users only require visibility of a smaller subset relevant to their operational responsibilities. Problem Statement Users currently do not have a dedicated dashboard view showing only the projects they are directly linked to. This can make it difficult for users to quickly identify and manage their relevant projects, particularly within larger environments containing high volumes of active projects. Suggested Improvement Introduce a “My Projects” dashboard for additional/restricted users that displays only the projects assigned or linked to them. Potential Benefits Improved user experience and navigation Faster access to relevant projects Reduced visibility of unrelated projects Cleaner interface for operational users Increased efficiency for day-to-day project management

Restore Deleted Project Contacts

Product Suggestion Introduce functionality that allows users to restore project contacts that have been accidentally deleted, without requiring intervention from the support team. This could include a temporary recycle bin, restore option, or audit history within the project contacts section, enabling authorised users to quickly recover recently removed contacts. The feature would help streamline project administration and reduce delays caused by accidental deletions. This would be particularly beneficial within busy operational environments where project contacts may be removed unintentionally and need reinstating quickly to maintain communication, approvals, or workflow continuity. Problem Statement Currently, if a project contact is accidentally deleted, users are unable to restore the contact themselves and must instead raise a support ticket for assistance. This creates unnecessary delays and additional administrative effort for both clients and support teams. Suggested Improvement Implement a self-service restore function for deleted project contacts, allowing authorised users to: View recently deleted contacts Restore contacts directly within the project Recover deletions without requiring support intervention Potential Benefits Faster recovery from accidental deletions Reduced dependency on support tickets Improved user experience and efficiency Reduced administrative delays Better operational continuity within live projects

Restricting the Ban Button

Product Suggestion Introduce a configurable permission setting that allows organisations to control which users have visibility and access to the Ban / Unban functionality within the system. Currently, the ability to ban or unban users may be visible to broader user groups than required, which can create concerns around access control, governance, and accidental misuse. This enhancement would allow administrators to specifically assign ban/unban authority only to authorised personnel or user roles. The functionality could operate as a standalone permission within global groups or role settings, ensuring organisations can align user access with their internal approval structures and operational responsibilities. Problem Statement There is currently limited ability to restrict visibility and access to the Ban / Unban button to only selected authorised users. This can create governance concerns where users may see or potentially access functionality that should be limited to specific administrators or management roles. Suggested Improvement Create a dedicated permission setting that controls: Visibility of the Ban / Unban button Ability to perform ban/unban actions Role-based assignment of this authority Potential Benefits Improved access control and governance Reduced risk of accidental misuse Clearer separation of administrative responsibilities Better alignment with internal organisational permissions Increased security and operational control

Ability to sort reports by preference

Product Suggestion Introduce an “Order By” or sorting dropdown within system reports, allowing users to organise report results based on the information most relevant to their workflow. Users would be able to sort report data by selectable fields such as: Expiry date Start date Alphabetical order Creation date Status Company or contractor name This enhancement would provide greater flexibility when reviewing large datasets and improve the usability of reports for operational, compliance, and management purposes. The functionality could also support ascending and descending sorting options to allow users to prioritise urgent or upcoming items more effectively. Problem Statement Currently, report results display in a fixed or limited order, which can make it difficult for users to quickly identify the information most relevant to them. This can slow down reporting workflows, particularly when managing high volumes of records or time-sensitive compliance data. Suggested Improvement Add an “Order By” dropdown or sorting functionality to reports, enabling users to organise report data based on their preferred criteria. Potential Benefits Improved report usability and flexibility Faster identification of urgent or relevant records Better visibility of upcoming expiries and key dates Reduced manual filtering and data manipulation Improved operational efficiency for users managing large datasets

Document Requests Audit Log

Product Suggestion Introduce a dedicated audit log for document and credential requests, providing clear visibility of all request activity within the system. The audit log would display: When a document was requested Who requested it Whether the request was system-generated or manually triggered The status of the request Potentially which project, permit, or workflow triggered the request This functionality would create a clearer history of credential request activity and improve transparency for both administrators and contractors managing compliance documentation. The feature would be particularly useful in environments with multiple administrators or automated workflows, where duplicate requests can occur due to limited visibility of previous request activity. Problem Statement Currently, users have limited visibility of previous document requests, making it difficult to determine: Whether a credential has already been requested When the request was sent Who initiated the request Whether the request came from automation or manual action This can result in duplicate credential requests, unnecessary contractor communication, and additional administrative workload. Suggested Improvement Add a document request audit log within the credential/document management areas of the system, allowing users to review historical request activity and request origins. Potential Benefits Reduced duplicate credential requests Improved transparency and auditability Better visibility of automated vs manual actions Improved contractor communication Reduced administrative confusion and workload Stronger compliance tracking and reporting

Auto archive of expired credentials

Product Suggestion Introduce functionality that automatically archives expired credentials once a new valid replacement credential has been uploaded and approved within the system. Rather than continuing to display both the expired and current versions within active credential views, the older expired credential would automatically move into an archived state. Archived credentials would remain accessible for audit and historical purposes but would be hidden from standard credential searches and reports by default. Users could optionally view archived credentials through: A “Show Archived” tick box A dropdown filter An archived credentials tab or section This enhancement would help maintain cleaner company and people profiles while improving the usability and accuracy of credential reporting. Problem Statement Currently, expired credentials continue to appear within active credential searches and reports even after a valid replacement has been uploaded and approved. This can create cluttered profiles, confusion around which credentials still require action, and unnecessary noise within compliance reporting. In larger environments with high volumes of credentials, this can make it more difficult for users to quickly identify genuine outstanding or expired items that still require chasing. Suggested Improvement Automatically archive expired credentials once: A replacement credential has been uploaded The replacement has been approved and marked as valid Archived credentials should: Remain accessible for audit/history purposes Be hidden from active views and reports by default Be viewable through optional filters or archive settings Potential Benefits Cleaner company and people profiles Improved readability of credential reports Easier identification of genuinely outstanding credentials Reduced administrative confusion Improved compliance visibility Retention of historical audit records without cluttering active data

Ability to Un approve an approved project

Product Suggestion Introduce functionality allowing authorised users to revert an approved project back to an “Awaiting Approval” status when a project has been approved in error. This would provide administrators and project managers with greater flexibility when managing project workflows and approvals, particularly in situations where: Approval was given accidentally Incorrect information was identified after approval Required documentation was missing Additional checks or amendments are needed before work proceeds The functionality could be controlled through permissions to ensure only authorised users are able to reverse approvals. Problem Statement Currently, once a project has been approved, there is limited ability to revert the project back into a pending or awaiting approval state. If a project is approved incorrectly or prematurely, users may need to rely on manual workarounds or support intervention to correct the status. This can create delays, confusion, and reduced control over project approval workflows. Suggested Improvement Add an “Unapprove Project” or “Revert to Awaiting Approval” option for authorised users, allowing approved projects to be moved back into the approval workflow when required. Potential Benefits Improved control over project approvals Faster correction of approval mistakes Reduced dependency on support intervention Improved compliance and governance Greater flexibility within operational workflows Clearer management of project status changes

User Profile Display Options

Product Suggestion Introduce configurable display options for user and contact profile views, allowing users to switch between a visual card layout and a compact list layout depending on their preference and workflow requirements. The current card-based view is useful for quick visual identification; however, some users managing large numbers of contacts may prefer a more condensed list-style view to improve navigation, scanning, and visibility of information. The feature could include: Toggle between card view and list view User preference saving Adjustable columns or displayed information within list view Faster scrolling and searching for high-volume environments Problem Statement Currently, user/contact profiles are displayed primarily in a card-style format with profile pictures. While visually useful, this can become difficult to navigate in environments with large numbers of users or contacts, where a more compact and data-focused view would improve usability and efficiency. Suggested Improvement Add a display toggle allowing users to switch between: Card view (with profile pictures) Compact list view This would allow users to choose the layout best suited to their operational needs. Potential Benefits Improved usability for high-volume user management Faster navigation and searching More efficient use of screen space Greater user customisation and flexibility Improved accessibility for different working styles

Add Induction Pie Chart to Project Dashboard

Product Suggestion Introduce an induction status pie chart within the Project Dashboard, similar to the existing credentials overview chart, to provide users with a quick visual summary of induction completion across a project. The chart would display the number or percentage of contacts who have: Passed their induction Failed their induction Not yet completed their induction This would provide project managers and administrators with immediate visibility of induction progress without needing to manually review each individual contact or induction record. The chart could potentially support: Click-through filtering to view affected users Live status updates Colour-coded breakdowns Dashboard visibility alongside credential compliance metrics Problem Statement Currently, users must manually review individual contacts or induction records to understand overall induction progress within a project. This can become time-consuming on larger projects with high contractor volumes and makes it harder to quickly identify outstanding inductions or failed completions. Suggested Improvement Add an induction status pie chart to the Project Dashboard showing: Passed inductions Failed inductions Outstanding/not completed inductions The functionality should mirror the usability and visibility of the existing credentials dashboard charts. Potential Benefits Improved visibility of induction progress Faster identification of outstanding or failed inductions Reduced manual checking and administration Better project oversight for managers and administrators Improved compliance monitoring across active projects Cleaner and more informative project dashboards

Ability to Display mandatory fields

Product Suggestion Introduce clearer visual indicators for mandatory fields throughout the system, allowing users to easily identify which information must be completed before submitting a form or progressing to the next stage. This functionality could include: Asterisks (*) beside required fields Colour highlighting “Required Field” labels Real-time validation prompts before submission The feature would be particularly useful on larger forms such as project creation, permit applications, onboarding workflows, and configuration screens where users may not immediately know which information is compulsory. Problem Statement Currently, users may only discover mandatory fields after attempting to submit a form, which can create confusion, additional clicks, and unnecessary delays when completing workflows. For example, when creating a new project, users may complete most of the form only to then receive validation errors highlighting missing required information. Suggested Improvement Add visible indicators to all mandatory fields across forms and workflows so users can clearly identify required information before submission. Potential Benefits Improved user experience and usability Reduced submission errors Faster form completion Reduced user frustration and confusion Improved workflow efficiency Clearer onboarding and project setup processes

Credential Recovery & Management Improvements

Introduce functionality that allows authorised users to recover or reinstate credentials that have been removed, expired, or archived in error, without needing to rely on support intervention. This could include a restore option, recovery workflow, audit history, or other credential management tools that enable organisations to quickly reinstate valid credentials and maintain continuity across active projects and contractor records. Problem Statement Currently, when a credential is removed or becomes unavailable unintentionally, clients may need to contact support or perform additional administrative steps to correct the issue. This can create delays, increase operational overhead, and impact project workflows while access or compliance records are being restored. Suggested Improvement Provide enhanced self-service credential recovery capabilities that allow authorised users to: View recently removed or archived credentials. Reinstate credentials where appropriate. Review an audit history of credential changes. Resolve accidental removals without requiring support assistance. Potential Benefits Faster recovery from accidental credential removals. Reduced dependency on support tickets. Improved administrative efficiency. Better operational continuity for live projects and contractor records. Increased visibility and control through credential change history.

Bulk contractor notifications

Product Suggestion Introduce a bulk contractor notification feature within the system, allowing authorised users to send alerts, updates, or important communications to multiple contractors simultaneously without needing to contact each company or individual manually. The functionality could allow users to: Send notifications to all contractor companies Target selected companies or contacts Filter recipients by: Company Group Contact type Project Site/location Status or approval stage Notifications could be used for: Site-wide updates Emergency notices Planned maintenance communications Compliance reminders Process changes Induction or permit reminders To maintain governance and prevent misuse, the feature could include: Permission-based access controls Confirmation prompts before sending Audit logging of notifications Recipient previews before distribution An additional enhancement could allow contractors to receive an email advising them that they have a new notification available within the portal, rather than sending the full communication content directly by email. Problem Statement Currently, users must contact contractors individually or outside of the platform when sending updates or important information to multiple recipients. This creates additional administrative effort, increases communication time, and can lead to inconsistent messaging across contractors and sites. For organisations managing large contractor bases, the lack of bulk communication tools can make urgent or site-wide communication difficult to manage efficiently. Suggested Improvement Add a bulk notification and communication feature within Heresafe that allows authorised users to send targeted communications to multiple contractors or contractor groups directly through the platform. Potential Benefits Faster contractor communication Reduced administrative workload More consistent messaging across contractors Improved operational efficiency Better visibility and auditability of communications Improved contractor engagement through portal notifications Enhanced control through permission-based access

Ability to have sub projects under a main project

Product Suggestion Introduce the ability to create sub-projects, sub-tasks, or scheduled work periods within a larger parent project, allowing contractors to be assigned only to the specific dates, phases, or activities relevant to their work. Rather than linking all contractors to the full duration of a project, users would be able to define smaller sections of work within the main project timeline and assign contractors accordingly. For example: A three-week refurbishment project could contain multiple sub-projects or work phases Electricians may only attend during week one Flooring contractors may only attend during week two Decorators may only attend during the final phase The functionality could potentially support: Date/time-specific contractor assignments Phase-based work scheduling Separate check-in expectations by task or work package Sub-project-specific permits or inductions Improved reporting visibility for attendance and activity tracking This would provide more accurate operational oversight without requiring users to create multiple standalone projects for smaller pieces of work. Problem Statement Currently, contractors assigned to a project may appear linked to the entire project duration, even if they are only expected on site for a short period or specific task. This can create inaccurate attendance expectations, reduce reporting accuracy, and make it harder to understand who is genuinely expected on site at any given time. To work around this, users may need to create multiple smaller projects, increasing administrative overhead and project duplication. Suggested Improvement Allow users to create sub-projects, work phases, or scheduled contractor work periods within a main project, enabling contractors to be linked only to the relevant sections of work and expected attendance dates. Potential Benefits More accurate contractor attendance visibility Improved check-in and onsite reporting Reduced need for duplicate or fragmented projects Better operational planning and oversight Improved management of phased or long-duration works Reduced administrative workload for project setup Clearer visibility of who is expected on site and when

Add workers and send induction notifications by phone number

Product Suggestion Introduce the ability to add workers to projects and send induction notifications using a mobile phone number, without requiring an email address as a mandatory field. This functionality would allow induction requests, onboarding notifications, and project communications to be delivered via SMS or secure mobile links, providing a more flexible onboarding process for contractors and site workers. The feature could potentially support: SMS induction invitations Secure mobile induction links Phone-number-based onboarding workflows Reminder notifications for incomplete inductions Verification codes for identity confirmation Optional email or phone-based communication preferences This would be particularly useful within industries or environments where workers: Do not regularly access email Share company email addresses Work primarily onsite without desktop access Are temporary or short-term labour resources Problem Statement Currently, an email address is typically required to add workers and issue induction notifications. This can create onboarding delays where workers: Do not have an accessible email address Cannot easily check emails while onsite Prefer mobile communication methods This can slow down project mobilisation and create additional administration when trying to onboard contractors quickly. Suggested Improvement Allow workers to be added and induction notifications to be issued using a phone number as an alternative to email-based onboarding. Notifications could be delivered through: SMS messages Mobile induction links Portal access links sent via text message Potential Benefits Faster contractor onboarding Reduced delays when email access is unavailable Improved communication flexibility Better accessibility for onsite workers Reduced administrative overhead Improved induction completion rates More flexible and modern onboarding workflows

Cancel a booking

Auto-populate General Permit from Work Authorisation

Populate the General Permit with the details of the associated Work Authorisation, or allow the Work Authorisation to be issued as the General Permit. Currently the same details have to be duplicated manually into the General Permit, which is repetitive and error-prone.

Auto reminders For Credentials not Submitted on a project

It would be beneficial if the system could automatically send reminder notifications where project or job documentation (such as the Health & Safety Questionnaire, RAMS, Professional Indemnity Insurance, and Employers' Liability Insurance) remains outstanding. Similarly, if a worker has been assigned to a project or job but has not completed their site induction, the system could automatically remind both the worker and the host manager of the outstanding induction. Ideally, the first reminder could be issued three days after the job is created or the worker is assigned to the project, with subsequent reminders sent at appropriate intervals (4 days). If, after three reminders, the required documentation or induction is still outstanding, the notification could be escalated to the company's primary contact. The escalation should include the job number, job title, and the name of the employee who has not completed the induction or details of the outstanding documentation. I believe this functionality would help improve compliance and reduce the need for manual follow-up.

Project/Job Questions improvements

We currently find the contractor rating system useful, but it is quite limited and there are a few improvements that would make it much more valuable for managing contractor performance. Review Overview It would be really helpful if the review list included the Review Date, overall star rating, and the first comment/question response. This would give us a much better overview of completed reviews without having to open each one individually, making it much quicker to identify specific reviews and assess contractor performance at a glance. Current Screen PROPOSED SCREEN Multiple Rating Categories At the moment, we're only able to capture a single rating as part of the review. We'd like the ability to add multiple rating categories, ideally up to five, so we can score different aspects of a contractor's performance, such as quality, communication, health and safety, timeliness, and professionalism. The system could then automatically calculate an overall rating based on these individual scores, giving us a more balanced and meaningful assessment of contractor performance.

Save Internal Notes During Credential Verification

Request Summary Addition of a Save button within the Internal Notes field during the credential verification process. Current Behaviour At present, any notes entered into the Internal Notes field can only be saved when the verifier either accepts or rejects the credential. This means users must make a verification decision in order to retain any notes entered. Requested Enhancement Introduce a standalone Save function that allows users to save Internal Notes without being required to accept or reject the credential. Business Need / Use Case The customer would like the ability to document observations, queries, or potential issues identified during the verification process and save these notes for future reference while leaving the credential in its current pending state. This would enable verification work to be paused and resumed later, without losing information or forcing a premature decision. Expected Benefit Allows verifiers to record findings during review without making an immediate approval or rejection decision. Improves auditability and traceability of the verification process. Supports collaboration and handover between users reviewing credentials. Provide a clearer audit trail of actions and observations made during credential verification.

Remove Credentials from Projects Without Deleting the Source Document

Current Behaviour: When a credential or document, such as a Quality Questionnaire, is removed from a project, the underlying document is also deleted from the contractor's records. This means that if the document is required elsewhere, it must be re-uploaded. Requested Enhancement: Allow users to remove credentials from a specific project without deleting the original document from the contractor portal. The action should simply disassociate the document from that project, while retaining it within the contractor's document library for future use. Benefit: This would provide greater flexibility when managing project-specific requirements and reduce the administrative burden of repeatedly requesting and uploading the same documentation. It would also minimise the risk of important credentials being unintentionally removed from the contractor's records when they are no longer required for a particular project.

Project Site Rules Improvements

At the moment, when adding documents, the only option is to upload a file directly from a local device. It would be really useful to have the ability to either upload a local file or select a document that has already been uploaded to a document group. For us, this would help ensure we're always using the correct version of a document and avoid the need for multiple uploads of the same file. A specific example is site-specific briefings. Our host managers don't necessarily have access to all of these documents on their local devices, but the documents already exist within document groups in the system. Being able to select them directly would make the process much simpler and reduce administration. Benefits: Reduces duplicate document uploads. Improves version control by using existing managed documents. Saves time for users creating records. Makes it easier to access documents that are already stored within the platform. Reduces reliance on users having local copies of documents available.

Separate Delete permissions from CRUD access

Product Suggestion Introduce a standalone Delete permission that can be managed independently from standard CRUD (Create, Read, Update, Delete) access controls. This would allow administrators to grant users the ability to create, view, and update records without automatically providing permission to permanently delete information from the system. The functionality could support: Independent delete permission toggles Role-based delete access Additional confirmation prompts for deletion actions Enhanced audit logging for deleted records Granular permissions across different modules and record types This would provide organisations with greater control over sensitive actions while maintaining operational flexibility for day-to-day users. Problem Statement Delete functionality is currently grouped within broader CRUD permissions. As a result, users who require standard operational access may also unintentionally receive the ability to delete records. This increases the risk of: Accidental deletions Loss of important records Additional support requests Audit and governance concerns Reduced control over sensitive system actions Suggested Improvement Separate Delete into its own configurable permission that can be assigned independently from Create, Read, and Update access. Potential Benefits Reduced risk of accidental deletions More controlled access to record removal Clearer permission management for administrators Fewer support queries linked to deleted records Improved audit and governance controls Greater flexibility when configuring user roles and permissions

Display subcontractor relationships on project views

Product Suggestion Introduce clearer visibility of subcontractor relationships within project views, allowing users to quickly identify when a contractor is operating as a subcontractor and who they are subcontracting for. This functionality could display subcontractor relationships directly within: Project dashboards Contractor lists Project contact views Onsite/expected attendance views Contractor profile project sections For example, the system could show: “ABC Electrical Ltd – Subcontractor to XYZ Construction” Parent contractor relationships Grouped contractor hierarchies Expandable subcontractor structures within projects This would provide users with clearer operational visibility of contractor structures without needing to manually open multiple records or investigate relationships separately. Problem Statement Currently, subcontractor relationships may not be immediately visible within project views, making it difficult for users to quickly understand: Which contractors are principal contractors Which companies are subcontracting Who subcontractors are working under This can create confusion on larger projects involving multiple contractor layers and may require users to manually cross-reference records to understand contractor relationships. Suggested Improvement Add visible subcontractor relationship indicators within project and contractor views, clearly showing: Which contractors are subcontractors Which principal contractor they are linked to Relevant contractor hierarchy information Potential Benefits Improved visibility of contractor relationships Faster understanding of project structures Reduced need to open multiple records Improved operational oversight on large projects Better contractor management and accountability Clearer reporting and onsite visibility for project teams

Product Request Overview: Project Scheduling & Recurrence

Product Suggestion Introduce a new project scheduling and recurrence capability that allows users to configure projects to repeat automatically on specific dates or according to a defined recurrence schedule. Repeated projects would be automatically generated as linked versions of the original project, improving visibility, consistency, and lifecycle management for recurring works and repeat contractor activity. This functionality would be particularly useful for: Planned maintenance Annual servicing Recurring compliance works Scheduled inspections Repeat shutdown works Cyclical contractor activities The feature would provide organisations with a more efficient and structured way to manage repeat projects without requiring manual recreation each time. Problem Statement Currently, users must manually recreate projects that follow recurring schedules such as: Weekly Monthly Quarterly Annual Ad-hoc scheduled repeats This creates: Additional administrative workload Increased risk of setup inconsistencies Duplicate manual effort Reduced visibility of project history and relationships There is also currently no structured way to link repeated or duplicated projects together, making it difficult to track project lifecycles and recurring work streams over time. Proposed Solution 1. Project Recurrence Configuration Add a dedicated recurrence section within the Project Edit screen allowing users to: Configure recurring schedules Define repeat frequencies: Daily Weekly Monthly Quarterly Annually Custom dates Set recurrence start and end dates Configure the number of future project occurrences Pause or stop recurrence schedules Manage recurrence settings from a single location 2. Project View Enhancements Enhance the Project View screen to display recurrence-related information including: Configured recurrence schedules Upcoming repeat dates Next scheduled occurrence Indicators showing whether a project is part of a recurring series Linked project history and future scheduled projects This would provide users with clearer visibility of ongoing and repeat work programmes. 3. Linked Project Versions When a recurring project triggers: Automatically generate a new linked project Carry over project configuration and structure Maintain historical linkage between all project versions Display linked projects within the project view for easy navigation and audit tracking This would allow users to move between historical, current, and upcoming projects within the same recurring work stream. Supporting Functionality: Project Duplication To support recurrence functionality, introduce a dedicated Project Duplication feature which: Copies project details and configuration Duplicates associated structures and settings Supports automated recurrence creation Can also be used manually for one-off duplication requirements Standalone duplication would also benefit users managing: Similar projects across multiple sites

Add inductions to the Matrix

Add employee and contractor inductions as a visible item within the People Matrix, allowing users to view induction status alongside existing competencies, training, and certifications. Requirements: Display assigned inductions within the People Matrix. Show completion status (Completed, In Progress, Expired, Not Started). Include completion and expiry dates where applicable. Allow filtering and reporting based on induction status. Maintain consistency with the existing matrix layout and functionality. Benefit: Providing induction information within the People Matrix would give administrators and managers a single view of workforce compliance, reducing the need to navigate between multiple areas of the system.

Bulk request inductions from the Induction Search page

Product Suggestion Introduce the ability to send induction requests in bulk directly from the Induction Search page, allowing users to select multiple contractors and issue induction requests in a single action. This functionality would streamline contractor onboarding and compliance management by removing the need to send induction requests individually for each contractor. The feature could support: Multi-select contractor actions Bulk induction request sending Resending induction requests regardless of previous request history Filtering by induction status, company, project, or expiry state Confirmation prompts before sending Audit logging of bulk request activity This would be particularly useful when: Large groups of contractors require onboarding Inductions need to be resent Compliance campaigns are being managed Outstanding inductions need chasing quickly Problem Statement Currently, induction requests must typically be sent individually, creating significant manual administration when managing large contractor groups or chasing outstanding inductions. This can become particularly time-consuming where: Multiple contractors are missing inductions Induction requests need resending Projects involve high contractor volumes Compliance deadlines are approaching The lack of bulk request functionality can slow onboarding processes and increase administrative workload. Suggested Improvement Add bulk induction request functionality within the Induction Search page allowing users to: Select multiple contractors Send or resend induction requests in one action Review selected recipients before submission via a confirmation step The functionality should support efficient management of contractor induction activity while maintaining appropriate user confirmation and oversight. Potential Benefits Faster contractor onboarding Reduced manual administration Improved induction compliance management Easier bulk chasing of outstanding inductions Improved operational efficiency for project teams Reduced repetitive actions for administrators Better scalability for high-volume contractor environments

Invalidate previously approved credentials

Product Suggestion Add the ability to invalidate a credential that has previously been approved. This would allow users to mark an approved credential as no longer valid if it was approved in error or if the submitted document is later found to be incorrect. Problem Statement Once a credential has been approved, it may continue to show as valid even if the approval was made by mistake. This can create confusion where the correct credential is still outstanding, as the contractor may appear compliant when they still need to provide the right document. Suggested Improvement Add an option to invalidate or cancel a previously approved credential. When invalidated, the credential should no longer count as valid, and the contractor should show as still needing to provide the correct credential. Potential Benefits Clearer credential status Reduced risk of incorrect compliance records Ability to correct approval mistakes Better visibility of outstanding credentials Improved control over contractor document approval

Self-configure inductions & assessments

Product Suggestion Introduce the ability for authorised users to self-configure inductions and assessments within Heresafe. This would allow clients to manage and update their own induction content, assessment questions, and related settings directly within the system, without needing to request changes through the Heresafe team. Problem Statement Induction and assessment content often needs to be updated regularly as site requirements, safety information, questions, answers, or pass criteria change. When these updates rely on manual requests, it can create delays and make it harder for organisations to keep onboarding content accurate, current, and aligned with operational requirements. Suggested Improvement Add self-configuration options for inductions and assessments, allowing authorised users to manage commonly updated elements such as: Induction name Expiry duration Pass percentage Questions and answers Acknowledgement text Signature message text Whether the induction is mandatory Allowed attempts Whether a signature is required These settings should be controlled via permissions to ensure only authorised users can make changes. Potential Benefits Faster updates to induction and assessment content Greater control for client administrators Reduced delays when safety or site requirements change Less reliance on Heresafe support for routine updates More accurate and up-to-date onboarding requirements Easier ongoing maintenance of assessments and pass criteria

Automated Reminder System for Expired Supplier Credentials

To ensure compliance and up-to-date documentation across all subcontractors and suppliers, an automated reminder system should be implemented for expired or soon-to-expire credentials on the system. The system will send reminders at a consistent and regular frequency (e.g., weekly) to all relevant subcontractors/suppliers whose credentials have expired or are due to expire. These reminders will continue to be issued automatically until the required updated documents are uploaded to the system. This approach will help maintain continuous compliance, reduce manual follow-ups, and ensure that all necessary documentation—such as insurances, policies, and certifications—remains valid and accessible at all times.

Client Facing Usage Report

Product Suggestion Introduce a client-facing usage report that allows authorised users to review which internal users are actively logging in and using Heresafe. The report should show user activity alongside role information, making it easier for administrators to audit access and identify users who may no longer need system access. Problem Statement Administrators need a clearer way to review internal user activity and permissions without checking each user profile individually. Without a central report, it can be harder to see which users are active, which users have not logged in recently and what access they have across different workspaces. Suggested Improvement Add an Internal User Report to the Reports menu. The report should provide a read-only overview of internal system users, including: user name and email address activity details, such as last login and number of logins global roles roles by workspace role search/filtering export functionality When exported, roles should be split into separate columns for each workspace, making it easier to review user access across multiple workspaces. The report should only include internal users and should not include contacts, contractors or external portal users. Potential Benefits Improved visibility of internal user activity Easier auditing of user access and roles Faster identification of inactive users Clearer workspace-level role review Reduced manual checking of individual user profiles Exportable role information for access reviews

Ability to score contractors after a project job / permit

Product Suggestion Introduce contractor performance scoring using a star rating after project, job, or permit-related work. This would allow teams to record structured feedback on contractor performance once relevant work has been completed. Problem Statement Contractor performance feedback is not currently captured in a simple, consistent way against completed work. This can make it harder for organisations to review how contractors have performed over time or identify patterns across previous projects, jobs, or permit-related activity. Suggested Improvement Add a contractor rating question that can be used when capturing feedback after project, job, or permit-related work. The rating could be displayed on the relevant contractor profile, with an average score calculated from previous feedback. Potential Benefits Clearer visibility of contractor performance Consistent feedback after completed work Average ratings shown against contractor profiles Easier identification of performance patterns Better informed decisions when selecting contractors for future work

Show name of user who has checked a contractor in out

Product Suggestion Display the name of the internal user who has completed a contractor check-in or check-out action. This would improve transparency and auditability within contractor attendance records by clearly showing who performed each movement. This information should be visible across relevant areas such as On-Site Now, visit history, and full contractor attendance details, particularly in environments where multiple check-in methods are used (e.g. manual entry, reception desk, kiosk, QR code, or helpdesk support). Problem Statement Currently, when contractors are checked in or out, it is not always clear which internal user completed the action. This reduces visibility within attendance records and can make it more difficult to: Investigate attendance activity Confirm who processed a check-in/out event Identify the correct contact for follow-up queries Suggested Improvement Add a visible field showing the internal user who performed each check-in and check-out action. This should be recorded and displayed within: On-Site Now view Contractor visit details Attendance history / audit logs Potential Benefits Clearer audit trail for contractor movements Improved accountability for check-in/check-out actions Easier investigation of attendance records Better visibility of operational activity Faster identification of responsible users for follow-up

People matrix view for the Supplier Portal

Supplier Portal People Matrix Product Suggestion Introduce a simplified People Matrix view within the Supplier Portal, allowing supplier company contacts to easily monitor the compliance status of their own workforce. The matrix would provide suppliers with a clear overview of: Staff members linked to their company Missing credentials Expired credentials Upcoming expiries Outstanding compliance requirements The functionality would mirror key benefits of the existing People Matrix while remaining restricted to the supplier’s own organisation and workforce data. This would allow suppliers to proactively manage their team’s compliance directly through the portal, reducing reliance on client-side administration and improving contractor readiness before work begins. The feature could potentially include: Colour-coded compliance indicators Quick upload/request actions Expiry filtering Search and sorting functionality Direct visibility of outstanding requirements Problem Statement Supplier contacts do not currently have a simple, centralised way to identify credential gaps across their own workforce within the Supplier Portal. As a result: Client teams may need to manually chase missing information Expired credentials can be overlooked Compliance updates may be delayed Administrative workload increases for both clients and suppliers This can reduce operational efficiency and slow down contractor onboarding or project mobilisation. Suggested Improvement Add a Supplier Portal version of the People Matrix that: Displays staff linked to the supplier’s own company Shows credential and compliance status Highlights missing, expired, or expiring documents Restricts visibility to the supplier’s own workforce only The functionality should enable suppliers to manage and maintain their own compliance requirements without visibility of unrelated contractor or company data. Potential Benefits Improved visibility for supplier contacts Reduced manual chasing by client teams Faster updates to missing or expired credentials Improved contractor readiness before mobilisation Clearer ownership of workforce compliance Reduced administrative workload Better overall compliance management within the Supplier Portal

Make Contractor Access and Login More Intuitive

Contractors frequently experience confusion when accessing the platform for the first time, often assuming they do not have an account or are unsure how to log in after receiving an invitation email. It would be beneficial to improve the contractor access journey by making it clearer that contractors can access the system using the email address their invitation was sent to, without needing to create a separate account. Additional guidance throughout the login and access process could help users understand: How to access the platform for the first time. Which email address they should use. The difference between available profile types where a user has multiple roles (e.g. Company Contact and Worker). Which option they should select based on the task they are trying to complete. Benefits: Reduce contractor login and access issues. Improve the first-time user experience. Reduce support requests relating to account access. Increase completion rates for inductions, questionnaires, and project requirements. Provide a clearer experience for users with multiple roles within the system. A more intuitive contractor access journey would help users reach the right area of the platform more quickly and with less reliance on support.

Showing Requested date on the Credential Matrices

Requested date to be shown when the request is sent to enable quick visibility on when actions were created rather than clicking into each individual profile

Re request button for credentials on Projects/Jobs

Product Suggestion Add a Re-request button for credentials linked to projects and jobs. This would allow users to quickly chase contractors where required documents or credentials have not yet been submitted. Problem Statement When contractors have missing documents or credentials for a project or job, users may need to follow up manually to avoid delays. Without a quick re-request option, chasing missing information can take longer and may involve contacting contractors outside the system. Suggested Improvement Add a Re-request button against missing or outstanding credentials on projects and jobs. This would allow users to resend the request to contractors, reminding them to provide the required documents before work begins. Potential Benefits Faster chasing of missing credentials Reduced risk of project or job delays Less manual follow-up outside Heresafe Clearer contractor compliance management Improved readiness before work starts

Auto Close Project

Product Suggestion Introduce an Auto Close option for projects, allowing projects to close automatically after their end date has passed. This would reduce the need for users to manually close projects once the work period has ended. Problem Statement Projects currently need to be closed manually. Where teams are managing multiple active projects, this can mean completed projects remain open longer than needed if users forget to close them. This can make project records less accurate and create extra admin when reviewing current or historic work. Suggested Improvement Add an option to automatically close a project shortly after midnight following its end date. For example, if a project ends on 1st March, it would close overnight and appear as closed by the morning of 2nd March. The setting could be applied when creating a new project, or added to an existing project by editing the project details. Potential Benefits Reduced manual admin More accurate project status Cleaner project records Fewer projects left open unnecessarily Easier management of multiple active projects

Calendar filters

The Project Calendar now includes additional filters to help users find the project information they need more quickly. Users can filter the calendar by Workspace, Location and Host Manager, making it easier to focus on relevant project activity without searching through every project at once. This is especially useful for clients managing multiple workspaces, sites or teams, where users may need to quickly see which projects are due at a specific location or under a specific host manager.