Straight into the service manual page
WrenchQuarry
More

3 paths when a permit, rule or form conflicts

WrenchQuarry Editorial Team · Published · 14 min read · How these guides are written

When two written requirements disagree on a job, you have three defensible paths: follow the governing document, trigger a formal change, or resolve the conflict before work continues.

  • Identify which text has the force of law — a permit, statute, or adopted standard outranks guidance, forms, and instructions
  • If two rules of equal standing conflict, raise it with the body that owns them for amendment or repeal rather than picking one on site
  • When you cannot yet tell which text governs, pause the affected step, pull the full controlling document, and resume once you have read it
  • Keep unaffected job steps running while the conflicting step is held, so the delay stays contained
  • Record the resolution — the two texts, which one governed, the action taken, and the date — in the project records

Start with the document that has the force of law

The first path is to identify which of the two conflicting texts actually governs, and follow it while you sort out the rest. Some written requirements carry legal weight, and some carry the weight of a contract or an instruction. Knowing which one you are holding decides the rest of the job.

A permit is one of the clearest examples. When an agency issues a permit, the permit's own conditions control. If a general information page, a guidance document, or an explainer says something that runs against the permit, the permit still governs the work. The EPA says this outright for the 2017 Construction General Permit: if any explanatory information conflicts with a provision of the permit itself, the permit's requirements are the ones you must meet (EPA Construction General Permit FAQ). That single sentence shows how EPA's FAQ expects its explanatory material to be read against the permit.

Apply that same habit to every document in your job packet. Ask which text is the permit, which is a rule, which is a contract term, and which is a form or an instruction that supports the other three. The permit, the statute, and the adopted rule sit at the top. An informational page, a checklist, or a sample form sits below them.

Some adopted standards blur the line on purpose. Under Minnesota's framework, the Claims Release Standards and the state implementation guides adopted by the commissioner are not treated as rules under the state's rulemaking chapter, yet they carry the force of law from the effective date stated in the State Register notice (Minnesota Statutes Sec. 176.231). If your job packet contains one of these adopted standards, treat it as binding even though the statute calls it something other than a rule.

The practical move is simple. Put every conflicting document on one table. Label each one by what it is: permit, statute, adopted standard, contract term, guidance, or form. The two that conflict will almost never sit at the same level. When they do sit at the same level, you are in a different situation, and the second path below is yours.

Trigger a formal change when the conflict runs deep

The second path exists for conflicts that cannot be resolved by choosing a higher document, because the conflict lives inside the governing documents themselves. When a rule, a permit condition, or a standard form has gone stale or fights with the work as it now stands, you do not quietly work around it. You start the change machinery.

Rules get amended and repealed when they conflict with each other or fall out of date. In Minnesota, the commissioner may amend or repeal conflicting or obsolete rules through the state's rulemaking procedures. That is the route for a conflict between two rules of equal standing. You do not pick a winner on site. You raise it, document it, and let the owning body amend or repeal.

Forms follow the same logic on a smaller scale. Caltrans sends its construction staff to its manual's changes section when an existing form no longer serves its purpose (Caltrans Construction Manual, Section 5-1). The instruction assumes forms have an owner, a revision path, and a place where the change gets recorded. Use that path instead of handwriting a correction on a live form.

Here is how this plays out on a job. Your crew has a standard reporting form that asks for fields the permit no longer requires, and misses a field the permit does require. Filling the form as written puts you out of compliance. Filling it as you think it should be written puts you out of alignment with the record set everyone else is using. The right move is to submit the change through the section the manual names, get the revised form into circulation, and only then resume reporting on it.

For rules, the same discipline applies. If two rules of equal rank conflict, and no permit or contract term breaks the tie, the conflict is a defect in the rules themselves. Raise it with the agency that owns them. Ask for the amendment or repeal. Track the State Register notice or the equivalent publication in your state so you know when the change lands.

The common thread in this path: the conflict does not get resolved by whoever is standing closest to the work. It gets resolved by the body that owns the text, through the procedure written for that purpose.

Pause the conflicting step and get the governing text in hand

The third path is the working answer on most job sites, because it is the one you can run in a single afternoon. When two requirements disagree and you cannot yet tell which one governs, you stop the step that the conflict touches, get the controlling text in front of you, and resume once you have read it.

The reason this works is that the governing document is always readable. A permit is a public document. A statute is published. In Minnesota, an adopted standard appears in the State Register notice. A contract is in your own files. The gap is rarely access. It is that the crew on the ground was working from a summary, a memory of a training session, or an outdated attachment while the actual text sat three clicks away.

Make this a standing habit on every job. The moment two requirements disagree, put the step on hold. Pull the full document, not the excerpt. Read the provision in context. Then decide with the full text open.

EPA's Construction General Permit FAQ gives a useful working definition when you need one: CWA section 502 and 40 CFR 122.2 hold the complete definitions for point source. That redirect pattern shows up everywhere. A summary points to a definition. A definition points to a statute. Follow the chain until you reach the text that actually defines your obligation.

Two more details from the same permit are worth having in hand when the conflict touches coverage. Whether the permit comes from EPA, a state, or a tribe, it still has to carry requirements implementing the technology-based effluent limitations for construction and development at 40 CFR part 450. If someone tells you a state-issued permit can be looser on that floor, the permit framework says otherwise.

When the sources leave a genuine gap, raise it with the agency that issued the governing document. That body can confirm what applies to your site.

Here is a worked case in plain words. Your field crew is using a project reporting form. The form's instructions came from an older revision. The current permit says one of the fields needs data the old form never captured. You run path one first: the permit controls, so the form must carry the data. If the form itself cannot be corrected without a revision, you move to path two: submit the change through the changes section of your manual and wait for the revised form. Until either lands, path three keeps the reporting step paused so no one files a record they will have to retract.

A quick map of the three paths

Use this small map to decide which path fits the conflict in front of you.

PathUse it whenWho resolves it
Follow the governing documentA permit, statute or adopted standard outranks the other textYou, on site, with the full text open
Trigger a formal changeTwo rules or a rule and its form conflict at the same levelThe agency or body that owns the text
Pause and pull the controlling textYou cannot yet tell which text governsYou, then the issuing agency if a gap remains

Read every supporting page as a subordinate

Guidance pages, FAQ sheets, explainer articles, and training decks are built to be helpful. They are also built to be shorter than the thing they explain. Reading them as if they were the rule is how conflicts start.

Treat every supporting page as subordinate to its parent document. The permit is the parent of its FAQ. The statute is the parent of its implementation guides. The contract is the parent of the forms and instructions that flow from it. When a child page and a parent text disagree, the parent text wins.

This is the same discipline you apply to reading a news story about a regulation. The story is a summary. It may be accurate. It may also be describing a different revision, a different jurisdiction, or a different phase of the same program. The permit sitting in your project file is the version that binds your work.

Build the habit of checking the revision marker on every supporting page you pull. A FAQ can be updated on a different schedule than the permit it describes. If the FAQ and the permit disagree, and you cannot tell which was revised last, go with the permit. That is the document whose text states it controls.

Give your team one rule to follow on this point: any summary, checklist, or excerpt in the job packet is reference material, and the full document it came from is the authority. Print the authority. Keep it with the packet. Mark the page that settles the question.

Name the conflict in writing before anyone argues about it

Conflicts get resolved faster when both sides can see the same two texts side by side and agree on what each one actually says. That happens when someone writes the conflict down.

Do not walk into a meeting and say the instructions conflict. Write two short paragraphs. In the first, state requirement A in its own words, with a pointer to where it lives. In the second, state requirement B the same way. Then state, in one sentence, the specific step on the job where the two cannot both be followed.

This stops the conversation from drifting into opinions about intent. The meeting now has an artifact. Everyone reads the same two sentences. The person who owns the governing text can say which one stands, and the person who owns the form or the process can start the revision.

The same note becomes your record if the conflict is later questioned. A dated memo showing the conflict, the two texts, and the step affected is worth more than a memory of a phone call. File it with the project records. If the change path runs through a manual section, attach the memo to the request.

Keep the note neutral. Describe what each text says. Do not characterize either one as wrong. The point is to hand the owning body a clean description of the problem, not to win the argument in advance.

Check who owns each text before you act

Every requirement in your packet has an owner. The permit has the issuing agency. A statute has the legislature. An adopted standard has the commissioner or the adopting body. A contract term has the parties who signed it. A form has the office that maintains it.

Before you act on a conflict, name the owner of each side. That tells you which path applies. If both texts belong to the same owner, ask that owner which one stands, or ask for the amendment. If the texts belong to different owners, the conflict may be a genuine gap between two systems, and the issuing agency of the governing document is the right place to raise it.

Ownership also tells you how fast the resolution can move. A form can often be revised inside a single office. A rule moves through a published procedure and takes longer. A contract term changes by agreement between the parties. Knowing the owner keeps your expectation of the timeline honest.

Assign this check to one person on the job. When a conflict surfaces, that person identifies the owner of each text, routes the note, and tracks the response. A conflict with no named owner and no named router tends to sit in an inbox while the crew waits.

Keep the job moving inside the bounds of the higher text

You still have work to do while a conflict is open. The trick is to keep moving only on the steps the governing text clearly allows, and to hold the step the conflict actually touches.

Sort your job steps into two piles. In pile one: steps where no conflicting requirement applies. Keep those running. In pile two: the single step where the two texts collide. Put that step on hold under path three, run the change request under path two if needed, and resume when the controlling text is in hand.

This is how a permit conflict becomes a contained delay instead of a full stop. The crew keeps working the parts of the job that are unambiguous. Only the ambiguous step waits. Your records stay clean because nothing gets filed under a requirement you have not confirmed.

The discipline here is resisting the urge to guess on the held step. A guess that turns out right still leaves you without a record of why you chose that reading. A guess that turns out wrong puts a defective record into the project file. Holding the step costs you the time it takes to read the text. Guessing costs you the credibility of the record.

When the text arrives and the step resumes, write one line in the project record: which document settled the question, and what the step now requires. That line closes the loop for the next person who opens the file.

Put the resolution into the record set

A resolved conflict belongs in your records with the same care you give any other project document. Otherwise the next person on the job inherits the same disagreement you just spent the afternoon clearing.

Your closing record for a resolved conflict needs four things. First, the two texts as they stood when the conflict was found, with pointers to each. Second, which one governed and why, in one plain sentence. Third, the action taken: step held, text pulled, form revised, or rule raised for amendment. Fourth, the date the resolution took effect for your job.

If the resolution came from a formal change, include the reference for that change as well. A revised form carries a revision marker. An amended rule carries a publication reference. That reference is what ties your on-site decision back to the document that authorized it.

File the record with the project records, in the same place you keep the permit and the contract. A resolution that lives only in a supervisor's email thread will not be found at the moment it is needed.

Run one review pass over the packet after a conflict closes. Look for other copies of the stale document still circulating: an old attachment, a printed excerpt, a saved draft. Retire them. A single surviving copy of the superseded text starts the whole cycle again the next time someone finds it.

Answering the questions owners actually ask

Which text wins when my permit and my agency's guidance page disagree? The permit wins. EPA's Construction General Permit FAQ states that when explanatory information conflicts with a corresponding provision of the permit, the permit's requirements are what you must follow. Read the guidance as a helper, and work from the permit text.

What do I do when two rules of equal standing conflict? Raise it with the body that owns them and ask for the amendment or repeal. Minnesota's statute gives the commissioner the power to amend or repeal conflicting or obsolete rules through the state's rulemaking procedures. Do not resolve an equal-rank rule conflict by picking the one that suits the schedule.

My form does not match what the job now needs. Who fixes it? Route the change through your manual's changes section. Caltrans sends its construction staff there when an existing form no longer meets its intended purpose. Use that path rather than annotating a live form in the field.

Does a state-issued permit carry the same federal floor as an EPA one? Yes on that floor. Whether EPA, a state, or a tribe issues the permit, the CWA and EPA regulations require NPDES permits to include requirements implementing the technology-based effluent limitations for construction and development at 40 CFR part 450.

What if an adopted standard is not technically a rule but still binds my job? Treat it as binding. Under Minnesota's statute, the Claims Release Standards and state implementation guides adopted by the commissioner are not rules under the rulemaking chapter, yet they carry the force of law from the effective date published in the State Register. The label on the document does not decide whether it governs your work.

Where do I find the definition that a permit keeps pointing to? Follow the reference chain. For point source, CWA section 502 and 40 CFR 122.2 carry the complete definitions. Keep following until you reach the statute or regulation itself.

General information, not legal or tax advice.

Sources

More field guides