The job is the record
A work order carries its own checklist, defects, materials, labour, meter readings, signature and audit history. Nothing important lives in a separate spreadsheet, because there is no separate spreadsheet.
Ground support equipment maintenance
Every work order, check and refuel — in one operational workspace.
RampWorks runs GSE maintenance for airport ground handlers and fleet teams: work orders, daily health checks, refuelling, preventive maintenance, inventory and reporting, in one API-backed application for web, iOS and Android.
- Role, station and provider scoped
- Excel and PDF export throughout
- Multi-station, multi-tenant ready
- 11Operational modulesFrom the ramp check to the board report
- 3Platforms, one codebaseResponsive web, iOS and Android
- 8Work-order statesA stalled job is visibly stalled
- 3Layers of access scopeRole, station and provider
Why teams move onto it
Maintenance falls apart between the systems, not inside them.
A defect found on a whiteboard, a job tracked in a spreadsheet, a fuel log in a notebook and a report typed up at month end. RampWorks closes those gaps by making one record carry the job from discovery to evidence.
Defects become work, immediately
A failed item on the morning health check links straight to a work-order number and a repair date. The gap between finding a fault and tracking it stops being where things get lost.
Scheduled work schedules itself
PMI groups generate due work orders for every matching asset, idempotently. Run generation twice, or nightly from a scheduler, and the fleet is never double-booked.
Contractors see their work, and only theirs
Service-provider accounts are scoped to work rolled out to their company at the stations they cover. You get contractor visibility without handing over the whole workspace.
Reports built from live records
Created versus completed over eight months, status distribution, fleet risk and fuel consumption — all computed from what the crews recorded today, not from a monthly re-key.
Made for a device in a gloved hand
The same workspace runs as a responsive web app and as native iOS and Android builds, with a bottom tab bar and touch targets sized for the apron rather than a desk.
The workspace
11 modules, grouped the way a shift actually runs.
Navigation is grouped into overview, operations, fleet and supply, and administration. What each account sees is decided by its role, so a technician gets a queue and an administrator gets the whole board.
Overview2 modules
Operations4 modules
Work orders
Plan, allocate and complete maintenance work.
Explore the moduleRefuelling
Fuel entries per asset, per day, with a matrix report behind them.
Explore the moduleDaily health checks
The pre-use inspection, captured where the defect is found.
Explore the modulePreventive maintenance
Define recurring PMI groups and generate due work orders.
Explore the moduleFleet & supply2 modules
Administration3 modules
Checklist library
Reusable inspection steps by work and asset type, with change history.
Explore the moduleReports & insights
Operational performance, fleet risk and resource trends from one live view.
Explore the moduleWorkspace setup
Control people, locations, access and operational master data.
Explore the moduleA day on the ramp
One defect, followed from 05:45 to the month-end pack.
Nothing below is re-keyed into a second system. Each step writes to the same record, which is why the report at the end is trustworthy.
- 05:45
Pre-use inspection
A ramp operator opens Daily health checks, scans to the belt loader by its GSE number, and works the inspection list mapped to that asset type. Item four fails.
Guide - 05:52
Defect raised as work
The check is marked unserviceable with a note. A work order is raised against the same asset and its number is recorded on the health check, so the clock on that defect is now running.
Guide - 07:10
The technician picks it up
My day has the job at the top of the queue — overdue and due-soon work sorts first. The technician works the checklist on the phone at the equipment.
Guide - 11:30
Parts, labour, signature
Two parts are recorded on the Materials tab, drawing stock down in Inventory. Labour hours go on, the completion signature is captured, and the status moves to Complete.
Guide - 16:00
The supervisor closes the day
The command centre shows overdue down by one. Nobody typed a status update anywhere — the number moved because the work moved.
Guide - Month end
The pack writes itself
Reports filters to the station and period, and exports an executive PDF and detailed Excel. The compliance evidence is the same records the crews created.
Guide
In the app
Built to be read at arm's length, on a bright apron.
The same interface scales from a phone in a hi-vis pocket to a supervisor's desktop. These are real screens from the shipping application.
Access model
People see the work that is theirs.
Access is decided in three layers that combine, rather than one role list that has to anticipate every case.
- Role — a named set of visible modules, defined once and applied to accounts.
- Station — each account carries the stations it can see; records outside them are invisible.
- Provider — provider accounts are further narrowed to work rolled out to their own company.
- Administration — account creation is reserved for Super Admin, because granting access is granting everything.
Getting started
Three steps to a working workspace.
01
Set up the workspace
Stations, roles, provider companies and reference values — the master data every other module draws on.
Setup guide 02Load the fleet
Bulk upsert the asset registry from a spreadsheet against the supplied template, then set asset types correctly.
Asset guide 03Define what "inspected" means
Import the checklist library, map items to work and asset types, then let every future job populate itself.
Checklist guideSee RampWorks against your own fleet
Tell us how many stations and how much equipment you run, and we will walk the workspace through your operation rather than a demo dataset.