A program you can't document is a program you can't defend. Here's what good reporting looks like and how boards use it at meetings, audits, and the reserve study.
There's a version of iguana control where a truck shows up, does something, and leaves — and the board has no idea what it paid for. And there's a version where every visit produces a record the manager can file and the treasurer can show a skeptical owner. The difference is documentation, and for a board it's the difference between a defensible line item and a soft target at the annual meeting.
Good reporting isn't paperwork for its own sake. It's what lets a board see whether the program is working, justify the spend, and make the case at reserve time.
What a service record should contain
After each visit, a board should get a clear record of what happened — not a vague 'serviced the property.' The useful version tells you where the crew worked, what they found, and what they did about it, in a form the manager can drop into a file without translating.
- Date of service and which common areas were worked.
- Activity found — burrows located, basking hot spots, fresh diggings.
- Work performed — removal, trapping, burrow collapse, climb-route prevention.
- Catch counts where relevant, so trends are visible over time.
- Any recommendations for the board — a stretch of seawall trending worse, say.
How boards actually use it
The reporting earns its keep in three places. At the monthly or annual meeting, it's what the treasurer shows the owner who thinks the program is a waste — here's the activity, here's what came out. At audit time, it's the paper trail for the expense. And at the reserve study, a run of reports showing steady pressure on the seawall banks is the evidence that ties iguana control to the shoreline reserve line. Documentation is what turns 'we spend money on this' into 'here's what it's protecting.'
Trends matter more than any single visit
A single service record is a snapshot; a run of them is a trend, and the trend is what tells you something. Rising catch counts on one lake bank means that stretch needs more cadence. A quiet season after a heavy spring means the nesting work held. A board reading the trend can spend smarter — putting cadence where the pressure is instead of spreading it evenly — which is exactly the kind of decision documentation makes possible.
One contact, consistent format
Reporting is only useful if it's consistent, which is another argument for one accountable contact rather than a rotating crew. Nick knows the property, so the reports build on each other instead of resetting every visit. For managers running several communities, that same consistent format across the portfolio makes every board meeting easier. You can see how we structure it at /commercial or fold it into a proposal at /commercial/request-a-proposal.
Questions we hear
What should we get after each visit?
A service record showing the date, which common areas were worked, the activity found, the work performed, and catch counts where relevant — plus any recommendations. Enough for the manager to file and the treasurer to show an owner, not a vague 'serviced the property.'
How does reporting help at the reserve study?
A run of reports showing steady pressure on the seawall and lake banks ties iguana control to the shoreline reserve line — it's the evidence that the program is protecting a capital asset. That framing is what turns the spend from a nuisance expense into reserve protection.
Why does trend data matter more than one report?
A single record is a snapshot; a run of them shows where pressure is rising and where nesting work held. Reading the trend lets a board put cadence where it's actually needed rather than spreading it evenly — smarter spending, backed by documentation.
Services in this guide
