Frequently asked questions

Accounts are created by a Super Admin inside your organisation's workspace. There is no public sign-up, so the fastest route is to ask whoever administers RampWorks where you work. If your organisation does not have a workspace yet, request access from this site.

An administrator can reset it from Workspace setup without needing to know the old one. Once you are back in, change it to something only you know from the account menu in the top bar.

The sign-in guard steps in after repeated failed attempts on an account. It is working as designed. Wait rather than continuing to guess, or ask an administrator to reset the password.

Module visibility comes from your role. If the navigation entry is absent entirely, the role does not grant it — an administrator can add it in Workspace setup → Roles & access.

Account deletion is handled by your workspace administrator, and there is a public request route as well. See the account deletion page for the process.

My day shows only work orders assigned to you by name. Work sitting in a station pool, unassigned, appears in Work orders until somebody allocates it. Ask a supervisor to assign it, or pick it up from Work orders if your role allows.

Check the filters first — station, status and work type persist while you move around the module, and Clear filters resets them all. If it is genuinely gone, check whether the record belongs to a station outside your scope.

Counters respect station scope. Two accounts with different station access legitimately see different totals for the same fleet.

Provider accounts are scoped to work rolled out to their own company. In-house work and work rolled out to a different provider are invisible by design.

Checklists populate from the library based on the work type and asset type pair. If no items are mapped to that combination, nothing populates. Either map items in the checklist library, or add ad-hoc items to the individual work order.

Add it as an ad-hoc item on that work order. Ad-hoc items are reusable and are tracked separately from the library, so a one-off does not become a fleet-wide standard by accident.

Complete means the work is done. Closed means the record is finalised and no longer active. Operations differ in where they draw that line — agree it once with your supervisors rather than per technician.

Waiting materials. It exists precisely so a blocked job is visibly blocked in reporting rather than quietly running overdue.

Work orders carry a version stamp, so a second save against a stale version is refused rather than silently overwriting the first. Reload, re-apply your change and save again.

Yes. Operational modules export to Excel and PDF, work orders also export to CSV, and reports produce an executive PDF alongside detailed Excel. Exports carry the filters currently on screen.

Assets, work orders and checklist items all import from XLSX or CSV against a template you download from the module. Imports upsert, so a corrected sheet can be re-uploaded without creating duplicates.

Because it carries your on-screen filters. That is usually what you want; when it is not, clear the filters before exporting.

Reports are computed from the records in your workspace, so the history is as deep as your data. The created-versus-completed trend shows the last eight calendar months.

Stations, then roles, then provider companies, then reference values, then the asset registry, then the checklist library, then PMI groups, and user accounts last. Each step depends on the one before it.

A result of all-skipped means every matching asset already has its due work order. That is the normal steady state, not a failure. Generation is idempotent, so running it again is always safe.

Yes — the generation operation is designed to be called on a schedule for unattended nightly running, so due work appears in queues without anybody remembering to press the button.

No. Work orders keep the items they were created with, so past results stay intelligible. Roll changes out at the start of a period rather than mid-cycle.

Yes. Stations, provider companies, roles and reference data are workspace-owned, and tenant branding is configuration. Multi-station operation is the normal case, not an add-on.

Both, from one codebase. A responsive web application, plus native iOS and Android builds created with Capacitor. The feature set is the same on all three.

No. The client reads and writes through the API in real time, so a working connection is required. In a dead spot, record the work once you are back in coverage.

Native builds are distributed by your organisation rather than found by searching a store. Your administrator will send an invitation. In the meantime, adding the web app to your home screen gives you the same thing.

Entries are attributed to whoever is signed in, so sign out at the end of a shift. Otherwise the next person's work is recorded under your name.