No Compliance Forms Are Showing
The Compliance tab lists the forms your state requires for a project. It finds those forms by matching the project's state against the compliance rules DrillerDB holds for that state. If DrillerDB cannot work out which state a project is in, it has nothing to match, so the tab comes up empty even though forms exist for the state you work in.
Quick Start: Fill an Empty Compliance Tab
- Open the project and click the Compliance tab.
- Read the message on the empty card. It tells you which of the causes below applies.
- If the message names a state you do not work in, set the state on the project itself.
- If the message names no state, go to Settings > Company Info.
- In the Company Information card, set Default State, then click Save.
- Reload the project's Compliance tab.
Setting Default State is the fix for most empty Compliance tabs. It also gives every future project a state to fall back on, so the problem does not come back on the next job.
What the Empty Card Is Telling You
The Compliance tab shows one of five messages when it has no forms to list. They mean different things, so read the message before you change anything.
| Message | What it means | What to do |
|---|---|---|
| No Compliance Requirements | DrillerDB worked out a state for this project and found no forms configured for it. The message names the state. | Check the named state is right. If it is, contact support so the forms for that state can be added. |
| Add the county on the Location tab to finish the requirements check | The project has no county. DrillerDB needs one before it can work out which local permits apply. | Click Go to Location under the message. It opens the project with the County field selected. Choose the county, then reload the tab. |
| Requirements not fully determined | DrillerDB could not finish deciding which rules apply, and the county is not what is missing. A warning appears above the card and names what it needs. | Set the field the warning names, then reload the tab. See When the Tab Says Requirements Not Fully Determined. |
| No [timing] forms required | You have a timing filter on, such as After Completion, and nothing matches it. | Clear the timing filter to see all required forms. |
| No State Set | DrillerDB found no state on the project. A second line is added when it can confirm you have no company default either. If that line is absent, it could not read your company settings on that load. | Set the project's state in the Main tab. To cover every blank-state project at once, set a company Default State instead. |
When the Tab Asks for the County
A project with no county cannot be matched against county permit rules, so the requirements check stops before it finishes. Rather than say the check did not finish, the tab says what it needs:
Add the county on the Location tab to finish the requirements check
You see that line in the warning above the requirements, and as the heading on the card when there is nothing to list.
Under it is a Go to Location link. It opens the project's Overview tab and puts the cursor in the County field, which sits in the Well Location section. The message names a Location tab, and no tab carries that name. Use the link and it takes you to the right field.
When the county is the only thing missing, that one sentence is the whole message. When something else is missing too, a second sentence follows it:
Add the county on the Location tab to finish the requirements check. Select the project Well Type or Drill Type on Overview to determine all applicable compliance requirements. Displayed requirements are partial; requirements scoped to missing project details are not included.
Read the whole message before you leave the tab. Each thing the check needs gets its own link, so a project missing the county and the Well Type or Drill Type shows Go to Location and Go to Overview. Setting the county alone leaves the check unfinished and the message comes back for the rest.
The county is what adds local permits. State requirements do not wait on it, so the forms DrillerDB holds for the project's state are listed whether or not the county is set.
When the Tab Says Requirements Not Fully Determined
This warning means DrillerDB needs one more project detail before it can list every form that applies. The line under the heading names the detail. The forms already on the tab are correct, but the list is not complete yet. Until it is, the badge beside the bar shows Partial requirements instead of a percentage.
Under the message are links to the tab where you set the detail: Go to Location, Go to Overview, or Go to Well Log.
| The warning names | Where to set it |
|---|---|
| Well Type or Drill Type | Overview tab, the Well Type and Drill Type fields |
| well type or well use | Overview tab, the Well Type field |
| well depth | Overview tab, the Well Depth field in the Completed Job card |
| well yield (GPM) | Overview tab, the GPM field in the Completed Job card |
| high-capacity permit status | Overview tab, the Hi-Cap Notification field in the Permits card |
| county | Overview tab, the County field in the Well Location section |
After you set the field, reload the Compliance tab.
Some of these fields only show in certain cases:
- The Completed Job card shows when the project's status is Complete.
- The GPM field shows only when GPM is turned on in Settings > Custom Fields, in the Built-in Project Fields card.
- Hi-Cap Notification shows when the Well Type is Hi-Cap, Commercial, Municipal, or Low-Cap on Hi-Cap Property. Click the Permits card to open it.
The Go to Well Log link opens the Well Log. Saving the Well Log fills in the well depth from the deepest row of the drillhole table, and the yield from Pumping Rate (GPM). It does this only while the project has no well depth, casing depth, GPM, static water level, or suggested pump depth saved yet. If the warning is still there after you save the Well Log, set the value on the Overview tab instead.
How Well Type and Drill Type choose the forms
DrillerDB works out what kind of job this is from the project's Well Type and Drill Type. The kind of job decides which state forms apply.
- A name that contains Pump Install or Pump Service, or is just Pump, makes the project a pump job. The tab then lists the state's pump forms. For example, a Residential well with a Pump Service drill type is a pump job. Other names with "pump" in them, such as Heat Pump or Pump Repair, do not count.
- A name with Abandon in it makes the project an abandonment job. A name with Rehab or Reconstruct in it makes it a rehabilitation job.
- A drilling method, such as Rotary, Mud, or Air Rotary, does not say what kind of job it is. DrillerDB then goes by the Well Type.
- If the two fields point at two different kinds of work, such as a Pump Service drill type on a Monitoring well type, DrillerDB cannot tell which forms apply. The warning then asks for Well Type or Drill Type. Change one of the two so they agree.
Your company's list of Drill Types is in Settings > Custom Fields, in the Well Types, Drill Types & Service Categories card. If you do pump work, make sure the list has a Drill Type named Pump, Pump Install, or Pump Service, and use it on pump jobs.
Forms marked If applicable
Some state rules depend on a fact that is not on the project, such as whether a Colorado permit needs advance notice. DrillerDB does not hold the check open for these rules. It lists the form under Project Permits with an If applicable label instead.
- Click Project Permits in the bar above the forms.
- Find the forms marked If applicable. The text on the card states the rule. You can also point to the label to read it.
- Decide from the rule whether the form applies to your job, then answer
Applies to this project? on the card:
- Yes: the form becomes a required form. It moves to Forms & Status and counts toward the percentage complete. Fill it in like any other form.
- No: the form stays under Project Permits with a Does not apply label.
To clear an answer, click the same button again. The form goes back to If applicable.
A form marked If applicable that you have not answered does not count toward the percentage complete.
Where the Project's State Comes From
DrillerDB looks in two places, in order.
First, the project's own state. This is the well state recorded on the project. When it is a state DrillerDB recognizes, the Compliance tab uses it as it is. If we carry no forms for that state, the tab shows No Compliance Requirements and names the state, so you can tell a gap in our catalog from a wrong state on the project.
A project's state is not always typed by a person. DrillerDB can fill it in, for example from the customer's address. The Compliance tab uses a filled-in state the same way and shows no note for it, so if the forms look wrong, check the state on the project's main tab.
Second, your company's Default State. When the project has no state of its own, or its state is not a code DrillerDB recognizes (a typo such as "Vi"), DrillerDB falls back to the Default State in your company settings. This is what fills most empty Compliance tabs.
When the default is used, a note above the forms reads Using company default state followed by the two-letter code, and "This project has no state of its own." A Set the project's state link takes you straight to the project's main tab.
If neither is set, the tab has no state to work with and lists no forms. Setting Default State is what fixes that case.
The tab says so on screen. It shows No State Set and asks you to set the project's state in the Main tab. When DrillerDB could also read your company settings, it adds that your company has no default state either and links you to Settings, where setting a default covers every project with a blank state.
If that second sentence is missing, DrillerDB could not read your company settings on that load. It is not telling you that you have no default. Reload the tab, and set the project's state in the meantime.
If DrillerDB could not work out the state at all on that load, the tab says "The compliance state could not be determined. Please try again." Reload the tab.
When the state comes from your company default, nothing is written to the project. You keep seeing your default state's forms until you set the state on the project itself. If you work in more than one state, set the state on each project rather than relying on the default.
Step-by-Step: Set Your Company Default State
- Go to Settings > Company Info.
- Find the Company Information card.
- Click the Default State field and choose your state from the list. Each option shows the
two-letter code and the full name, such as
VA - Virginia. - Click Save.
- Open the project again and click the Compliance tab. The required forms now appear.
If your company's Country is set to Canada, this field is labeled Default Province and lists provinces instead of states. It works the same way.
Your change takes effect the next time the Compliance tab loads. You do not need to wait or sign out and back in.
Still Empty After Setting the Default State
Work through these in order.
The project has its own state, and it is blank or wrong. The project's own state beats the company default. Open the project, set the correct well state on it, and reload the Compliance tab.
The message names a state, but no forms are listed. That means DrillerDB has no compliance forms configured for that state yet. Contact support at support@drillerdb.com and say which state you need.
A warning sits above the empty card. The warning names what the requirements check still needs. If it asks for the county, click Go to Location and set the county on the project. Otherwise set the field the warning names (see When the Tab Says Requirements Not Fully Determined). Then reload the tab.
You cannot open the settings page. The Company Info page is open to Admin and Office users only. A Field Supervisor, Driller, or Accountant cannot reach it, so ask an Admin or an Office user on your account to set the Default State.
Related Topics
- General Settings - Where Default State lives
- Submit a Required Compliance Form - Filling and submitting a form once it appears
- User Roles - Who can change company settings
- Contact Support - How to reach the DrillerDB team