Fleet and logistics software, built to your operation.
Trucking fleets, 3PLs, drayage and yard operations use Genwright to build the systems that packaged software never quite fit — driver hiring and qualification, dispatch, inspections, breakdowns and settlement — on a platform that has run logistics workloads for twelve years.
Where most fleets start.
The fleet software you can buy was not designed around your hardest problem
For most fleets the hardest problem is not routing. It is getting a qualified driver seated, keeping the qualification file defensible, and knowing what a truck is doing when it stops moving.
Those three things live in different systems, or in no system at all. Recruiting runs on a spreadsheet and a phone. The driver qualification file is a folder in a filing cabinet that somebody hopes is complete. Breakdowns run on a dispatcher calling around until someone answers. Then an auditor asks for a two-year history and the whole thing has to be reassembled by hand.
A TMS will not fix this, because a TMS was built to move freight, not to prove that the person moving it was qualified to.
One spine, from application to timecard
The workforce modules are already built and already running. They connect end to end, so a document collected during onboarding is the same record an auditor sees three years later.
- 01
Applicant tracking
Applications, sources, stage movement and recruiter activity in one place, sized for high-volume hiring rather than corporate requisitions.
- 02
Onboarding
Document collection, e-signature, policy acknowledgement and equipment issue — driven from a checklist that will not close while an item is missing.
- 03
Integrated background checks
Screening ordered and returned inside the same workflow, with results attached to the applicant record rather than emailed around and re-filed.
- 04
Credential tracking
Licenses, endorsements, medical cards, training and certifications tracked per person, with expiry alerts that fire before the lapse, not after.
- 05
Compliance monitoring
The qualification file assembled continuously as a by-product of the work, exportable per person, per date range, on demand.
- 06
Scheduling
Assignment against availability, qualification and hours — so an unqualified or expired driver cannot be scheduled into a run in the first place.
- 07
Time & attendance
Hours captured in the field, tied to the assignment and the asset, and carried straight through to settlement and payroll.
Most fleets already own tools for four or five of these. The cost is not the licenses — it is re-keying between them and the gaps that open where they meet. One record from application to timecard is the point.
A national emergency roadside repair network, wired into the breakdown workflow
When a truck goes down, the expensive part is the hour spent finding someone who can get to it. Knomatic works with national emergency roadside repair providers, and that coverage is built into the breakdown workflow rather than living in a dispatcher's contact list.
Dispatch to coverage
The breakdown record carries the unit, the location and the fault. Provider dispatch happens from inside that record, with the location shared to the responder by SMS link.
The clock runs on the record
Reported, dispatched, on-scene, rolling. Response and downtime become measurable per provider, per lane and per unit instead of anecdotal.
Straight into the work order
Photos, parts, the invoice and the repair narrative land on the asset history — so a recurring roadside failure shows up as a maintenance pattern rather than a surprise.
Coverage, response commitments and pricing vary by provider and geography and are confirmed during scoping. Genwright builds the workflow around the network; it does not replace your own vendor relationships where you already have them.
You are not starting from a blank canvas
Modules already running in production on the Knomatic platform. Genwright starts from the ones that fit your operation and shapes them to how you work.
Workforce & compliance
Application through timecard.
- Applicant tracking
- Onboarding & document collection
- Integrated background checks
- Credential & certification tracking
- Compliance monitoring
- Scheduling
- Time & attendance
- Contractor management
- Settlements & driver pay
Fleet & field operations
The truck, the load and the person with it.
- Dispatch & work assignment
- Inspections and defect-to-work-order
- Offline-tolerant mobile entry
- GPS tracking & visibility
- Asset tracking & geolocation
- SMS location links
- Radius-based notifications
- Inventory & parts
- Vendor settlement
Order to cash
From the customer's request to the money arriving.
- Customer portals
- Order intake & distribution management
- Reservations
- Contract management
- Invoicing
- Automated payables & receivables
- Revenue-leak and fraud detection
Safety & environmental
The records a regulator or insurer asks for.
- Inspections & incident records
- Corrective action tracking
- E-permitting
- Lockout / tagout
- Mustering
- OSHA recordkeeping
Records & oversight
What turns activity into something you can prove.
- Forms digitization & scanning
- Dashboards & analytics
- Real-time reporting
- Enforced audit trail
- Integration to existing systems
- In-app chat
From a safety director's description to a fleet in production
- STEP 01
Describe one workflow
Usually driver qualification or inspections — whichever currently generates the most re-keying and the worst audit scramble.
- STEP 02
Build in the Studio
Starting from the modules that already fit, then shaped to your job codes, terminal structure and approval chain.
- STEP 03
Pass pre-flight
Data model, permissions, audit coverage and offline behavior inspected before a driver ever sees it.
- STEP 04
Launch one terminal, then the fleet
Prove it at one location for a full cycle. Roll out from a workflow that has already carried real load.
Logistics questions we are asked most
Can Genwright manage driver qualification files?
Yes. Applicant tracking, onboarding documents, integrated background checks, license and endorsement tracking, medical card expiry and training records run as connected modules on the Knomatic platform. The qualification file assembles continuously as a by-product of the work and exports per driver, per date range, with an enforced audit trail behind every entry.
Does Genwright replace our TMS?
Usually not. Most fleets keep the TMS for freight movement and use Genwright for the workflows around it that the TMS was never designed to hold — driver qualification, inspections, breakdowns, settlement exceptions and compliance evidence. Applications read from and write to existing systems over documented interfaces.
How does the roadside repair network work?
Knomatic works with national emergency roadside repair providers, and that coverage is built into the breakdown workflow: dispatch happens from inside the breakdown record, the location is shared to the responder by SMS link, and response times, parts, invoices and the repair narrative land on the asset history. Coverage and pricing vary by provider and geography and are confirmed during scoping.
Will inspections work without cell signal?
Yes. Field capture is offline-tolerant. Drivers complete inspections wherever they are and the application synchronizes when signal returns, preserving the original timestamp and author rather than the sync time — which is what makes the record defensible later.
How long does a first fleet build take?
A scoped pilot covering two to three workflows typically runs four weeks from kickoff to a production pre-flight review. Because the workforce and field modules already exist, most of that time goes into fitting them to your terminology and approval chain rather than building from nothing.
How is this priced across a large fleet?
Genwright is priced on a platform footprint that scales with deployed users or units under management, not per application and not per field user. Putting every driver on it does not multiply the bill — which is deliberate, because a field workflow that excludes field users produces an incomplete record.
Bring the workflow your safety director dreads.
A scoping call is a working session, not a demo. Describe what currently gets re-keyed between systems, and you will leave knowing what a first build covers and what it costs.