Skip to content

A whole region asks. One commission plans.

The bulky waste collection tool of the Kent Regional Service Commission, built by Witify: residents ask online, the commission plans and sends the schedules.

Client
Sector
Municipal waste management
Technologies
Laravel, Vue, Sprintify

01 The numbers

Five numbers, and where they come from

First, the scale of the service and the limits the system enforces.

  • 76

    municipalities served One tool for the whole region.

  • 2

    automatic mailings every week Zone schedules on Thursday, resident reminders on Friday.

  • 8

    item categories to choose from Three of them (metal, appliances, electronics) are flagged in the list of collections.

  • 6

    items at most per request The form says so before it is sent.

  • 5days

    before the collection, the list is frozen No new request is added to it.

The first number comes from the previously published page, with the client’s approval. The other four are rules of the system.

02 Request

A collection request in a few minutes

The resident enters an address, a community, contact details and a list of items, from eight categories. The system finds the next collection of their zone by itself and, given an email address, sends the confirmation. The form is available in French and English.

Fig. 01 The public collection request form

03 Planning

Collections are created in series, with no overlap

The commission picks a zone, the date of the first collection, an interval in weeks and a number of collections: the system creates the whole series at once. A zone never has two collections on the same day. Requests find their place in the zone’s next collection on their own, and a flag marks the collections that hold metal, appliances or electronics.

Fig. 02 Creating a series of collections, over the list of upcoming collections

04 Emails

Schedules and reminders go out on their own

Nobody has to prepare a mailing: the system sends them on a fixed calendar.

Resident

A confirmation, then a reminder

Given an email address, the resident gets a confirmation at sign-up. Every Friday, a reminder goes out for the following week’s collections.

Zone

The zone’s schedule, every Thursday

Every Thursday, the zone manager receives the upcoming collections as a PDF and an Excel file, ready to hand to the crews.

05 Our choices

Three rules so that the routes hold

Three rules of the system matter more than the others. For each: the risk to avoid, what we chose, and what the commission gains.

  1. One collection per day and per zone.

    The risk
    An overlapping zone calendar, with requests that no longer know which collection to join.
    Our choice
    The system refuses to create a second collection on the same day for a zone, even in a batch.
    The gain
    Each zone has a readable calendar and each request a single collection.
  2. The list freezes five days before.

    The risk
    Requests that keep arriving after the schedule has gone to the crews.
    Our choice
    Every night, collections starting within the next five days are locked. A request that arrives afterwards goes to the zone’s following collection.
    The gain
    The schedule sent on Thursday no longer changes.
  3. One request per address and per collection.

    The risk
    One household registering items over and over and overloading the route.
    Our choice
    A resident already signed up for the next collection is placed on the one after. A third request is refused. Each request holds six items at most.
    The gain
    A predictable load per collection, with no file to check by hand.

06 Under the hood

What the system is made of

A custom web application: a public side for residents, an administration for the commission. A second public form, the civic address request, has since been added.

Application
Laravel, Vue, TypeScript, Tailwind
Interface
Sprintify UI, Witify’s component library
Scheduled tasks
Locking, schedules, reminders, every night at 12:01 a.m., Thursdays, Fridays at 8:30 a.m.
Exports
PDF and Excel, on demand, or sent every Thursday
Reliability
Audit trail, backups, nightly backup, error tracking with Sentry
Languages
French and English, forms and emails

How many of your routes are still planned by hand?

Thirty minutes to see how a collection service can receive, plan and send on its own.

Or write to us
Next case study SAUVéR systems Read the case study

Names and figures shown in the interfaces are examples.