People trust systems less because promises are made than because promises are tracked afterward. The promise is the cheap part. Any agency can announce a plan, any landlord can say the plumber is coming, any committee can vote to look into it. What separates a reliable institution from a hopeful one is what happens in week two, when the announcement has gone quiet and someone either sends an update or does not.
I have come to think of the follow-up as the real product. The pothole repair matters, obviously. But the moment that changes how a resident feels about city hall is the message that says the pothole was filled on Tuesday, here is who did it, here is a photo. That message costs almost nothing. Its absence costs a great deal.
The report that vanishes
Here is the ordinary failure. A resident notices a broken streetlight, finds the right form after some digging, fills it out, and clicks submit. A confirmation number appears. Then nothing. Weeks pass. The light stays dark, or it gets fixed and no one says so. Either way the reporter learns the same lesson: your effort went into a hole.
The person who had that experience does not just skip the streetlight form next time. They generalize. They tell a neighbor the city never answers. They stop reporting the fallen branch, the graffiti, the leaking hydrant. One unclosed loop quietly trains a whole block to stop participating, and the agency never sees the damage because the damage is silence.
What Boston does differently
Boston built its 311 system around closing that loop. The BOS:311 app, launched in 2009, lets residents photograph a pothole or a graffiti tag and file it from the sidewalk. The report drops straight into the city's work order system, and the resident can watch its status change. When a case closes, the app shows who handled it, and in some cases a photo of the finished work, the filled pothole itself.
That last detail is the interesting one. Nobody needs a photograph of asphalt. The photo exists because it is proof, and proof is what turns a claim into a record. The results suggest residents felt the difference: app-based reports grew from about 6 percent of Boston's service requests in 2010 to roughly 28 percent by 2014. People report more when reporting visibly works. The public case log extends the same idea, since anyone can browse what was requested and what happened next, a working example of the local website as public memory.
Bad news travels well when it is dated
Follow-up does not mean good news. It means specific news. A repair delay with a date and a reason lands differently than no response, for the same reason apologies need operational details. Compare two messages from a building manager. First: we are aware of the elevator issue. Second: the elevator part arrives March 4, installation is booked for March 6, and until then the freight elevator is unlocked from 7 a.m. to 9 p.m. The second message contains a delay just as long as the first. It still feels like competence, because it can be checked against reality and it tells people how to plan around the problem.
Send the update even when the update is imperfect. An honest "we have not started yet, and here is when we will" preserves more trust than a polished statement that arrives after the frustration has hardened. Timeliness beats polish in almost every case I can think of.
A follow-up habit for small institutions
You do not need Boston's software budget to do this. A school office, a condo board, a volunteer group, or a six-person nonprofit can run the same discipline with a spreadsheet and a calendar. The mechanics are boring on purpose.
- Log every promise the moment it is made, with a named owner and a date. A promise without an owner is a wish.
- Decide the update rhythm when you make the commitment, not when people start asking. Weekly is fine. Predictable matters more than frequent.
- Report status changes to the person who raised the issue first, before announcing anything publicly. They did the work of noticing.
- Close every item out loud. Fixed, declined, or deferred, say which, and say why in one sentence.
- Keep the log where members can see it. A visible list of kept and broken promises is uncomfortable, which is exactly why it works.
The pattern scales down further than people expect. Even between two neighbors, "I checked on the fence quote, the guy comes Thursday" is the sentence doing the trust-building, not the fence.
Silence is a message too
Institutions tend to treat no news as neutral. Recipients never do. Silence after a decision creates space for suspicion and rumor, and the story people invent to fill a quiet gap is almost always worse than the truth. A hiring committee that never rejects candidates, only ghosts them, is teaching every applicant something about how it treats people it no longer needs. A council that holds a listening session and never publishes what it heard has converted goodwill into evidence for the cynics.
This is why I distrust the phrase "we will keep you posted" unless it comes with a date. It is a promise about communication, and it gets broken more often than promises about the actual work.
Try one tracked promise
Pick a single commitment you are owed right now. A permit under review, a warranty claim, a repair ticket, a committee decision. Write down what was promised, by whom, and when you were last updated. Then watch what the institution does with the gap. Does an update arrive before you have to chase it? Is the update specific enough to check? Do the same for one promise you made to someone else this month. Trust is built in the follow-up, and the follow-up is a habit you can start auditing, in both directions, this week.