So, you’ve realized that your current EHS system (whether it’s built on paper, spreadsheets, or outdated software) has reached its limits. You’ve done the legwork, identified the right digital EHS tool, and built a solid business case. Great. But even the strongest pitch will face objections from senior management—they’re responsible for keeping a close eye on the company’s finances, after all.

The good news? With the right answers ready, you can confidently justify EHS investment and turn pushback into approval. Here are nine objections you’ll likely face—and how to handle them like a pro.

#1. What’s wrong with how we currently manage EHS?

It’s only natural for people to resist change. No matter how inefficient, the status quo is familiar and comfortable. To counter:

• Highlight the inefficiencies, limitations, and risks in your current processes.
• Show the hidden costs of inaction (from lost productivity to regulatory fines).
• Remind senior leadership of the ROI that comes from lower operational costs.

#2. It’s too expensive.

Sticker shock is common. No matter how phased your rollout, the upfront costs of new software can trigger a knee-jerk reaction. Flip the conversation to ROI and focus on:

• Lower insurance premiums
• Reduced payouts for accidents
• Less admin work = increased employee productivity
• Higher product quality = fewer reworks
• Stronger reputation with regulators and clients

Most organizations recover their investment within 12–36 months. Use a cost-benefit analysis (and our ROI tool) to show how quickly savings add up.

#3. IT doesn’t have time to approve new software

Involve IT from the start to show that you’ve already got their buy-in. Even better, demonstrate how they’ve played a key role in defining requirements.

#4. Why should EHS get the budget over other departments?

Senior leadership gets budget requests from all over your organization, so you need to show how investing in EHS protects the entire business. For example:

• Suppliers increasingly require EHS documentation in tenders. Digital tools ensure you always have this data at your fingertips.

• Strong EHS practices protect brand reputation and customer trust—crucial for winning and keeping clients.
• Incidents or non-compliance have enterprise-wide impact, from legal costs to downtime.

#5. Will implementing new EHS software disrupt our operations?

Implementing new software is a big task, but you can show how you’ll minimize disruption.

• Share your phased rollout plan: start small (one site, one module) before scaling.
• Emphasize vendor support, including training and configuration that will smooth the transition.
• Position disruption as short-term pain for long-term efficiency.

#6. Employees won’t use it

Senior leadership has probably seen software projects fail before. Reassure them by:

• Involving employees during planning so the tool meets their needs.
• Providing hands-on training and ongoing support.
• Sharing proof of usability. For instance, TenForce scored a perfect rating for UI and mobile usability in the 2023 PSM Verdantix Green Quadrant.

#7. How long does it take to see ROI from EHS software?

ROI is one of your most persuasive arguments. Show that the upfront investment is dwarfed by the long-term gains in efficiency, safety, and cost savings.

• Explain that most companies see a return within the first year, with full payback in three to five years.
• Present a cost-benefit analysis including fewer incidents, lower insurance costs, streamlined processes, and reduced waste.
• Share success stories from similar organizations.

#8. Isn’t EHS software too complex for our organization?

Complexity is a misconception. What seems “simple” today (like spreadsheets) quickly becomes complicated when you’re managing multi-site operations and thousands of records. To counter:

• Highlight how modular design lets you start with only what you need today and add more later.
• Stress how software can be customized with tailored workflows that fit your processes.
• Emphasize vendor training, intuitive UI, and ongoing support.

#9. Can’t we build this in-house?

On the surface, building in-house looks like a cost-saving option. In reality, it creates risk. Here’s how to counter that argument with senior leadership:

• Point out that your IT team is already stretched thin. Building and maintaining custom software pulls focus from critical projects.
• Remind them that if a developer leaves, the expertise goes too, leaving you with unsupported software.
• Commercial EHS tools like TenForce are updated regularly to keep up with new regulations and security standards. In-house builds can’t adapt as quickly.
• Stress the time difference: in-house projects can take years before they deliver real value. With TenForce, you can begin rolling out in weeks and expand at your own pace.

By choosing a proven vendor, IT stays focused on core responsibilities while you benefit from expert support.

Pro tip: Bring an IT colleague into the discussion. Their firsthand experience often reinforces just how costly and risky in-house development really is.

Ready to turn objections into wins?

With your responses prepared, you’ll be well-equipped to confidently defend the business case for your new EHS tool. Just remember, each objection is a chance to highlight the value and pressing need for your new tool, ultimately helping you justify EHS investment and win senior leadership over.

Want the full playbook for winning over leadership? Download our EHS Business Case Guide:

Sign Up for email updates about our latest projects, articles and online events.

Join our 1k+ subscribers