Guide · Start here

Getting started

What to do in your first ten minutes, whether you have just been given an account or you are standing a whole workspace up from nothing.

Your first sign-in

  1. Sign in with the credentials your administrator issued

    RampWorks uses a username and password — there is no self-service sign-up, because access is granted per organisation. If you do not have credentials, the person who administers your workspace issues them.

  2. Expect extra verification after repeated failures

    The sign-in guard steps in after several failed attempts on an account. This is deliberate and it is not a fault; wait, or ask an administrator to reset the password rather than continuing to guess.

  3. Change the password you were given

    Open the account menu in the top-right and choose the password option. Setting your own password immediately means the credential that travelled to you by email or message stops being valid.

  4. Check your name and scope

    The same account menu shows your display name, role and station scope, and lets you correct the display name. The scope is what decides which records you can see anywhere in the workspace.

Finding your way around

  1. The sidebar is grouped, not alphabetical

    Navigation is organised as Overview, Operations, Fleet & supply and Administration. You will only see the groups your role has modules in, so a shorter menu than a colleague's is normal.

  2. On a phone, the bottom bar carries the essentials

    Mobile shows a bottom tab bar with Home, My Day, Orders and Checks. The full menu is behind the hamburger in the top-left.

  3. Command centre for the picture, My day for the work

    If you supervise, live in the command centre. If you turn spanners, live in My day. Almost nobody needs both open at once.

  4. Filters are consistent everywhere

    Station, date range, type and status behave the same in every module, and Clear filters resets them. What is on screen is also what an export contains.

Standing up a new workspace

This is the administrator path. The order matters: each step depends on the data created by the one before it, and doing them out of sequence means going back to re-point records.

  1. Stations first

    Create every station, with its country. Station access is assigned per user, so the stations have to exist before accounts can be scoped to them.

  2. Roles second

    A role is a named set of visible modules plus a provider flag. Build the three or four roles your operation genuinely has — technician, supervisor, administrator, provider — rather than tuning access per person.

  3. Provider companies third

    If contractors do any of your maintenance, create each company and list the stations it covers. Provider accounts then see only work rolled out to their own company at those stations.

  4. Reference values fourth

    PM types, asset types, fuel types and locations populate dropdowns across every module. Asset types carry the checklist key that decides which inspection each asset receives — this is the one to get right.

  5. The asset registry fifth

    Download the asset template, fill it from your current register, and bulk upsert. The import updates rather than duplicates, so a corrected sheet can be re-uploaded safely.

  6. The checklist library sixth

    Import your inspection items and map each to a work type and asset type pair. From this point on, every new work order and health check populates its own checklist.

  7. PMI groups seventh

    Define recurring maintenance per asset type, with a frequency, a start date and a service sequence. Stagger the start dates so generation does not land the whole fleet on the same day.

  8. User accounts last

    Now that roles, stations and providers exist, create the accounts against them. Grant the narrowest station list that lets someone do their job — widening later is a two-click change.

Where to go next

See 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.