Demonstration with synthetic data. Not connected to any City system.
Mithril
Bylaw services · demonstration

Try it in your browser

A records system for bylaw services, with a portal for residents and an app for officers.

Everything on this site runs inside your browser on made-up data. What you enter stays in this browser, it reaches no City, and nobody else sees it.

For residents

Resident portal

Report a bylaw concern, follow it with a tracking code, look up or dispute a ticket, and read the published service figures. In English and French.

Open the resident portal

For staff, on a desktop

Records management system

Triage incoming calls, work a file from intake to resolution, issue tickets, review patrols, the live map and response analytics. Sign in as an officer, a supervisor or an administrator; each is offered the controls that role has.

Open the staff system

Best on a laptop or desktop screen.

For officers, on a phone

Mithril Field

The officer's phone app: their queue, a file, evidence, resolving a call, writing a new call and printing a ticket. The staff system opens as Mithril Field on any screen 760 pixels wide or narrower.

On a phone, open /rms/

A five-minute walk-through

  1. A resident reports noise. In the resident portal choose Report a concern, then Noise. Describe it, give an address, choose Report anonymously and submit. Keep the reference and the tracking code it gives you.
  2. A supervisor picks it up. Open the staff system and sign in as the Supervisor. The report is in Command Centre, marked Received. Search for its reference if the list is long.
  3. The file is worked and closed. Open it, assign it to an officer and dispatch them, record their arrival, write the narrative, and resolve it. Referred to Outreach hands it to the social response partner.
  4. The resident sees the outcome. Back in the portal choose Track a report and enter the tracking code. It shows Resolved, the outcome and which partner took it on, and none of the officer's notes or anyone's name.
  5. The officer's view. Show Mithril Field above, or open the staff system on a phone, and sign in as the officer.

One browser holds one set of demo data, shared by every tab of the portal and the staff system. Signing in or out in one staff tab does the same in the others. Data starts fresh after twelve hours, or when you reset it.

What is real here, and what is not

Works as in the product

  • The screens and the workflow, from a resident's report to a closed file
  • Which controls each role is offered
  • What a resident may see about their own report, and what is withheld
  • Published figures, with counts under five withheld
  • The ticket layout sent to the printer, and its QR code

Simulated, and labelled where it appears

  • Signing in: you choose a role, there is no password
  • The ticket printer connection
  • Photo and audio capture, location, and offline working in Mithril Field
  • Payments, parking and other City integrations
  • Ask Istari, which gives scripted answers
  • Some permission checks: the real system refuses certain actions on its server that this demo allows

Not in this demo

  • Any City system, data or account
  • The City's zoning and parcel layers on the staff map
  • Resident accounts and "My reports"
  • Email, text messages and notifications outside the app
  • The resident portal's offline queue, which only runs when its server cannot be reached

Start again

Reset puts every record back as it was. Open tabs reload with the fresh data.