Hiring and firing with a paper trail

You have never fired anyone. The operator you need to let go has been at the utility longer than you have, and knows every valve and connection in the ground better than anyone else on staff. There is nothing in the file that says any of this was a problem before today.

That gap is the real risk. A decision made without a paper trail looks arbitrary even when it is not, and it leaves the utility exposed the moment anyone asks why.

Rung 4 of the manager track.

None of what follows is legal advice, and a real separation decision belongs in front of an employment attorney before you act on it. What follows is the documentation habit that makes a later review, by a board, an attorney, or a court, start from a written record instead of a memory.

What the file is actually for

A personnel file earns its value on the day nobody expected to need it. If you have documented performance conversations, completed training, and problems raised as they happened, a separation looks like the end of a pattern. If the file is empty, it looks like a decision made on a bad day, whatever the truth actually is.

The habit has to start before there is a problem, not after. Waiting until you are ready to let someone go, then building a file from memory, is the most common mistake a first-time manager makes. It is also the hardest one to fix after the fact.

A paper trail protects the person being managed as much as it protects the utility. A documented performance conversation gives someone a fair chance to fix a problem before it turns into a separation, and a written expectation is not a trap. It is notice, given early enough to matter.

Hiring the next operator on paper

The hiring decision is where the file starts, and small utilities skip steps here more than anywhere else, because the labor pool is thin and the need is urgent. A background check belongs in that process for every employee of the system, the certified operator included. Confirm a licensed operator's certification history directly with the state board rather than taking the application at face value.

Verify experience, not just employment. An employer's letter proves someone had a job, not what they did on it. Ask for a reference from another licensed operator who can speak to the actual work: Florida already requires exactly that peer reference before it will credit hands-on plant experience.

Build the interview around what a person can do, not just what the résumé says. Ask them to walk through locating a leak, recognizing an illegal connection, or explaining a basic compliance rule in plain language. A scenario question shows whether someone can still do the job, not just whether they once could.

Put the terms in writing before the first day: the role, the compensation, who is in responsible charge of what, the training and continuing education the job requires, and what happens if the person is unavailable in an emergency. A written agreement that spells this out is the first real entry in a file that would otherwise stay empty until something goes wrong.

If you cannot keep a certified operator on payroll and are contracting instead, the same habit applies with a few extra lines: how often the operator will visit and for how long, who the named backup is, how fast that person can be physically on site in an emergency, and proof of liability insurance naming the utility as additional insured. Whichever arrangement you choose, divide the tasks explicitly between what the utility's decision-maker owns and what the operator owns, write it down, and revisit it. A contract does not move the legal responsibility off the utility's books; it only changes who is doing the day-to-day work.

What goes in the file, and when

A file that only holds a hiring letter and a termination letter tells no story in between. Build it as you go, not after the fact.

• At hiring: job description, written offer or agreement, background-check documentation, proof of certification and its expiration date.
• On an ongoing basis: copies of renewed licenses, continuing-education records, and a dated note for every performance conversation, written or verbal, with what was discussed.
• At any disciplinary step: a dated, written account of what happened, what was said to the employee, and what is expected going forward.

Keep the file after someone leaves too. Records guidance compiled across state manuals recommends holding personnel files at least a few years past the end of employment, and considerably longer, sometimes decades, if a workplace injury was involved. Write the note the same day if you can; a short, dated account beats a long one reconstructed from memory later.

Progressive discipline as a ladder, not a cliff

Employees are not the only ones who face a discipline ladder in this line of work. States run one for the operator certificate itself, worth borrowing even though it governs the license, not the job: a first issue draws extra scrutiny, a repeated or more serious one draws a suspension, and only a pattern or something severe ends in the certificate being pulled outright, with no way back.

The employer's version should run the same shape. A single missed expectation is a conversation and a note in the file. A pattern, or something serious enough to skip ahead, is a written warning stating plainly what has to change, with termination as the last step, not the first.

Two things make that ladder credible later. Apply it the same way to everyone, since a policy enforced selectively looks worse than no policy at all. And put it in writing, as an actual personnel policy the board has adopted covering hiring and firing, grievance, and conflict of interest, not a habit the manager carries around unwritten.

A personnel policy earns trust the same way a rate policy or a shutoff policy does, by having the same three parts every time: why it exists, who it covers and how someone can appeal a decision under it, and exactly what is required and for how long. A one-page hiring-and-firing policy with those three parts, adopted by the board and handed to every new hire, does more for a future separation than any amount of good intentions in the moment.

Separation that survives a second look

By the time you reach a separation, the paper trail should already exist. The final step is documenting the decision itself as carefully as everything that led to it. Write down the reason, tie it to the pattern already in the file, and keep the reasoning consistent with how the same policy has been applied to others.

If the decision goes to the board, the same practices that protect a board member from personal liability protect the decision itself. A member who acts in good faith within their authority is generally protected; one who acts outside it, or ignores a known problem, is not. An attorney's advice recorded in the minutes, a written motion stating exactly what was decided, and an accurate vote count are what make that record real.

Silence in the file is not neutral; it reads later as if nothing was documented because nothing needed to be, and that is rarely the actual story. None of this replaces legal review of an individual decision, especially one involving a long-tenured employee or anything that could look like retaliation. What a consistent paper trail does is make sure the answer is already written down by the time anyone asks the question.

You have the paper trail now. What keeps you from needing it as often is a different problem entirely: read keeping a good water operator next, or head back to the manager track.