My Membership

Member Billing

For more information on the billing and payments please visit the Colorado811 Billing & Payment page.

Updates to Membership Records

To update any membership information please contact Member Relations at member-services@co811.org.

Member Notification Area Database and Mapping Updates

How do you know what tickets to send me? 

Each member defines a notification area database by submitting digital mapping files for polygonal coverage or hand draw an area using the Colorado 811 Online Ticketing System.

What is Member Notification Area Database? 

The Member Notification Area Database defines the specific geographic area in which a facility owner or operator member receives notifications of proposed excavation activities.

It is the sole responsibility of the facility owner or operator member to ensure that their notification area coverage database remains current. Maintaining accurate and up-to-date information in the database is essential for proper notification and protection of underground facilities.

Member Notification Area Database Update Guidelines

Updating Member owned/operated facilities to the Colorado 811 notification area database is the responsibility of the facility owner. All changes to the notification area database must be submitted via e-mail to notify CO811 Member Relations of the requested change. All change requests will be processed in the order they were submitted, by date. 

To better serve member needs, the following timeline is recommended: 

• Digital data, to include GIS shapefiles and Google Earth files, should be submitted at least ten (10) business days prior to the date that member facilities require notification of proposed excavation for the geographic location. From the date Colorado 811 receives the database update request, a total of five (5) business days are needed to complete the entry into the existing database. The member facility owner will be informed via e-mail when the update is complete. It is the members’ responsibility to review and approve the notification area database. Contact Member Relations personnel for more information.

• Requests for a GIS shape file of the existing notification area database coverage will require an email sent to the Member Relations Department. 

• Requests for notification area database updates due to an emergency will be accommodated in a timely manner, with the resources and personnel available at the time of the request.

• A Database Validation Form must be signed and returned to confirm the accuracy and location of the digital data transferred from the GIS shape file into the Colorado 811 system. 

• All requests will be processed in the order they were received unless otherwise communicated by the member facility owner or operator. 

In the Colorado One Call Law, it states that if you own or operate any underground facilities on or near a public right-of-way or easement, you should be registered with Colorado 811. 

Requirements for Importing ESRI Shape Files for Member Notification Area 

This describes the required format of Shapefiles that can be imported into the Colorado 811 notification database. 

The Shapefile types supported are POINT, LINE and POLYGON. For POINT and LINE shapefiles, you must specify a buffer distance to apply to the file to create a polygon shapefile. A buffer is a radius of a point and/or a line. Minimum buffer that can be applied to linear and radian polygons is 30ft and the maximum is 1000ft. 

Each Shapefile submission should be packaged in a ZIP file, with the following four (4) files at a minimum and sent in an email: 

• ESRI Shapefile (.SHP) 

• ESRI Shape (.SHX) Index File 

• ESRI Shape (.DBF) Attributes File 

• ESRI Shape (.PRJ) Coordinate System File 

**Shapefiles submitted must be in the coordinate system of NAD 83 LAT/LONG decimal degrees. 

Along with the data please include the following information about the data. 

1. Sender Information – Who is supplying the shapefile(s): 

2. Name and contact information. 

3. Member Code – The member code for which the notification areas will be applied to. 

4. Addition, Partial Replacement or Complete Replacement – The person sending the shapefile update must specify if the files submitted are an addition, a partial replacement, or a complete replacement of the existing notification area. 

NOTE: For a partial replacement, the files submitted must contain the data for the entire county. If multiple counties are being replaced a complete replacement of the database is highly recommended. 

1. Effective Date – The date at which the notification areas will become “effective”. You may specify that the notification areas be effective immediately or at some date in the future. 

2. Expiration Date – The date at which the notification areas will expire. You may specify that the notification areas expire NEVER or at some specific date in the future. 

3. Counties Covered – Which counties are covered by the submitted shapefile. This can be a list of one or more counties, or you can specify the entire state (i.e., any counties the shapes fall into.) 

4. Buffer Distance (in FEET) – If the shapefile being submitted contains point or line features, they will be buffered and converted into polygons. You must specify the buffer distance in feet for these types of shapefiles. Shapefiles containing polygons are assumed to already include the necessary buffers. 

E-mail shapefiles to the Member Relations Department at member-services@co811.org  

Important Notes and Limitations

1. When shapefiles are imported into the mapping database, they are automatically clipped to the county or counties they intersect. 

2. Polygons are limited to 4 square miles in area. Polygons that are larger than 4 square miles will be partitioned into smaller polygons that cover the same area. 

3. Polygons which are made up of more than 9 points will be simplified. 

4. There is a maximum density limit of 16 polygons per quarter minute grid. 

5. In processing the importation of data, small gaps/holes less than 300ft in extent (width or height) will automatically be filled in due to the minimum buffer of 150ft of the dig site to limit complexity of the output.