Help Centre

Last updated: September 10, 2026

Getting started

Digrules helps you identify the damage-prevention practices and regulatory requirements that apply to a planned excavation. It is not a substitute for calling 811, not a locate request, and not engineering or legal advice.

  1. Go to the App page.
  2. Fill in the details of your planned excavation: depth, method, surface type, distance to the nearest marked facility, locate ticket status, ticket date, planned excavation date, your state (optional), and which utilities are marked on site.
  3. Describe the dig in the free-text field — this helps the tool identify additional risk factors from your description.
  4. Click "Assess this dig" and review the results. Each requirement is named, explained, and cited to its source (CGA Best Practice, OSHA standard, or state one-call law).
  5. Share the results with your crew, foreman, or utility risk manager. The tool does not store your submission — if you navigate away, the results are gone.

You do not need an account, a login, or a credit card. Everything runs on the Free plan.

Frequently asked questions

Where do the regulatory citations come from?

The tool checks a defined set of practices from:

The tool does not guarantee completeness. Requirements vary by local jurisdiction and facility owner. Always consult the applicable one-call centre and your facility owners.

What does the tool check?

The tool evaluates your input against these areas:

What does the tool NOT check?

What do I do if my locate ticket has expired or is about to expire?

The tool computes the 14-day validity window from the ticket date you enter and compares it to the planned excavation date. If the ticket has expired or will expire before the dig date, the tool will flag this and cite the requirement for a renewed ticket. You will need to call 811 again to request a new ticket. The tool cannot renew a ticket or notify you when one expires — there is no email sender or notification system in this product. Check the ticket date yourself and plan accordingly.

What happens to my data?

Nothing. The excavation details you enter are sent to the server over HTTPS, processed in memory during the request, and discarded immediately after the response is returned. No data is written to a database, log file, or any persistent storage. There are no user accounts, no saved history, and no cookies. The results exist only in your browser tab for the duration of the page view. See the Privacy Policy for full details.

Do I need an account? Can I save my assessments?

No account is needed. Digrules does not offer user accounts, saved history, or any form of persistent storage. Every assessment is a fresh submission. If you need to refer back to a result, take a screenshot or note the applicable practices before navigating away. There is no email-based recovery or saved-dig log. (A Team plan with dig history is planned but not yet available.)

Can I use Digrules for multiple dig sites?

Yes — there is no limit on the number of assessments you can run. Each submission is independent. If you are managing multiple dig sites for a crew or company, you can submit each one separately. A Team plan with batch assessment and workspace features is planned but not yet available.

Can I get API access or exportable reports?

API access and PDF export of assessment results are planned features for the Team plan. Neither is available today. If you have a specific integration need, contact us at digrules@agen2ic.ai — we may be able to help.

Known limitations

Contact us

If you have a question that is not answered here, or you need to report an issue:

We aim to respond within 1–2 business days. Please include a description of your question or issue and, if it relates to a specific assessment, the details you entered so we can reproduce the result.

For urgent excavation safety concerns, call 811 or your local one-call centre immediately. Do not wait for an email response.

Note: digrules@agen2ic.ai is a real mailbox. All mail sent to any address at agen2ic.ai reaches a human.