FleetPoynt turns the vehicle lists you already keep into one clean, searchable register — duplicates flagged, and a human in control before anything is saved. It then keeps that register living: a log book behind every vehicle, and a reminder before anything lapses.
An entry made the day of the trip and an entry made three weeks later are not the same evidence. FleetPoynt marks the difference on the face of the record — permanently, and without a word of judgement. You can still backfill. Paper fleets always do. It just cannot pass as something it is not.
Three jobs, in the order a transport office actually does them. All three are running in the product today.
Upload the CSV or Excel file you maintain today — or a PDF or Word register, so long as its text is selectable. FleetPoynt reads the structure, maps your columns onto fleet code, plate and chassis, and drafts entries. History transcribed at import is marked migrated, never passed off as newly recorded.
Exact matches, probable matches, duplicates, incomplete rows and genuinely new vehicles, separated and scored — with the differences against the existing record named. Nothing reaches the register until a person says so, one decision at a time.
Six log books behind every vehicle file, each entry carrying its provenance mark. And FleetPoynt prints the blank job cards and movement sheets your drivers actually write on — pre-printed with the fleet code and the right columns.
Twenty vehicles, or three hundred. A transport officer who is personally accountable when the auditors arrive, and custodians who hold one vehicle each and want to know when it is next due for service.
Five screens from our demo organisation — the register, the import queue, a vehicle file, a log book and the printed output. This is the same FleetPoynt you would sign into on day one of a pilot.
Fleet code first — it is painted on the door and survives a plate change. Plate second, because that is what the police read.
The uploaded row against the existing record, the differences named, and a confirm step a person has to press.
Identity, custodian, service position, tyre size, and the log books stacked behind it.
Movements, fuel, maintenance, insurance, statutory papers and disposals. Every entry carries when it was written down.
The register on paper, with the signature block the rest of the office already works in. Printed, signed, filed.
No — because the surface they get is deliberately tiny. A custodian sees one vehicle: its fleet code, its tyre size, their driver’s number, and when it next falls due for service on both days and kilometres. That is the whole thing. A custodian who can see their own service-due date is one who stops ringing the office to ask.
We agree what success means in week one, and check it against the same definition in week four. Any fleet size. Your data stays yours.
Your workspace, the vehicle register, roles for the transport office and for custodians, and the import structure — mirroring how the office is already organised.
The vehicle list you already keep, in whatever shape it is. Bring the bound book pages and any certificates too, and we will transcribe them with you during the pilot.
Importing the list, resolving duplicates, confirming matches, logging a week of movements, and printing the blank sheets your drivers write on.
One clean register, a vehicle file per vehicle, and a Monday-morning “needs attention” list your officer actually uses.
A printed monthly report for your director — and your register, exported, yours to keep either way.
FleetPoynt implements Chapter 20 of the Financial Regulations, 2009 edition — the edition in force. A draft revision, published by the Accountant-General’s office, would go considerably further.
We would rather point at the source than characterise it. The document is public and says “DRAFT” on its own title page.
Source: Draft Federal Government Financial Regulations 2023, Office of the Accountant-General of the Federation. In-force edition: Financial Regulations (Revised to January 2009), Official Gazette No. 72, Vol. 96, 27 October 2009.
The auditor never logs in, and that shapes everything. So does the fact that the transport officer is the one personally accountable when they arrive.
Credibility in this market comes from what a product refuses to claim. Being caught overclaiming once ends the sale.
The ledger, the spreadsheets, the drawer of certificates. Thirty days from now it is one register, with a printed report you can put in front of your director.
