BaseLeap FS

BaseLeap FS, in detail.

Work orders, dispatch, the offline field app and the invoice at the end of it. Each area below is in the product today; the pictures are close-ups of the screens and of the components they are built from.

Get Started Back to field service
01

Work orders

One order carries the whole job, from the first call to QA and the invoice.

Every job is a service order with its own stage path, so the office always knows what is booked, in progress or waiting on QA. Checklists, time, parts, quotes and invoices all hang off the same record, and nothing about the job lives in a side note or somebody's inbox.

  • Field Service and Mechanical Service record types
  • A stage path with a QA gate before completion
  • Checklists, time & materials, quotes and invoices on the order
  • Multi-day jobs shown on every day they span
  • Full field history and activity
02

Scheduling and dispatch

Who is going, when, and what happens when it changes.

The dispatch board lays the crew out by service stream and trade across the week, with their rostered days and utilisation. Unassigned work waits in a tray until someone drags it onto a day, and every change lands on the technician's phone.

  • Timeline, calendar, by-client and My Day views
  • Unassigned tray with drag-to-assign or quick assign
  • Rostered days, rest days and leave on the board
  • Capacity and utilisation per technician
  • Hire deliveries and collections on the same board
03

The field app

A phone-first app the technician works in, even with no signal.

Technicians see My Day, open the job, clock on, work through checklists, add parts and photos and get the customer to sign. Everything queues on the phone in a dead zone and replays in order when coverage returns.

  • My Day, the job, the asset and its history
  • Checklists, parts, photos and a drawn signature
  • Clock on and off against the order
  • Works offline and replays in order
  • Pricing hidden from the crew
04

Resources and compliance

Who you can send, and what happens when a ticket lapses.

Every technician has a resource record with their skills, rates, roster and the tickets that let them on site. Expiring certifications raise reminders before they lapse, and incidents and investigations are records rather than emails.

  • Skills and levels with charge-out rates
  • Tickets and certifications with expiry reminders
  • Restricted access for field technicians
  • Cases, incidents and corrective actions
  • Job categories and checklist templates
05

Sites, assets and maintenance

The place, the thing in it, and what it is due for.

Sites carry their address, map pin, manager and the equipment on them. Each asset can carry several maintenance regimes, each with its own interval and service stream, and the next service rolls up onto the asset automatically.

  • Site records, geocoded onto a map
  • Many maintenance regimes on one asset
  • Intervals by date or by hours and kilometres
  • Service history and certificates on the record
  • Several assets, each with its own report, on one job
06

Quoting, cost and invoicing

What it was quoted at, what it cost, and what the customer is billed.

Quotes break out labour, materials, equipment and charges. Parts bought at the counter go on a purchase order against the job, and the invoice is built from the hours and parts actually logged, with the client's PO checked before it goes out.

  • Quotes with labour, materials, equipment and charges
  • Purchase orders raised against the job, approved
  • Charges, variations and signed adjustments
  • The client's PO required before invoicing
  • Invoices and payments

Ready when you are.

Create an account, or sign in and pick up where you left off.

Get Started → Sign in