Introduction to Site, digitised

Plant compliance, from the gate to the end of the asset's life.

Raion Ready digitises the Introduction to Site process and keeps one live record of every machine on site — using your site's own requirements, approvers and approval order.

A web application — no installs One login, every site you manage or work at
Equipment Register
North Pit · sample site
Dashboard
Equipment Register
Introductions
Approvals
Configuration
42Equipment on site
35Compliant
4Expiring soon
3In progress
EquipmentOwnerBrake testFire suppression
Haul truck 31Site ownedValidValid
Excavator 07ContractorExpiring SoonValid
Water cart 02ContractorPending ApprovalValid
Light vehicle 114Site ownedValidN/A
Dozer 12ContractorExpiredNot Started
Illustrative screens · sample data
Watch the overview

See Raion Ready in two minutes

How a machine gets from the gate to a compliant record on site — and stays that way.

The problem

Every machine on site carries a trail of approval requirements, plant safety files, records and expiry dates. Someone has to manage all of it.

Inspections, certificates, registrations and sign-offs have to be in place before plant goes to work, and kept current for as long as it stays. Run through paper packs, inboxes and spreadsheets, that creates four problems.

THE PROBLEM
WITH RAION READY
01

Approval chains are complex

Each plant type has its own requirements and its own approvers. Mechanical, electrical, planning and owner sign-offs are typically all required, often in sequence, and the whole approval chain can stall when any one person is unavailable or the paperwork is misplaced.

WITH RAION READY

Approvals that run themselves

You set who completes each requirement, who approves it, and in what order. The work routes itself electronically, in parallel where it can and in sequence where it must. If an approver is away, a stand-in can easily be nominated.

02

Nobody can see where things are up to

Is the approval with the inspector, an engineer or nobody? Which certificates expire next month? The answer is often in someone's inbox, a pigeonhole, a shared drive, or a spreadsheet only one person maintains.

WITH RAION READY

Live status for every machine

Every requirement on every machine shows a live status, including its current compliance status, who any approvals are currently with. Where each approval is up to is always live.

03

The admin load is enormous

Paper packs to chase, sign, scan and file. Registers to keep in step with the documents behind them. It's time spent on administration that adds nothing to the safety of the machine.

WITH RAION READY

Less paper to push

Requests, evidence and approvals move through one system instead of between inboxes. Contractors and inspectors upload directly against the right requirement, and once evidence is approved it's locked and filed.

04

Compliance never finishes

Every inspection, certificate and registration expires on its own schedule. Each renewal restarts the paperwork, and missing one is easy.

WITH RAION READY

Expiry calculated, not remembered

Expiry dates are worked out from the record date and your validity periods, with a warning before anything lapses. One expired certificate is renewed on its own, without re-introducing the machine.

When this lives in spreadsheets, shared drives and people's heads, the answer takes a day. It should take a screen.

See how it fits together
The plant record hub

One source of truth

Every piece of plant. Every record. Every expiry date. All workflow history.

Submits record
Flags expiry
Requests inspection
Submits evidence
One source of truth
Site plant record
  • Expiry dates
  • Record details
  • Workflow status & history
  • Site record configuration
Pending review
Approved
Flags expiry
Submits record
Submits or requests Renewal trigger Supporting evidence Approved
Responsibility where it belongs

Whoever owns or introduces the plant, is responsible for keeping its records current.

Different sites, different rules, same product

The site's configuration lives in the record too: which workflow applies, which roles must approve, and how long a record stays valid. Two sites can run genuinely different approval paths without changing how vendors, requestors or inspectors work.

See it by role

Four roles. Four views of the same record.

Pick a role to see what that person does and what they see. The full product is best seen in a walkthrough.

How it works

One system from the gate to the end of the asset's life

01

Configure

The site sets what applies to each plant type, who completes it, who approves it, and in what order.

02

Introduce

Equipment is requested, approved at the site's gateway, and registered.

03

Comply

Each requirement is routed to its completer, evidence is uploaded, and approvals are given in sequence.

04

Maintain

Live status, expiry warnings, and single-record renewals — no re-introduction.

Request lodged Gateway approval Registered Tasks routed Evidence uploaded Approved & locked
What makes it different

Flexible to set up. Regimented once it's running.

Configured, not hardcoded

Plant types, requirements, validity periods, approval chains and sequencing are all set by your administrators. Two sites in the same company can run different regimes.

"When your standard changes, you change the configuration — you don't raise a change request."

The site owns its record

Contractors keep their own fleet data, and it follows the machine between sites. The compliance record — evidence, approvals, status — belongs to the site, and a vendor can't alter it.

"The contractor keeps their fleet. The site keeps its evidence."

Approved means closed

Once evidence is approved it's locked. It can't be edited or deleted through the workflow, and superseded revisions stay in the history.

"The audit trail is the product, not a by-product."
Configuration

Your requirements. Your approvers. Your order.

The workflow sequencer holds your whole regime on one screen. Requirements with the same number run together; a higher number waits until the step before it is approved.

1
Same number runs in parallelAll tasks at that step launch together.
2
A higher number waitsIt starts once everything before it is approved.
—
N/A removes the requirement"Not applicable" and "not yet configured" are different states.
RequirementHaul truckExcavatorLight vehicle
Brake test111
Fire suppression22N/A
Isolation points221
Engineering sign-off332
Illustrative configuration for one workflow pathway
Keeping it current

Every requirement, every machine, one live status

Expiry is calculated, not remembered: record date plus validity period. A warning window — 30 days by default — turns it amber before it lapses.

Valid

Approved and in date.

Expiring Soon

Inside the warning window.

Expired

Past its expiry date.

Pending Approval

A workflow is running.

Not Started

No record yet.

Equipment is compliant when every applicable requirement is current — and you can see the exceptions without going looking for them.

Book a demo

See how Raion Ready takes a machine from the gate to its first renewal.