No one knows what would make Heresafe better than the people using it every day. We already use your feedback to shape our roadmap, but this is your chance to share ideas openly and see what other administrators are thinking too. Drop your idea in the comments below. And if you want to go further, head to our feature board where you can submit suggestions, vote on existing ideas, and see what's already in the pipeline.

Kelly Szabo 4 days ago

1

Community Support

Anything big?

justjake about 15 hours ago

Community Support

Looking back at those early days with Heresafe, most of us would do a few things differently. Maybe it's how you structured your contractor types, how you configured notifications, or something you didn't think about until it became a problem. If you could go back and give yourself one piece of setup advice, what would it be? Would love to build up a list of things new administrators can learn from.

Kelly Szabo 4 days ago

Config

Community Support

There seem to be two schools of thought here, some teams work primarily through main contractors and hold them accountable for their supply chain, while others prefer to deal with each supplier directly. Which approach does your organisation take, and what are the pros and cons you've found in practice?

Kelly Szabo 4 days ago

Community Support

When copying a permit, all fields are currently editable except for the "Issue To" field. It would be beneficial if users were able to amend the "Issue To" field when creating a copied permit, particularly for long-running projects where supervisors or responsible persons may change over time. At present, this means a new permit must be created from scratch if the permit needs to be issued to a different supervisor. Allowing this field to be edited would reduce administration, improve efficiency, and make the permit copying function more flexible for ongoing works.

Chris Butler 5 days ago

1

Permits

💡

Feature Request

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.

Kelly Szabo 8 days ago

Projects

💡

Feature Request

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.

Jake Gordon 9 days ago

💡

Feature Request

When a document has expired and no further updated versions will be uploaded under that specific document category, it should be archived. When we archive a document ourselves, it should no longer appear on the dashboard as an expired item. Archived documents are no longer active or required, so they should not continue to show as overdue or expired. This will help keep the dashboard accurate, reduce unnecessary expired document notifications, and ensure users focus only on current compliance requirements.

Yusra Sunnan 10 days ago

1

Config

+2

💡

Feature Request

As a contractor/portal user, I want to be able to delete or remove a document that I uploaded in error, so that I can correct mistakes without having to contact the client or host organisation.

Nick Arran 18 days ago

1

Permission changes

💡

Feature Request

Product Suggestion Introduce a Site Notice field within the system that allows authorised users to create and manage important site-wide notifications which are then displayed directly on relevant permits. This would ensure that critical information is consistently visible at the point of permit creation and review, improving awareness of site conditions, restrictions, and ongoing activity. Examples of site notices could include: Health & safety alerts Fire alarm testing schedules Car parking restrictions Severe weather warnings Concurrent works being carried out on site Temporary access restrictions or diversions Problem Statement There is currently no centralised way to display important site-wide notices directly within permits. As a result, users may need to communicate this information separately, which can lead to: Important updates being missed Inconsistent communication across contractors Reduced visibility of live site conditions Increased reliance on external messaging or manual updates Suggested Improvement Add a configurable Site Notice field at site or workspace level, allowing authorised users to: Create and update active site notices Set visibility rules (e.g. workspace, project, or permit-level display) Display notices prominently on all relevant permits Update or remove notices as site conditions change The notice should be clearly visible during permit creation, review, and approval workflows. Potential Benefits Improved visibility of critical site information Better communication of live risks and restrictions Reduced chance of contractors missing important updates More consistent messaging across permits Enhanced safety awareness on site Centralised management of temporary site conditions

Chris Butler about 1 month ago

1

Permits

💡

Feature Request

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.

Yusra Sunnan about 1 month ago

1

High Priority

💡

Feature Request

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

Kelly Szabo about 2 months ago

Projects

💡

Feature Request

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

Maddie Highet about 2 months ago

Reports

💡

Feature Request

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

Shaun Thomas about 2 months ago

💡

Feature Request

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

Yusra Sunnan about 2 months ago

Reports

💡

Feature Request

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

Kelly Szabo about 2 months ago

Projects

+1

💡

Feature Request

Product Suggestion Add an internal-only comments box to project and job records. This would allow internal users to record notes about contractor correspondence, follow-up actions or other project-related activity. Problem Statement Project and job activity often involves follow-up outside the main record, such as emailing contractors for missing RAMS, chasing documentation or noting conversations with relevant contacts. Without an internal comments area, these updates may be stored separately or not recorded clearly, making it harder for other users to understand what has already happened. Suggested Improvement Add an internal comments box to project and job records where authorised internal users can add notes. For example, users could record updates such as: emailed contractor again to request RAMS chased missing documents contractor confirmed documents will be uploaded spoke to site contact about project timing These comments should be visible to internal users only and not shown to contractors or external portal users. Potential Benefits Clearer internal record of project activity Better visibility of contractor follow-up Reduced duplicate chasing by different team members Improved handover between internal users Easier tracking of correspondence and outstanding actions

Chris Butler about 2 months ago

Projects

💡

Feature Request

Users would like a visual workflow map showing how the main Heresafe processes connect. This would help users understand the end-to-end flow across key areas such as contractor onboarding, document submission, approvals, inductions, projects, permits, check-in/out and ongoing compliance. A clear flowchart would make it easier to see which steps happen in sequence, where information is entered or approved, and how different parts of Heresafe link together. This would be useful for onboarding new users, training internal teams and helping clients understand how Heresafe supports their contractor management process from initial setup through to work taking place on site.

Umar Sayi about 2 months ago

💡

Feature Request

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

Rosie Lawrence 2 months ago

Projects

+1

💡

Feature Request

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

Matthew Vaughan-Hughes 3 months ago

1

Permits

💡

Feature Request