Clients and Jobs

Clients and jobs at https://rotorlab.app/jobs answer the question the flight record alone does not: who the flying was for. Name a client, open a job for them, and pick that job when you file a flight. From then on the hours on the job are the hours of the flights that name it, never a figure anybody typed.

This is not an invoice. RotorLab records what was flown for whom; it does not price it, bill it, or decide what is chargeable. A job carries no rate and no money total.

Cards at the top count Open jobs, Clients, Flights on a job, and Hours on a job.

The dashboard#

Below the cards the page opens on the shape of the year, all of it counted from the flights.

Work over the year plots the last twelve months. Each bar is the hours flown that month; the solid part of the bar is the hours booked to a job and the pale part is everything flown. The line across the bars is the flight count, read against the right-hand scale, so a month of many short sorties looks different from one long survey. Hover a bar for the exact figures. Every month in the window is drawn whether or not anything flew in it, so a quiet quarter shows as a gap rather than a straight line.

Wants a decision lists jobs that are past their end date and jobs with nothing flown on them yet. Both are ordinary states, not faults: a job can legitimately run long or be booked months ahead. The card is hidden when there is nothing in it. Each entry opens the job.

Jobs by status counts every job on the books at each of the four statuses.

Where the work comes from ranks clients by hours flown, with each client's share of the total. Busiest first.

The job page#

Open a job by its title, or with Open on its card. The job page carries, in one place: its status, client, reference, site and dates; the flights, hours, aircraft and pilots on it; the scope of work as your client will read it and your internal notes; a month-by-month chart of the flying on this job alone; which aircraft flew it and who flew them, ranked by hours; and every flight against the job, with the airspace each was flown in as it was recorded at the time.

The buttons at the top produce the client deliverable and open the logbook filtered to this job.

The client page#

Open a client by name, or with Open on their card. The client page carries their contact details and reference, the jobs count with how many are open, their flights and hours, a month-by-month chart of the flying across all of their jobs, which aircraft and pilots do their work, every job for them with its own totals, and their recent flights. Each job opens the job page; each aircraft and pilot opens that record.

Creating a client#

Press Add a client and fill in Name, Contact, Email, Phone, Reference, and Notes. Client names are unique within your organization, so a name means one thing on the list. A search box filters the client list, and each client card shows its job count, flight count, and hours across all of its jobs.

Deleting a client keeps its jobs; they simply stop naming a client. Flying hours are never deleted through a customer record.

Creating a job#

Press Add a job:

Title: what the work is, for example "Route 9 corridor survey".
Client: pick one, or leave the first option selected for internal work with no client. Training and test flights are real work with nobody to bill, so a job never requires a client.
Reference: the client's PO number or your own job number. Jobs are searchable by it.
Site: where the work is.
Status: see the flow below.
Starts and Ends dates.
Scope of work: what this job covers, in your words. This is printed on the flight record your client reads; leave it empty and the report simply omits the section.
Weather: tick to include the conditions each flight was flown in on this job's report. The report reads what was recorded with the flight at the time, never looked up again later, so it says what the weather was, not what it is now. A flight with nothing on record prints so plainly.
Notes: internal, never printed on the report.

Deleting a job keeps its flights; they stop naming a job. The job's photos are removed with it.

Job status flow#

A job is in one of four statuses: Quoted, Open, Complete, or Cancelled. Quoted exists because operators plan flying for work they have not won yet, and those flights still happened and still count. The job list sorts finished work (complete and cancelled) below live work, and a status filter and search box narrow the list.

Linking flights to jobs#

When you file a flight in the Pilot Logbook, the Job field offers every open and quoted job. A finished job is no longer offered for new flights, but a flight already filed against one keeps it, so a late correction to a closed job stays possible.

Each job card shows its derived totals: flight count, hours, and the first and last flight dates. The Flights button on a job card opens the logbook filtered to that job, and Open opens the job page.

The client deliverable#

Every job card has two export buttons:

Flight record (PDF): the printable flight record for the client.
Text: the same record as plain text, for anyone who wants the numbers without a PDF.

The record states the operator, job title, reference, client, site, status, and scope of work, then one line per flight (date, aircraft, pilot, time), with per-flight weather lines when the job's weather option is on. The figure at the bottom is the sum of the lines above it, so a client can check it rather than take it on trust. Use Branding & logo to put your own branding on the document.

Photos on the report#

The Photos button on a job card opens the job's photo sheet. Add photos uploads images; location and camera metadata is removed from every image on upload. Tick Include in report on each photo you want in the client's flight record, and add a caption. Nothing is included unless you tick it.