MILabs
Integrations

Asset utilisation report for Current RMS hire fleets

How an asset utilisation report can draw on Current RMS bookings to show which hire stock earns its keep and which sits idle.

Updated 2026-08-26

Asset utilisation report with Current RMS

Hire businesses that run on Current RMS already hold the raw material for a utilisation report. Bookings and quotes show which items went out, for how long, and which stayed on the shelf. What is usually missing is one view of those days across every category and site. A report built on the platform's API can gather booking history on a schedule, apply the same definitions each time and show booked days against available days for each item. A coordinator or owner can then see which staging kit is always out, which camera bodies rarely leave the store, and where a new purchase would be backed by figures. Access to records depends on the API permissions the account holds, so the first step is confirming what can be read. This page sets out how the build fits the platform and what should stay with a person to decide.

How it works

  1. Confirm which booking, quote and stock fields the account's API permissions allow the build to read, and which, if any, it may write.

  2. Set a read schedule, because the report is only as current as its last fetch from Current RMS.

  3. Match each booked day to the item's stock record, so utilisation is booked days over available days for every asset and category.

  4. Pass the calculated figures to a reporting tool such as Power BI, Looker Studio or Metabase, where filters for site, asset class and date range can sit.

  5. Send the weekly idle-time summary to the owner, and keep any change to availability or pricing in Current RMS under staff review.

good questions, straight answers

Frequently asked questions

What does an asset utilisation report with Current RMS need from me?
You need to name the questions the report should answer, such as which kit sits idle or which categories run out. You also need someone who can confirm the account's API permissions and decide which stock fields may be read. Agree the definitions too, for example whether a day in maintenance counts as available. Those choices shape every figure, so they should be written down before any build starts.
What does an asset utilisation report not do with Current RMS?
It does not edit bookings, change availability or set prices in Current RMS. The report reads records and presents figures, and any change to the live stock record stays with a staff member. It also does not reconcile every cost in your accounts, because maintenance and invoice data may sit elsewhere. Where a figure looks wrong, the report points to the source record so someone can check it against the platform.
Which tools sit between an asset utilisation report and Current RMS?
A scheduled connector or small custom script usually reads records through the Current RMS API and passes them on. Automation platforms such as Make, n8n, Zapier or Power Automate can handle that step. A business intelligence tool like Power BI, Looker Studio or Metabase then turns the data into filtered views and a weekly summary. The right choice depends on your existing software and on who will maintain the connection.
Is an asset utilisation report right for a small Current RMS team?
Yes, provided the team has a clear reason to measure idle stock. A small hire operation may only need the per-item utilisation rate and a weekly idle-time list, which keeps the first release modest. If the team cannot name who reviews the figures, the report will sit unread. Start with the smallest set of records that answers one buying or maintenance question, then widen it once the figures are trusted.
Does an asset utilisation report change how my team uses Current RMS?
Mostly it does not. Coordinators keep recording bookings and quotes as they do now, and the report reads from those records. Some teams will need to tidy booking status or stock categories, because the report is only as consistent as the data beneath it. Staff may also agree a short routine to review the weekly summary and log why an idle unit is idle, such as damage or seasonal demand.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.