Rodent Monitoring Program Consulting

Device layout, trend reporting an in-house team can actually run, and an audit of a program that is producing records instead of data.

The problem this solves

Most rodent monitoring programs are inherited. Somebody installed devices, somebody else took over servicing them, and the layout has never been re-read against the building it sits in. The paperwork is complete. The site still cannot answer the question an auditor, an insurer or a board eventually asks: is this getting better or worse, and how do you know?

That gap is not usually a technician problem. It is a design problem. A program that was never built to produce an answer will not start producing one because it is serviced diligently.

Designing the device layout

Placement follows the structure. A device earns its position because of what is behind, beneath or beside it — an entry point, a dock door, a drain, a wall base, a void, a route between two of those things. It does not earn it by being twenty feet from the last one.

Evenly spaced perimeters are the most common inherited layout and the least informative. They satisfy a count. They tell you a number was met. What they cannot tell you is which opening the animals are using, because they were never placed against the openings in the first place.

A layout designed against the building produces something the even-spacing version cannot: catch that means something. When a device that sits eight feet from a specific penetration starts producing and the ones either side of it do not, that is a location, not a statistic.

Trend reporting the team can actually run

This is where most engagements spend their time, and it is the part that decides whether the program survives the consultant leaving.

Reporting has to be built so that the people on site can run it. That constrains the design in useful ways. It has to use the units they already record. It has to survive staff turnover, which means it cannot depend on one person’s spreadsheet or one person’s memory of what a column meant. It has to produce the comparison an auditor asks for — this quarter against the last, this area against the others, this species against the rest — without anyone rebuilding the analysis by hand each time.

And the thresholds have to be written down in advance. A threshold decided after the fact is not a threshold, it is a justification. Deciding beforehand what level of activity in which area triggers which response is what turns a monitoring program into a control program.

Auditing a program that is not producing data

The third piece is reading an existing program and saying plainly where it fails. The questions are consistent across sites:

Does the map match the floor? Pick three numbers off the map and go find them. This fails more often than anyone expects, usually because devices were moved for a good operational reason and the map was never updated.

Do the records support aggregation? If the catch column is free text, nothing can be plotted from it, and nobody discovers that until a year of data is worthless.

Is anything actually plotted? A site with clean raw data and no analysis has a filing system.

Are corrective actions closed with an action? “Continue monitoring” is not a corrective action. It is a note that the problem is still there.

Does anyone own the structural half? Rodent findings resolve into sanitation items and structural items, and the structural ones are the ones that stop recurrence. A program where every corrective action lands on the cleaning schedule will keep generating the same findings indefinitely.

The independence principle

The deliverable is a program the facility’s own people maintain.

That is stated as the goal because the alternative is easy and profitable, and it is worth being explicit about not doing it. A monitoring program can be designed so that only its designer can read the output — bespoke thresholds, an analysis nobody on site can reproduce, a reporting format that requires a return visit to interpret. That produces a recurring engagement and a client who never becomes competent at their own operation.

A program handed over properly ends with the site able to run it, read it, and defend it in an audit without the consultant in the room. If a facility calls afterwards, it should be because something changed in the building, not because they cannot understand their own numbers.

How this sits with the rest of the work

This is advisory work and it is sold separately from service. A site that keeps its existing contractor is a normal client here — arguably the most common one — and the engagement is not a route into a service contract.

Where it connects to the rest of Graduate’s work is the reading. The same discipline that decides which four openings out of forty are worth closing is the one that decides where a device belongs and what its catch is telling you. Structural exclusion closes the routes; monitoring tells you whether the closure worked and where the pressure moved to.

Where this work happens

The service business covers New York City and Nassau and Suffolk counties, and stops there.

Consulting does not. This work is delivered internationally, including on offshore assets — which is the practical reason for the TWIC, HUET and Tier 1 offshore credentials. Unescorted access to a secure maritime facility requires the first; boarding a helicopter to a platform requires the second.

What it costs

Quoted per engagement, with no published rate. Local work, onshore travel and offshore work are three different numbers and one figure would misrepresent two of them. Describe the site, where it is, and which of the three pieces you need, and that is enough to quote against.