Sales Process, CRM & Deal Stories — Environmental / DEQ

DEQ Worksheet & Examples

← Resource Library Rhino U

Print this worksheet and use the example below as a reference to guide you through the process of finding DEQ answers for your customers: the DEQ Approval Worksheet.

Worked Example — Idaho

A completed worksheet to compare against. Citations point to where each answer lives.

State: Idaho    Target market area: statewide

A. The basics

B. The approval path

C. Logistics

D. Local layers

E. Design standards that touch our spec

F. The sales takeaway

Overwatch hook: because a lift station always goes through DEQ in Idaho on a 42-day clock, the firm's schedule risk lives in that review. We help them assemble a clean, code-compliant package and answer DEQ's questions, which protects the timeline.

Teaching note: notice which rows came from the code (agency, citation, who approves, design standards, review deadline) and which required confirming with the agency (fees, current reviewer, local permits). Expect that split for every state and never invent the logistics.

Worked Example — Utah (home state)

Use this in the walkthrough so trainees see a completed worksheet on familiar ground. Notice how different the shape is from Idaho even though both are "DEQ" states.

State: Utah    Target market area: statewide (home base)

A. The basics

B. The approval path

C. Logistics

D. Local layers

E. Design standards that touch our spec

F. The sales takeaway

Overwatch hook: in Utah the leverage is the construction-permit-vs-municipal-sewer question — getting that call right early decides whether the firm faces a permit at all and how long the schedule is. We help them frame the project correctly to DWQ and assemble a clean R317-3 package.

Idaho vs Utah — the contrast to teach

The lesson: same agency type, very different process. That's exactly why a rep researches each state instead of assuming the last one applies.

DEQ Game Plan — making the case for approval

"Selling the DEQ" doesn't mean dodging the rules. It means knowing that most rules give you more than one compliant path, then helping the engineering firm pick the path that's cheapest and fastest while still meeting the rule's intent — protecting public health and water. A reviewer's job is to say yes when the intent is met; your job is to make that yes easy and well-documented. Done right, this is the support that makes a firm spec Overwatch instead of treating it as a commodity pump.

Step 1 — find the "OR" in the rule

Idaho's reliability requirement is the model example. Section 440.07.b doesn't demand one fixed solution — it accepts emergency pumping capability (two independent utility substations, a generator, or portable pumping), or adequate emergency storage, or (for an existing station being modified) a demonstration of overall system reliability to DEQ. Each path has a different cost and footprint. If a site has no room or budget for storage volume, the reliability or standby-power route may be the better sell — and you're the one who points that out.

Step 2 — talk to DEQ before the design is locked

Use the early touchpoint every state offers: Idaho's regional office, Utah's pre-design meeting. Ask the reviewer which path they prefer to see and what evidence convinces them. A reviewer who has agreed to the approach in a pre-design conversation rarely fights it at formal review. This is where the 42-day clock either runs clean or restarts on a rejection.

Step 3 — hand them an evidence package, not a promise

Whatever path the firm chooses, back it with documentation a reviewer can sign off on: redundancy and standby-power details, alarm and telemetry specs, pump performance and design calcs, and an O&M plan showing response times. For a reliability argument especially, the case is only as strong as the proof that the system won't overflow before someone responds.

Step 4 — position it to the firm as risk and schedule relief

Tie it back to what the firm cares about: "We'll help you build the reliability case so you can right-size or skip the emergency-storage volume and still clear DEQ on the first pass." That's time, cost, and schedule certainty — the reasons to choose Overwatch.

Keep it straight with DEQ. Use the paths the code allows and document them honestly. Overstating reliability or misrepresenting a design to win an approval burns the firm, the project, and our standing with that reviewer on every future deal. The durable advantage is being the partner DEQ trusts, not the one who games them.

← Back to the Resource Library