How 4fleet is organized: requests, bookings, jobs and stops

Four levels, one word each

Every piece of work in 4fleet sits on one of four levels, and the app uses one word for each.

A request is what a client sends in one go. One email asking for an airport pickup on Friday and a return on Sunday can become two sibling enquiries; together they are one request.

A booking is the commercial record the client pays for. It is priced, confirmed and invoiced, and it is the word the client sees on their confirmation and their invoice.

A job is one piece of driving inside a booking. A return transfer is one booking with two jobs.

A stop is a point inside a job: the pickup, any stops on the way, and the dropoff.

Why the job carries the driver, vehicle and price

Each job has its own driver, vehicle, partner, fare, service and flight number. That matches how the work is done: the Friday pickup and the Sunday return can have different drivers, different vehicles, and a different partner if you hand one of them out.

Because of this, you assign drivers per job, a driver is briefed per job, and a partner is paid per job. When you open a booking, the Jobs list is where most of the operational work happens. When the same order grows, for example a client adds a return, use Add job on the booking rather than creating a second booking.

Who pays and who performs

The client is whoever pays. The driver is whoever drives. They are often different people: an assistant books for an executive, an agency books for a traveler.

The Covered by field tells you who performs a job: your Own fleet, or a partner. Read it before you look at margin, because a job covered by a partner has a partner cost against it.

The words your clients see

Your office, your drivers and your partners all read "job". Clients never do. On the client portal and on quotes, invoices and confirmations, one job is called a journey, and the booking is still a booking. If a client asks about "the second journey", they mean the second job.