Research · The Complaint Record · September 2026

What the 311 record actually says

Between June 3 and September 18, 2026, twenty-seven Alex311 service requests were filed about a single residential charging cable in Rosemont — twenty-four logged against the address where the cable is, two against the house across the way, and one that the City re-dated and re-filed under the same case number. Because Alex311 is a public record, the whole corpus can be read as evidence rather than argued about — every complaint text, every photograph, every City disposition. This page is a content analysis of all twenty-seven. The finding that matters most for policy is not that neighbors complained; it is what the complaints ask for, and what three months of them never establish.

What the complaints allege

The complaints are consistent, and their central concern is legitimate: a cable crossing a public walkway could hurt someone. Seventeen of the twenty-six texts name a trip or fall hazard, and seven invoke the Americans with Disabilities Act or disabled pedestrians. Nothing in this analysis treats that concern as unreasonable — the proposal on this site exists precisely because a cord lying loose across a sidewalk is a bad answer. The question is what the record establishes beyond the concern.

What the complaints never mention

The most consequential feature of the corpus is an absence. Searching all twenty-six texts for the words protector, ramp, cover, guard, temporary, or any reference to the equipment being taken up after charging returns nothing across all twenty-six texts. Not one complaint acknowledges that a commercial pedestrian cable protector is in use, that it is removed when charging ends, or that the crossing is present for a few hours a week rather than continuously. Every filing describes a cord draped across a sidewalk. Nor does any later filing note the retroreflective tape and floodlight added after the one reported night-time trip, or the signed pledge to stop charging across the sidewalk until the City makes it lawful — which one filing instead reports as “threatening.”

That gap is the whole policy problem in miniature. Under today's rules there is no published standard, so there is no difference — to a neighbor, to a 311 form, or to the City — between a loose extension lead and a rated protector deployed to a specification. A resident doing the safest available thing and a resident doing the most careless thing generate the same complaint, because the system has no vocabulary for the distinction. Publishing a standard creates that vocabulary: it gives neighbors something specific to check, and gives the City something specific to enforce.

What each filing actually reports

Theme counts show what the complaints talk about. A second coding asks a narrower question: does the filing report anything a City inspector could go and check? Read that way, the twenty-six texts fall into five groups. One reports an incident involving a person. Four report the crossing in use on a stated date and time. Sixteen report it in general terms — “again,” “yet again,” “constantly” — with no date. Three describe no condition on the sidewalk at all: they concern the signs posted on the fence, or the resident personally — and the City's own handling drew the same line, routing each to the Parking category and closing it within a day. The last two, filed on September 18, report neither a sidewalk condition nor a sign: their subject is the City's disposition of the complainants' own earlier filings, and the exhibits attached to them are screenshots of those records.

The photographic record

The filings carry 37 photo submissions. Only 30 are distinct files, and only 26 are distinct photographs — comparing the images themselves, rather than their bytes, shows eight scenes submitted more than once. Two of those repeats are the same picture re-saved as a new file, which byte-comparison alone would miss. One photograph was filed three times over 44 days; another three times in three weeks, the third time with a red arrow drawn on it. The images are consistent with the texts — most show the vehicle at the curb with the protector deployed across the walkway.

Photographs submitted to 311 are public records, but they were taken by residents who are not the author of this site and are not reproduced here. They are described, counted, and compared only.

Two submissions are worth noting for what they depict rather than how often they appear. One photograph carried three filings — July 26, August 13, and August 14 — and the August 13 version is the same earlier exposure with a red arrow drawn onto it, marking the cable where it crosses the walkway. The underlying image is unchanged between the three filings; only the annotation is new. Eight of the thirty-seven submissions are photographs of signs rather than of a cable: five on August 31, one on September 4, and one each on September 14 and 15. Three more, filed on September 18, are not photographs of the street at all — they are screenshots of the Alex311 portal showing the complainants' own earlier records, one marked “CLOSED” and one “Investigation Status: Void.”

One cable, two addresses, three filings for one evening

Two of the twenty-seven filings are logged against 2 West Oak Street — the property across the way, roughly forty yards from the cable they describe. Both plainly concern the same crossing: one places it “on Commonwealth right before Oak Street,” and its photograph shows the same vehicle, curb and walkway as the filings at the correct address. Nothing here suggests bad faith; a 311 form asks for a location and a passer-by supplies the nearest house number. But the consequence is worth stating plainly, because it cuts against a policy vacuum: a complaint-driven system quietly attributes conduct to whichever address the reporter picks, and the resident at the misattributed address never learns a case exists.

The clustering is tighter still once the corpus is read by event rather than by case number. The evening of September 3 produced three separate service requests — one that night and two the following day, one of them against the neighboring address. The afternoon of September 8 produced two more, sixty-six minutes apart, again split across the two addresses, carrying near-identical photographs of the same moment. The September 8 photograph was filed a third time on September 13, captioned as a new day. Counting filings therefore overstates the number of distinct events: twenty-seven filings describe substantially fewer occasions than twenty-seven.

How the City has handled it

Twenty-two of the twenty-six records have been closed, at a median of 5.7 days, in at least one case recorded as “Work is Complete.” Between August 20 and September 13 the City closed nothing, and the six filings from August 31 to September 8 carried the disposition “Work is On Hold” with no stated reason. On September 14 it closed all six, plus the September 11 filing, in a single afternoon, again without a stated finding; the three filings that followed were closed within a day each. Three filings from one afternoon on July 2 remain open, now past eleven weeks.

Closure here plainly did not mean resolution. The condition that prompted the first filing continued after twenty-two closures, because closing a service request does not answer the underlying question: what is this resident supposed to do instead? Under the current rules there is no answer to give, so the loop simply restarts. That is a design failure, not an enforcement failure — and it is expensive for everyone in it, including the City staff who have processed twenty-seven filings about one household.

What happened after the condition stopped

On September 11 the resident signed and posted a dated pledge to stop charging across the sidewalk until the City makes it lawful, unplugged, and began charging at a public fast charger instead. That is the outcome the complaints had been asking for. It did not end the filings. Six of the twenty-seven arrived on or after that date — September 11, 13, 14, 15 and twice on September 18 — which is more filings than the corpus produced in all of June.

Four of those six exhibits are not photographs of a sidewalk. Two are pictures of what the household wrote — one of them the pledge itself, reported as a threat — and the last two are pictures of the complaint system, filed because the City had closed the earlier complaints. By September 18 the corpus has changed subject twice: from the cable, to the household's speech about the cable, to the City's handling of the filings about the cable.

Where the complainants and this proposal agree

The most striking result of reading the whole corpus is how much of it the proposal already accepts.

• Sidewalks must stay passable. Seventeen filings say so. So does the proposed standard, which requires the cable to be protected across the entire pedestrian travel surface with no exposed cable, and requires removal when not charging and immediately for snow, ice, or City direction.
• The same rules should apply to everyone. Five filings make this argument, including one that says the resident “is no more important than anyone else and should not be receiving special treatment.” Agreed — and that is the argument for a published, uniform standard available to every household without a driveway, rather than an unwritten rule enforced unevenly by complaint.
• Better equipment should be required. One filing asks the City to require an overhead swing arm. That device is an approved method in the crossing-options analysis, and a recessed channel is the permanent version of the same idea. The disagreement is not about engineering.
• The City should act. Ten filings are, at bottom, complaints that Alexandria has no working process here. That is precisely this site's position.

What separates the two positions is narrower than the volume of filings suggests. Everyone in this record wants a passable sidewalk and a rule that applies evenly. Only one side currently has a way to get there, because only one side is proposing a rule.

Sources & method