Skip to main content

How we prioritise and respond to reported issues

When you contact our Support team, we’ll investigate your query to understand what’s happening, how it affects you and whether there is an available solution or workaround.

If our investigation identifies an issue that requires further input from our Research & Development (R&D) team, we’ll assign an appropriate priority based on its impact and urgency.

This article explains how we determine that priority, what our internal R&D response targets mean and what you can expect while your issue is being investigated.

How do we determine priority?

We consider two main factors when prioritising an issue:

  • Impact: How significantly does the issue affect your ability to use OnRent Events or carry out your normal operations?

  • Urgency: How quickly does the issue need attention to prevent further disruption or harm?

We also consider:

  • How many customers or users are affected

  • Whether essential functionality is unavailable

  • Whether customers can continue their normal operations

  • Whether a reasonable workaround is available

  • Whether there is a risk of data loss or a security concern

  • The wider business and operational impact

Considering these factors together allows us to prioritise the issues causing the greatest disruption while continuing to manage other reported issues fairly.

Our priority levels

The examples below illustrate how different issues may be prioritised. They are not fixed rules, as the priority of an individual issue will depend on its overall impact, urgency and the circumstances of the problem.

Priority 1 – Urgent

Priority 2 – High

Priority 3 – Medium

Priority 4 – Low

Impact

Critical impact. Essential functionality is unavailable.

Significant impact. Key functionality is disrupted or a substantial group of users is affected.

Moderate impact. Something isn't working as expected, but customers can continue working, with a reasonable workaround.

Minimal operational impact. Users can continue working normally. Requests and How-to questions.

Internal R&D response target

Up to 2 working days

Up to 40 working days

Up to 176 working days

Up to 264 working days

Example 1

OnRent Events is unavailable and customers are unable to access the platform.

Invoice PDFs fail to generate under particular conditions, preventing affected customers from completing their normal invoicing workflow.

Availability figures display incorrectly in one area, but the correct stock information remains available elsewhere.

A field, button or other element is incorrectly aligned on screen, without affecting functionality.

Example 2

Customers across the platform are unable to log in.

Stock availability incorrectly prevents affected customers from allocating equipment they need for upcoming work.

A report displays an incorrect total, but the underlying data is still available and recoverable.

A label or piece of wording within the platform is incorrect, but its functionality works normally.

Example 3

Severe performance degradation makes the platform effectively inaccessible or unusable.

An important supported integration is unavailable for active customers, significantly disrupting their normal workflow.

A workflow isn't behaving as expected and requires additional manual steps, but customers can continue working using a reasonable workaround.

A minor cosmetic or edge-case display issue has no operational impact.

Example 4

A widespread issue creates a serious risk of data loss or a significant security concern.

An important area of functionality is unavailable to a significant group of users, although the wider platform remains accessible.

Information briefly displays incorrectly before showing the correct value, causing confusion but not preventing work.

A general task, request or questions on how to use the platform.

A note about our response targets

The timeframes shown above are internal R&D response targets that we use to help us prioritise and manage our workload.

These are not contractual SLAs, policy commitments, agreed resolution timeframes or guaranteed fix dates.

They also represent maximum internal targets rather than the amount of time we expect every issue to take. For example, a Priority 3 issue having an internal response target of up to 176 working days does not mean that we will wait 176 working days before investigating or resolving it.

Priority 3 and Priority 4 issues may be investigated and resolved considerably sooner depending on factors such as:

  • The complexity of the issue

  • Current R&D workload and capacity

  • The number and priority of other issues being investigated

  • Features and improvements currently being developed

  • Whether the issue can be addressed alongside related development work

  • The amount of development and testing required

Where workload and development capacity allow, lower-priority issues may therefore be progressed much sooner than their maximum internal target.

What happens after an issue is reported?

Our Support team will investigate the issue as thoroughly as possible before referring it to Development. Depending on the issue, this may include:

  • Reviewing the affected area of your system

  • Attempting to reproduce the behaviour

  • Checking whether an existing solution or workaround is available

  • Reviewing relevant records, orders or invoices

  • Gathering screenshots or screen recordings

  • Collecting the steps required to reproduce the problem

We may ask you to provide:

  • Examples of affected records

  • Screenshots or screen recordings

  • Steps to reproduce the problem

  • Details of the users affected

  • Support Access to be opened

  • Details of troubleshooting you've already completed

Providing this information can help us understand both the problem and its impact and may enable our Support team to resolve the issue without further escalation.

Does the response target mean my issue will be fixed within that time?

No - Our internal response targets aren't resolution or fix deadlines. Software issues can vary considerably in complexity. Something that initially appears straightforward may require additional investigation, development, testing or changes to other areas of the platform before a solution can be safely released.

For this reason, we're unable to guarantee a resolution date based on the priority or internal R&D response target alone.

Where appropriate, our Support team will share relevant updates with you and let you know if an available workaround can help reduce the impact while the issue is being investigated.

Can the priority of my issue change?

Yes - Priority is based on the information and impact known at the time and may change as we investigate further.

For example, an issue may initially appear to affect a small number of users but later be found to affect customers more widely. This could increase its priority.

Similarly, if a reliable workaround is identified that allows customers to continue their normal operations, this may affect the priority assigned to the issue.

Why isn't my issue considered Priority 1?

We understand that an issue affecting your business can feel extremely urgent. Priority 1 is reserved for the most serious situations, such as:

  • The OnRent Events platform being inaccessible

  • A widespread inability to log in

  • Severe performance problems making the system effectively unusable

  • Widespread loss of critical functionality

  • Serious security concerns

  • Data loss

  • Financial impact where no reasonable workaround is available

An issue affecting a particular feature isn't automatically Priority 1 simply because that area of the platform is important.

For example, one user being unable to log in while everyone else can access the platform normally has a very different overall impact from customers across the platform being unable to log in.

Similarly, an invoicing issue that can be worked around has a different impact from a widespread failure that completely prevents customers from processing critical financial operations.

This is why priority is based on the overall impact and urgency of the issue, rather than the feature affected, the size of an organisation or how frequently an issue is raised.

Our approach

Our priority process helps us balance individual customer needs with issues and development work affecting the wider OnRent Events platform.

By consistently assessing impact, urgency and the availability of reasonable workarounds, we can focus resources on the most disruptive issues first while continuing to progress lower-priority issues as development capacity allows.

Our aim is always to investigate and resolve issues as efficiently as possible, while making sure the most significant problems receive the appropriate level of attention.

Did this answer your question?