Most wellness programs are bought the same way. A vendor demos something, it looks reasonable, and it gets approved, because saying no to firefighter mental health isn't a good look in a budget meeting.
Then adoption stays low, and nobody says anything, because the program isn't the problem anyone wants to name.
I spent over twenty years in the fire service. These are the five questions I'd put to any vendor before signing, and the answers that should end the conversation early.
Why department wellness programs stall
Most programs aren't bad. They're bought against the wrong test.
The demo shows features. The contract counts enrollment. Neither one tells you whether a member in the worst month of their career will use the thing, or whether they'll trust what happens to their data when they do.
In this job, trust decides adoption. A member weighs every program the same way: what does using this cost me? If the answer is unclear, the safe move is to stay away, and most do. Five questions change the test.
1. What does it reach, and when?
If a program activates after someone raises their hand, you've bought triage. Triage is worth having. It isn't prevention.
Raising your hand in this job costs something real, and plenty of members never do it. A program that waits for the hand misses the people who never raise it.
Ask the vendor what the program sees in week one of a drift, not week twelve of a crisis. If the honest answer is "nothing until someone calls," write that down. It's the difference between monitoring stress and managing it.
2. Who sees the individual data?
Ask three things, and get the answers in writing:
- Who at the department sees an individual member's data, if anyone.
- Where the data is stored, and who owns it.
- Whether a subpoena or a fitness-for-duty review reaches it, and what the vendor does when that happens.
Your people will assume the worst answer unless you show them the real one. If the vendor can't answer in one sentence, your crews already know.
Put the answers in the member-facing rollout material, in plain language. A privacy policy nobody reads protects the vendor. A one-page answer your members have read protects the program.
3. What's the opt-out, and what happens to someone who takes it?
A program with a soft penalty for declining isn't voluntary. The penalty doesn't have to be written down. It shows up as a captain who notices who didn't sign up, or a question at a promotion board.
Ask the vendor, and ask yourself: if a member opts out tomorrow, who finds out, and what changes for them? The right answer is nobody, and nothing.
4. What does the vendor measure to prove it worked?
If the only metric is enrollment, you'll get enrollment. Sign-ups prove the rollout worked. They say nothing about your people.
Ask what the program will change in the numbers you already track:
- Sick time
- Light duty
- Separations and early retirements
- Overtime driven by vacancies
Pull those numbers for the last two years before the program starts. Without a baseline, nobody will be able to say whether anything changed.
A vendor who won't name any of those in advance is telling you they don't expect to move them.
5. Does anyone on their side know what a 48 is?
Not sympathy. Working knowledge. The rotation, the tones at 3am, what a bad run does to the next shift.
Your members decide within one sentence whether the person on the other end has done the job. If not, they give the edited version, the one they give every outsider, and the program never sees the real problem.
The demo shows the features. The opt-out tells you whether it's voluntary.
Put a member in the room
Run the demo with two or three members at the table, not only the officers who sign off. Pick people the crews trust, not the ones most likely to say yes.
Let them ask the five questions, then watch the answers land. Members hear things in a vendor pitch that a budget meeting misses: the phrase that sounds like it came from HR, the pause before the privacy answer, the clinician who has never ridden an engine.
If the people you're buying it for don't believe the answers, the contract won't change their minds. Better to know that before you sign.
Answers that should end the conversation
- "We share aggregate reports with command," with no clear line on individual data.
- Success measured in enrollment or downloads, and nothing else.
- An opt-out that runs through a supervisor.
- "Our clinicians are trained in first responder culture," with nobody on the team who has worked the job.
- Any claim that the program diagnoses, predicts or prevents a condition. Wellness tools don't diagnose. A vendor who says theirs does is overselling it.
None of this needs a bigger budget
It needs the questions asked before the contract instead of at the renewal.
The IAFF and IAFC publish a joint Wellness-Fitness Initiative for department programs. These five questions sit on top of any framework you use. They're about one thing: whether your people will trust a program enough to use it.
If you're evaluating something this budget cycle and want Neurovus's answers to all five, ask me. I'll put them in writing, including the uncomfortable ones.