Research · The Complaint Record · September 2026
What the 311 record actually says
Between June 3 and September 8, 2026, twenty-one Alex311 service requests were filed about a single residential charging cable in Rosemont — eighteen 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. 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-one. 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.
Method, and its limits
Every figure here is counted from the public Alex311 records themselves, retrieved September 9–10, 2026, and re-checked against the portal. Complaint texts are quoted verbatim. The portal does not identify who filed a request, so this page makes no claim about how many people are involved or who they are, and does not name or characterize anyone. Several filings are written in the first person and at least one claims authorship of an earlier filing, but that is weak evidence and is not relied on. Read the tallies as properties of a body of text, not of any person. The subject of the complaints is a named resident — the author of this site — which is disclosed here rather than hidden.
What the complaints allege
The complaints are consistent, and their central concern is legitimate: a cable crossing a public walkway could hurt someone. Fourteen of the twenty 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.
| Theme | Filings | What it sounds like |
|---|---|---|
| Trip or fall hazard | 14 | “creating hazard for those the walking”; “before someone gets hurt” |
| Names the resident or address | 10 | “Its Jordan Eccles at 1 west oak street in Rosemont” |
| Frustration at non-enforcement | 7 | “Why is this not being enforced?”; “What remedy does the city have?” |
| Cites City code | 6 | “Sec. 5-2-16 … Sec. 5-2-29” |
| ADA or disability access | 7 | “violates the Americans with Disabilities Act” |
| Equal treatment under the rules | 4 | “All Alexandrians should have to abide by the same rules” |
| Vulnerable pedestrians specifically | 2 | “making passage difficult for elderly neighbors”; “particularly for disabled pedestrians” |
| Fear of precedent | 1 | “others will think this is legal and will do the same” |
| Describes an actual incident | 1 | “I tripped over it walking my dogs at night” |
| Proposes a solution | 1 | “should require them to use an overhead swing arm … (they exist)” |
Key finding — the harm record after 97 days
Across twenty-one filings and three months, the record contains one description of anything actually happening: a filing of August 14 reporting a trip while walking dogs at night, with no injury described and no medical or incident report referenced. There is no other reported contact, no injury, no citation, no City finding that a violation occurred, and no measurement of the obstruction anywhere in the corpus. This is not proof that the setup is safe, and one person stumbling in the dark is a real event that deserves a real answer. But a policy debate should be honest about the size of the evidentiary record it is reasoning from — and about the fact that a lit, beveled, high-visibility protector is the specific remedy for exactly that complaint. It is also what happened next: after that report, the resident added retroreflective tape to the protector and mounted a solar floodlight covering the crossing. Both are visible in the photographs on Safe for pedestrians?, and no further night-time incident appears anywhere in the record. That is what a good-faith actor does with a specific, actionable complaint — and it is the behavior a published standard would make routine rather than improvised.
What the complaints never mention
The most consequential feature of the corpus is an absence. Searching all eighteen 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 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.
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.
The photographic record
The filings carry 30 photo submissions. Only 24 are distinct files, and only 20 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.
| Image | Times filed | Dates |
|---|---|---|
| Vehicle at curb, protector deployed | 3 | Jun 3, Jun 4, Jul 17 — same file each time |
| Walkway from the north | 3 | Jul 2 (two filings), Jul 17 — same file each time |
| Planting strip and crossing | 3 | Jul 26, Aug 13 (arrow added), Aug 14 |
| Walkway from the south | 2 | Jul 2, Jul 13 — same photograph, saved as a different file |
| Fence with posted signs | 2 | Aug 31, Sep 4 — same scene, two files |
| Vehicle charging, 6:30 pm Sep 3 | 2 | Sep 3, Sep 4 — two filings, two addresses |
| Vehicle charging, Sep 8 | 2 | Sep 8, 66 minutes apart — two filings, two addresses |
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. And the filing of August 31 submitted five photographs, all of them of the explanatory signs posted on the fence — none of a cable at all.
When the complaint changed subject
The August 31 filing does not allege that the cable was out that day. It objects to the signage: “The owner has now posted additional signage asking to not be reported for their illegal activity. Unfortunately, that is not how it works.” It closes with a fair point, fairly put — “No one asked this homeowner to buy an electric car or a house without a driveway to charge it.” That is exactly the question this site exists to answer, and the answer is that a substantial minority of Alexandria households — provisionally estimated at 10–20% of vehicles, pending the parcel and parking GIS work the City would need to do to measure it — park where they live with no driveway to charge in. A rule that works only for households with off-street parking is a rule that decides who is allowed to drive an electric car. The signs in question and the arithmetic behind them are both published here.
One cable, two addresses, three filings for one evening
Two of the twenty-one 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. Counting filings therefore overstates the number of distinct events: twenty-one filings describe substantially fewer occasions than twenty-one.
Why this matters beyond one household
A published standard is checkable at the curb: either the protector is a listed device, laid to specification, present only while charging, or it is not. That is a question a neighbor, a passer-by or an inspector can answer about a crossing — without needing to guess which house it belongs to, and without the answer changing depending on who files first. Volume of complaint is a poor instrument for measuring a condition; a specification is a good one.
How the City has handled it
Eleven of the twenty records have been closed, at a median of 5.6 days, in at least one case recorded as “Work is Complete.” Since August 20 the City has closed nothing. Three filings from a single afternoon on July 2 have now been open for more than two months, and the six most recent filings all carry the same disposition: “Work is On Hold.” The City states no reason for the hold, and none should be inferred; it is recorded here because it is the current status of every pending filing.
| Status | Records | Detail |
|---|---|---|
| Closed | 11 | Median 5.6 days to closure; earliest Jun 10, latest Aug 20 |
| Open — Work On Hold | 6 | Aug 31, Sep 3, Sep 4 (two), Sep 8 (two) |
| Open — no disposition | 3 | All three filed Jul 2; open 70 days |
Closure here plainly did not mean resolution. The condition that prompted the first filing continued after eleven 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-one filings about one household.
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. Fourteen filings say so. So does the proposed standard, which sets a clear-width requirement, a removability requirement, and immediate removal for snow, ice, or City direction.
- The same rules should apply to everyone. Four 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. Seven 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.
What this record argues for
Twenty-one filings, eleven closures, zero injuries, and no change in the underlying condition is what a policy vacuum looks like from the inside. It consumes City staff time, it gives neighbors no mechanism that actually resolves their concern, and it leaves a resident with real legal exposure for an activity no published rule tells them how to do safely. A standard ends the loop for everyone in it — which is why the two-track proposal pairs a compliance specification with the enforcement the complainants are asking for.
Sources & method
- Alex311 public service-request records concerning this crossing, requested 2026-06-03 through 2026-09-08: 20 unique records, 18 logged at 1 W Oak St and 2 at 2 W Oak St. One record appears twice in the dossier's count of 21 because the City re-dated and re-categorized it. Records were identified by address and by full-text and proximity search, because an address filter alone misses filings coded to a neighboring property. Retrieved from the public Alex311 portal, September 9–10, 2026.
- Theme counts: keyword-and-read coding of the 20 complaint texts; a filing may fall under several themes. Absence checks ran over the full concatenated corpus.
- Photograph counts and re-submission detection: SHA-256 hashing of the 30 stored image files to find identical files, plus perceptual difference-hashing (64-bit dHash, Hamming distance ≤ 10) to find the same photograph re-saved as a different file. Both methods were checked by eye.
- Disposition and timing:
requested_datetimeandclosed_datetimefields as published by the portal; “Work is On Hold” as displayed on each pending record. - Individual case links, and the satirical treatment of the same corpus, appear in the Scofflaw Dossier. One record is deliberately not linked there pending redaction of a photograph that includes a minor.