Fleet and Boat Records
Why boat records matter, what information they control, and how availability and service work fit together.
The fleet area is the shared record of every boat the company operates. It is used by booking, check-in, pricing, maintenance, member information, and reports. A wrong value here can therefore affect several parts of the service at once.
What a boat record is for
A boat record answers five practical questions:
- What is this boat? Name, identifier, model, images, and description.
- Where does it belong? Company, region, location, and boat type.
- Can members book it? Active state, category, and booking-related settings.
- How should it be operated? Engine, dimensions, checklists, and member guidance.
- Does it need attention? Open issues, service visits, and monitoring data.
The record is not just an inventory card. It is the link between the physical boat and every trip made with it.
Adding or changing a boat
Use the main boat form when a boat enters the fleet, moves to another location, changes its public description, or receives updated operating information.
The information falls into four groups:
| Group | Why it matters |
|---|---|
| Identity and ownership | Prevents operators and members from confusing similar boats and keeps the boat inside the correct company and region. |
| Member-facing information | Helps a member decide whether the boat suits the trip and understand it before arrival. |
| Technical information | Supports safe operation, service decisions, fuel and engine-hour tracking, and reports. |
| Booking settings | Determines where and how the boat appears in availability searches and booking flows. |
Typical fields include the boat name and code, company, location, type, description, photos, dimensions, engine details, fuel information, checklists, and links to external monitoring.
Active and inactive boats
An active boat is part of normal operations. An inactive boat is kept in the system for history but should not be offered as ordinary available capacity.
Deactivate a boat when it leaves service for a meaningful period, is sold, or should no longer be booked. Do not deactivate it merely to hide a short service visit if the operating process uses calendar blocks or service check-ins for that purpose.
Before deactivation, check future bookings. Hiding the boat does not by itself move or cancel trips already promised to members.
How saving affects the wider system
When an operator saves a boat, the new information becomes the basis for later availability checks, booking screens, member instructions, and reporting. A change of company, region, location, or type has a wider effect than editing a description or photo.
After a major change, verify:
- the boat appears under the intended company and location;
- future bookings still point to the correct boat;
- the member-facing information is complete;
- open service issues and historical trips are still visible;
- any external monitoring identifier still refers to this physical boat.
Boat issues and service visits
Each boat can have two related but different kinds of operational information:
- Issues describe damage, a defect, or another problem that needs attention.
- Service check-ins describe a period when the boat is being inspected or worked on.
An issue explains what is wrong. A service check-in explains when and why the boat is in service. Closing one does not automatically prove that the other is complete.
See Maintenance and “Frogs” for the full workflow.
Monitoring and measured values
Some boats are connected to external fleet monitoring. The platform can use that connection to show values such as position, fuel level, or engine data. These readings help operators investigate a situation, but they do not replace the saved check-in/check-out record or a physical inspection.
If a reading looks wrong, first check when it was recorded and whether the boat has the correct external identifier. A missing reading is not the same as a measured value of zero.
Common mistakes
| Mistake | Why it causes problems |
|---|---|
| Reusing one record for a replacement boat | History and monitoring from two physical boats become mixed. |
| Moving a boat without checking future bookings | Members may still be told to collect it from the old place. |
| Treating “inactive” as a cancellation tool | Existing bookings remain separate records and need their own decision. |
| Closing an issue without checking the service visit | The defect record and the work period can disagree. |
| Entering zero for an unknown measurement | Reports cannot distinguish “not known” from a real zero. |
Technical reference
The admin form and actions live under admin/templates/resources and
admin/js/actions/resources.js. The Symfony admin API groups boat operations
under /api/v1/resources, including availability, measured values, check-ins,
issues, service information, and activation checks.