Skip to main content
MapTrack

Test & tag register

One register for every tested item: interval, last result, tag and certificate on the asset, with due and overdue lists you can actually send someone out with.

Lachlan McRitchie

Lachlan McRitchie

GM of Operations

Updated 3 September 2026
Start free trial

Trusted by construction, mining and field service teams

Saunders InternationalMineral ResourcesSupagasHacer GroupMetro TunnelUltrabuilt
Rated 4.9 out of 5 on G2Rated 5.0 out of 5 on Capterra15 reviews on G2 · 17 reviews on CapterraCapterra Best Value 2026 badgeCapterra Best Ease of Use 2026 badge

The interval belongs to the environment, not the item

This is the part spreadsheets get wrong, and it is why a register held on the assets behaves differently to one held in a sheet. AS/NZS 3760 recommends in-service testing intervals according to the environment the equipment operates in, while other standards or state rules may set additional requirements. The same extension lead can sit on a short interval on a construction site and a long one in an office, because the risk of damage belongs to where it lives and how it is treated, not to the lead. A spreadsheet row carries one due date, so when equipment moves between a yard, a site and a workshop, that date can quietly stop being right. Holding the history, location and interval on the asset makes the change visible so the interval can be reviewed. MapTrack does not choose or recalculate it for you.

  • Practical consequence: Ask "what is overdue at this site" and the answer is a filter, not a reconciliation of three sources.
  • What we do not do: MapTrack does not decide your intervals or certify the testing. It holds the interval you set and the result your competent person records.

Why the register should outlive the contractor

Most teams do not do their own testing, which is fine, but it creates a failure that only shows up at handover. If the register lives in the testing contractor's system or spreadsheet, changing contractor means losing the history. The new contractor starts from whatever tags are physically on the equipment - a partial and undated picture - so the first round after a change is a re-baseline rather than a test. Keeping the register on your own assets means the contractor supplies results into your record. You change who does the testing without changing where the evidence lives.

The problem

Test and tag falls apart in the gap between the test and the record. The testing itself is usually done well. What goes wrong is afterwards: the tag is on the tool, the result is in a contractor's spreadsheet, the due date is in someone's calendar and the certificate is in an email. Nobody can answer 'what is overdue at this site' without rebuilding the register from three sources, so the honest answer becomes 'we think we're fine'. And when an item moves site, the interval that applied to it usually does not move with it.

How MapTrack addresses it

MapTrack holds the register on the assets themselves. Each item carries its testing interval, its last result, its tag and its certificates, so the due date is a property of the item rather than a row someone maintains separately. Scan a QR or barcode label to open the record and log the result on the spot. Filter by due date and site to produce the round before a tester goes out, not after. When an item moves between sites, its history moves with it and its interval stays visible for review against the new environment. The same register holds your other recurring compliance work - fire equipment, calibration, lifting gear, pre-starts - so electrical testing is not a separate system with its own login.

How it works

  • 1

    Get the items into the register

    Add each tested item as an asset with its last test date, its interval and its certificate. Bulk import if you are starting from a contractor spreadsheet.

  • 2

    Label and scan

    Put a QR or barcode label on the item. Scanning opens its record, which is what makes a testing round fast instead of a typing exercise.

  • 3

    Record the result where it belongs

    Log pass, fail, date and tester against the asset. A fail stays visible on the item until a later pass sits above it.

  • 4

    Work the due list, not the calendar

    Filter by next due and site to produce the round. Due and overdue alerts mean the list comes to you rather than being remembered.

What the register actually holds

Each of these sits on the asset, so the item and its compliance history stay together.

Interval and next due date

Set per asset, so equipment in a hostile environment can carry a shorter interval than the same item in an office.

Results and history

Pass, fail, date and tester, in sequence. A fail stays visible until a later pass sits above it.

Tags, certificates and documents

Attach the contractor report or certificate to the item it belongs to instead of a shared folder.

Asset documents & certificates

Due and overdue lists by site

Filter to produce a testing round before someone drives out, not a report after they get back.

Why teams move test and tag off a spreadsheet

The history follows the item

Location and interval stay on the asset, so a move can trigger a deliberate interval review without losing the testing history.

Scan instead of type

A QR or barcode label opens the record. On a round of a hundred tagged items that is the difference between an afternoon and a day.

One register across sites

Filter by site to see what is due where, without maintaining a sheet per location.

Same system as your other recurring checks

Fire equipment, calibration, lifting gear and pre-starts run on the same register rather than four separate ones.

Other recurring compliance run on the same register

Calibration tracking

The same interval-and-certificate shape, applied to measuring equipment.

Explore

Bulk inspections & testing

Planning and running whole testing rounds across sites rather than item by item.

Explore

Fire equipment inspections

Monthly and annual fire equipment checks on the same register.

Explore

The instruments this recordkeeping sits under

In-service electrical testing intervals, competent-person requirements and the records you have to keep are set by the instruments below, not by MapTrack. We support the recordkeeping; the testing and the compliance judgement remain yours.

Check the current source

MapTrack keeps the records these standards ask you to keep. It does not certify your work or make you compliant, and the current text of each instrument is the authority.

Track every tagged item automatically

Full access to every feature. No credit card required. Per-asset pricing so you scale as your fleet grows.

Start free trial
  • No credit card required
  • 30 days free trial
  • Cancel anytime

Frequently asked questions

The interval depends on the jurisdiction, the work and the environment the equipment operates in. AS/NZS 3760 provides recommended intervals, while construction work and some state regulations add or replace requirements. A workshop is treated differently to an office because the risk of damage comes from how and where the equipment is used. MapTrack keeps the item, its location, its testing history and the interval you set together, but it does not select or recalculate the interval when equipment moves. Check the current rules and standards for the environment in question.

Yes. Each item is an asset with its test results, tags, certificates and due dates attached. You record when it was tested, by whom and the outcome, and the history stays on the asset rather than in a folder somewhere else. Expiry alerts remind you when the next test is due.

Record the fail against the asset and take it out of service. The value of holding it on the asset is that the next person who scans that item sees the fail and the date, instead of finding a missing tag and guessing. When it is repaired and retested, the pass sits above the fail in the same history, which is the sequence an auditor is actually looking for.

You can put QR or barcode labels on assets and scan to open the record, which is what most teams doing a testing round use because it removes the typing. You can also search by name or ID. Both work; the scan is faster when you are moving through a room of tagged items.

Yes. Filter by next test due, site, type or status, so you can pull the list of what is due at one site before a tester goes out rather than after. That list is the practical output of a register: it turns a compliance obligation into a route.

The test results and certificates attach to the asset, so the evidence for a given item is its own history rather than a reconstruction. Filter to a site or a date range and you have the register for that scope. MapTrack keeps the records; it does not certify the testing or confer compliance, which remains the responsibility of the competent person who did the work.

Yes, and it is the more common arrangement. The contractor does the testing; you keep the register. Give them access to record results directly, or record their results against the assets afterwards and attach their report. Either way the register stays yours, which matters when you change contractors and their spreadsheet leaves with them.

Explore

Related use cases

Go digital with test and tag

Join construction, mining and field service teams across Australia.

Start free trialBook a demo
G2 4.9 out of 5 stars4.9 on G2 · 5.0 on CapterraCapterra 5.0 out of 5 stars
  • No credit card required
  • 30 days free trial
  • Cancel anytime

Compliance · AS/NZS 3760 test and tag record template · Test and tag checklist template · Pricing

Start free trialBook a demo