How we built it

Our team gathered in a meeting to look at the information provided and analyze the current state of the public Toronto website to see what we can work on. We came up with Sequitu, a standard layout that sits on a city’s existing project page: A phase tracker, then a short plain-language summary. The following sections are what was proposed, what Council decided, what changed, and how to take part. We modelled the first example on the New Park at 114 Church Street project.

Challenges we ran into

Process types differ: rezoning, variances, subdivisions, and heritage each have their own stages, and Ontario’s planning rules have recently changed. Given only 36 hours, we had to resist adding features and focus on one core workflow.

Accomplishments that we’re proud of

A working prototype with a consistent four-question layout that a city could embed without replacing its systems.

What we learned

Cities resist replacing their systems, so building on top of them is more realistic than a new portal. Plain language is a design decision, not just a writing style. Residents’ confusion is mostly about where information is found, where municipalities are in the process, and whether they can still act.

What’s next for Sequitur

AI-assisted summary generation connected to municipal documentation systems for automatic updates, change tracking, and participation updates, with municipal review to keep residents informed as projects evolve.​ Stage templates for more process types, checked by local planners, and adapt them for other provinces. Test with stakeholders and run a full accessibility audit.

Share this project:

Updates

Submission history