For community association managers

HOA violation photos in Utah: the fine process runs on two pictures, and an owner can dispute either one

A manager drives the community on a Tuesday and photographs a trailer parked on a driveway against the rules. The association sends a written warning with the photo attached. Two days later the owner emails back a photo of an empty driveway: fixed. A week later the manager drives past and the trailer is there again.

Utah’s fine process for community associations turns on two pictures: the one that shows the violation, and the one that shows it was cured. This piece is about what the statute asks for, where each photo comes in, and what the files themselves can and cannot tell you when someone says one of them is wrong. It is not legal advice.

What the statute says

For homeowners associations, the rule is Utah Code 57-8a-208, part of the Community Association Act. Before a board can fine a lot owner, it must give a written warning that:

The board may fine if the owner repeats the same violation within a year of the warning, or, for a continuing violation, does not cure it in the time given. If the governing documents allow it, the board may then fine again without another warning each time the owner repeats it within a year, or lets it continue for 10 days or longer after the fine. The amount comes from the governing documents, not the statute.

Then the owner’s side. An owner who is fined may request an informal hearing before the board within 30 days of receiving notice of the fine. At the hearing the board must give the owner “a reasonable opportunity to present the lot owner’s position”, and no interest or late fees accrue until the owner has the board’s final decision. After that, the owner has 180 days to appeal by filing a civil action.

Two more details matter for managers. The board “may delegate the board’s rights and responsibilities under this section to a managing agent”, so the warnings and fines are often your work, but it may not delegate the hearing itself. And condominiums have a near-identical section, Utah Code 57-8-37, with “management committee” and “unit owner” in place of board and lot owner, and the same 48 hours, 30 days and 180 days.

The statute does not mention photographs at all. But a warning has to describe the violation, and in practice the description is a photo. So does the owner’s answer.

Photo one: yours, of the violation

Your photo is the thing the owner will argue with at the hearing. The ordinary arguments are old: that is not my lot, that was taken on a different day, the trailer was only there for an hour. A newer one is that the picture is fake, or made with AI. We have written about what to do when someone says your photos are AI, and most of it applies here.

The short version is that your best answer is the original file. A photo taken on a phone usually carries a record written by the camera: which phone took it, the date and time, often the time zone. That record supports what you say about when the picture was taken. It is also easy to lose by accident. A photo screenshotted out of an inspection app, pasted into a warning letter, or sent through a messaging app may arrive with none of it. If your violation photos travel from the phone to the letter that way, keep the original somewhere as well. See where you keep inspection photos for the storage settings that quietly replace originals with smaller copies.

Take a wide shot as well as the close-up. A close-up of a trailer hitch could be on any driveway in Utah. A wide shot with the house number or the street sign in frame is a photo of this lot.

Photo two: theirs, of the cure

For a continuing violation, the owner has at least 48 hours to cure. Many owners answer with a photo: the weeds pulled, the trash cans put away, the paint colour corrected. Accepting that photo is quicker than driving out, and most of the time it is honest.

It can still be wrong in three ways, and only one needs anyone to be dishonest:

The way the photo reaches you decides how much you can check. An owner who emails the original as an attachment usually sends the camera record with it. One who texts it, or sends it through WhatsApp or Facebook Messenger, often does not: those routes strip or compress the file on the way. A stripped photo may be perfectly honest. You just cannot check its date. More on which routes keep the file in how to get the original photo; the advice there for tenants works the same for owners.

The answer to every one of these doubts is the same, and it is not software: go and look. A drive-by after the cure deadline settles whether the trailer is gone in a way no file can. Where you cannot go, the file can tell you whether the photo is at least what it claims to be.

What the file can tell you

Our checker reads the record inside the file, in your browser, without uploading it. For a phone original it says “Camera Original”, names the device and shows the capture time, so you can hold it against the date of the warning and the cure deadline. If the file names an AI tool, or carries Content Credentials that say it was made or edited with AI, it says “AI Generated” or “AI Edited”. If the record is gone, it says “Can’t Verify”. That is not an accusation. It means: ask for the original, or go and look.

If the two clocks disagree, for example a photo whose own record puts it a month before the warning, that is worth a question, not a conclusion. Camera clocks can be set wrong. We wrote about what to do when photo and video timestamps disagree.

A routine for violation files

  1. Keep the original of every violation photo, not only the copy in the letter. Take a wide shot that identifies the lot as well as the close-up.
  2. Ask for cure photos as email attachments, and say so in the warning letter. One sentence does it: “If you send a photo showing the violation is cured, please attach the original photo to an email rather than sending a screenshot or a text.”
  3. Before you close the violation on a photo, check it. Look at the capture date against the warning date. If it says “Can’t Verify”, drive by.
  4. Before a hearing, save a report. The report is dated and lists each file’s SHA-256 fingerprint, so if the owner later goes to court within the 180 days, anyone can confirm the file you produce is byte-for-byte the one you checked before the hearing.

The limits, stated plainly


ImposterShield reads the evidence inside image and video files. It runs in your browser and uploads nothing. If a file has been stripped, it says so. That is the product working, not failing.

Check the photos before the hearing

Drop the files on the page. It shows what each one says about where it came from and when it was taken, and a saved report lists each file’s SHA-256 so you can show later that the file is unchanged. The check runs in your browser, so no photo is uploaded.

Open the checker