Skip to content
All projects

DNW Busing

A school transport platform where the hard part was never the bus.

Client
Darchei Noam Ways
Year
2026
Discipline
UI/UX
Services
UI/UX design, Platform architecture, Web design, Payments integration, Admin tooling

01

The challenge

Manual invoicing, an authentication flow parents could not get through, and a registration form that could not express how the business actually charges.

02

What we did

Six modules built around the one thing that has to be right: a parent finishing registration in a single sitting, on a phone, and being billed correctly for ten months afterwards.

01

Say the promise in the first screen

Safe and reliable is the entire product, so the homepage says it and shows it — a real bus on a real street, not an icon of one.

Yellow on near-black is the obvious palette for school transport and the easy way to look cheap. It works here because the yellow is rationed: one accent, on the thing you are meant to press.

Homepage — the promise, stated plainly

02

Answer the parent's real questions

Parents are not comparing features. They want to know who is driving, what happens if the bus is late, and whether their child gets picked up at the door.

So the homepage is built as answers — door-to-door service, government-screened drivers, safety-first operations, field trips and camps — each one a card that resolves a specific worry rather than advertising a capability.

Service cards, written as answers
On-time operations

03

Registration in one sitting

The registration module carries eight of the twenty-three scope items, because it is where the business was losing people: multi-student families, age and grade validation, a door-to-door opt-in that changes the price, and per-section terms.

It confirms by email, and chases an abandoned registration after forty-eight hours — the single highest-value automation in the build, because a half-finished form is a family who meant to come back.

Route and school selection
Registration and enquiry flow

04

Billing that matches how the year actually runs

A school year is not twelve equal months. Payment is a deposit, then ten instalments on a schedule with a gap in it, each carrying tax, some with door-to-door pricing added.

Card-on-file billing runs against the accounting system directly, so an invoice, a payment and a customer record are the same event rather than three people's afternoon. Declined cards get a retry path; families paying by cheque are exempted rather than chased.

Charter and additional services

05

The panel the office actually lives in

The admin side is seven scope items and no glamour: a filterable dashboard, exports, bulk and individual parent email, school and route management, and a banner system for the mornings when something has gone wrong.

The parent portal is its mirror — account, verification, registration status, and a lock after submission so records stop drifting the moment they matter.

Contact and office routing
Parent-facing calls to action

Our role on the project

Product

  • 23-item scope
  • 6 module architecture
  • Parent + admin flows
  • Charter services

Design

  • Brand system
  • Responsive layouts
  • Registration UX
  • Admin dashboard

Integration

  • Card-on-file payments
  • Accounting sync
  • Recurring instalments
  • Automated email