MapTrack frequently asked questions

MapTrack is asset tracking, maintenance and compliance software for teams managing tools, equipment, plant and fleet. It brings QR identification, asset assignments, digital forms, work orders, audits and maintenance records into one installable web app for phone, tablet and desktop.

Setup time depends on the quality of your existing data, the label rollout, the workflows you need and the number of people involved. Start with one asset class or site, import the register, configure roles and labels, test one field workflow, then expand after the first crew is working reliably.

MapTrack is an installable web app, not a separate App Store or Google Play download. Open MapTrack in a supported phone browser, sign in, then use the browser installation action described in the phone guide.

Current product guidance documents the Primary Owner plus Admin, Field User, Viewer / Scanner and Form Submitter. Choose the least access each person needs and test the exact workflow before a wider rollout.

Use CSV or XLSX for the supported import workflow. A Field User or Admin with access to the import route can run an import. Admin access is needed when custom fields must be created before mapping the file.

Use categories for repeatable asset types and custom fields for the extra details your team needs to search, inspect or report on. Agree the naming rules before importing a large register so the field crew sees consistent records.

MapTrack generates QR tags. Camera and compatible keyboard-wedge scanners can resolve supported codes. Validate an existing or externally generated barcode workflow, including the code format, scanner and record-linking behaviour, before rollout.

Admins and Field Users can search the asset list and apply quick or advanced filters. A saved view stores the filter tree, not the free-text search, sort order, columns or layout. Saving or changing a view needs an internet connection.

Previously loaded forms can be submitted offline. Once a work order is loaded, crews can complete its procedures and checklists, record per-asset pass or fail outcomes, add time and costs, and move it to Completed before syncing after reconnection. Creating or first loading a work order, assignments, audits, setup, imports, exports and server-side automations need a connection. Test the exact meter-reading workflow before relying on it offline.

No. A scan identifies the asset and opens the actions available to that person. Assignment, return and audit actions are deliberate connected steps. Scanning alone does not transfer custody, complete an audit or create location history.

Assign one or more assets to a Person, a saved Location, or the supported combined person-and-location destination. Return or Reassign records when custody changes. Assignment changes need an internet connection.

Create an Audit for a Person or Location, choose the required assignee, start it and scan the expected assets. Review anything still Unscanned before completing. Skip All leaves those records unchanged; Mark Missing changes only the remaining unscanned asset records to Missing. Audits need an internet connection.

An Admin can create and publish a form for the required workflow. People with access to the relevant form can submit it, and previously loaded forms can be submitted offline before syncing after reconnection.

Not by default. An Admin can configure a form-submission automation to create a task or work order from selected results. Test the trigger, conditions and action with one controlled submission before rollout.

Current public guidance confirms notification email and Create task. Confirm any other automation action before relying on it. Automation management needs Admin access and an internet connection.

Yes, after the work order has been loaded on the device. Crews can complete procedures and checklists, record per-asset outcomes, add time and costs, and move the work order to Completed before it syncs after reconnection. Creating or first loading the work order still needs a connection.

Schedules can use time or meter triggers. Choose the generation mode when configuring the schedule: manual, automatic per asset or automatic batch. Confirm schedule baselines, trigger behaviour and work-order defaults with a controlled test before a large rollout.

An Admin or Field User can create a meter. A person with access to the selected asset or location can record a reading against it. Before an offline rollout, test creating the meter, choosing the asset or location and saving the reading on the target device.

Yes. Admins can generate, name, copy, rename and delete API keys, then use the current Public API documentation for supported endpoints and request schemas. The API uses an account API key sent as a Bearer token or through the supported query-token parameter. Keep real keys out of screenshots, examples and support messages.

A user in an already configured SSO workspace can open MapTrack's SSO sign-in page, enter their work email and continue to their organisation's identity provider. Confirm provider support, provisioning, role mapping, enforcement and setup ownership before procurement or rollout.

MapTrack provides a public API and can surface GPS or telematics data where a specific device or integration has been configured. Integration availability and delivery scope vary. Confirm the exact OEM, accounting or business-system requirement before planning a rollout.

Confirm the security controls, hosting location, SSO setup, identity provisioning and data-residency requirements for your procurement process directly with MapTrack. We support vendor security questionnaires and can share our current security documentation on request.

Send the exact page and action, the error text, the approximate time and timezone, your browser or device, your MapTrack role and any Support Information shown on the error page. Never send a password, API key or secret token. Do not clear device data when unsynced offline work may remain unless support has confirmed the safe recovery step.