Odor Complaint Management: The First 24 Hours
The call comes in at 6:15 on a Tuesday. A neighbor a mile north says it smelled like rotten eggs at his kitchen window before he left for work. What you do in the next few hours decides how you spend the next month, explaining your operation or defending it. Odor complaint management isn't an equipment problem. It's a response problem, a recordkeeping problem, and a neighbor problem, in that order.
The first 24 hours, step by step
Work the list in order. Most of it takes one person, a meter, and a clipboard. Don't skip step two to get to step five.
Log the call before you walk outside
Time received, caller name, callback number, address or nearest cross streets. What they smelled, how strong, how long it lasted. Ask when it started, not just when they called. That gap matters later.
Pull the wind for the event hour
Direction and speed for the hour they described, not the hour the phone rang. If the caller sits north and the wind was out of the south, you're in the plume. If it was out of the north, write that down and keep looking anyway.
Walk the downwind property line
Two people, a meter each if you've got them. Walk the downwind fence and the road where the closest homes are. Note where it gets stronger and where it drops off. Record the time at every stop, not just the reading.
Write down what was running
Every unit operating during the complaint window. Turner passes on the windrows, a cover pulled off an aerated static pile, tipping floor doors open, sludge dewatering, headworks screening, a DAF skimming, a rendering cooker batch, a scrubber or baghouse down for service. Write down what wasn't running, too.
Check the controls before you blame the weather
Biofilter moisture and backpressure. Scrubber chemical feed and pH. Blower amps, cover condition, negative pressure on the building. If something was off, you'd rather find it this morning than have an inspector find it Thursday.
Call the neighbor back the same day
Even if you found nothing. Tell them what you checked and what you saw. A callback in four hours does more for your file than a letter three weeks out.
Fix it on the shift, or write down the interim step
If you found a cause, fix it and note the time. If the real fix takes two weeks, write down the temporary measure you put in place today and who signed off on it.
Notify the agency on your terms
If your permit has a reporting condition, meet it. If it doesn't, a short note to your county or state contact still beats them hearing it from the caller first.
Close the entry within 24 hours
Root cause if you have one, corrective action, who did it, follow-up date, signature. An open entry that just stops reads like a facility that quit caring.
What an odor complaint log has to capture
One page per complaint, nine fields. Fill it out at the time, not from memory on Friday afternoon. Every blank is a question somebody gets to ask you about later.
- Two separate stamps. People call hours after the fact, and by then the wind has turned. Without the event time, you can't line up anything else on this list.
- Name, phone, address or nearest intersection, and if they want a callback. Repeat callers aren't a nuisance. They're your early warning system, and they'll be the first witnesses if this goes further.
- Rotten egg, ammonia, sour, sweet, dead animal, burnt. Then your own descriptor and an intensity rating on one fixed scale your whole crew uses. Duration. Note if it held steady or came in waves.
- From your own station on site, at the height you actually measure. Airport data from 20 miles away is the first thing a decent expert takes apart.
- Temperature, humidity, barometric pressure, rain, cloud cover. Calm mornings under an inversion are when the phone rings. Write down the ground fog sitting on the pad at sunrise, because that detail explains the call.
- Hydrogen sulfide, ammonia, methane, total VOCs, carbon dioxide. Add PM1, PM2.5, PM4, and PM10 if you measure them. Time-stamped, with the location of each point. Upwind and downwind, so you've got your own background to compare against.
- Equipment, loads received, feedstock changes, pile ages, batch numbers, anything down for maintenance. Crews skip this field more than any other, and it's the one that usually answers the question.
- Names, times, the route they walked, what they found, what they changed on the spot. Short sentences beat a paragraph nobody can parse two years from now.
- Who you called back and when. If you called the agency, that goes here too. Then the follow-up date, the root cause once you have it, and the closing signature.
The mistakes that weaken your position
None of these are about odor control equipment. They're about paper and posture, and they cost more than a biofilter rebuild.
Opening with "that wasn't us"
Maybe it wasn't. You still have to show it, and a flat denial on the first call is the line that gets read back to you in a deposition. Say you're looking into it and you'll call back with what you find.
A log that starts the day the complaints started
A file with nothing but bad days says nothing about a normal one. You need the quiet weeks on record too, or you have no baseline and no way to say what changed.
Borrowing weather data
The wind at your property line isn't the wind at the regional airport. Terrain, buildings, and pile geometry all bend it. Your own station settles the arguments that borrowed data starts.
Grab readings taken after the fact
A reading at 10 a.m. says nothing about a 6 a.m. event. By the time somebody walks a meter out to the fence, the inversion has lifted and the plume is gone. That reads as no data, not as no odor.
Blank fields and back-filled entries
Handwriting that shifts, times that are suspiciously round, four complaints logged in one sitting. Reviewers catch it. One honest "unknown" is worth more than a tidy guess.
Entries that never close
An open complaint with no corrective action and no follow-up is worse than no log at all. It documents that you knew and did nothing.
Going quiet with the neighbors
Silence turns four callers into a neighborhood group with an attorney and a Facebook page. People will put up with an occasional bad morning. They won't put up with being ignored about it.
With a continuous record, and without one
The inspector never shows up during the event. They show up Thursday afternoon and ask about Tuesday at 6 a.m. Same five questions, two very different meetings.
- Without a record: you pull up a weather site and estimate. With a met station logging on site: you print direction and speed at the fence line, minute by minute, and the conversation moves on.
- Without a record: nobody had a meter out there at 6:15. With continuous points: you show hydrogen sulfide, ammonia, and particulate for that hour, plus the hours on either side of it.
- Without a record: you say you don't think so, which sounds like you don't know. With months of history: you show the same signature on four calm mornings and the operating change that followed each one.
- Without a record: a spreadsheet somebody typed up last night. With an automated system: readings written as they were measured, time-stamped, with nobody's handwriting in the middle.
- Without a record: an account from memory, three days later. With a closed entry: alert time, responder, corrective action, and the readings that came back down after the fix.
What a fence line point should record on its own
The log gets a lot easier to fill out when the data is already sitting there. A monitoring point at the property line should be writing this down around the clock, with nobody walking out to it.
The odorants, not one proxy
Hydrogen sulfide, ammonia, methane, total VOCs, and carbon dioxide, plus the mercaptans, trimethylamine, and sulfides that carry rendering and sludge odor. One gas by itself won't tell you which process is talking.
Particulate in four fractions
PM1, PM2.5, PM4, and PM10 off the same node. Dust calls and odor calls usually come from the same neighbors, often on the same morning.
Wind and weather at the site
A local met station on the same clock as the sensors. Direction, speed, temperature, humidity, pressure. That's what turns a reading into an argument about where it came from instead of a number with no context.
Enough points to cover the compass
In our layouts, composting sites and water resource recovery facilities come out to 3 to 8 points. Rendering and refuse-derived fuel operations, 4 to 10. Landfills, 5 to 15, depending on acreage and where the receptors sit.
Alerts before the phone rings
Thresholds you set, pushed to whoever is on shift. Catching a rise while the wind is still carrying it toward the county road is the difference between a correction and a complaint.
History you can hand over
Continuous readings, kept and exportable. When somebody asks for last quarter at the north fence, that should take a minute, not a week of digging.
Turning one complaint into a program you can defend
One logged complaint is paperwork. Twelve months of logged complaints with wind and readings attached is a program. That's what an agency wants to see, and what a plaintiff's expert would rather not find.
Map every call
Pin each complaint on an aerial photo with the wind vector for that hour. Patterns show up fast. If your callers cluster in one downwind sector on calm mornings, you know where the money goes.
Find your own operating windows
Once the events line up with operations, you can move the work that stinks. Turning at 2 p.m. with a 10 mph crosswind is a different day than turning at 6 a.m. under an inversion, and your log will prove it.
Set thresholds off your baseline, not a textbook
Watch a few quiet weeks at the fence line first. Then put the alert where your normal ends. A threshold copied from somebody else's site cries wolf until the crew stops looking.
Write the odor management plan around what you actually do
Response times, who answers the phone at 2 a.m., the escalation ladder, the monitoring route, the corrective action list. Then follow it. A plan you don't follow becomes evidence against you.
Train the front desk and the night shift
Calls land off-hours with whoever picks up. If that person doesn't know what to write down, the record is broken before anyone with a title hears about it.
Bring the agency in on a good day
An inspector who has already walked your site, read your plan, and looked at your data treats the bad morning differently than one meeting you for the first time at the gate.
Give the neighbors something real
You don't have to publish everything. Quarterly numbers at the property line and a straight answer about what you changed will cool down most of it.
Talk it through with our team
SmartCompost has been running continuous environmental monitoring since 2019, with gases and four particulate fractions on the same node (Smart.Odor at the perimeter, Smart.Mini when you need to walk a route). Send us your site layout and where the callers are, and we'll walk through what a fence line setup would have caught on the morning you just had.
Frequently asked questions
What do I do first when an odor complaint comes in?
Write it down before you walk outside. Time of the call, time of the odor, caller, location, what they smelled. Then pull the wind for the event hour and walk the downwind property line with a meter. Investigating first and writing it up from memory afterward is how good records go bad.
How fast do I have to respond to an odor complaint?
Check your permit conditions and your state or county rules first, since some spell out a response window and a notification trigger. Where nothing is written down, treat the shift as your deadline. Investigate the same day, call the neighbor back the same day, and close the log entry inside 24 hours.
What fields does an odor complaint log need?
Nine. Time received and the time of the odor event. Who called and where they were standing. What they smelled and how strong it was. Wind direction and speed from your own station. Weather. Gas and particulate readings at the property line, time-stamped, with locations. What was running. Who responded and what they changed. Then the follow-up: root cause, corrective action, closing date.
Should I log a complaint if I don't think the odor came from my site?
Yes. Log it, investigate it, and log what you found. A file full of entries reading "wind out of the north, upwind reading higher than downwind, source not confirmed on site" is worth far more than a thin file. It also protects you when the real source is the operation down the road.
Is continuous monitoring required for odor complaints?
Usually not. Odor is generally handled as a nuisance rather than a permitted pollutant with a numeric limit, so enforcement turns on complaints and an inspector's judgment. Continuous data is something you choose to have so that judgment call has facts under it. Consent orders and settlements do sometimes add a monitoring condition after the fact, and that's a much worse time to start.
Can gas readings prove the odor didn't come from my facility?
One reading proves nothing. A time-stamped series at several points, paired with wind from your own station, is a different matter. If the wind was out of the north and your north fence reads higher than your south fence, you have an argument that starts from data instead of opinion. It cuts both ways, which is exactly why people believe it.
How do gas readings relate to what the neighbor actually smelled?
Concentration and perceived odor are related, but they aren't the same thing. We turn continuous readings into an odor index, so a number at the fence line can be lined up against what people report. The index only works because the record behind it runs around the clock instead of showing up after the call.
Turn the playbook into a log
If your site cannot answer these questions today, that is the gap. Tell us how the plant runs and we will show what a continuous log would have caught.
Talk to our team →