Check SolveTO in Toronto →

Track Your Report

Enter your SolveTO reference (STO-A3F7K2) or your city 311 reference number.

311 toronto accountability civic-tech transparency

"Completed" does not mean fixed

Ahmed Nadar · · 7 min read

I’m writing this at 10:40 pm on June 4th, because I do not want to wait until morning to say it.

On June 1st, three days ago, a trusty caring citizen reported an issue at 235 Queens Quay West in the Harbourfront area.
On June 2nd, it was logged in the city’s system as a service request with reference number 09461550.
On June 3rd, the city marked it “Completed.”

All good, right?
NO.
Nothing was fixed.

Toronto's 311 tracker for report 841: status marked Completed, Inspection and Work scheduled both shown as not required, and a staff note redirecting the issue to Harbourfront Centre Office.

Toronto’s own 311 tracker for report 841. Marked “Completed” the day after it was filed, with no inspection, no work, and a quiet redirect to a third party.

What the city’s own tracker shows

Read the city’s status page for this request, word for word, and it tells on itself.

Under Inspection, it says “This part of the process wasn’t required this time.”
Under Work scheduled, the same line again.
And under Closed: “We closed your request. The park pathway and trails issue was fixed if needed.”

Fixed if needed. That phrase is the whole problem in three words. It is the city admitting, in writing, that nobody checked whether anything needed fixing.

The staff notes fill in the rest. The issue was handed to the Harbourfront Centre Office, and the resident was told to chase Visitor Services for any updates from here. No inspection, no work order, no repair. A handoff, stamped “Completed.”

The problem is the label, not the redirect

I want to be fair to the city here, because the distinction matters. Redirecting a report is sometimes the right call. Harbourfront Centre manages that land, so handing it over is not absurd, and I am not going to pretend the redirect itself was wrong.

The redirect is fine. The stamp is the problem.

“Completed” is not a description on this screen. It is a performance metric. The city tracks how quickly it closes requests, and “Completed” is the word that moves that number. So the moment a redirect gets counted as “Completed,” the close rate stops measuring things that got fixed and starts measuring things that got relabeled.

Picture what that resident is told. Your request is resolved. Except the pathway was never inspected, no work was ever scheduled, and if they walk past it tomorrow it will look like it did the morning they reported it. The only thing that changed is a word on a screen.

There is an honest version of this, and it is not hard. Call it “Redirected, still open.” The resident knows they were heard. They know someone else now holds the responsibility. And the request stays alive until that someone confirms the work is done. That is a closed loop. A handoff is not an outcome, and calling it one is how a close rate fills up with things that were never fixed.

I have one case. That is the point, not the weakness.

This is one report. 841. City reference 09461550. I am not claiming some share of the city’s completions are fake, because I do not have that number yet.

But one clean case is enough to ask the question out loud. How often does this happen?

I am going to find out, and whatever the answer turns out to be, I will publish it.

Because one case already proves the thing that matters. Nobody at the city had to break a rule for this to happen. No bad actor, no cover-up, nothing hidden. The label “Completed” got applied to an unverified redirect, and that is how the system runs. That is the part that should bother everyone.

The city’s own words

This is not a standard I invented and then held the city to. The 311 plan the city presented uses a phrase of its own: “Closing the Loop.” The promise is that residents should hear back when their issue is resolved, and that “Completed” should mean what a normal person assumes it means.

The target for all of it is 2027.

And report 841 was closed today in the exact way that 2027 plan is meant to prevent. The plan paints a future where the status means something. The system, right now, is handing out outcomes on things that do not have an outcome yet.

That gap is not a future problem to schedule. It is happening today, on a park trail in Harbourfront.

What this costs

You cannot close a loop by relabeling it closed. A resident who sees “Completed,” then walks past the same broken trail a week later, learns something the city never meant to teach them. Not that the city is overwhelmed. Not that these things take time. They learn that “Completed” is just a word the system reaches for when it wants to move on.

And once someone learns that, they stop reporting. Why would they bother.

Now make it personal. If you have ever reported something and watched it close as “Completed,” you cannot be sure it was fixed. You believed the status. You had every reason to. That belief is the trust the city is spending without telling you.

I wrote a while back about the city fixing things and telling no one, the silence that follows a real repair. This is the mirror image. There, the city does the work and says nothing. Here, the city does nothing and says it is done. Two different failures, one identical lesson for the resident: the status is not the truth.

That is the line SolveTO holds. We follow the real outcome, not the paperwork. A request the city closes without a fix is not a resolved report on our side, and the resident deserves to see that difference in plain sight.

The city says it wants to earn back the public’s trust on 311 by 2027. Good. But you cannot trust a status that counts a handoff as a fix. Not in 2027, when the city promises to do better. Not tonight, while it is already happening.

I am not asking you to be angry at the city. I am asking you to look. Open the tracker on a report you filed and read it slowly. Ask whether “Completed” meant fixed, or just closed.

The fix is us

I did not build SolveTO to count reports. The city already counts. It counts what it opened, what it closed, and it calls that a job done. You have seen tonight what some of those closures are worth.

I built it for the other side of that number. For us.

Here, a report does not end when the city says so. It ends when the people who live there say so. Every report on SolveTO has a community update. You walk past it, you tell us whether it is fixed, and you show us with your own photo. You leave a comment. You say what you see, in the open, where everyone can read it.

That is the whole idea. We label what we see. We write what we confirm. We close what we watched get fixed with our own eyes, not because a screen told us to.

This is not a place to attack the city. When the city does the work, we say so, and we mean it. When it does not, we say that too. Not to blame. Not to shame. To say it straight, this is not right yet, and to ask the city to meet us here in the open.

A city and its residents looking at the same trail, the same photo, agreeing on what “fixed” means. That is what trust looks like. It is not a label on a screen you are asked to believe. It is something we build together, in public, where nobody can change the word without all of us seeing.

So come check on your city with us. Confirm a report near you. Add the photo. Leave the comment. It is open, it is free, and it is yours. Your right to know, and your right to be heard, both at once, out loud.

Report 841 is still open. It stays that way until it is fixed.

solveto.ca · solvesauga.ca