The inspector placed an internal supervisor note — the "handyman" label and the representative's complaints to elected officials — inside a single July 18, 2025 email addressed to the owner's friend and copied to the owner, rather than in a separate, supervisor-only message. ---
A city inspector included internal supervisor business in an email addressed to the property owner’s friend and copied to the owner. On July 18, 2025, the inspector sent a message discussing backyard structures and electrical work needed to bring the property into compliance. Within the same email, he addressed his supervisor directly, labeling a property representative as a “handyman” and listing the various officials the representative had complained to, including city council and the mayor. These types of internal characterizations and staff-management notes are typically handled in a separate, supervisor-only message rather than being shared with the property owner. This specific note only became visible because the record was manually read from a scanned image, as the text does not surface in keyword searches of the digital case file.
On July 18, 2025 at 7:28:50 a.m., the assigned inspector sent one email — subject "Re: 4800 T St." — addressed to the property owner's friend, with the property owner and the inspector's supervisor on copy S.10. The message opens "Karin," and runs as owner-facing correspondence: it covers the pending inspection, the storage shed and work room built in the backyard, the electrical added to the front of the house, and what is needed to get the property "back to what it was prior to work performed there, or get it permitted" S.10. In that same paragraph block the inspector writes "I have also added my supervisor to the email," then turns and addresses the supervisor directly: "Doug, I left paper work on your desk that was provided to me from the handyman on the property for you to look at. The handyman has sent complaints to city council, councilman Guerra, the mayor, the chief, etc." S.10. That note — a characterization of the property representative as "the handyman" and a list of whom the representative had complained to — is internal supervisor business, delivered inside a message whose addressed recipient is the owner's friend and whose copy list includes the owner. Douglas Pierson's title, Supervising Building Inspector, Housing and Dangerous Buildings, appears on the City's own contacts page CITY.CodeEnforcementContacts.
A city inspector was emailing back and forth with a friend of the property owner about an upcoming inspection. On July 18, 2025 he sent one email to that friend, with the owner copied, and added his own supervisor to it. Most of the email is normal inspection talk — what was built in the backyard, the wiring added to the front of the house, and how to get it permitted. Inside the same email is a side note to his supervisor: that he had left some paperwork on the supervisor's desk, that he was calling the property representative "the handyman," and that this person had been complaining about the case to city council, a councilman, the mayor, and the police chief. That kind of note is internal staff business; the ordinary handling is a separate message to the supervisor only, not a message addressed to the owner's friend with the owner copied. This detail became visible only because the owner's side obtained the City's records and the actual scanned email was read by hand — the language does not appear in a text search of the case file, because it exists only as a scanned image S.10.
---
The City-produced scan shows a single email dated July 18, 2025 7:28:50 a.m., subject "Re: 4800 T St.," To the owner's friend, Cc the property owner and the supervisor S.10.
The body begins "Karin," and addresses the inspection, the storage shed and work room, the front-of-house electrical added with extension cords, and getting the property permitted or restored S.10.
The same message says, in the owner-facing text, "I have also added my supervisor to the email" S.10 — the single send, as composed, put the supervisor on the owner-facing thread.
Directly after, addressed to "Doug": "I left paper work on your desk that was provided to me from the handyman on the property for you to look at. The handyman has sent complaints to city council, councilman Guerra, the mayor, the chief, etc." S.10.
The "handyman" characterization of the representative and the list of the representative's complaints to elected officials sit inside a message addressed to the owner's friend and copied to the owner — content the ordinary handling would carry in a separate, supervisor-only email.
The City's own scan shows one email, sent to the owner's friend and copied to the owner, carrying both owner-facing inspection content and an internal note to the inspector's supervisor S.10. The owner-facing text itself states the supervisor was "added to the email," and the supervisor note then characterizes the representative as "the handyman" and lists his complaints to city council, Councilman Guerra, the Mayor, and "the chief" S.10. The produced record shows internal staff-management content and a label for the representative placed in front of the owner side of the case.
Anticipated City defense: the inspector was efficiently handling a single thread, the supervisor was a copied recipient who needed the update, and combining the owner-facing note with the supervisor note in one message was a harmless administrative shortcut.
Answer: The supervisor being on copy does not explain placing the internal note inside a message addressed to the owner's friend, where the owner side reads it S.10. That note characterizes the representative as "the handyman" and lists his complaints to city council, the Mayor, and "the chief" — internal staff-management content with no owner-facing purpose S.10. The ordinary handling was a separate, supervisor-only message; the City's own scan shows it was not done that way. This is a record-handling point in an enforcement case carrying notices, penalties, and permit consequences. A produced native record showing the supervisor note and the owner-facing message were separate communications joined only in scanning or export would disprove this claim. A native email showing the supervisor note was sent separately would disprove the claim. No such record has been produced.
---