For rental and fleet operators

A rental or fleet operation is the opposite of a walk-in repair shop. You know exactly which bikes are coming, because you own them or you are contracted to maintain them. The work is not mysterious. It is the same pre-rental check, the same monthly inspection, the same brake pads and tires, on thirty or eighty bikes that look alike and differ only by a number on the top tube.

The hard part is keeping track. Which bikes are due this week? Which one was pulled from the line on Saturday with a soft rear brake, and did anyone fix it? Did every bike on the corporate campus get its quarterly inspection, and can you prove it to the facilities manager who asks? A bike-share operator or a corporate fleet contract often requires a signed inspection record for every bike on every visit, and a missing one is a contract problem.

On a busy rental weekend, the pressure is at the counter: bikes come back, get a quick check, and go out again. A bike with a problem has to be caught at check-in, tagged out of service, and not rented again until it is fixed.

For a fleet, the inspection record is the product. It is what the contract pays for and what protects you when a renter has a crash. Service checklists handle this today. Build a template for each kind of check, make the fleet number and the key safety questions required, and add photo questions for damage. Every submission is stored against its template version, so a record from March still reads correctly after you add a question in June.

The checklists report pulls every inspection of one template for a date range, with one column per question, and exports it as CSV. For a corporate fleet contract, that is the monthly proof: every bike number, the date, the result of each check, and who did it. Because columns are keyed by question and not by label, a template that asks two questions with the same wording still exports cleanly.

Rental agreements and waivers are a separate job, done in the Sign module, which is live today.

Today a fleet contract can be one job at the customer's site with a visit for each inspection date. The dates are typed in, one per line, when you create the job, and each visit lands on the week schedule with a mechanic assigned. Attach the inspection checklist and mark it required, and no visit can be closed until the inspection is submitted. That covers a season of monthly visits, but it is not a repeat rule, and adding next season means typing the dates again.

The Service plan includes true recurring jobs, with visits created on a repeating schedule and the ability to update every future visit at once. It also includes equipment records with serials and service history. Put together for a fleet, that becomes a record per bike and a monthly inspection that appears on the schedule for each one automatically, with the last result visible on the bike's record. Both are on the roadmap and not built yet.

The plan also has fleet features for your own service vehicles: vans, assignments, maintenance schedules, inspections and telematics connections. Those are for the vans your mechanics drive, not the bikes you rent, and they are on the roadmap too. For now, a fleet's own bikes are best tracked by fleet number on the inspection checklist.