--- language: "en" --- # Online Services ## Documentation ### [DigAlert Direct®, Online Ticket Portal \& Mobile App](https://docs.digalert.org/os/digalert-direct.md) ### [Electronic Positive Response (EPR)](https://docs.digalert.org/os/electronic-positive-response.md) * ### [SMS (Text Messages)](https://docs.digalert.org/os/sms-text-messages.md) * ### [Training \& Help](https://docs.digalert.org/os/training-help.md) --- language: "en" --- # Approved Abbreviations **Released**: 2/15/23 **Effective**: 2/15/23 *** ** * ** *** This list is all approved abbreviations that can be found on DigAlert® Tickets. Any abbreviation used on the map is allowed only when referring to that street. ## **All abbreviations street names, prefixes, suffixes and direction shown on the map MUST be used in the street and cross street fields.** | **Color** | **Meaning** | |-----------|----------------------------------------------| | | Required to use | | | Must be spelled out completely the first use | | **Abbreviation** | **Description** | |------------------|------------------------------| | ABDN | ABANDON | | APPROX | APPROXIMATELY | | ASAP | AS SOON AS POSSIBLE | | AVD | AVENIDA | | AVE | AVENUE | | AVE/OF | AVENUE OF | | AVE/OF THE | AVENUE OF THE | | B-YARD | BACKYARD | | BLVD | BOULEVARD | | BTWN | BETWEEN | | C/L | CENTERLINE | | C/OF | CITY OF | | CATV | CABLE TELEVISION | | CIR | CIRCLE | | CMTO | CAMINITO | | CO/AREA | COUNTY AREA | | CO/OF | COUNTY OF | | COMM | COMMUNICATION | | CONST | CONSTRUCTION | | CONT | CONTINUE | | CONTR | CONTRACTOR | | COR | CORNER | | COR/OF | CORNER OF | | CORP | CORPORATION | | CT | COURT | | CTE | CORTE | | CV | COVE | | DEPT | DEPARTMENT | | DEV | DEVELOPMENT | | DOT | DEPARTMENT OF TRANSPORTATION | | DR | DRIVE | | E/OF | EAST OF | | E/ON | EAST ON | | E/SIDE | EAST SIDE | | E/TO | EAST TO | | ELEC | ELECTRIC | | ENGR | ENGINEER | | EST | ESTIMATE | | ETA | ESTIMATED TIME OF ARRIVAL | | EXCAV | EXCAVATING | | EXCAV | EXCAVATION | | EXCAV | EXCAVATED | | EXT | EXTENDED | | EXWY | EXPRESSWAY | | F-YARD | FRONT YARD | | FRM | FROM | | FRWY | FREEWAY | | FRY | FERRY | | FT | FEET (OR FOOT) | | H/O | HOMEOWNER | | HTS | HEIGHTS | | HWY | HIGHWAY | | INSTALL | INSTALL | | INSTALL | INSTALLING | | INSTALL | INSTALLED | | INSTALL | INSTALLATION | | INTER | INTERSECTION | | INTER/OF | INTERSECTION OF | | IRRIG | IRRIGATION | | JCT | JUNCTION | | LN | LANE | | LOC | LOCATION | | LOC | LOCATED | | LOT # | LOT NUMBER | | MAINT | MAINTENANCE | | MAINT | MAINTENED | | MHP | MOBILE HOME PARK | | MT | MOUNT | | MTN | MOUNTAIN | | MTWY | MOTORWAY | | N/E | NORTHEAST | | N/OF | NORTH OF | | N/ON | NORTH ON | | N/SIDE | NORTH SIDE | | N/TO | NORTH TO | | N/W | NORTHWEST | | NATL | NATIONAL | | OWN | OWNER | | OWN/BLDR | OWNER BUILDER | | P/L | PROPERTY LINE | | PKWY | PARKWAY | | PL | PLACE | | PLZ | PLAZA | | PROP | PROPERTY | | PROP/O | PROPERTY OWNER | | PT | POINT | | PWR | POWER | | R/R TRACKS | RAILROAD TRACKS | | RD | ROAD | | RDG | RIDGE | | RDWY | ROADWAY | | RELOC | RELOCATE | | REM | REMOVE | | REPL | REPLACE | | RTE | ROUTE | | S/E | SOUTHEAST | | S/OF | SOUTH OF | | S/ON | SOUTH ON | | S/SIDE | SOUTH SIDE | | S/TO | SOUTH TO | | S/W | SOUTHWEST | | SERV | SERVICE | | SP | SPACE | | SQ | SQUARE | | ST | STREET | | ST/OF | STREET OF | | ST/OF THE | STREET OF THE | | TEL | TELEPHONE | | TEMP | TEMPORARY | | TER | TERRACE | | TKTR | TRUCK TRAIL | | TR | TRAIL | | TR # | TRACT NUMBER | | TRAF | TRAFFIC | | UTIL | UTILITY | | UTIL | UTILITIES | | VLY | VALLEY | | VW | VIEW | | W/OF | WEST OF | | W/ON | WEST ON | | W/SIDE | WEST SIDE | | W/TO | WEST TO | | WAY | WAY | | WTR | WATER | | X/ST | CROSS STREET | --- language: "en" --- # Best Practices **Released**: 10/29/24 **Effective**: 1/1/25 *** ** * ** *** ## Overview This page is intended to provide descriptions of each Electronic Positive Response (EPR) code and a set of example of when they should be used by members. Following these best practices will not only ensure members are consistent as well as helping excavators understand what the member is communicating back to them. While the best practice is a living document, it is important to remember that not every situation can be identified. There will be cases where the member will have to use the best response available to them using all the information available at that time. ## Response Code Definitions and Examples ### 001 : Clear - No conflict **Definition:** The members lines are not in the area to be excavated. This does NOT mean that the member doesn't have any line in the area. A member may have lines near by, but based on the delineation and the location on the ticket, they are clear for that area. If, for any reason the excavation area or type of work changes, the excavator MUST contact the notification center and get a new ticket issued for the changes. **When to use:** ONLY when there are no underground facilities within the area of delineation and/or the location on the ticket. ### 003 : Existing markings adequate **Definition:** The markings on site are reasonably visible and marked to the extent of the delineation and/or ticket location. If, for some reason the excavation area or type of work changes, the excavator MUST contact the notification center and get a new ticket issued for the changes. **When to use:** When the existing markings on site are complete and accurate. ### 004 : No markings requested **Definition:** The excavator is asking certain members or all members not to mark. The most common use the centers see for this is on emergency work where the job was completed but the excavator needs a ticket number to make the permit valid. **When to use:** ONLY when the excavator is not asking for any marks. ### 010 : Locate area marked **Definition:** The area of delineation and/or the ticket location area has been marked completely and accurately. **When to use:** After the entire area of delineation and/or the ticket location area has been marked completely and accurately. ### 014 : Partially marked - more time is needed **Definition:** The area of delineation and/or the ticket location area has been partially marked. Member needs more time to complete marking. **When to use:** Member has been called away or needs more information to complete markings. NOTE: this code does NOT close the ticket. ### 015 : Provided facility information to excavator (California Government Code 4216.3(a)(1)(A)(ii)) **Definition:** The member to the extent and degree of accuracy that the information is available, provides information to the excavator where the active or inactive lines are located. **When to use:** Member does NOT locate and field mark their active or inactive lines but otherwise provides information to the excavator of where the lines are located. ### 016 : Operator has located and marked all subsurface installations known to be embedded in the pavement (4216.3 (e)) **Definition:** The member located and marked all known facilities embedded in the pavement. **When to use:** When ONLY the embedded lines are marked. ### 020 : Bad address/incorrect street/location info - New ticket required **Definition:** Member cannot find the location on the ticket. Excavator will need to contact center to correct location. Additional time may be needed to complete marking. If mapping changes a new ticket will need to be issued. **When to use:** Member cannot reach excavator by communication methods available on ticket to request the excavator to clarify or correct the location. ### 021 : No access to locate area - Resend ticket requested **Definition:** The member cannot access the area listed on the ticket due to a locked gate, fence or other hindrance (ex - dog in yard). Excavator please provide access information or time when access to location will be available. Additional time may be needed to complete marking. **When to use:** Member cannot reach excavator by communication methods available on ticket and the area is inaccessible. ### 022 : No delineation (California Government Code 4216.2(a)) - Resend ticket requested **Definition:** The area is not delineated as required by 4216.2(a). Member has chosen not to locate and field mark until the area to be excavated is delineated. Excavator needs to delineate the area where the excavation will take place and submit an amendment through the center when the area is delineated. Additional time may be needed to complete marking. **When to use:** The excavator has not delineated the area to be excavated. ### 031 : Requires stand-by at time of excavation - Contact facility owner **Definition:** The member requires a representative to be on site while the excavation is taking place. Excavator required to contact the member to set up date and time for the stand-by. **When to use:** The member has marked BUT needs to also be on site during the excavation. ### 033 : High priority line in area - On Site Meeting Required (California Government Code 4216.2(e)) **Definition:** The member has a high priority line as defined in 4216(j) and is required to meet with the excavator and the member will contact excavator to set up an on site meeting. **When to use:** Anytime a high priority line meeting is required. ### 034 : Field meet required - Contact facility owner to schedule **Definition:** The member wants to meet with the excavator prior to excavation commencing. Excavator needs to contact member to set up a meeting. **When to use:** The member has NOT marked the lines and requires a meeting before excavation begins. ### 040 : Excavator completed work prior to due date **Definition:** The job is completed before the member has marked their line. **When to use:** The member did not mark as job was completed before the start date and time on the ticket. ### 041 : Excavator no-show for meet **Definition:** The excavator and member agreed to a meet date and time and the excavator did not show. **When to use:** After a meeting has been scheduled and the excavator did not meet with the member at the specified date and time. ### 042 : Excavator canceled request **Definition:** The excavator cancels the ticket before the member has responded. **When to use:** SYSTEM USE ONLY. ONLY to clear a ticket as having a response if a CNCL ticket is sent before the member has responded. ### 050 : Negotiated marking schedule (California Government Code 4216.3(a)(1)(A)) **Definition:** The member and excavator have mutually agreed to the sequence and time frame in which to locate and field mark **When to use:** The member and excavator have discussed and agreed to a marking schedule. ### 051 : Mutually agreed to a later start date and time (California Government Code 4216.3(a)(1)(A)) **Definition:** The member and excavator have mutually agreed to a later start date and time for the excavation to begin. **When to use:** The member and excavator have discussed and agreed to a new start date and time. ### 053 : Scheduled meet with excavator at requested date and time **Definition:** The excavator has asked for a joint meet and mark on the ticket. This code is designed to communicate to the excavator that your company will be present during the meet at the scheduled date and time and to avoid an automatic late notice since responses must be submitted prior to the legal date and time. **When to use:** ONLY when you are confirming to be present at the scheduled meet date and time. ### 080 : Extraordinary circumstances exist - No locate due to weather/emergency/safety conditions **Definition:** There are circumstances that make it impossible to locate the ticket prior to the legal date and time. **When to use:** ONLY when there are weather, emergency or safety conditions that prevent marking from taking place. ### 998 : DigAlert® Test Code - No Lines In Area (System use only) **Definition:** DigAlert® has test member codes that are used to test and monitor the system. These codes are not "real" members and do not have any lines or facilities. Since reports will show the number of no responses tickets with these codes are automatically responded with this internal code. **When to use:** Not available for use by the member. This is a system generated response. ### 999 : Member did not respond by the required time (System use only) **Definition:** The member did not respond to the electronic positive response system prior to the legal date and time. **When to use:** Not available for use by the member. This is a system generated response. --- language: "en" --- # Changing Information of Tickets **Released:** 10/30/25 **Effective:** 11/07/25 *** ** * ** *** When using Amendment in DigAlert Direct® or when calling in a change to a location. Only the below information can be changed on the ticket. If the change being requested is not on the list below, a new ticket will be required. This is for safety and Electronic Positive Response requirements. ![:warning:](https://docs.digalert.org/__attachments/a_ac3fbe36eb2c11cbe18b4ad4b9e38ca21638db2c9ac6471908530df63480f479/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **NOTE** **Once the ticket is issued the start date and time** ++**can't**++ **be changed. If it needs to be changed, a NEW ticket must be created and the old ticket must be canceled.** ![:cross_mark:](https://docs.digalert.org/__attachments/a_487bccba7407b9c6208e2dc08b91386ba6a18599e9e94041090eb1b2ef66470d/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) If changing a ticket to an emergency, a **NEW** emergency ticket **must** be created for **ONLY** the area that is an emergency. Sometimes this area will be the same as the original ticket, sometimes the area may be less than the original area on the existing ticket. | **What can be changes on a ticket once issued** | **Available to change through DigAlert Direct®** | |---------------------------------------------------------------|--------------------------------------------------| | Caller phone | | | Company name (BEFORE START DATE/TIME ONLY) | | | Company address | | | Company city | | | Company state | | | Company zip code | | | Caller email | | | Caller email confirmation | | | Caller cell | | | Caller txt confirmation | | | Site contact name | ✅ | | Site contact phone | ✅ | | Site contact email | ✅ | | Site contact email confirmation | ✅ | | Site contact txt confirmation | ✅ | | Delineation method (A RETURN TRIP ticket ONLY, not Amendment) | | | Permit number | | | Work order/job | | | Direct notify | | | Anything directed to you from DigAlert® personnel | | **\* DigAlert® personnel direction is on a case by case basis and should not be confused with policy unless expressly stated.** --- language: "en" --- # DigAlert Direct®, Online Ticket Portal & Mobile App ## Create tickets in a few easy steps, 24/7. * Create tickets anytime including after business hours without having to wait! * Submit any type of location. * Pinpoint your location with GPS coordinates. * Compatible with GPS enabled devices to create tickets on site! ## Manage your tickets and keep them organized all in one place. * Access to all ticket functions without having to call! * Renew, request Re-marks, Amend, Duplicate, report a No Response, report a Damaged/Exposed line, any time. * Stay up to date with your tickets by Renewing multiple tickets at once! * Access to a list of current and expired tickets to assist in managing tickets. ## Create an account to have access to all our features! * Creating an account is free and provides a place to save your company information in order to create tickets in a flash! * As a registered user, you will find many features that help keep your tickets organized and help save time when creating tickets. ## Use our time-saving features! * Our features will help you create and access tickets in a fraction of the time it would take to call. * Features can be accessed as a registered user in your account settings. * Our Ticket Profile feature will allow your commonly used ticket information to auto-populate so that you save even more time! * Alternate company will allow an alternate contractor's information to auto-populate, and Alternate Number will allow access to tickets * created under different numbers within your company. * All of these features make creating tickets the fastest and most convenient way of using our service. --- language: "en" --- # Electronic Positive Response (EPR) **Released**: 11/1/21 **Effective**: 1/1/22 *** ** * ** *** ## **What is Electronic Positive Response (EPR)** Electronic Positive Response (+Response or EPR) is communication from the utility member (contract locator) to the excavator regarding the status of a DigAlert® ticket. California has always had +Response in the law by requiring members to notify the excavator with status or mark the area to be excavated on site. What changed in Government Code 4216 on January 1st, 2017, is that Electronic Positive Response can now be made through the Notification Center starting January 1st, 2018. However, DigAlert® began offering this service starting November 1st, 2017. During 2018, 2019 \& 2020 EPR was voluntary but starting on January 1st, 2021 EPR became mandatory for members, unless a 1 year extension was given prior by the Underground Safe Excavation Board. Then on January 1st, 2022, EPR became mandatory for all members. This means that members must respond to DigAlert's® servers about the marking status of the ticket. DigAlert® will then allow the excavator to check the responses through the website, SMS and apps anytime during life of the ticket. In addition, DigAlert® will email the excavator at the start date and time listed on the ticket a complete status of responses, if the excavator has supplied an email address on the ticket and given permission to send emails. ### **How it works** Once a ticket is created, it is sent out to all utility members who asked for notification in that area. As members clear or respond to the site they send a response back to DigAlert® with information about what was completed. For example; "locate area marked", "no access to area", "clear - no conflict", etc. DigAlert® will store that information with the ticket along with a date \& time stamp. Members can make multiple responses to the same ticket however responses can't be edited or deleted. This means that all responses will show with their corresponding date and time. There are four ways for members to submit responses to DigAlert®. Manually via web portal/mobile app, manually via a link on the ticket delivery, through a web service/TCP connection (this requires you to already have a ticket management system or application that can send TCP requests to our server) or through a REST API. Technical documents can be found here → [Automated Electronic Positive Response via TCP Connection](https://docs.digalert.org/um/responding-via-tcp-connection) or via a REST API. REST API documentation can be found here → [Automated Electronic Positive Response via REST API](https://docs.digalert.org/um/responding-via-rest-api). ### **What are the Requirements?** To use Electronic Positive Response as a utility member (or contract locator) you must; 1. Be a member in good standing of DigAlert® (for contract locators, the company you are locating for must be a member in good standing) 2. Be assigned at least one active member code (done at the time of joining) 3. Notify DigAlert® you wish to use EPR through the center by emailing Member Services at [memberservices@digalert.org](mailto:memberservices@digalert.org) 4. Decide how you will submit your responses to DigAlert® from one of the four available ways, found on the left menu **Warning!** If you have multiple facilities (water, electric, sewer) and you only have ONE member code, when you respond you CANNOT respond differently per facility. There can be only one response PER member code. This is why it is required to have one code per facility type. **Important Information!** DigAlert® requires that if you have multiple facility types (water, electric, sewer, etc) that you have a member code for each type. ### **When are Responses Required?** | Ticket Type | Ticket Type Description | Response Required | Optional Response Accepted if Sent (Only applies to NO Response Required) | Response Required Date/Time | |-------------|-------------------------|-------------------|---------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | AMND | Amendment | NO | YES | If before the original Work Date/Time on the ticket or Legal notice then the response due date/time remain the same. If after the response required date/time become legal notice. | | CNCL | Cancel | NO | NO | None | | DMGE | Damage | NO | YES | None | | EXPD | Exposed | NO | YES | None | | NEW | New | YES | | Legal notice or Work Date/Time on ticket (whichever is later) | | NRSP | No Response | YES | | None | | REMK | Request Re-marks | YES | | Legal notice | | RNEW | Renew Only | NO | YES | None | | RTRN | Return Trip | YES | | Legal notice or Work Date/Time | ### **Benefits of using EPR** For the member, EPR is an effective means of reducing the number of retransmits that they receive because the excavator saw no markings at the dig site. For excavators, EPR provides them with information about the member facilities prior to arriving on the job site. If they provided an email address when the locate request was called in they will receive an email confirmation after the start date \& time listed on the ticket. ### **Is Testing Available?** Testing is available for members that wish to test posting responses using the [Automated Electronic Positive Response via TCP Connection](https://docs.digalert.org/um/responding-via-tcp-connection) and [Automated Electronic Positive Response via REST API](https://docs.digalert.org/um/responding-via-rest-api) methods ONLY. In order to test, you MUST be an active member of Underground Service Alert of Southern California. --- language: "en" --- # Group comparisons | **New Ticket** |||| | | Guest User | Standard User | Professional User | | Single Address Ticket | ✅ | ✅ | ✅ | | Multiple Address Ticket | ✅ | ✅ | ✅ | | Intersection Ticket | ✅ | ✅ | ✅ | | Working on Street Ticket | ✅ | ✅ | ✅ | | All Others Ticket (GPS Coordinates) | | ✅ | ✅ | | Add Custom Location Notes | | ✅ | ✅ | | Legal Notice Ticket | ✅ | ✅ | ✅ | | New Emergency Ticket | | ✅ | ✅ | | New Short Notice Ticket | | ✅ | ✅ | | Auto Draw Location if Address is Found | ✅ | ✅ | ✅ | | Always Receive Ticket Number | | | ✅ | | Additional Location Information | | ✅ | ✅ | | Ticket (Location) Size Limits (\*[++View Documentation++](https://docs.digalert.org/display/DAS/Ticket+%28Location%29+Size+Requirements) for details on limitations) | 1/2 linear or square mile \* | 1/2 linear or square mile \* | 2 linear miles or 1/2 linear or square mile \* | |----------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------------------------|------------------------------|------------------------------------------------| | **Secondary Functions on Ticket** |||| | | Guest User | Standard User | Professional User | | Renewal a Ticket | ✅ | ✅ | ✅ | | Bulk Renewal Tickets | ✅ | ✅ | ✅ | | Request Re-marks on Ticket | ✅ | ✅ | ✅ | | Duplicate an Existing Ticket | ✅ | ✅ | ✅ | | Report No Response on Ticket **(being removed 1/1/2026)** | | ✅ | ✅ | | Submit a Damage and/or Exposed Ticket | | ✅ | ✅ | | Submit an Amendment Ticket | | ✅ | ✅ | | Submit a Return Trip Ticket | | ✅ | ✅ | | Cancel a Ticket | | | ✅ | |-----------------------------------------------------------|------------|---------------|-------------------| | **My Tickets** |||| | | Guest User | Standard User | Professional User | | View Ticket by Ticket Number | ✅ | ✅ | ✅ | | View Active Tickets based on Phone Number(s) (\*Includes Alternate Phone Numbers) | Expiring in Today, Tomorrow, 3 or 7 Days | All Active Tickets \* | All Active Tickets \* | | View Expired Tickets based on Phone Number(s) (\*Includes Alternate Phone Numbers) | Tickets that have expired Yesterday, 3 or 7 days ago | Tickets that have expired 7 days ago | Tickets that have expired 7 days ago | |------------------------------------------------------------------------------------|------------------------------------------------------|--------------------------------------|--------------------------------------| | **My Tickets** |||| | | Guest User | Standard User | Professional User | | View Ticket by Ticket Number | ✅ | ✅ | ✅ | | View Active Tickets based on Phone Number(s) (\*Includes Alternate Phone Numbers) | Expiring in Today, Tomorrow, 3 or 7 Days | All Active Tickets \* | All Active Tickets \* | | View Expired Tickets based on Phone Number(s) (\*Includes Alternate Phone Numbers) | Tickets that have expired Yesterday, 3 or 7 days ago | Tickets that have expired 7 days ago | Tickets that have expired 7 days ago | |------------------------------------------------------------------------------------|------------------------------------------------------|--------------------------------------|--------------------------------------| | **ETA** |||| | | Guest User | Standard Member User | Professional Member User | | View Ticket Count for Area | | ✅ | | | View Tickets and Details for Area | | | ✅ | |-----------------------------------|------------|----------------------|--------------------------| | **EPR (Electronic Positive Response)** |||| | | Guest User | Standard User | Professional User | | View Electronic Positive Responses | ✅ | ✅ | ✅ | |------------------------------------|------------|---------------|-------------------| | **Account Settings** |||| | | Guest User | Standard User | Professional User | | Alternate Companies | | 5 | 10 | | Ticket Profiles | | 5 | 15 | | Alternate Phone Numbers | | 5 | 15 | |-------------------------|------------|---------------|-------------------| **Alternate Companies \& Ticket Profiles** Alternate Companies and Ticket Profiles allows the end user to create templates for Company and Ticket Information to be used during New Tickets instead of having to type out the information each time. **Alternate Phone Numbers** Alternate Phone Numbers allows you to add your co-workers phone numbers to your account to be able to manage their tickets through My Tickets. --- language: "en" --- # No Response Tickets **Released**: 11/01/25 **Effective**: 01/01/26 *** ** * ** *** ## Auto No Response History Effective January 1st 2025, Underground Service Alert of Southern California (DigAlert®) started sending automatic No Response tickets to members who failed to respond to the Electronic Positive Response (EPR) system by the required date and time on behalf of the excavator. These No Response tickets are sent to the members until they respond to the EPR system as required by CA GC 4216 every 2 working days, not including the date of notification. DigAlert® has allowed excavators to submit No Response tickets manually as well since this change took place. ### Manual No Response Changes 1/1/2026 Effective **January 1st, 2026**, the manual No Response process will no longer be allowed since No Responses are sent automatically at the legal date/time of the ticket on behalf of the excavator. The excavator no longer needs to worry about these as the system does it for them automatically. ### What does this mean? This change means that as of January 1st, 2026, you will no longer be able to submit a No Response ticket outside of the system automatically doing it for you. ### What if I disagree with the response the member has given? If the member posts an EPR that you disagree with and need them back out for any reason there are a few steps to take. First, submit the ticket as a **Return Trip** and state in the comments, the reason you are asking the member to come back out and the facts you believe the EPR provided is not accurate. If you are not in need of the members to respond back out to the location, then submit the ticket as an **Amendment** with the same type of comments described previously. Remember, this is a business and a legal document so there is no need for any hostility or unprofessional comments to be listed on a ticket, make sure the comments are professional. Second, you can **file a complaint** with the Underground Safe Excavation Board by visiting the following link → . Be sure to complete the form in its entirety so the investigators can get a complete understanding of the complaint. ### I need to call someone, who do I call? If you need to call someone, look at your ticket confirmation for the phone number for the member you are wishing to contact. These are the most up to date phone numbers DigAlert® has available in the system. If you do not have a copy of your ticket, you can go here → and look up the contact information for the members notified on your ticket. ### Recap Instead of sending a No Response for a member that has already supplied a response to the EPR system, send the ticket either as a; * Return Trip when asking for a member(s) to respond back out for any reason (other than for Re-marks, Damage or Exposed lines), be sure to list why in the comments * Amendment when just passing on information to the member without asking them to respond to the site. ![:warning:](https://docs.digalert.org/__attachments/a_ac3fbe36eb2c11cbe18b4ad4b9e38ca21638db2c9ac6471908530df63480f479/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **CAUTION** Amendment ticket **DO NOT** require members to respond to the job site or the EPR system. Never use this ticket type asking them to visit the site. --- language: "en" --- # Response Codes **Released**: 10/29/24 **Effective**: 1/1/25 *** ** * ** *** ## Electronic Positive Response (EPR) Codes as defined by DigAlert® The EPR codes on this page are maintained by DigAlert®. These codes are used for members to submit responses to DigAlert's® EPR servers. For Excavators wishing to check responses, please see → [Verifying Responses via Website](https://docs.digalert.org/ed/verifying-responses-via-website). The responses will be displayed with the description, not the code. **More information!** For more information on what the response codes mean and when to use them, please see [Best Practices](https://docs.digalert.org/um/epr-best-practices-2025.md). | Response Code | Description | |---------------|-------------------------------------------------------------------------------------------------------------| | 000 | Reserved for system use only | | | | | 001 | Clear - No conflict | | 003 | Existing markings adequate | | 004 | No markings requested | | | | | 010 | Locate area marked | | 014 | Partially marked - More time is needed | | 015 | Provided facility location information to excavator (4216.3(a)(1)(A)(ii)) | | 016 | Operator has located and marked all subsurface installations known to be embedded in the pavement 4216.3(b) | | | | | 020 | Bad address/incorrect street/location info - New ticket required | | 021 | No access to locate area - Resend ticket requested | | 022 | No delineation - Resend ticket requested | | | | | 031 | Requires stand by at time of excavation - Contact facility owner | | 033 | High priority line in area - On site meeting required | | 034 | Field meet required - Contact facility owner to schedule | | | | | 040 | Excavator completed work prior to due date | | 041 | Excavator no show for meet | | 042 | Excavator canceled request (system use only) | | | | | 050 | Negotiated marking schedule | | 051 | Mutually agreed to a later start date and time (4216.3(a)(1)(A)) | | 053 | Scheduled meet with excavator at requested date and time | | | | | 080 | Extraordinary circumstances exist - No locate due to weather/emergency/safety conditions | | | | | 998 | DigAlert® Test Code - No Lines In Area | | 999 | Member did not respond by required time (system use only) | To integrate these response codes with your ticket management system, you can retrieve this list via API by accessing as a GET. This API will return the following JSON formatted message. Field definitions: "last_change" displays the date the last change was made to the EPR codes as a string "version" displays the EPR Codes JSON file version as a string "response_codes": "response" displays the EPR response code (three numbers as a string) "state" displays the state/center as a string (max 4 chars) - For Underground Service Alert of Southern California will always show CA-S "description" displays the readable description of the EPR response code as a string "allowed" displays wether the EPR code is available for public use as a bit/boolean. "false" means this code can only be used by DigAlert's® system internally. "true" means the EPR code can be used by members when posting. JSON {{ "last_change": "2024-11-12", "version": "24.11.12.1", "response_codes": [ { "response": "000", "state": "CA-S", "description": "Member has not responded yet", "allowed": false }, { "response": "001", "state": "CA-S", "description": "CLEAR - NO CONFLICT", "allowed": true }, { "response": "003", "state": "CA-S", "description": "EXISTING MARKINGS ADEQUATE", "allowed": true }, { "response": "004", "state": "CA-S", "description": "NO MARKINGS REQUESTED", "allowed": true }, { "response": "010", "state": "CA-S", "description": "LOCATE AREA MARKED", "allowed": true }, { "response": "014", "state": "CA-S", "description": "PARTIALLY MARKED - MORE TIME IS NEEDED", "allowed": true }, { "response": "015", "state": "CA-S", "description": "PROVIDED FACILITY LOCATION INFORMATION TO EXCAVATOR (4216.3(A)(1)(A)(II))", "allowed": true }, { "response": "016", "state": "CA-S", "description": "OPERATOR HAS LOCATED AND MARKED ALL SUBSURFACE INSTALLATIONS KNOWN TO BE EMBEDDED IN THE PAVEMENT (4216.3 (e))", "allowed": true }, { "response": "020", "state": "CA-S", "description": "BAD ADDRESS/INCORRECT STREET/LOCATION INFO - NEW TICKET REQUIRED", "allowed": true }, { "response": "021", "state": "CA-S", "description": "NO ACCESS TO LOCATE AREA - RESEND TICKET REQUIRED", "allowed": true }, { "response": "022", "state": "CA-S", "description": "NO DELINEATION - RESEND TICKET REQUESTED", "allowed": true }, { "response": "031", "state": "CA-S", "description": "REQUIRES STAND BY AT TIME OF EXCAVATION - CONTACT FACILITY OWNER", "allowed": true }, { "response": "033", "state": "CA-S", "description": "HIGH PRIORITY LINE IN AREA - ON SITE MEETING REQUIRED", "allowed": true }, { "response": "034", "state": "CA-S", "description": "FIELD MEET REQUIRED - CONTACT FACILITY OWNER TO SCHEDULE", "allowed": true }, { "response": "040", "state": "CA-S", "description": "EXCAVATOR COMPLETED WORK PRIOR TO DUE DATE", "allowed": true }, { "response": "041", "state": "CA-S", "description": "EXCAVATOR NO SHOW FOR MEET", "allowed": true }, { "response": "042", "state": "CA-S", "description": "EXCAVATOR CANCELED REQUEST", "allowed": false }, { "response": "050", "state": "CA-S", "description": "NEGOTIATED MARKING SCHEDULE", "allowed": true }, { "response": "051", "state": "CA-S", "description": "MUTUALLY AGREED TO A LATER START DATE AND TIME (4216.3(A)(1)(A))", "allowed": true }, { "response": "053", "state": "CA-S", "description": "SCHEDULED MEET WITH EXCAVATOR AT REQUESTED DATE AND TIME", "allowed": true }, { "response": "080", "state": "CA-S", "description": "EXTRAORDINARY CIRCUMSTANCES EXIST - NO LOCATE DUE TO WEATHER/EMERGENCY/SAFETY CONDITIONS", "allowed": true }, { "response": "998", "state": "CA-S", "description": "DIGALERT TEST CODE - NO LINES IN AREA", "allowed": false }, { "response": "999", "state": "CA-S", "description": "Member did not respond by the required time", "allowed": false } ] } --- language: "en" --- # SMS (Text Messages) **Released**: 11/1/17 **Effective**: 1/1/18 *** ** * ** *** ## What is SMS? SMS stands for Short Message Service but is commonly know as Text Messages. Although most phones today are not limited to 144 characters per text message SMS is not really "short" anymore. With the addition of MMS or MultiMedia Message Service, text messages now can be so much more. They can be longer than 144 characters, they can contain music, pictures, videos, links and so much more. Something most of us use every day of our life. ## What are the options? Great question. There is a lot of information you can receive from DigAlert® instantly, at any time of the day and any day of the year. SMS notifications are sent to excavators that allow with confirmations of their DigAlert® tickets as well as Electronic Positive Response (EPR) so you can stay up to date in the field at all times. In addition, you can text us to get information as well as start a conversations. ## Sending us Text Messages **To use any of the following options please text the command to DIGALT (344-258)** * Apps (Will return links for the DigAlert ®mobile apps in all the app stores) * Color Codes (Will return all APWA approved color codes and their meaning) * Email A123456789 YOUREMAILADDRESS (Will email the requested ticket to the specified email address) * ER A123456789 (Will return all available emergency contact information for members on the requested ticket) * Feedback MESSAGE (Will send us feedback that you may want us to know) * Help (Will return a standard message required by the carriers) * Holidays (Will return the next upcoming holiday that will affect the center and the legal notice) * Law (Will return a link to the current CA Government Code 4216) * More (Will return more options) * New Ticket (Will return a link to DigAlert Direct® to allow you to enter a new ticket online) * Options (Will return a list of popular options or commands available) * Stats (Will return if the center is open or closed, number of calls on hold and number of tickets completed for the day) * Ticket A123456789 (Will return details for the requested ticket and a link to view the entire ticket) * Presp A123456789 (Will return positive response details and a link to view all positive responses) * Renew (Will renew your ticket for an additional 28 calendar days after a few simple questions back and forth) * Vacuum A123456789 (Will return all available vacuum contact information for members on the requested ticket) * Website (Will return a link to our website) --- language: "en" --- # Ticket Location Size Examples **Released**: 2/15/24 **Effective**: 2/15/24 *** ** * ** *** ## Ticket Size Examples 1. **1/2 linear mile maximum** 1. Single addresses are exempt 2. Rule #2 is exempt 3. Rule #6 is exempt ![worddav7a0fedc5d15e0d34c05c8c1cde980846.png](https://docs.digalert.org/__attachments/a_4ceb9cef143971b1a6ce582e5f3cb11de405b295f40dfdf21f53973dc5edbcec/worddav7a0fedc5d15e0d34c05c8c1cde980846.png?cb=7a0fedc5d15e0d34c05c8c1cde980846) Single Address Location Example: 1379 Pico St x/st California Ave ![worddav127b215053f698ec2c68dfc3308694df-2.png](https://docs.digalert.org/__attachments/a_69bd1cb14bf213b8121f6a0deb54e0e66753cc5f0d09bd6778c8f4312bf9111f/worddav127b215053f698ec2c68dfc3308694df-2.png?cb=127b215053f698ec2c68dfc3308694df) Multiple streets limited to ½ linear mile Location Example: Both sides of Olympic Dr from California Ave to Rimpau Ave; Both sides of Rimpau Ave from California Ave to Sunset Park; Both sides of Sunset Park From Rimpau Ave to Mount Baldy Ct; Both sides of Mount Baldy Ct from Sunset Park to Trabucco Park 2. **2 linear mile maximum on freeways or railroad tracks** ![worddav5244a7323d65de67c5436feabec022f7.png](https://docs.digalert.org/__attachments/a_7f76a069f2c5ed7d40f8cf1106c7c26bf74d7baf9226e2a8382b5456061f7f59/worddav5244a7323d65de67c5436feabec022f7.png?cb=5244a7323d65de67c5436feabec022f7) 2 linear miles of freeway Location example: S/bound side of 15 freeway from 91 Frwy to Old Temescal Rd 3. **Intermittent locations** ![worddav127b215053f698ec2c68dfc3308694df.png](https://docs.digalert.org/__attachments/a_8c838ca84c5a58946101d25e35402a22129787a63e13121880316ccbc524d9f6/worddav127b215053f698ec2c68dfc3308694df.png?cb=127b215053f698ec2c68dfc3308694df) Intermitted Locations Location Example: Intersection of Olympic Dr and California Ave; S/E corner of Olympic Dr and Rimpau Ave; Inter of Sunset Park and Rimpau Ave; inter of sunset park and Mount Baldy Ct; S/W coroner of Mount Baldy Ct and Bighorn Park; S/W coroner of Mount Baldy Ct and Santiago Park; S/W corner of Mount Baldy Ct and Trabucco Park 4. **County lines** 1. Tickets will stop at county lines no matter the distance and will be issued a ticket for each county ![worddava3bfb6761fa7858266099927b7aae91c.png](https://docs.digalert.org/__attachments/a_19b511b8146535d764d5621cc4914c95372d25396014b863b92d152649ced430/worddava3bfb6761fa7858266099927b7aae91c.png?cb=a3bfb6761fa7858266099927b7aae91c) Location Example: County = Riverside, City = Corona Inter of Aldergate Dr and Hellman Ave ![worddav09c1c6a50af03c2600f82ac3ae4ff1f7.png](https://docs.digalert.org/__attachments/a_1575fd31a3e7e7724896f1bf40d371e1cf8f6de30d969061d192ebd7177ecd27/worddav09c1c6a50af03c2600f82ac3ae4ff1f7.png?cb=09c1c6a50af03c2600f82ac3ae4ff1f7) Location Example: County = San Bernardino, City = Chino Inter of Aldergate Rd and Hellman Ave 5. **Bounded areas** 1. Cannot contain any named public roads 2. Internal roads, private roads, driveways, trails or other unnamed roads are exempt ![worddav58b006bc8a79d0e09ecedcefcc3cd726.png](https://docs.digalert.org/__attachments/a_c5ac7e11e377a072762ada9ef7671b57680bebc52c7480096817e7f09bb0296a/worddav58b006bc8a79d0e09ecedcefcc3cd726.png?cb=58b006bc8a79d0e09ecedcefcc3cd726) ½ square mile bounded area, no streets Location example: Working in bounded area n/w by January Ct if extended s/w; n/e by Somerdale if Extended s/e; s/w by approx. ½ mile s/w/of Somerdale; s/e/by approx. ½ mile s/e/of January ct. 6. **Farms** 1. Locations are limited to 1 square mile 7. **Exceptions** * Center supervisory staff may allow exemptions to any rule when warranted by the project, location and/or circumstances * All tickets that fall outside of these rules have been pre-approved by supervisory staff * Existing tickets issued prior to the effective date above are grandfathered in and will not be re-done to comply with these rules * Existing tickets where streets were not present when issued but after a map update appear are grandfathered in and will not be re-done to comply with these rules --- language: "en" --- # Ticket Location Size Requirements **Released**: 2/15/24 **Effective**: 2/15/24 *** ** * ** *** ## Maximum Ticket Sizes (Location policies) 1. **1/2 linear mile maximum** 1. Locations larger than 1/2 mile should be broken up into 1/2 mile segments at intersections when practical 2. When intersections are not practical or available, footage will be used instead. Example: Both sides of Main St from 1st St E/For 1/2 Mile 3. Distance from road into property should be specified and cannot extend so far that it continues into properties that face other roads or into other roads completely 4. Single addresses known as parcels that are bigger than 1/2 mile are exempt from this rule 5. Locations in #2 are exempt from this rule 6. Locations in #6 are exempt from this rule 2. **2 linear mile maximum on freeways or railroad tracks** 1. Freeways are defined as a road that has on and off ramps 2. Locations larger than 2 miles should be broken up into 2 mile segments at exits, milepost markers and/or cross streets when practical 3. When exits, milepost markers and/or cross streets are not practical, footage will be used. Example: Both sides of I-15 from Main St N/FOR 2 Miles 3. **Intermittent locations** 1. Intermittent locations are defined as street signs, power poles, trees, soil borings, etc 2. If possible, the number of locations should be specified on the ticket and each location be marked and numbered (in white) in the field. The number should correspond to the number of locations on the ticket. 3. Locations that are technically intermittent but are very close to each other may be considered continuous and may be marked with starting and ending points 4. **County lines** 1. Locations that enter into more than one county must be broken up into one ticket per county 5. **Bounded areas** 1. Locations are limited to 1/2 square mile 2. Locations within boundaries cannot contain any named public streets 3. Internal roads, private roadways, private driveways, trails or other unnamed roads are exempt 6. **Farms** 1. Locations are limited to one square mile 7. **Exceptions** 1. Center supervisory staff may allow exemptions to any rule when warranted by the project, location and/or circumstances 2. All tickets that fall outside of these rules have been pre-approved by supervisory staff 3. Existing tickets issued prior to the effective date above are grandfathered in and will not be re-done to comply with these rules 4. Existing tickets where streets were not present when issued but after a map update appear are grandfathered in and will not be re-done to comply with these rules --- language: "en" --- # Training & Help ## What are training options, if any? Please see our YouTube channel for videos and online instructional courses. ### Schedule dedicated training ## ![](https://icons-confluence.presago.net/icon/90e4957d-2b22-4cd8-a65c-89c82cde3b6d/svg?color=%237030a0&shape=none&filled=false) - [Online Services Training Request](https://digalert.org/education/training/online-services) ### YouTube ## ![](https://icons-confluence.presago.net/icon/b02890cc-e61c-4491-9c92-def101bb04cf/svg?color=%237030a0&shape=none&filled=false) - [DigAlert's YouTube Channel](https://www.youtube.com/channel/UCeWBjKbi2GNEtds8OWzPvAg) --- language: "en" --- # Verifying Responses via Website **Released**: 1/1/17 **Effective**: 1/1/17 *** ** * ** *** ## How to check for responses Checking Electronic Positive Responses (EPR) can be done the following ways 1. Visit [digalert.org](http://DigAlert.org) , click Web Services on the menu, then click "Check Electronic Positive Response" or if using the mobile app, click the Electronic Positive Response menu item 2. If an email address was supplied on the ticket and permission was given to send messages, an email will be sent at the time EPRs are due with all available responses. Additional emails will be sent each time a member submits a new response or updates a response after the due date/time. 3. If a cell phone number was supplied on the ticket and permission was given to send text messages, a text message will be sent at the time EPRs are due with all available responses. Additional text messages will be sent each time a member submits a new response or updates a response after the due date/time. ## Step by step details To check EPRs via [digalert.org](http://DigAlert.org) or the mobile apps, follow options 1 or 2 from above and the main screen will appear shown below. ![EPR-2.5.png](https://docs.digalert.org/__attachments/a_5116c07b8b4ab41b1a590bdd624d13dd25a3592290b9bd4eba273bc12799b374/EPR-2.5.png) 1. Enter the complete ticket number, then click the search icon to search for your ticket. 2. Some brief information from the ticket will display to ensure you are viewing the correct ticket number. If the ticket number is incorrect, simply repeat step 1. ![EPR-3.png](https://docs.digalert.org/__attachments/a_a8b95f819763654e1790c2fa7caf0e42d8448aa89e856b13973e7cc26d9ae102/EPR-3.png) 3. Once a ticket has been inquired and displayed, responses for the most current revision will be displayed automatically in the timeline, if any were made. 4. If other revisions of your ticket exist, you may select the checkbox to the left to show or hide positive responses for the selected revision. ![EPR-5.png](https://docs.digalert.org/__attachments/a_44d80c1a603269890ae96aaea922af158bad976b84ade165e0707a7f36222f4a/EPR-5.png) EPRs will show Comments and URL for additional information if provided by that member when they respond --- language: "en" --- # Mobile Apps ## Documentation * ### [SMS (Text Messages)](https://docs.digalert.org/ma/sms-text-messages.md) ### [Electronic Positive Response (EPR)](https://docs.digalert.org/ma/electronic-positive-response-epr.md) --- language: "en" --- # Best Practices **Released**: 10/29/24 **Effective**: 1/1/25 *** ** * ** *** ## Overview This page is intended to provide descriptions of each Electronic Positive Response (EPR) code and a set of example of when they should be used by members. Following these best practices will not only ensure members are consistent as well as helping excavators understand what the member is communicating back to them. While the best practice is a living document, it is important to remember that not every situation can be identified. There will be cases where the member will have to use the best response available to them using all the information available at that time. ## Response Code Definitions and Examples ### 001 : Clear - No conflict **Definition:** The members lines are not in the area to be excavated. This does NOT mean that the member doesn't have any line in the area. A member may have lines near by, but based on the delineation and the location on the ticket, they are clear for that area. If, for any reason the excavation area or type of work changes, the excavator MUST contact the notification center and get a new ticket issued for the changes. **When to use:** ONLY when there are no underground facilities within the area of delineation and/or the location on the ticket. ### 003 : Existing markings adequate **Definition:** The markings on site are reasonably visible and marked to the extent of the delineation and/or ticket location. If, for some reason the excavation area or type of work changes, the excavator MUST contact the notification center and get a new ticket issued for the changes. **When to use:** When the existing markings on site are complete and accurate. ### 004 : No markings requested **Definition:** The excavator is asking certain members or all members not to mark. The most common use the centers see for this is on emergency work where the job was completed but the excavator needs a ticket number to make the permit valid. **When to use:** ONLY when the excavator is not asking for any marks. ### 010 : Locate area marked **Definition:** The area of delineation and/or the ticket location area has been marked completely and accurately. **When to use:** After the entire area of delineation and/or the ticket location area has been marked completely and accurately. ### 014 : Partially marked - more time is needed **Definition:** The area of delineation and/or the ticket location area has been partially marked. Member needs more time to complete marking. **When to use:** Member has been called away or needs more information to complete markings. NOTE: this code does NOT close the ticket. ### 015 : Provided facility information to excavator (California Government Code 4216.3(a)(1)(A)(ii)) **Definition:** The member to the extent and degree of accuracy that the information is available, provides information to the excavator where the active or inactive lines are located. **When to use:** Member does NOT locate and field mark their active or inactive lines but otherwise provides information to the excavator of where the lines are located. ### 016 : Operator has located and marked all subsurface installations known to be embedded in the pavement (4216.3 (e)) **Definition:** The member located and marked all known facilities embedded in the pavement. **When to use:** When ONLY the embedded lines are marked. ### 020 : Bad address/incorrect street/location info - New ticket required **Definition:** Member cannot find the location on the ticket. Excavator will need to contact center to correct location. Additional time may be needed to complete marking. If mapping changes a new ticket will need to be issued. **When to use:** Member cannot reach excavator by communication methods available on ticket to request the excavator to clarify or correct the location. ### 021 : No access to locate area - Resend ticket requested **Definition:** The member cannot access the area listed on the ticket due to a locked gate, fence or other hindrance (ex - dog in yard). Excavator please provide access information or time when access to location will be available. Additional time may be needed to complete marking. **When to use:** Member cannot reach excavator by communication methods available on ticket and the area is inaccessible. ### 022 : No delineation (California Government Code 4216.2(a)) - Resend ticket requested **Definition:** The area is not delineated as required by 4216.2(a). Member has chosen not to locate and field mark until the area to be excavated is delineated. Excavator needs to delineate the area where the excavation will take place and submit an amendment through the center when the area is delineated. Additional time may be needed to complete marking. **When to use:** The excavator has not delineated the area to be excavated. ### 031 : Requires stand-by at time of excavation - Contact facility owner **Definition:** The member requires a representative to be on site while the excavation is taking place. Excavator required to contact the member to set up date and time for the stand-by. **When to use:** The member has marked BUT needs to also be on site during the excavation. ### 033 : High priority line in area - On Site Meeting Required (California Government Code 4216.2(e)) **Definition:** The member has a high priority line as defined in 4216(j) and is required to meet with the excavator and the member will contact excavator to set up an on site meeting. **When to use:** Anytime a high priority line meeting is required. ### 034 : Field meet required - Contact facility owner to schedule **Definition:** The member wants to meet with the excavator prior to excavation commencing. Excavator needs to contact member to set up a meeting. **When to use:** The member has NOT marked the lines and requires a meeting before excavation begins. ### 040 : Excavator completed work prior to due date **Definition:** The job is completed before the member has marked their line. **When to use:** The member did not mark as job was completed before the start date and time on the ticket. ### 041 : Excavator no-show for meet **Definition:** The excavator and member agreed to a meet date and time and the excavator did not show. **When to use:** After a meeting has been scheduled and the excavator did not meet with the member at the specified date and time. ### 042 : Excavator canceled request **Definition:** The excavator cancels the ticket before the member has responded. **When to use:** SYSTEM USE ONLY. ONLY to clear a ticket as having a response if a CNCL ticket is sent before the member has responded. ### 050 : Negotiated marking schedule (California Government Code 4216.3(a)(1)(A)) **Definition:** The member and excavator have mutually agreed to the sequence and time frame in which to locate and field mark **When to use:** The member and excavator have discussed and agreed to a marking schedule. ### 051 : Mutually agreed to a later start date and time (California Government Code 4216.3(a)(1)(A)) **Definition:** The member and excavator have mutually agreed to a later start date and time for the excavation to begin. **When to use:** The member and excavator have discussed and agreed to a new start date and time. ### 053 : Scheduled meet with excavator at requested date and time **Definition:** The excavator has asked for a joint meet and mark on the ticket. This code is designed to communicate to the excavator that your company will be present during the meet at the scheduled date and time and to avoid an automatic late notice since responses must be submitted prior to the legal date and time. **When to use:** ONLY when you are confirming to be present at the scheduled meet date and time. ### 080 : Extraordinary circumstances exist - No locate due to weather/emergency/safety conditions **Definition:** There are circumstances that make it impossible to locate the ticket prior to the legal date and time. **When to use:** ONLY when there are weather, emergency or safety conditions that prevent marking from taking place. ### 998 : DigAlert® Test Code - No Lines In Area (System use only) **Definition:** DigAlert® has test member codes that are used to test and monitor the system. These codes are not "real" members and do not have any lines or facilities. Since reports will show the number of no responses tickets with these codes are automatically responded with this internal code. **When to use:** Not available for use by the member. This is a system generated response. ### 999 : Member did not respond by the required time (System use only) **Definition:** The member did not respond to the electronic positive response system prior to the legal date and time. **When to use:** Not available for use by the member. This is a system generated response. --- language: "en" --- # Electronic Positive Response (EPR) **Released**: 11/1/21 **Effective**: 1/1/22 *** ** * ** *** ## **What is Electronic Positive Response (EPR)** Electronic Positive Response (+Response or EPR) is communication from the utility member (contract locator) to the excavator regarding the status of a DigAlert® ticket. California has always had +Response in the law by requiring members to notify the excavator with status or mark the area to be excavated on site. What changed in Government Code 4216 on January 1st, 2017, is that Electronic Positive Response can now be made through the Notification Center starting January 1st, 2018. However, DigAlert® began offering this service starting November 1st, 2017. During 2018, 2019 \& 2020 EPR was voluntary but starting on January 1st, 2021 EPR became mandatory for members, unless a 1 year extension was given prior by the Underground Safe Excavation Board. Then on January 1st, 2022, EPR became mandatory for all members. This means that members must respond to DigAlert's® servers about the marking status of the ticket. DigAlert® will then allow the excavator to check the responses through the website, SMS and apps anytime during life of the ticket. In addition, DigAlert® will email the excavator at the start date and time listed on the ticket a complete status of responses, if the excavator has supplied an email address on the ticket and given permission to send emails. ### **How it works** Once a ticket is created, it is sent out to all utility members who asked for notification in that area. As members clear or respond to the site they send a response back to DigAlert® with information about what was completed. For example; "locate area marked", "no access to area", "clear - no conflict", etc. DigAlert® will store that information with the ticket along with a date \& time stamp. Members can make multiple responses to the same ticket however responses can't be edited or deleted. This means that all responses will show with their corresponding date and time. There are four ways for members to submit responses to DigAlert®. Manually via web portal/mobile app, manually via a link on the ticket delivery, through a web service/TCP connection (this requires you to already have a ticket management system or application that can send TCP requests to our server) or through a REST API. Technical documents can be found here → [Automated Electronic Positive Response via TCP Connection](https://docs.digalert.org/um/responding-via-tcp-connection) or via a REST API. REST API documentation can be found here → [Automated Electronic Positive Response via REST API](https://docs.digalert.org/um/responding-via-rest-api). ### **What are the Requirements?** To use Electronic Positive Response as a utility member (or contract locator) you must; 1. Be a member in good standing of DigAlert® (for contract locators, the company you are locating for must be a member in good standing) 2. Be assigned at least one active member code (done at the time of joining) 3. Notify DigAlert® you wish to use EPR through the center by emailing Member Services at [memberservices@digalert.org](mailto:memberservices@digalert.org) 4. Decide how you will submit your responses to DigAlert® from one of the four available ways, found on the left menu **Warning!** If you have multiple facilities (water, electric, sewer) and you only have ONE member code, when you respond you CANNOT respond differently per facility. There can be only one response PER member code. This is why it is required to have one code per facility type. **Important Information!** DigAlert® requires that if you have multiple facility types (water, electric, sewer, etc) that you have a member code for each type. ### **When are Responses Required?** | Ticket Type | Ticket Type Description | Response Required | Optional Response Accepted if Sent (Only applies to NO Response Required) | Response Required Date/Time | |-------------|-------------------------|-------------------|---------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | AMND | Amendment | NO | YES | If before the original Work Date/Time on the ticket or Legal notice then the response due date/time remain the same. If after the response required date/time become legal notice. | | CNCL | Cancel | NO | NO | None | | DMGE | Damage | NO | YES | None | | EXPD | Exposed | NO | YES | None | | NEW | New | YES | | Legal notice or Work Date/Time on ticket (whichever is later) | | NRSP | No Response | YES | | None | | REMK | Request Re-marks | YES | | Legal notice | | RNEW | Renew Only | NO | YES | None | | RTRN | Return Trip | YES | | Legal notice or Work Date/Time | ### **Benefits of using EPR** For the member, EPR is an effective means of reducing the number of retransmits that they receive because the excavator saw no markings at the dig site. For excavators, EPR provides them with information about the member facilities prior to arriving on the job site. If they provided an email address when the locate request was called in they will receive an email confirmation after the start date \& time listed on the ticket. ### **Is Testing Available?** Testing is available for members that wish to test posting responses using the [Automated Electronic Positive Response via TCP Connection](https://docs.digalert.org/um/responding-via-tcp-connection) and [Automated Electronic Positive Response via REST API](https://docs.digalert.org/um/responding-via-rest-api) methods ONLY. In order to test, you MUST be an active member of Underground Service Alert of Southern California. --- language: "en" --- # Response Codes **Released**: 10/29/24 **Effective**: 1/1/25 *** ** * ** *** ## Electronic Positive Response (EPR) Codes as defined by DigAlert® The EPR codes on this page are maintained by DigAlert®. These codes are used for members to submit responses to DigAlert's® EPR servers. For Excavators wishing to check responses, please see → [Verifying Responses via Website](https://docs.digalert.org/ed/verifying-responses-via-website). The responses will be displayed with the description, not the code. **More information!** For more information on what the response codes mean and when to use them, please see [Best Practices](https://docs.digalert.org/um/epr-best-practices-2025.md). | Response Code | Description | |---------------|-------------------------------------------------------------------------------------------------------------| | 000 | Reserved for system use only | | | | | 001 | Clear - No conflict | | 003 | Existing markings adequate | | 004 | No markings requested | | | | | 010 | Locate area marked | | 014 | Partially marked - More time is needed | | 015 | Provided facility location information to excavator (4216.3(a)(1)(A)(ii)) | | 016 | Operator has located and marked all subsurface installations known to be embedded in the pavement 4216.3(b) | | | | | 020 | Bad address/incorrect street/location info - New ticket required | | 021 | No access to locate area - Resend ticket requested | | 022 | No delineation - Resend ticket requested | | | | | 031 | Requires stand by at time of excavation - Contact facility owner | | 033 | High priority line in area - On site meeting required | | 034 | Field meet required - Contact facility owner to schedule | | | | | 040 | Excavator completed work prior to due date | | 041 | Excavator no show for meet | | 042 | Excavator canceled request (system use only) | | | | | 050 | Negotiated marking schedule | | 051 | Mutually agreed to a later start date and time (4216.3(a)(1)(A)) | | 053 | Scheduled meet with excavator at requested date and time | | | | | 080 | Extraordinary circumstances exist - No locate due to weather/emergency/safety conditions | | | | | 998 | DigAlert® Test Code - No Lines In Area | | 999 | Member did not respond by required time (system use only) | To integrate these response codes with your ticket management system, you can retrieve this list via API by accessing as a GET. This API will return the following JSON formatted message. Field definitions: "last_change" displays the date the last change was made to the EPR codes as a string "version" displays the EPR Codes JSON file version as a string "response_codes": "response" displays the EPR response code (three numbers as a string) "state" displays the state/center as a string (max 4 chars) - For Underground Service Alert of Southern California will always show CA-S "description" displays the readable description of the EPR response code as a string "allowed" displays wether the EPR code is available for public use as a bit/boolean. "false" means this code can only be used by DigAlert's® system internally. "true" means the EPR code can be used by members when posting. JSON {{ "last_change": "2024-11-12", "version": "24.11.12.1", "response_codes": [ { "response": "000", "state": "CA-S", "description": "Member has not responded yet", "allowed": false }, { "response": "001", "state": "CA-S", "description": "CLEAR - NO CONFLICT", "allowed": true }, { "response": "003", "state": "CA-S", "description": "EXISTING MARKINGS ADEQUATE", "allowed": true }, { "response": "004", "state": "CA-S", "description": "NO MARKINGS REQUESTED", "allowed": true }, { "response": "010", "state": "CA-S", "description": "LOCATE AREA MARKED", "allowed": true }, { "response": "014", "state": "CA-S", "description": "PARTIALLY MARKED - MORE TIME IS NEEDED", "allowed": true }, { "response": "015", "state": "CA-S", "description": "PROVIDED FACILITY LOCATION INFORMATION TO EXCAVATOR (4216.3(A)(1)(A)(II))", "allowed": true }, { "response": "016", "state": "CA-S", "description": "OPERATOR HAS LOCATED AND MARKED ALL SUBSURFACE INSTALLATIONS KNOWN TO BE EMBEDDED IN THE PAVEMENT (4216.3 (e))", "allowed": true }, { "response": "020", "state": "CA-S", "description": "BAD ADDRESS/INCORRECT STREET/LOCATION INFO - NEW TICKET REQUIRED", "allowed": true }, { "response": "021", "state": "CA-S", "description": "NO ACCESS TO LOCATE AREA - RESEND TICKET REQUIRED", "allowed": true }, { "response": "022", "state": "CA-S", "description": "NO DELINEATION - RESEND TICKET REQUESTED", "allowed": true }, { "response": "031", "state": "CA-S", "description": "REQUIRES STAND BY AT TIME OF EXCAVATION - CONTACT FACILITY OWNER", "allowed": true }, { "response": "033", "state": "CA-S", "description": "HIGH PRIORITY LINE IN AREA - ON SITE MEETING REQUIRED", "allowed": true }, { "response": "034", "state": "CA-S", "description": "FIELD MEET REQUIRED - CONTACT FACILITY OWNER TO SCHEDULE", "allowed": true }, { "response": "040", "state": "CA-S", "description": "EXCAVATOR COMPLETED WORK PRIOR TO DUE DATE", "allowed": true }, { "response": "041", "state": "CA-S", "description": "EXCAVATOR NO SHOW FOR MEET", "allowed": true }, { "response": "042", "state": "CA-S", "description": "EXCAVATOR CANCELED REQUEST", "allowed": false }, { "response": "050", "state": "CA-S", "description": "NEGOTIATED MARKING SCHEDULE", "allowed": true }, { "response": "051", "state": "CA-S", "description": "MUTUALLY AGREED TO A LATER START DATE AND TIME (4216.3(A)(1)(A))", "allowed": true }, { "response": "053", "state": "CA-S", "description": "SCHEDULED MEET WITH EXCAVATOR AT REQUESTED DATE AND TIME", "allowed": true }, { "response": "080", "state": "CA-S", "description": "EXTRAORDINARY CIRCUMSTANCES EXIST - NO LOCATE DUE TO WEATHER/EMERGENCY/SAFETY CONDITIONS", "allowed": true }, { "response": "998", "state": "CA-S", "description": "DIGALERT TEST CODE - NO LINES IN AREA", "allowed": false }, { "response": "999", "state": "CA-S", "description": "Member did not respond by the required time", "allowed": false } ] } --- language: "en" --- # SMS (Text Messages) **Released**: 11/1/17 **Effective**: 1/1/18 *** ** * ** *** ## What is SMS? SMS stands for Short Message Service but is commonly know as Text Messages. Although most phones today are not limited to 144 characters per text message SMS is not really "short" anymore. With the addition of MMS or MultiMedia Message Service, text messages now can be so much more. They can be longer than 144 characters, they can contain music, pictures, videos, links and so much more. Something most of us use every day of our life. ## What are the options? Great question. There is a lot of information you can receive from DigAlert® instantly, at any time of the day and any day of the year. SMS notifications are sent to excavators that allow with confirmations of their DigAlert® tickets as well as Electronic Positive Response (EPR) so you can stay up to date in the field at all times. In addition, you can text us to get information as well as start a conversations. ## Sending us Text Messages **To use any of the following options please text the command to DIGALT (344-258)** * Apps (Will return links for the DigAlert ®mobile apps in all the app stores) * Color Codes (Will return all APWA approved color codes and their meaning) * Email A123456789 YOUREMAILADDRESS (Will email the requested ticket to the specified email address) * ER A123456789 (Will return all available emergency contact information for members on the requested ticket) * Feedback MESSAGE (Will send us feedback that you may want us to know) * Help (Will return a standard message required by the carriers) * Holidays (Will return the next upcoming holiday that will affect the center and the legal notice) * Law (Will return a link to the current CA Government Code 4216) * More (Will return more options) * New Ticket (Will return a link to DigAlert Direct® to allow you to enter a new ticket online) * Options (Will return a list of popular options or commands available) * Stats (Will return if the center is open or closed, number of calls on hold and number of tickets completed for the day) * Ticket A123456789 (Will return details for the requested ticket and a link to view the entire ticket) * Presp A123456789 (Will return positive response details and a link to view all positive responses) * Renew (Will renew your ticket for an additional 28 calendar days after a few simple questions back and forth) * Vacuum A123456789 (Will return all available vacuum contact information for members on the requested ticket) * Website (Will return a link to our website) --- language: "en" --- # Verifying Responses via Website **Released**: 1/1/17 **Effective**: 1/1/17 *** ** * ** *** ## How to check for responses Checking Electronic Positive Responses (EPR) can be done the following ways 1. Visit [digalert.org](http://DigAlert.org) , click Web Services on the menu, then click "Check Electronic Positive Response" or if using the mobile app, click the Electronic Positive Response menu item 2. If an email address was supplied on the ticket and permission was given to send messages, an email will be sent at the time EPRs are due with all available responses. Additional emails will be sent each time a member submits a new response or updates a response after the due date/time. 3. If a cell phone number was supplied on the ticket and permission was given to send text messages, a text message will be sent at the time EPRs are due with all available responses. Additional text messages will be sent each time a member submits a new response or updates a response after the due date/time. ## Step by step details To check EPRs via [digalert.org](http://DigAlert.org) or the mobile apps, follow options 1 or 2 from above and the main screen will appear shown below. ![EPR-2.5.png](https://docs.digalert.org/__attachments/a_5116c07b8b4ab41b1a590bdd624d13dd25a3592290b9bd4eba273bc12799b374/EPR-2.5.png) 1. Enter the complete ticket number, then click the search icon to search for your ticket. 2. Some brief information from the ticket will display to ensure you are viewing the correct ticket number. If the ticket number is incorrect, simply repeat step 1. ![EPR-3.png](https://docs.digalert.org/__attachments/a_a8b95f819763654e1790c2fa7caf0e42d8448aa89e856b13973e7cc26d9ae102/EPR-3.png) 3. Once a ticket has been inquired and displayed, responses for the most current revision will be displayed automatically in the timeline, if any were made. 4. If other revisions of your ticket exist, you may select the checkbox to the left to show or hide positive responses for the selected revision. ![EPR-5.png](https://docs.digalert.org/__attachments/a_44d80c1a603269890ae96aaea922af158bad976b84ade165e0707a7f36222f4a/EPR-5.png) EPRs will show Comments and URL for additional information if provided by that member when they respond --- language: "en" --- # DigAlert Support Center ## Documentation * ### [Get Support](https://docs.digalert.org/dsc/get-support.md) * ### [Training \& Videos](https://docs.digalert.org/dsc/training-videos.md) --- language: "en" --- # Get Support Choose from the following available help centers. ## ![https://icons-confluence.presago.net/icon/9306780c-2bff-468f-a60c-2d6138c17748/svg?color=%237030a0&shape=none&filled=false](https://icons-confluence.presago.net/icon/9306780c-2bff-468f-a60c-2d6138c17748/svg?color=%237030a0&shape=none&filled=false) **-** [**DigAlert Utility Member Help Center**](https://mshelp.digalert.org) For member related issues, including mapping, ticket deliveries, ticket resends, contact updates, EPR, etc. ## ![https://icons-confluence.presago.net/icon/423d3887-3efe-4433-b669-e80c4f6bd35c/svg?color=%237030a0&shape=none&filled=false](https://icons-confluence.presago.net/icon/423d3887-3efe-4433-b669-e80c4f6bd35c/svg?color=%237030a0&shape=none&filled=false) **-** [**DigAlert Direct Help Center**](https://oshelp.digalert.org) For all DigAlert Direct, online services, mobile apps, user accounts, etc. ## ![https://icons-confluence.presago.net/icon/7a8b655a-c06f-4e00-9700-ac5845513eea/svg?color=%237030a0&shape=none&filled=false](https://icons-confluence.presago.net/icon/7a8b655a-c06f-4e00-9700-ac5845513eea/svg?color=%237030a0&shape=none&filled=false) **-** [**DigAlert I.T. Help Center**](https://ithelp.digalert.org) For all external I.T. related issues, including website, hosting services, DNS, telephone, etc. --- language: "en" --- # Training & Videos ## What are training options, if any? Please see our YouTube channel for videos and online instructional courses. ### Schedule dedicated training ## ![](https://icons-confluence.presago.net/icon/90e4957d-2b22-4cd8-a65c-89c82cde3b6d/svg?color=%237030a0&shape=none&filled=false) - [++Online Services Training Request++](https://digalert.org/education/training/online-services) ### YouTube ## ![](https://icons-confluence.presago.net/icon/b02890cc-e61c-4491-9c92-def101bb04cf/svg?color=%237030a0&shape=none&filled=false) **-** [DigAlert's YouTube Channel](https://www.youtube.com/channel/UCeWBjKbi2GNEtds8OWzPvAg) --- language: "en" --- # Excavators & DIYers Home ## Documentation * ### [Approved Abbreviations](https://docs.digalert.org/ed/approved-abbreviations.md) * ### [California Government Code 4216 - "The call before you dig law"](https://docs.digalert.org/ed/california-government-code-4216-the-call-before-yo.md) * ### [Ticket Location Size Requirements](https://docs.digalert.org/ed/ticket-location-size-requirements.md) * ### [Ticket Location Size Examples](https://docs.digalert.org/ed/ticket-location-size-examples.md) * ### [No Response Tickets](https://docs.digalert.org/ed/no-response-tickets.md) ### [Ticket Types \& Explanations](https://docs.digalert.org/ed/ticket-types-explanations.md) * ### [Excavator Confirmations via Email/SMS](https://docs.digalert.org/ed/excavator-confirmations-via-email-sms.md) ### [Electronic Positive Response (EPR)](https://docs.digalert.org/ed/electronic-positive-response-epr.md) * ### [Training \& Help](https://docs.digalert.org/ed/training-help.md) --- language: "en" --- # Approved Abbreviations **Released**: 2/15/23 **Effective**: 2/15/23 *** ** * ** *** This list is all approved abbreviations that can be found on DigAlert® Tickets. Any abbreviation used on the map is allowed only when referring to that street. ## **All abbreviations street names, prefixes, suffixes and direction shown on the map MUST be used in the street and cross street fields.** | **Color** | **Meaning** | |-----------|----------------------------------------------| | | Required to use | | | Must be spelled out completely the first use | | **Abbreviation** | **Description** | |------------------|------------------------------| | ABDN | ABANDON | | APPROX | APPROXIMATELY | | ASAP | AS SOON AS POSSIBLE | | AVD | AVENIDA | | AVE | AVENUE | | AVE/OF | AVENUE OF | | AVE/OF THE | AVENUE OF THE | | B-YARD | BACKYARD | | BLVD | BOULEVARD | | BTWN | BETWEEN | | C/L | CENTERLINE | | C/OF | CITY OF | | CATV | CABLE TELEVISION | | CIR | CIRCLE | | CMTO | CAMINITO | | CO/AREA | COUNTY AREA | | CO/OF | COUNTY OF | | COMM | COMMUNICATION | | CONST | CONSTRUCTION | | CONT | CONTINUE | | CONTR | CONTRACTOR | | COR | CORNER | | COR/OF | CORNER OF | | CORP | CORPORATION | | CT | COURT | | CTE | CORTE | | CV | COVE | | DEPT | DEPARTMENT | | DEV | DEVELOPMENT | | DOT | DEPARTMENT OF TRANSPORTATION | | DR | DRIVE | | E/OF | EAST OF | | E/ON | EAST ON | | E/SIDE | EAST SIDE | | E/TO | EAST TO | | ELEC | ELECTRIC | | ENGR | ENGINEER | | EST | ESTIMATE | | ETA | ESTIMATED TIME OF ARRIVAL | | EXCAV | EXCAVATING | | EXCAV | EXCAVATION | | EXCAV | EXCAVATED | | EXT | EXTENDED | | EXWY | EXPRESSWAY | | F-YARD | FRONT YARD | | FRM | FROM | | FRWY | FREEWAY | | FRY | FERRY | | FT | FEET (OR FOOT) | | H/O | HOMEOWNER | | HTS | HEIGHTS | | HWY | HIGHWAY | | INSTALL | INSTALL | | INSTALL | INSTALLING | | INSTALL | INSTALLED | | INSTALL | INSTALLATION | | INTER | INTERSECTION | | INTER/OF | INTERSECTION OF | | IRRIG | IRRIGATION | | JCT | JUNCTION | | LN | LANE | | LOC | LOCATION | | LOC | LOCATED | | LOT # | LOT NUMBER | | MAINT | MAINTENANCE | | MAINT | MAINTENED | | MHP | MOBILE HOME PARK | | MT | MOUNT | | MTN | MOUNTAIN | | MTWY | MOTORWAY | | N/E | NORTHEAST | | N/OF | NORTH OF | | N/ON | NORTH ON | | N/SIDE | NORTH SIDE | | N/TO | NORTH TO | | N/W | NORTHWEST | | NATL | NATIONAL | | OWN | OWNER | | OWN/BLDR | OWNER BUILDER | | P/L | PROPERTY LINE | | PKWY | PARKWAY | | PL | PLACE | | PLZ | PLAZA | | PROP | PROPERTY | | PROP/O | PROPERTY OWNER | | PT | POINT | | PWR | POWER | | R/R TRACKS | RAILROAD TRACKS | | RD | ROAD | | RDG | RIDGE | | RDWY | ROADWAY | | RELOC | RELOCATE | | REM | REMOVE | | REPL | REPLACE | | RTE | ROUTE | | S/E | SOUTHEAST | | S/OF | SOUTH OF | | S/ON | SOUTH ON | | S/SIDE | SOUTH SIDE | | S/TO | SOUTH TO | | S/W | SOUTHWEST | | SERV | SERVICE | | SP | SPACE | | SQ | SQUARE | | ST | STREET | | ST/OF | STREET OF | | ST/OF THE | STREET OF THE | | TEL | TELEPHONE | | TEMP | TEMPORARY | | TER | TERRACE | | TKTR | TRUCK TRAIL | | TR | TRAIL | | TR # | TRACT NUMBER | | TRAF | TRAFFIC | | UTIL | UTILITY | | UTIL | UTILITIES | | VLY | VALLEY | | VW | VIEW | | W/OF | WEST OF | | W/ON | WEST ON | | W/SIDE | WEST SIDE | | W/TO | WEST TO | | WAY | WAY | | WTR | WATER | | X/ST | CROSS STREET | --- language: "en" --- # California Government Code 4216 - "The call before you dig law" ## ![https://icons-confluence.presago.net/icon/f3d00a7a-ee8b-4408-94ac-6f7610d025f5/svg?color=%237030a0&shape=none&filled=false](https://icons-confluence.presago.net/icon/f3d00a7a-ee8b-4408-94ac-6f7610d025f5/svg?color=%237030a0&shape=none&filled=false) **-** [**View the CA Government Code 4216**](https://leginfo.legislature.ca.gov/faces/codes_displayText.xhtml?lawCode=GOV&division=5.&title=1.&part=&chapter=3.1.&article=2.) ## ![https://icons-confluence.presago.net/icon/9d78fea6-d1e9-473e-97da-fd618f9d6e22/svg?color=%237030a0&shape=none&filled=false](https://icons-confluence.presago.net/icon/9d78fea6-d1e9-473e-97da-fd618f9d6e22/svg?color=%237030a0&shape=none&filled=false) **-** [**View the CA Code of Regulations**](https://govt.westlaw.com/calregs/Browse/Home/California/CaliforniaCodeofRegulations?guid=I2EFBE0205BE511EC98C8000D3A7C4BC3&originationContext=documenttoc&transitionType=Default&contextData=(sc.Default)&bhcp=1) ## ![https://icons-confluence.presago.net/icon/4386b315-082d-43cb-8242-296c86ddee8e/svg?color=%237030a0&shape=none&filled=false](https://icons-confluence.presago.net/icon/4386b315-082d-43cb-8242-296c86ddee8e/svg?color=%237030a0&shape=none&filled=false) **-** [**Report a possible violation or damage**](https://www.contact811.org) --- language: "en" --- # Electronic Positive Response (EPR) **Released**: 11/1/21 **Effective**: 1/1/22 *** ** * ** *** ## **What is Electronic Positive Response (EPR)** Electronic Positive Response (+Response or EPR) is communication from the utility member (contract locator) to the excavator regarding the status of a DigAlert® ticket. California has always had +Response in the law by requiring members to notify the excavator with status or mark the area to be excavated on site. What changed in Government Code 4216 on January 1st, 2017, is that Electronic Positive Response can now be made through the Notification Center starting January 1st, 2018. However, DigAlert® began offering this service starting November 1st, 2017. During 2018, 2019 \& 2020 EPR was voluntary but starting on January 1st, 2021 EPR became mandatory for members, unless a 1 year extension was given prior by the Underground Safe Excavation Board. Then on January 1st, 2022, EPR became mandatory for all members. This means that members must respond to DigAlert's® servers about the marking status of the ticket. DigAlert® will then allow the excavator to check the responses through the website, SMS and apps anytime during life of the ticket. In addition, DigAlert® will email the excavator at the start date and time listed on the ticket a complete status of responses, if the excavator has supplied an email address on the ticket and given permission to send emails. ### **How it works** Once a ticket is created, it is sent out to all utility members who asked for notification in that area. As members clear or respond to the site they send a response back to DigAlert® with information about what was completed. For example; "locate area marked", "no access to area", "clear - no conflict", etc. DigAlert® will store that information with the ticket along with a date \& time stamp. Members can make multiple responses to the same ticket however responses can't be edited or deleted. This means that all responses will show with their corresponding date and time. There are four ways for members to submit responses to DigAlert®. Manually via web portal/mobile app, manually via a link on the ticket delivery, through a web service/TCP connection (this requires you to already have a ticket management system or application that can send TCP requests to our server) or through a REST API. Technical documents can be found here → [Automated Electronic Positive Response via TCP Connection](https://docs.digalert.org/um/responding-via-tcp-connection) or via a REST API. REST API documentation can be found here → [Automated Electronic Positive Response via REST API](https://docs.digalert.org/um/responding-via-rest-api). ### **What are the Requirements?** To use Electronic Positive Response as a utility member (or contract locator) you must; 1. Be a member in good standing of DigAlert® (for contract locators, the company you are locating for must be a member in good standing) 2. Be assigned at least one active member code (done at the time of joining) 3. Notify DigAlert® you wish to use EPR through the center by emailing Member Services at [memberservices@digalert.org](mailto:memberservices@digalert.org) 4. Decide how you will submit your responses to DigAlert® from one of the four available ways, found on the left menu **Warning!** If you have multiple facilities (water, electric, sewer) and you only have ONE member code, when you respond you CANNOT respond differently per facility. There can be only one response PER member code. This is why it is required to have one code per facility type. **Important Information!** DigAlert® requires that if you have multiple facility types (water, electric, sewer, etc) that you have a member code for each type. ### **When are Responses Required?** | Ticket Type | Ticket Type Description | Response Required | Optional Response Accepted if Sent (Only applies to NO Response Required) | Response Required Date/Time | |-------------|-------------------------|-------------------|---------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | AMND | Amendment | NO | YES | If before the original Work Date/Time on the ticket or Legal notice then the response due date/time remain the same. If after the response required date/time become legal notice. | | CNCL | Cancel | NO | NO | None | | DMGE | Damage | NO | YES | None | | EXPD | Exposed | NO | YES | None | | NEW | New | YES | | Legal notice or Work Date/Time on ticket (whichever is later) | | NRSP | No Response | YES | | None | | REMK | Request Re-marks | YES | | Legal notice | | RNEW | Renew Only | NO | YES | None | | RTRN | Return Trip | YES | | Legal notice or Work Date/Time | ### **Benefits of using EPR** For the member, EPR is an effective means of reducing the number of retransmits that they receive because the excavator saw no markings at the dig site. For excavators, EPR provides them with information about the member facilities prior to arriving on the job site. If they provided an email address when the locate request was called in they will receive an email confirmation after the start date \& time listed on the ticket. ### **Is Testing Available?** Testing is available for members that wish to test posting responses using the [Automated Electronic Positive Response via TCP Connection](https://docs.digalert.org/um/responding-via-tcp-connection) and [Automated Electronic Positive Response via REST API](https://docs.digalert.org/um/responding-via-rest-api) methods ONLY. In order to test, you MUST be an active member of Underground Service Alert of Southern California. --- language: "en" --- # EPR Best Practices **Released**: 10/29/24 **Effective**: 1/1/25 *** ** * ** *** ## Overview This page is intended to provide descriptions of each Electronic Positive Response (EPR) code and a set of example of when they should be used by members. Following these best practices will not only ensure members are consistent as well as helping excavators understand what the member is communicating back to them. While the best practice is a living document, it is important to remember that not every situation can be identified. There will be cases where the member will have to use the best response available to them using all the information available at that time. ## Response Code Definitions and Examples ### 001 : Clear - No conflict **Definition:** The members lines are not in the area to be excavated. This does NOT mean that the member doesn't have any line in the area. A member may have lines near by, but based on the delineation and the location on the ticket, they are clear for that area. If, for any reason the excavation area or type of work changes, the excavator MUST contact the notification center and get a new ticket issued for the changes. **When to use:** ONLY when there are no underground facilities within the area of delineation and/or the location on the ticket. ### 003 : Existing markings adequate **Definition:** The markings on site are reasonably visible and marked to the extent of the delineation and/or ticket location. If, for some reason the excavation area or type of work changes, the excavator MUST contact the notification center and get a new ticket issued for the changes. **When to use:** When the existing markings on site are complete and accurate. ### 004 : No markings requested **Definition:** The excavator is asking certain members or all members not to mark. The most common use the centers see for this is on emergency work where the job was completed but the excavator needs a ticket number to make the permit valid. **When to use:** ONLY when the excavator is not asking for any marks. ### 010 : Locate area marked **Definition:** The area of delineation and/or the ticket location area has been marked completely and accurately. **When to use:** After the entire area of delineation and/or the ticket location area has been marked completely and accurately. ### 014 : Partially marked - more time is needed **Definition:** The area of delineation and/or the ticket location area has been partially marked. Member needs more time to complete marking. **When to use:** Member has been called away or needs more information to complete markings. NOTE: this code does NOT close the ticket. ### 015 : Provided facility information to excavator (California Government Code 4216.3(a)(1)(A)(ii)) **Definition:** The member to the extent and degree of accuracy that the information is available, provides information to the excavator where the active or inactive lines are located. **When to use:** Member does NOT locate and field mark their active or inactive lines but otherwise provides information to the excavator of where the lines are located. ### 016 : Operator has located and marked all subsurface installations known to be embedded in the pavement (4216.3 (e)) **Definition:** The member located and marked all known facilities embedded in the pavement. **When to use:** When ONLY the embedded lines are marked. ### 020 : Bad address/incorrect street/location info - New ticket required **Definition:** Member cannot find the location on the ticket. Excavator will need to contact center to correct location. Additional time may be needed to complete marking. If mapping changes a new ticket will need to be issued. **When to use:** Member cannot reach excavator by communication methods available on ticket to request the excavator to clarify or correct the location. ### 021 : No access to locate area - Resend ticket requested **Definition:** The member cannot access the area listed on the ticket due to a locked gate, fence or other hindrance (ex - dog in yard). Excavator please provide access information or time when access to location will be available. Additional time may be needed to complete marking. **When to use:** Member cannot reach excavator by communication methods available on ticket and the area is inaccessible. ### 022 : No delineation (California Government Code 4216.2(a)) - Resend ticket requested **Definition:** The area is not delineated as required by 4216.2(a). Member has chosen not to locate and field mark until the area to be excavated is delineated. Excavator needs to delineate the area where the excavation will take place and submit an amendment through the center when the area is delineated. Additional time may be needed to complete marking. **When to use:** The excavator has not delineated the area to be excavated. ### 031 : Requires stand-by at time of excavation - Contact facility owner **Definition:** The member requires a representative to be on site while the excavation is taking place. Excavator required to contact the member to set up date and time for the stand-by. **When to use:** The member has marked BUT needs to also be on site during the excavation. ### 033 : High priority line in area - On Site Meeting Required (California Government Code 4216.2(e)) **Definition:** The member has a high priority line as defined in 4216(j) and is required to meet with the excavator and the member will contact excavator to set up an on site meeting. **When to use:** Anytime a high priority line meeting is required. ### 034 : Field meet required - Contact facility owner to schedule **Definition:** The member wants to meet with the excavator prior to excavation commencing. Excavator needs to contact member to set up a meeting. **When to use:** The member has NOT marked the lines and requires a meeting before excavation begins. ### 040 : Excavator completed work prior to due date **Definition:** The job is completed before the member has marked their line. **When to use:** The member did not mark as job was completed before the start date and time on the ticket. ### 041 : Excavator no-show for meet **Definition:** The excavator and member agreed to a meet date and time and the excavator did not show. **When to use:** After a meeting has been scheduled and the excavator did not meet with the member at the specified date and time. ### 042 : Excavator canceled request **Definition:** The excavator cancels the ticket before the member has responded. **When to use:** SYSTEM USE ONLY. ONLY to clear a ticket as having a response if a CNCL ticket is sent before the member has responded. ### 050 : Negotiated marking schedule (California Government Code 4216.3(a)(1)(A)) **Definition:** The member and excavator have mutually agreed to the sequence and time frame in which to locate and field mark **When to use:** The member and excavator have discussed and agreed to a marking schedule. ### 051 : Mutually agreed to a later start date and time (California Government Code 4216.3(a)(1)(A)) **Definition:** The member and excavator have mutually agreed to a later start date and time for the excavation to begin. **When to use:** The member and excavator have discussed and agreed to a new start date and time. ### 053 : Scheduled meet with excavator at requested date and time **Definition:** The excavator has asked for a joint meet and mark on the ticket. This code is designed to communicate to the excavator that your company will be present during the meet at the scheduled date and time and to avoid an automatic late notice since responses must be submitted prior to the legal date and time. **When to use:** ONLY when you are confirming to be present at the scheduled meet date and time. ### 080 : Extraordinary circumstances exist - No locate due to weather/emergency/safety conditions **Definition:** There are circumstances that make it impossible to locate the ticket prior to the legal date and time. **When to use:** ONLY when there are weather, emergency or safety conditions that prevent marking from taking place. ### 998 : DigAlert® Test Code - No Lines In Area (System use only) **Definition:** DigAlert® has test member codes that are used to test and monitor the system. These codes are not "real" members and do not have any lines or facilities. Since reports will show the number of no responses tickets with these codes are automatically responded with this internal code. **When to use:** Not available for use by the member. This is a system generated response. ### 999 : Member did not respond by the required time (System use only) **Definition:** The member did not respond to the electronic positive response system prior to the legal date and time. **When to use:** Not available for use by the member. This is a system generated response. --- language: "en" --- # Excavator Confirmations via Email/SMS **Released**: 10/25/23 **Effective**: 1/1/23 *** ** * ** *** When creating a ticket, either online or over the phone with one of our Customer Service Respresentives (CSR), you will be asked if you would like to receive a copy of the ticket and any Electronic Positive Response (EPR) notifications. These notifications are by Email, SMS or both. Here are examples of what each one looks like. ## Email Confirmations ![confirmation-epr-notice-pt-1.png](https://docs.digalert.org/__attachments/a_2077abe93abb93e57b8f3ce818d95ea1366f6f0c12477927ba9bbced31717d30/confirmation-epr-notice-pt-1.png?cb=9ed589767d826fc3b52c56c1247a920f) Email ticket notification (1) ![confirmation-epr-notice-pt-2.png](https://docs.digalert.org/__attachments/a_2b88f93f8180587f977b6bd377f0153fcccae1de5b848acbaefef1e306ba3418/confirmation-epr-notice-pt-2.png?cb=017fabcdc73f2c550e67c24e8d6d34f0) Email ticket notification (2) ![confirmation-epr-notice-pt-3.png](https://docs.digalert.org/__attachments/a_c1d9f1a29569f9e37ca5a772112da961629672baac8f4c59ec7ed5fd99cc5b4e/confirmation-epr-notice-pt-3.png?cb=4fb8efcfd8f15f25011e7c1879486c5e) Email ticket notification (3) ![confirmation-epr-update-pt-1.png](https://docs.digalert.org/__attachments/a_27c5e93c4d4cb75257ecbae8cba4fab2ad7f5a75efba0dedced9ac2003676862/confirmation-epr-update-pt-1.png?cb=c9b41b38fa0043fe37d72a6b084088a6) EPR Update (1) ![confirmation-epr-update-pt-2.png](https://docs.digalert.org/__attachments/a_ff4fbc0bc947a7246e08dead777dee2803a5c2c1b79002f7490f7327dfb21524/confirmation-epr-update-pt-2.png?cb=6968ef1a3e79ef25fb38645084b07c24) EPR Update (2) ## SMS Confirmations ![ticket-confirmation-sms.png](https://docs.digalert.org/__attachments/a_38da6854901a399bf0408e62a309f1af02358703e42971003b6f7e3d717cbdff/ticket-confirmation-sms.png?cb=a0ea666357ec11a3780faf658ad756ca) SMS ticket confirmation ![epr-confirmation-sms.png](https://docs.digalert.org/__attachments/a_ecb19421d83b9e109e7b9de4b1829d4fbf2c6010460f50b4875d6981dcce208f/epr-confirmation-sms.png?cb=1cb3d31bc1034a841152629239d67e5b) SMS EPR confirmation --- language: "en" --- # No Response Tickets **Released**: 11/01/25 **Effective**: 01/01/26 *** ** * ** *** ## Auto No Response History Effective January 1st 2025, Underground Service Alert of Southern California (DigAlert®) started sending automatic No Response tickets to members who failed to respond to the Electronic Positive Response (EPR) system by the required date and time on behalf of the excavator. These No Response tickets are sent to the members until they respond to the EPR system as required by CA GC 4216 every 2 working days, not including the date of notification. DigAlert® has allowed excavators to submit No Response tickets manually as well since this change took place. ### Manual No Response Changes 1/1/2026 Effective **January 1st, 2026**, the manual No Response process will no longer be allowed since No Responses are sent automatically at the legal date/time of the ticket on behalf of the excavator. The excavator no longer needs to worry about these as the system does it for them automatically. ### What does this mean? This change means that as of January 1st, 2026, you will no longer be able to submit a No Response ticket outside of the system automatically doing it for you. ### What if I disagree with the response the member has given? If the member posts an EPR that you disagree with and need them back out for any reason there are a few steps to take. First, submit the ticket as a **Return Trip** and state in the comments, the reason you are asking the member to come back out and the facts you believe the EPR provided is not accurate. If you are not in need of the members to respond back out to the location, then submit the ticket as an **Amendment** with the same type of comments described previously. Remember, this is a business and a legal document so there is no need for any hostility or unprofessional comments to be listed on a ticket, make sure the comments are professional. Second, you can **file a complaint** with the Underground Safe Excavation Board by visiting the following link → . Be sure to complete the form in its entirety so the investigators can get a complete understanding of the complaint. ### I need to call someone, who do I call? If you need to call someone, look at your ticket confirmation for the phone number for the member you are wishing to contact. These are the most up to date phone numbers DigAlert® has available in the system. If you do not have a copy of your ticket, you can go here → and look up the contact information for the members notified on your ticket. ### Recap Instead of sending a No Response for a member that has already supplied a response to the EPR system, send the ticket either as a; * Return Trip when asking for a member(s) to respond back out for any reason (other than for Re-marks, Damage or Exposed lines), be sure to list why in the comments * Amendment when just passing on information to the member without asking them to respond to the site. ![:warning:](https://docs.digalert.org/__attachments/a_ac3fbe36eb2c11cbe18b4ad4b9e38ca21638db2c9ac6471908530df63480f479/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **CAUTION** Amendment ticket **DO NOT** require members to respond to the job site or the EPR system. Never use this ticket type asking them to visit the site. --- language: "en" --- # Response Codes **Released**: 10/29/24 **Effective**: 1/1/25 *** ** * ** *** ## Electronic Positive Response (EPR) Codes as defined by DigAlert® The EPR codes on this page are maintained by DigAlert®. These codes are used for members to submit responses to DigAlert's® EPR servers. For Excavators wishing to check responses, please see → [Verifying Responses via Website](https://docs.digalert.org/ed/verifying-responses-via-website). The responses will be displayed with the description, not the code. **More information!** For more information on what the response codes mean and when to use them, please see [Best Practices](https://docs.digalert.org/um/epr-best-practices-2025.md). | Response Code | Description | |---------------|-------------------------------------------------------------------------------------------------------------| | 000 | Reserved for system use only | | | | | 001 | Clear - No conflict | | 003 | Existing markings adequate | | 004 | No markings requested | | | | | 010 | Locate area marked | | 014 | Partially marked - More time is needed | | 015 | Provided facility location information to excavator (4216.3(a)(1)(A)(ii)) | | 016 | Operator has located and marked all subsurface installations known to be embedded in the pavement 4216.3(b) | | | | | 020 | Bad address/incorrect street/location info - New ticket required | | 021 | No access to locate area - Resend ticket requested | | 022 | No delineation - Resend ticket requested | | | | | 031 | Requires stand by at time of excavation - Contact facility owner | | 033 | High priority line in area - On site meeting required | | 034 | Field meet required - Contact facility owner to schedule | | | | | 040 | Excavator completed work prior to due date | | 041 | Excavator no show for meet | | 042 | Excavator canceled request (system use only) | | | | | 050 | Negotiated marking schedule | | 051 | Mutually agreed to a later start date and time (4216.3(a)(1)(A)) | | 053 | Scheduled meet with excavator at requested date and time | | | | | 080 | Extraordinary circumstances exist - No locate due to weather/emergency/safety conditions | | | | | 998 | DigAlert® Test Code - No Lines In Area | | 999 | Member did not respond by required time (system use only) | To integrate these response codes with your ticket management system, you can retrieve this list via API by accessing as a GET. This API will return the following JSON formatted message. Field definitions: "last_change" displays the date the last change was made to the EPR codes as a string "version" displays the EPR Codes JSON file version as a string "response_codes": "response" displays the EPR response code (three numbers as a string) "state" displays the state/center as a string (max 4 chars) - For Underground Service Alert of Southern California will always show CA-S "description" displays the readable description of the EPR response code as a string "allowed" displays wether the EPR code is available for public use as a bit/boolean. "false" means this code can only be used by DigAlert's® system internally. "true" means the EPR code can be used by members when posting. JSON {{ "last_change": "2024-11-12", "version": "24.11.12.1", "response_codes": [ { "response": "000", "state": "CA-S", "description": "Member has not responded yet", "allowed": false }, { "response": "001", "state": "CA-S", "description": "CLEAR - NO CONFLICT", "allowed": true }, { "response": "003", "state": "CA-S", "description": "EXISTING MARKINGS ADEQUATE", "allowed": true }, { "response": "004", "state": "CA-S", "description": "NO MARKINGS REQUESTED", "allowed": true }, { "response": "010", "state": "CA-S", "description": "LOCATE AREA MARKED", "allowed": true }, { "response": "014", "state": "CA-S", "description": "PARTIALLY MARKED - MORE TIME IS NEEDED", "allowed": true }, { "response": "015", "state": "CA-S", "description": "PROVIDED FACILITY LOCATION INFORMATION TO EXCAVATOR (4216.3(A)(1)(A)(II))", "allowed": true }, { "response": "016", "state": "CA-S", "description": "OPERATOR HAS LOCATED AND MARKED ALL SUBSURFACE INSTALLATIONS KNOWN TO BE EMBEDDED IN THE PAVEMENT (4216.3 (e))", "allowed": true }, { "response": "020", "state": "CA-S", "description": "BAD ADDRESS/INCORRECT STREET/LOCATION INFO - NEW TICKET REQUIRED", "allowed": true }, { "response": "021", "state": "CA-S", "description": "NO ACCESS TO LOCATE AREA - RESEND TICKET REQUIRED", "allowed": true }, { "response": "022", "state": "CA-S", "description": "NO DELINEATION - RESEND TICKET REQUESTED", "allowed": true }, { "response": "031", "state": "CA-S", "description": "REQUIRES STAND BY AT TIME OF EXCAVATION - CONTACT FACILITY OWNER", "allowed": true }, { "response": "033", "state": "CA-S", "description": "HIGH PRIORITY LINE IN AREA - ON SITE MEETING REQUIRED", "allowed": true }, { "response": "034", "state": "CA-S", "description": "FIELD MEET REQUIRED - CONTACT FACILITY OWNER TO SCHEDULE", "allowed": true }, { "response": "040", "state": "CA-S", "description": "EXCAVATOR COMPLETED WORK PRIOR TO DUE DATE", "allowed": true }, { "response": "041", "state": "CA-S", "description": "EXCAVATOR NO SHOW FOR MEET", "allowed": true }, { "response": "042", "state": "CA-S", "description": "EXCAVATOR CANCELED REQUEST", "allowed": false }, { "response": "050", "state": "CA-S", "description": "NEGOTIATED MARKING SCHEDULE", "allowed": true }, { "response": "051", "state": "CA-S", "description": "MUTUALLY AGREED TO A LATER START DATE AND TIME (4216.3(A)(1)(A))", "allowed": true }, { "response": "053", "state": "CA-S", "description": "SCHEDULED MEET WITH EXCAVATOR AT REQUESTED DATE AND TIME", "allowed": true }, { "response": "080", "state": "CA-S", "description": "EXTRAORDINARY CIRCUMSTANCES EXIST - NO LOCATE DUE TO WEATHER/EMERGENCY/SAFETY CONDITIONS", "allowed": true }, { "response": "998", "state": "CA-S", "description": "DIGALERT TEST CODE - NO LINES IN AREA", "allowed": false }, { "response": "999", "state": "CA-S", "description": "Member did not respond by the required time", "allowed": false } ] } --- language: "en" --- # Ticket Location Size Examples **Released**: 2/15/24 **Effective**: 2/15/24 *** ** * ** *** ## Ticket Size Examples 1. **1/2 linear mile maximum** 1. Single addresses are exempt 2. Rule #2 is exempt 3. Rule #6 is exempt ![worddav7a0fedc5d15e0d34c05c8c1cde980846.png](https://docs.digalert.org/__attachments/a_4ceb9cef143971b1a6ce582e5f3cb11de405b295f40dfdf21f53973dc5edbcec/worddav7a0fedc5d15e0d34c05c8c1cde980846.png?cb=7a0fedc5d15e0d34c05c8c1cde980846) Single Address Location Example: 1379 Pico St x/st California Ave ![worddav127b215053f698ec2c68dfc3308694df-2.png](https://docs.digalert.org/__attachments/a_69bd1cb14bf213b8121f6a0deb54e0e66753cc5f0d09bd6778c8f4312bf9111f/worddav127b215053f698ec2c68dfc3308694df-2.png?cb=127b215053f698ec2c68dfc3308694df) Multiple streets limited to ½ linear mile Location Example: Both sides of Olympic Dr from California Ave to Rimpau Ave; Both sides of Rimpau Ave from California Ave to Sunset Park; Both sides of Sunset Park From Rimpau Ave to Mount Baldy Ct; Both sides of Mount Baldy Ct from Sunset Park to Trabucco Park 2. **2 linear mile maximum on freeways or railroad tracks** ![worddav5244a7323d65de67c5436feabec022f7.png](https://docs.digalert.org/__attachments/a_7f76a069f2c5ed7d40f8cf1106c7c26bf74d7baf9226e2a8382b5456061f7f59/worddav5244a7323d65de67c5436feabec022f7.png?cb=5244a7323d65de67c5436feabec022f7) 2 linear miles of freeway Location example: S/bound side of 15 freeway from 91 Frwy to Old Temescal Rd 3. **Intermittent locations** ![worddav127b215053f698ec2c68dfc3308694df.png](https://docs.digalert.org/__attachments/a_8c838ca84c5a58946101d25e35402a22129787a63e13121880316ccbc524d9f6/worddav127b215053f698ec2c68dfc3308694df.png?cb=127b215053f698ec2c68dfc3308694df) Intermitted Locations Location Example: Intersection of Olympic Dr and California Ave; S/E corner of Olympic Dr and Rimpau Ave; Inter of Sunset Park and Rimpau Ave; inter of sunset park and Mount Baldy Ct; S/W coroner of Mount Baldy Ct and Bighorn Park; S/W coroner of Mount Baldy Ct and Santiago Park; S/W corner of Mount Baldy Ct and Trabucco Park 4. **County lines** 1. Tickets will stop at county lines no matter the distance and will be issued a ticket for each county ![worddava3bfb6761fa7858266099927b7aae91c.png](https://docs.digalert.org/__attachments/a_19b511b8146535d764d5621cc4914c95372d25396014b863b92d152649ced430/worddava3bfb6761fa7858266099927b7aae91c.png?cb=a3bfb6761fa7858266099927b7aae91c) Location Example: County = Riverside, City = Corona Inter of Aldergate Dr and Hellman Ave ![worddav09c1c6a50af03c2600f82ac3ae4ff1f7.png](https://docs.digalert.org/__attachments/a_1575fd31a3e7e7724896f1bf40d371e1cf8f6de30d969061d192ebd7177ecd27/worddav09c1c6a50af03c2600f82ac3ae4ff1f7.png?cb=09c1c6a50af03c2600f82ac3ae4ff1f7) Location Example: County = San Bernardino, City = Chino Inter of Aldergate Rd and Hellman Ave 5. **Bounded areas** 1. Cannot contain any named public roads 2. Internal roads, private roads, driveways, trails or other unnamed roads are exempt ![worddav58b006bc8a79d0e09ecedcefcc3cd726.png](https://docs.digalert.org/__attachments/a_c5ac7e11e377a072762ada9ef7671b57680bebc52c7480096817e7f09bb0296a/worddav58b006bc8a79d0e09ecedcefcc3cd726.png?cb=58b006bc8a79d0e09ecedcefcc3cd726) ½ square mile bounded area, no streets Location example: Working in bounded area n/w by January Ct if extended s/w; n/e by Somerdale if Extended s/e; s/w by approx. ½ mile s/w/of Somerdale; s/e/by approx. ½ mile s/e/of January ct. 6. **Farms** 1. Locations are limited to 1 square mile 7. **Exceptions** * Center supervisory staff may allow exemptions to any rule when warranted by the project, location and/or circumstances * All tickets that fall outside of these rules have been pre-approved by supervisory staff * Existing tickets issued prior to the effective date above are grandfathered in and will not be re-done to comply with these rules * Existing tickets where streets were not present when issued but after a map update appear are grandfathered in and will not be re-done to comply with these rules --- language: "en" --- # Ticket Location Size Requirements **Released**: 2/15/24 **Effective**: 2/15/24 *** ** * ** *** ## Maximum Ticket Sizes (Location policies) 1. **1/2 linear mile maximum** 1. Locations larger than 1/2 mile should be broken up into 1/2 mile segments at intersections when practical 2. When intersections are not practical or available, footage will be used instead. Example: Both sides of Main St from 1st St E/For 1/2 Mile 3. Distance from road into property should be specified and cannot extend so far that it continues into properties that face other roads or into other roads completely 4. Single addresses known as parcels that are bigger than 1/2 mile are exempt from this rule 5. Locations in #2 are exempt from this rule 6. Locations in #6 are exempt from this rule 2. **2 linear mile maximum on freeways or railroad tracks** 1. Freeways are defined as a road that has on and off ramps 2. Locations larger than 2 miles should be broken up into 2 mile segments at exits, milepost markers and/or cross streets when practical 3. When exits, milepost markers and/or cross streets are not practical, footage will be used. Example: Both sides of I-15 from Main St N/FOR 2 Miles 3. **Intermittent locations** 1. Intermittent locations are defined as street signs, power poles, trees, soil borings, etc 2. If possible, the number of locations should be specified on the ticket and each location be marked and numbered (in white) in the field. The number should correspond to the number of locations on the ticket. 3. Locations that are technically intermittent but are very close to each other may be considered continuous and may be marked with starting and ending points 4. **County lines** 1. Locations that enter into more than one county must be broken up into one ticket per county 5. **Bounded areas** 1. Locations are limited to 1/2 square mile 2. Locations within boundaries cannot contain any named public streets 3. Internal roads, private roadways, private driveways, trails or other unnamed roads are exempt 6. **Farms** 1. Locations are limited to one square mile 7. **Exceptions** 1. Center supervisory staff may allow exemptions to any rule when warranted by the project, location and/or circumstances 2. All tickets that fall outside of these rules have been pre-approved by supervisory staff 3. Existing tickets issued prior to the effective date above are grandfathered in and will not be re-done to comply with these rules 4. Existing tickets where streets were not present when issued but after a map update appear are grandfathered in and will not be re-done to comply with these rules --- language: "en" --- # Ticket Type Detail Matrix **Released**: 12/24/24 **Effective**: 1/1/25 *** ** * ** *** Now that you know all about ticket types from the previous page ([Ticket Types, Headers \& Explanations](https://docs.digalert.org/um/ticket-types-headers-explanations.md)), below is a matrix of what each type does and requires. | Type | Description | Increases Revision | Extends Expiration | Possible Priorities | Delivered to Member | Positive Response Required | Positive Response Due Date/Time | See Notes | |------|----------------------|--------------------|--------------------|------------------------|---------------------|----------------------------|--------------------------------------------------------------------------------------------------------------------------------------|-----------| | ACMT | Add Internal Comment | Y | N | NORM | N | N | None | | | AMND | Amendment | Y | N | RUSH, SHRT, NORM, EMER | Y | N | If before the original Work Date/Time on the ticket or Legal notice then the response due date/time remains the same. If after, none | 1 | | CNCL | Cancel | Y | N | RUSH | Y | N | None | | | DMGE | Damage | Y | N | EMER | Y | N | None | | | DSGN | Design | N | N | DSGN | N | N | None | 2 | | EXPD | Exposed | Y | N | RUSH | Y | N | None | | | NEW | New | N | Y | RUSH, SHRT, NORM, EMER | Y | Y | Legal notice or the work date and time listed on the ticket, whichever is later | | | NRSP | No Response | Y | N | RUSH | Y | Y | Legal notice | | | REMK | Re-Marks Requested | Y | Y | NORM | Y | Y | Legal notice | | | RNEW | Renewal | Y | Y | NORM | Y | N | None | | | RTRN | Return Requested | Y | N | NORM | Y | Y | Legal notice | 3 | **NOTES** 1. If an Amendment is sent BEFORE the work starts date/time the priority is carried forward from the last transmission unless the priority is being upgraded. If an Amendment is sent AFTER the work start date/time the priority is changed to NORM. 2. Design tickets are for future use only. Tickets WILL NOT be sent until a later date that has not been determined. 3. Return Requested tickets are sent when the excavator is requesting one or more members to return to the job site for any other reason than stated in other ticket types. ## Comment Area Formatting by Type (Comments are only available for secondary types) | Type | Comment formatting | |------|------------------------------------------------------------------------------------------------------------------------------------------------------| | AMND | \*\*AMENDMENT\*\* additional information from the requestor PER requestor--\[USER DateTime Stamp\] | | CNCL | \*\*CANCEL TICKET\*\* additional information from the requestor PER requestor--\[USER DateTime Stamp\] | | DMGE | \*\*DAMAGED\*\* A LINE FOR list types/members -- additional information from the requestor PER requestor--\[USER DateTime Stamp\] | | EXPD | \*\*EXPOSED\*\* AN UNKNOWN/UNMARKED LINE FOR list type/members -- additional information from the requestor PER requestor--\[USER DateTime Stamp\] | | NRSP | \*\*NO RESPONSE\*\* FROM affected members -- additional information from the requestor PER requestor--\[USER DateTime Stamp\] | | NRSP | \*\*NO RESPONSE\*\* FROM affected members -- AUTO GENERATED DUE TO LACK OF EPR RESPONSE BY LEGAL START DATE/TIME -- \[DIRECTAPI DateTime Stamp\] | | REMK | \*\*REQUEST RE-MARKS\*\* FROM list of types/members -- WORK CONTINUING any additional comments from requestor PER requestor--\[USER DateTime Stamp\] | | RNEW | \*\*RENEW TICKET\*\* WORK CONTINUING PER requestor--\[USER DateTime Stamp\] | | RTRN | \*\*RETURN REQUESTED\*\* additional information from the requestor PER requestor--\[USER DateTime Stamp\] | --- language: "en" --- # Ticket Types & Explanations **Released**: 7/7/22 **Effective**: 1/1/23 *** ** * ** *** ## Email Header \& Subject Line ![EmailHeaderSubjectLine19.3.1b.png](https://docs.digalert.org/__attachments/a_edbd1f9c7604c9226b7a4cf86355ded78afe9d80ba9075357f187e1b872cd4ba/EmailHeaderSubjectLine19.3.1b.png?cb=517410f2510de469e453fae8c2fefc27) ![19TicketHeader.png](https://docs.digalert.org/__attachments/a_e26073cf5a937cdc960ceeff8443ace71a3178821742acfd0869941c3a8e33fc/19TicketHeader.png?cb=7ca7d608e6b614cadcca9591e54db8d6) ## **Explanations:** 1. Center identification -- USAS = Underground Service Alert Southern California 2. Member Code -- sometimes referred to as a CDC code or Member ID 3. Date (or Date and Time) the ticket was completed 4. Ticket Sequence number. This is incremented from zero each day from each server (A or B). This tells you how many tickets you receive each day from each server. 5. Ticket Number 1. The server ID. This will either be A or B 2. Last 2 digits of the year the ticket was issued 3. The Julian date. The number of the day in the year the ticket was issued 4. The number of the ticket issued for that day. Incremented from 0001 on each day from each server 6. Ticket revision number. Incremented each time the ticket is sent. The Server ID will change each time depending on which server issued the revision. 7. Ticket Priority 8. Ticket Type 9. States how the member was added to the ticket. This will always be 'POLY' 10. Category of ticket. 1. LREQ - Locate Request 2. **PRJT - Project ticket (FOR FUTURE USE)** Center identification -- USAS = Underground Service Alert Southern California 3. Member Code -- sometimes referred to as a CDC code or Member ID 4. Date (or Date and Time) the ticket was completed 5. Ticket Sequence number. This is incremented from zero each day from each server (A or B). This tells you how many tickets you receive each day from each server. 6. Ticket Number 1. The server ID. This will either be A or B 2. Last 2 digits of the year the ticket was issued 3. The Julian date. The number of the day in the year the ticket was issued 4. The number of the ticket issued for that day. Incremented from 0001 on each day from each server 7. Ticket revision number. Incremented each time the ticket is sent. The Server ID will change each time depending on which server issued the revision. 8. Ticket Priority 9. Ticket Type 10. States how the member was added to the ticket. This will always be 'POLY' 11. Category of ticket. 1. LREQ - Locate Request 2. **PRJT - Project ticket (FOR FUTURE USE)** ## **Ticket Types:** * AMND -- (Amendment tickets). For all reasons other than listed below that is not requesting any members to respond, for example: correcting a ticket, adding more information, clarifying the location, etc. * CNCL -- (Cancel tickets). When the ticket is being canceled. * DMGE -- (Damaged line ticket). When the excavator states there is a damaged line and requests members to respond. * **DSGN -- (Design tickets).** **FOR FUTURE USE ONLY. These tickets will not be used until a later date that has not been determined at this time.** * EXPD - (Exposed tickets). When the excavator states there is an unmarked exposed line and requests the members to respond to be identified. * NEW -- (New tickets). New first time tickets. The revision number will always be 00A or 00B. * NRSP -- (No Response tickets). When the excavator states that any or all members failed to respond by the work date and time on the ticket. * RNEW -- (Renewal tickets). Tickets where the work is continuing past 28 calendar days. * REMK -- (Re-mark requested tickets). When the excavator requests any or all members to remark their lines. Also extends the ticket for 28 calendar days. * RTRN - (Return Trip requested). When the excavator states they need any or all members to respond to the site for any reason other than listed above. This ticket type will reset the legal notice for members required to respond back to the site. ## **Ticket Priorities:** * NORM or (2) -- 2 working days or more notice (not including the date of notification) * SHRT or (1) -- From 4 hours to 1 minute less than 2 working days' notice (not including the date of notification) * RUSH or (0) -- From 0 hours to 3 hours 59 minutes notice * **DSGN or (8) -- Dedicated priority for design tickets.** **FOR FUTURE USE ONLY. These tickets will not be used until a later date that has not been determined at this time.** * EMER or (9) -- Dedicated priority for Emergency tickets ## **Excavator Types:** * CDOT - Caltrans * CITY - City * CNTY - County * CONT - Contrator * FARM - Farmer * HOME - Home owner * MEMB - Member of DigAlert® * MILT - Military ## **Searchable Tags:** Searchable tags is the name of the field that will hold hashtags for systems to index, parse and also for members to read. If the hashtag appears, then that means whatever the hashtag says will be done on that ticket. For example, #microtrench would mean that micro trenching is taking place on this ticket. If it isn't there, then micro trenching will not be done on this ticket. This field allows the format to adapt to excavation situations in the future without needing a format change which is lengthy and costly for members. This list will be a living list and change as needed. Searchable tags will be listed with a space between each tag, for example "Searchable Tags: #microtrench #pipe_burst" Possible hashtags: * #microtrench * #PipeBurst * #night_weekend ## **Possible Email Subject Headers by Ticket Type:** ### **New (NEW):** * USAS USA01 2015/01/01 #00001A A0121231234-00A NEW NORM LREQ * USAS USA01 2015/01/01 #00001A A0121231234-00A NEW SHRT LREQ * USAS USA01 2015/01/01 #00001A A0121231234-00A NEW RUSH LREQ * USAS USA01 2015/01/01 #00001A A0121231234-00A NEW EMER LREQ ### **Renewal Only (RNEW):** * USAS USA01 2015/01/01 #00001A A0121231234-01A RNEW NORM LREQ ### **Request Remarks \& work Continuing (REMK):** * USAS USA01 2015/01/01 #00001A A0121231234-01A REMK NORM LREQ ### **Amendment (AMND):** * USAS USA01 2015/01/01 #00001A A0121231234-01A AMND NORM LREQ * USAS USA01 2015/01/01 #00001A A0121231234-01A AMND SHRT LREQ * USAS USA01 2015/01/01 #00001A A0121231234-01A AMND RUSH LREQ * USAS USA01 2015/01/01 #00001A A0121231234-01A AMND EMER LREQ ### **No Response (NRSP):** * USAS USA01 2015/01/01 #00001A A0121231234-01A NRSP RUSH LREQ * USAS USA01 2015/01/01 #00001A A0121231234-01A NRSP EMER LREQ ### Damage (DMGE): * USAS USA01 2015/01/01 #00001A A0121231234-01A DMGE EMER LREQ ### Exposed (EXPD): * USAS USA01 2015/01/01 #00001A A0121231234-01A EXPD RUSH LREQ ### Return Trip Requested (RTRN): * USAS USA01 2015/01/01 #00001A A0121231234-01A RTRN NORM LREQ ### **Cancel (CNCL):** * USAS USA01 2015/01/01 #00001A A0121231234-01A CNCL RUSH LREQ **NOTE** Be sure to read about ticket formats [Ticket Formats \& Delivery Options](https://docs.digalert.org/um/ticket-formats-delivery-options.md) --- language: "en" --- # Training & Help ## What are training options, if any? Please see our YouTube channel for videos and online instructional courses. ### YouTube ## ![](https://icons-confluence.presago.net/icon/b02890cc-e61c-4491-9c92-def101bb04cf/svg?color=%237030a0&shape=none&filled=false) **-** [DigAlert's YouTube Channel](https://www.youtube.com/channel/UCeWBjKbi2GNEtds8OWzPvAg) --- language: "en" --- # Verifying Responses via SMS/Mobile App **Released**: 1/1/18 **Effective**: 1/1/18 *** ** * ** *** ## Verifying via Mobile App 1. Click on Check Electronic Positive Response from the main app window 2. Once there enter the ticket number and click the search icon ![epr-view-app-1.png](https://docs.digalert.org/__attachments/a_826039fb08f6c677a491ce76352ffd094934f92708231b1ee4a93b4b09773cd0/epr-view-app-1.png?cb=6a2af903f18b0a6768d060dd0553128e) ![epr-view-app-2.png](https://docs.digalert.org/__attachments/a_462c3553028389b251b3b56c89bcdb64d04962b4efaa7e86b11891c06dc260af/epr-view-app-2.png?cb=4874fc73584e08c0ccc774159ea7279a) 3. Scroll to see the responses. Check/uncheck the different revisions to see the responses for each revision. ## Verifying via SMS 1. Open up your text message application and text "Presp" followed by the ticket number to DIG-ALT (or 344-258) ![epr-confirmation-sms.png](https://docs.digalert.org/__attachments/a_5522c65ea7a3de3579a39676f120e10efb2fcc2637b90c07973492df70b2fa08/epr-confirmation-sms.png?cb=1cb3d31bc1034a841152629239d67e5b) 2. You will receive the text back shown above. --- language: "en" --- # Verifying Responses via Website **Released**: 1/1/17 **Effective**: 1/1/17 *** ** * ** *** ## How to check for responses Checking Electronic Positive Responses (EPR) can be done the following ways 1. Visit [digalert.org](http://DigAlert.org) , click Web Services on the menu, then click "Check Electronic Positive Response" or if using the mobile app, click the Electronic Positive Response menu item 2. If an email address was supplied on the ticket and permission was given to send messages, an email will be sent at the time EPRs are due with all available responses. Additional emails will be sent each time a member submits a new response or updates a response after the due date/time. 3. If a cell phone number was supplied on the ticket and permission was given to send text messages, a text message will be sent at the time EPRs are due with all available responses. Additional text messages will be sent each time a member submits a new response or updates a response after the due date/time. ## Step by step details To check EPRs via [digalert.org](http://DigAlert.org) or the mobile apps, follow options 1 or 2 from above and the main screen will appear shown below. ![EPR-2.5.png](https://docs.digalert.org/__attachments/a_5116c07b8b4ab41b1a590bdd624d13dd25a3592290b9bd4eba273bc12799b374/EPR-2.5.png) 1. Enter the complete ticket number, then click the search icon to search for your ticket. 2. Some brief information from the ticket will display to ensure you are viewing the correct ticket number. If the ticket number is incorrect, simply repeat step 1. ![EPR-3.png](https://docs.digalert.org/__attachments/a_a8b95f819763654e1790c2fa7caf0e42d8448aa89e856b13973e7cc26d9ae102/EPR-3.png) 3. Once a ticket has been inquired and displayed, responses for the most current revision will be displayed automatically in the timeline, if any were made. 4. If other revisions of your ticket exist, you may select the checkbox to the left to show or hide positive responses for the selected revision. ![EPR-5.png](https://docs.digalert.org/__attachments/a_44d80c1a603269890ae96aaea922af158bad976b84ade165e0707a7f36222f4a/EPR-5.png) EPRs will show Comments and URL for additional information if provided by that member when they respond --- language: "en" --- # Policies & Procedures ## Documentation * ### [About DigAlert Documentation Center](https://docs.digalert.org/pp/about-digalert-documentation-center.md) * ### [2026 Changes](https://docs.digalert.org/pp/2026-changes.md) * ### [Billing Methodology Effective July 1, 2026](https://docs.digalert.org/pp/billing-methodology-effective-july-1-2026.md) * ### [2026 Rates](https://docs.digalert.org/pp/2026-rates.md) * ### [2026 Holiday Closures](https://docs.digalert.org/pp/2026-holiday-closures.md) * ### [2025 Changes](https://docs.digalert.org/pp/2025-changes.md) * ### [Approved Abbreviations](https://docs.digalert.org/pp/approved-abbreviations.md) * ### [Ticket Location Size Requirements](https://docs.digalert.org/pp/ticket-location-size-requirements.md) * ### [Ticket Location Size Examples](https://docs.digalert.org/pp/ticket-location-size-examples.md) * ### [Changing Information on Tickets](https://docs.digalert.org/pp/changing-information-on-tickets.md) * ### [No Response Tickets](https://docs.digalert.org/pp/no-response-tickets.md) * ### [California Government Code 4216 - "The call before you dig law"](https://docs.digalert.org/pp/california-government-code-4216-the-call-before-yo.md) --- language: "en" --- # 2025 Changes ## Law Changes - California Government code section 4216 has been changed and will take effect on January 1st, 2025. Listed below are some of the important changes, but the complete law can be found by visiting [www.digalert.org/calaw](http://www.digalert.org/calaw). * 4216 (e) "Electronic positive response" means an electronic response from an operator to the regional notification center providing the status of an operator's obligations under subparagraph (A) of paragraph (1) of subdivision (a) of Section 4216.3. * 4216.2 (g) (1) Unless an emergency exists, an excavator shall not begin excavation until all operators of subsurface installations that are listed on the ticket have fulfilled their obligations under subparagraph (A) of paragraph (1) of subdivision (a) of Section 4216.3 and until the completion of any onsite meeting, if required by subdivision (c). * (2) The excavator may begin excavation before the legal excavation start date and time if all of the conditions in paragraph (1) have been satisfied. * 4216.2 (i) If a ticket obtained by an excavator expires but work is ongoing, the excavator shall immediately cease excavation, contact the regional notification center and get a new ticket pursuant to subdivision (b), and may not resume excavation until the conditions in subdivision (g) have been satisfied. * 4216.4 (2) (A) An excavator may use a vacuum excavation device to expose subsurface installations within the tolerance zone if the excavator has informed the regional notification center of their intent to use a vacuum excavation device when obtaining a ticket and the operator has agreed to the use of a vacuum excavation device. An operator not agreeing to the use of a vacuum excavation device shall include that information on their electronic positive response. * 4216.4 (b) If the exact location of the subsurface installation cannot be determined by hand excavating in accordance with subdivision (a), the excavator shall request the operator to provide additional information to the excavator, to the extent that information is available to the operator, to enable the excavator to determine the exact location of the installation. The operator shall provide relevant existing additional information to the excavator within one working day. If the excavator has questions about the markings that an operator has placed, the excavator may contact the notification center to send a request to have the operator contact the excavator directly. The regional notification center shall provide the excavator with the contact telephone number of the subsurface installation operator. (c) (1) An excavator shall immediately call 911 emergency services upon discovering or causing damage to one of the following: * (A) A gas or hazardous liquid pipeline subsurface installation in which the damage results in the escape of any flammable, toxic, or corrosive gas or liquid. * (B) A high priority subsurface installation of any kind, except that the excavator does not need to call 911 if all of the following conditions are satisfied: * (i) The excavator is the operator of the high priority subsurface installation. * (ii) The damage was discovered by the operator during operations and maintenance activities. * (iii) The damage does not meet the circumstances in subparagraph (A). * (2) An excavator shall immediately notify the operator upon discovering or causing damage to a subsurface installation, including all breaks, leaks, nicks, dents, gouges, grooves, or other damage to subsurface installation lines, conduits, coatings, or cathodic protection. In the event of damage to a subsurface excavation described in paragraph (1), the excavator must contact the operator immediately after calling 911 emergency services. The excavator may contact the regional notification center to obtain the contact information of the subsurface installation operator. If the operator is unknown and the damage or discovery of damage occurs outside the working hours of the regional notification center, the excavator may follow the instructions provided by the regional notification center through its internet website or the telephone line recorded message. * (3) Except as provided in subparagraph (A), an excavator shall notify the regional notification center within 48 hours of discovering or causing damage to any subsurface installation pursuant to paragraph (2). * (A) An excavator does not need to notify the regional notification center of damage discovered by the excavator if all of the following conditions are satisfied: * (i) The excavator is the operator of the subsurface installation. * (ii) The damage was discovered by the operator during operations and maintenance activities. * (iii) The damage does not meet the circumstances in subparagraph (A) of paragraph (1). ## **Electronic Positive Response (EPR) Code Changes -** Electronic positive response codes are changing to better describe and streamline responses for excavators. A complete list of changes can be found at [EPR Response Codes 2025](https://docs.digalert.org/um/response-codes-2025.md). ## **No Response Tickets -** * No response tickets will change to require an EPR by the legal date/time * No response tickets will only be sent to members requested, not necessarily all members on the ticket * No response tickets will now automatically be sent to members that have not responded by the legal date/time on the ticket If you have any question about these changes, please contact our Member Services department. --- language: "en" --- # 2026 Changes ## **Damage, Exposed \& Return Trip Tickets (implementation date to be determined) -** Coming in 2026 (at least a 3 month notice will be given), Damage, Exposed and Return Trip ticket types will now be sent only to the members that are selected and not to all members on the ticket unless the excavator cannot identify the owner of the line. If the excavator is unable to identify the owner of the line, the ticket will be sent to all members on the ticket. ## **Re-mark Tickets -** At the same time frame TBD above, Re-mark tickets will no longer extend the life of the ticket. Instead, when requesting a Re-mark on a ticket, the ticket will first be sent to all members as a Renewal extending the life the of the ticket for an additional 28 calendar days. Then the system will automatically send the request for Re-marks to only the members selected by the excavator who are needed to re-mark their facilities. This does not change the fact that Re-mark tickets require an Electronic Positive Response (EPR) by the legal date and time for the members receiving the Re-mark. Also, for those members that choose to respond to Renewals, this change will not affect your ability to respond to the renewal whether or not you are asked to re-mark your lines. The EPR system is revision specific, so make sure when responding to respond to the revision. ## **No Response Tickets -** No Response tickets will no longer be sent manually. Please read [No Response Tickets](https://docs.digalert.org/pp/no-response-tickets.md) for more information. ## **Rates Change for Members -** The Board of Directors approved a rate change for members to go into effect January 1st, 2026. For more information please read [2026 Rates](https://docs.digalert.org/pp/2026-rates.md) **Update: 2/6/2026** The Board of Directors have approved a billing methodology change effective July 1st, 2026. For more information, please read [Billing Methodology Effective July 1, 2026](https://docs.digalert.org/pp/billing-methodology-effective-july-1-2026.md) --- language: "en" --- # 2026 Holiday Closures Underground Service Alert of Southern California (DigAlert®) will be closed the following days in observance of the State and/or Federal Holidays. * January 1st - New Years Day * January 19th - Martin Luther King Jr. Day * February 16th - President's Day * March 31st - Cesar Chavez Day * May 25th - Memorial Day * June 19th - Juneteenth * July 3rd - Independence Day (Observed) * September 7th - Labor Day * October 12th - Indigenous People's Day * November 11th - Veteran's Day * November 26th - Thanksgiving * November 27th - Day after Thanksgiving * December 25th - Christmas Day In addition to these holidays, DigAlert® will close at 3:00 PM on the following days; * December 24th - Christmas Eve * December 31st - New Years Eve --- language: "en" --- # 2026 Rates ## **EXHIBIT I** **Dues Schedule** **Effective July 1, 2026** I. Principal and Associate members will pay a percentage of the previous month's budgeted costs. The percentage will be determined by the number of new DigAlert^®^ tickets received in the previous month in relation to the total new DigAlert^®^tickets sent to all members in the previous month. Amounts will be rounded to the nearest $0.05. II. Principal members may be assessed from time to time an amount as determined by the Board to maintain the level of working capital necessary to ensure financial stability. Such assessment shall be based on the ratio which the number of miles of underground facilities owned or operated by that member bears to the total miles owned or operated by all Principal members within the area served by the Corporation. III. In addition to new ticket charges, all billed members will be charged $10 per month according to the number of member codes listed for each billed member according to the chart below: |---------------------------|---------------| | **Billed Member Codes** | **Rate** | | 1 -- 5 member codes | $10 per month | | 6 -- 10 member codes | $20 per month | | 11 -- 15 member codes | $30 per month | | 16 -- 20 member codes | $40 per month | | More than 20 member codes | $50 per month | *** ** * ** *** ## **EXHIBIT II** **Archive Record Fees** **Effective January 1, 2026** I. Member |-------------------------|---------------------------------------| | 20 Requests in a month | Free (does not include 5 year search) | | 21+ Requests in a month | $15.00 each addition request | | 5 year lookup | $50 each request | ++***\*\* Request is a ticket or conversation -- example 10 tickets with 10 conversations equals 20 requests \*\****++ II. Non Member |------------------------------|-----------------------------| | Each DigAlert® Ticket | $50 | | No DigAlert® Ticket Provided | $50 per each year requested | | Copy of conversation | $50 per location requested | --- language: "en" --- # About DigAlert Documentation Center ## Welcome to the DigAlert® documentation site. This site contains documentation on DigAlert® services available to the public. DigAlert® offers several services to utility members, professional excavators, home owners, contractors and designers. While this site does contain a lot of information, it is not geared toward education or general knowledge. Instead it is written for those needing help with specific services for example; ticket headers, ticket formats, help on setting up or updating information, how to use mobile apps, web portals and other technical documentation. For general information about DigAlert® or the California Law please visit → [www.digalert.org.](http://www.digalert.org./) --- language: "en" --- # Approved Abbreviations **Released**: 2/15/23 **Effective**: 2/15/23 *** ** * ** *** This list is all approved abbreviations that can be found on DigAlert® Tickets. Any abbreviation used on the map is allowed only when referring to that street. ## **All abbreviations street names, prefixes, suffixes and direction shown on the map MUST be used in the street and cross street fields.** | **Color** | **Meaning** | |-----------|----------------------------------------------| | | Required to use | | | Must be spelled out completely the first use | | **Abbreviation** | **Description** | |------------------|------------------------------| | ABDN | ABANDON | | APPROX | APPROXIMATELY | | ASAP | AS SOON AS POSSIBLE | | AVD | AVENIDA | | AVE | AVENUE | | AVE/OF | AVENUE OF | | AVE/OF THE | AVENUE OF THE | | B-YARD | BACKYARD | | BLVD | BOULEVARD | | BTWN | BETWEEN | | C/L | CENTERLINE | | C/OF | CITY OF | | CATV | CABLE TELEVISION | | CIR | CIRCLE | | CMTO | CAMINITO | | CO/AREA | COUNTY AREA | | CO/OF | COUNTY OF | | COMM | COMMUNICATION | | CONST | CONSTRUCTION | | CONT | CONTINUE | | CONTR | CONTRACTOR | | COR | CORNER | | COR/OF | CORNER OF | | CORP | CORPORATION | | CT | COURT | | CTE | CORTE | | CV | COVE | | DEPT | DEPARTMENT | | DEV | DEVELOPMENT | | DOT | DEPARTMENT OF TRANSPORTATION | | DR | DRIVE | | E/OF | EAST OF | | E/ON | EAST ON | | E/SIDE | EAST SIDE | | E/TO | EAST TO | | ELEC | ELECTRIC | | ENGR | ENGINEER | | EST | ESTIMATE | | ETA | ESTIMATED TIME OF ARRIVAL | | EXCAV | EXCAVATING | | EXCAV | EXCAVATION | | EXCAV | EXCAVATED | | EXT | EXTENDED | | EXWY | EXPRESSWAY | | F-YARD | FRONT YARD | | FRM | FROM | | FRWY | FREEWAY | | FRY | FERRY | | FT | FEET (OR FOOT) | | H/O | HOMEOWNER | | HTS | HEIGHTS | | HWY | HIGHWAY | | INSTALL | INSTALL | | INSTALL | INSTALLING | | INSTALL | INSTALLED | | INSTALL | INSTALLATION | | INTER | INTERSECTION | | INTER/OF | INTERSECTION OF | | IRRIG | IRRIGATION | | JCT | JUNCTION | | LN | LANE | | LOC | LOCATION | | LOC | LOCATED | | LOT # | LOT NUMBER | | MAINT | MAINTENANCE | | MAINT | MAINTENED | | MHP | MOBILE HOME PARK | | MT | MOUNT | | MTN | MOUNTAIN | | MTWY | MOTORWAY | | N/E | NORTHEAST | | N/OF | NORTH OF | | N/ON | NORTH ON | | N/SIDE | NORTH SIDE | | N/TO | NORTH TO | | N/W | NORTHWEST | | NATL | NATIONAL | | OWN | OWNER | | OWN/BLDR | OWNER BUILDER | | P/L | PROPERTY LINE | | PKWY | PARKWAY | | PL | PLACE | | PLZ | PLAZA | | PROP | PROPERTY | | PROP/O | PROPERTY OWNER | | PT | POINT | | PWR | POWER | | R/R TRACKS | RAILROAD TRACKS | | RD | ROAD | | RDG | RIDGE | | RDWY | ROADWAY | | RELOC | RELOCATE | | REM | REMOVE | | REPL | REPLACE | | RTE | ROUTE | | S/E | SOUTHEAST | | S/OF | SOUTH OF | | S/ON | SOUTH ON | | S/SIDE | SOUTH SIDE | | S/TO | SOUTH TO | | S/W | SOUTHWEST | | SERV | SERVICE | | SP | SPACE | | SQ | SQUARE | | ST | STREET | | ST/OF | STREET OF | | ST/OF THE | STREET OF THE | | TEL | TELEPHONE | | TEMP | TEMPORARY | | TER | TERRACE | | TKTR | TRUCK TRAIL | | TR | TRAIL | | TR # | TRACT NUMBER | | TRAF | TRAFFIC | | UTIL | UTILITY | | UTIL | UTILITIES | | VLY | VALLEY | | VW | VIEW | | W/OF | WEST OF | | W/ON | WEST ON | | W/SIDE | WEST SIDE | | W/TO | WEST TO | | WAY | WAY | | WTR | WATER | | X/ST | CROSS STREET | --- language: "en" --- # Billing Methodology Effective July 1, 2026 All members will pay a percentage of the previous month's budgeted costs. The percentage will be determined by the number of **new** DigAlert^®^ tickets received in the previous month in relation to the total **new** DigAlert^®^ tickets sent to all members in the previous month. Example: Monthly Budgeted Cost = $750,000 Monthly New Tickets sent to all Members = 270,312 ABCWater New Tickets = 60 ABCWater percentage of total new tickets = 0.02219% $750,000 \* .02219% = $166.45 \*\* Amounts will be rounded to the nearest $0.05 \*\* In addition to **new** DigAlert^®^ tickets, all billed members will be charged a monthly database maintenance fee based on the number of member codes listed for each billed member according to the chart below: | **Billed Member Codes** | **Rate** | |---------------------------|---------------| | 1 -- 5 member codes | $10 per month | | 6 -- 10 member codes | $20 per month | | 11 -- 15 member codes | $30 per month | | 16 -- 20 member codes | $40 per month | | More than 20 member codes | $50 per month | --- language: "en" --- # California Government Code 4216 - "The call before you dig law" ## ![https://icons-confluence.presago.net/icon/f3d00a7a-ee8b-4408-94ac-6f7610d025f5/svg?color=%237030a0&shape=none&filled=false](https://icons-confluence.presago.net/icon/f3d00a7a-ee8b-4408-94ac-6f7610d025f5/svg?color=%237030a0&shape=none&filled=false) **-** [**View the CA Government Code 4216**](https://leginfo.legislature.ca.gov/faces/codes_displayText.xhtml?lawCode=GOV&division=5.&title=1.&part=&chapter=3.1.&article=2.) ## ![https://icons-confluence.presago.net/icon/9d78fea6-d1e9-473e-97da-fd618f9d6e22/svg?color=%237030a0&shape=none&filled=false](https://icons-confluence.presago.net/icon/9d78fea6-d1e9-473e-97da-fd618f9d6e22/svg?color=%237030a0&shape=none&filled=false) **-** [**View the CA Code of Regulations**](https://govt.westlaw.com/calregs/Browse/Home/California/CaliforniaCodeofRegulations?guid=I2EFBE0205BE511EC98C8000D3A7C4BC3&originationContext=documenttoc&transitionType=Default&contextData=(sc.Default)&bhcp=1) ## ![https://icons-confluence.presago.net/icon/4386b315-082d-43cb-8242-296c86ddee8e/svg?color=%237030a0&shape=none&filled=false](https://icons-confluence.presago.net/icon/4386b315-082d-43cb-8242-296c86ddee8e/svg?color=%237030a0&shape=none&filled=false) **-** [**Report a possible violation or damage**](https://www.contact811.org) --- language: "en" --- # Changing Information on Tickets **Released:** 10/30/25 **Effective:** 11/07/25 *** ** * ** *** When using Amendment in DigAlert Direct® or when calling in a change to a location. Only the below information can be changed on the ticket. If the change being requested is not on the list below, a new ticket will be required. This is for safety and Electronic Positive Response requirements. ![:warning:](https://docs.digalert.org/__attachments/a_ac3fbe36eb2c11cbe18b4ad4b9e38ca21638db2c9ac6471908530df63480f479/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **NOTE** **Once the ticket is issued the start date and time** ++**can't**++ **be changed. If it needs to be changed, a NEW ticket must be created and the old ticket must be canceled.** ![:cross_mark:](https://docs.digalert.org/__attachments/a_487bccba7407b9c6208e2dc08b91386ba6a18599e9e94041090eb1b2ef66470d/atlassian-cross_mark?cb=a9c671cfc7809253be52d640dbbf1019) If changing a ticket to an emergency, a **NEW** emergency ticket **must** be created for **ONLY** the area that is an emergency. Sometimes this area will be the same as the original ticket, sometimes the area may be less than the original area on the existing ticket. | **What can be changes on a ticket once issued** | **Available to change through DigAlert Direct®** | |---------------------------------------------------------------|--------------------------------------------------| | Caller phone | | | Company name (BEFORE START DATE/TIME ONLY) | | | Company address | | | Company city | | | Company state | | | Company zip code | | | Caller email | | | Caller email confirmation | | | Caller cell | | | Caller txt confirmation | | | Site contact name | ✅ | | Site contact phone | ✅ | | Site contact email | ✅ | | Site contact email confirmation | ✅ | | Site contact txt confirmation | ✅ | | Delineation method (A RETURN TRIP ticket ONLY, not Amendment) | | | Permit number | | | Work order/job | | | Direct notify | | | Anything directed to you from DigAlert® personnel | | **\* DigAlert® personnel direction is on a case by case basis and should not be confused with policy unless expressly stated.** --- language: "en" --- # No Response Tickets **Released**: 11/01/25 **Effective**: 01/01/26 *** ** * ** *** ## Auto No Response History Effective January 1st 2025, Underground Service Alert of Southern California (DigAlert®) started sending automatic No Response tickets to members who failed to respond to the Electronic Positive Response (EPR) system by the required date and time on behalf of the excavator. These No Response tickets are sent to the members until they respond to the EPR system as required by CA GC 4216 every 2 working days, not including the date of notification. DigAlert® has allowed excavators to submit No Response tickets manually as well since this change took place. ### Manual No Response Changes 1/1/2026 Effective **January 1st, 2026**, the manual No Response process will no longer be allowed since No Responses are sent automatically at the legal date/time of the ticket on behalf of the excavator. The excavator no longer needs to worry about these as the system does it for them automatically. ### What does this mean? This change means that as of January 1st, 2026, you will no longer be able to submit a No Response ticket outside of the system automatically doing it for you. ### What if I disagree with the response the member has given? If the member posts an EPR that you disagree with and need them back out for any reason there are a few steps to take. First, submit the ticket as a **Return Trip** and state in the comments, the reason you are asking the member to come back out and the facts you believe the EPR provided is not accurate. If you are not in need of the members to respond back out to the location, then submit the ticket as an **Amendment** with the same type of comments described previously. Remember, this is a business and a legal document so there is no need for any hostility or unprofessional comments to be listed on a ticket, make sure the comments are professional. Second, you can **file a complaint** with the Underground Safe Excavation Board by visiting the following link → . Be sure to complete the form in its entirety so the investigators can get a complete understanding of the complaint. ### I need to call someone, who do I call? If you need to call someone, look at your ticket confirmation for the phone number for the member you are wishing to contact. These are the most up to date phone numbers DigAlert® has available in the system. If you do not have a copy of your ticket, you can go here → and look up the contact information for the members notified on your ticket. ### Recap Instead of sending a No Response for a member that has already supplied a response to the EPR system, send the ticket either as a; * Return Trip when asking for a member(s) to respond back out for any reason (other than for Re-marks, Damage or Exposed lines), be sure to list why in the comments * Amendment when just passing on information to the member without asking them to respond to the site. ![:warning:](https://docs.digalert.org/__attachments/a_ac3fbe36eb2c11cbe18b4ad4b9e38ca21638db2c9ac6471908530df63480f479/atlassian-warning?cb=14432459925d605e05cae2605cdfe666) **CAUTION** Amendment ticket **DO NOT** require members to respond to the job site or the EPR system. Never use this ticket type asking them to visit the site. --- language: "en" --- # Ticket Location Size Examples **Released**: 2/15/24 **Effective**: 2/15/24 *** ** * ** *** ## Ticket Size Examples 1. **1/2 linear mile maximum** 1. Single addresses are exempt 2. Rule #2 is exempt 3. Rule #6 is exempt ![worddav7a0fedc5d15e0d34c05c8c1cde980846.png](https://docs.digalert.org/__attachments/a_4ceb9cef143971b1a6ce582e5f3cb11de405b295f40dfdf21f53973dc5edbcec/worddav7a0fedc5d15e0d34c05c8c1cde980846.png?cb=7a0fedc5d15e0d34c05c8c1cde980846) Single Address Location Example: 1379 Pico St x/st California Ave ![worddav127b215053f698ec2c68dfc3308694df-2.png](https://docs.digalert.org/__attachments/a_69bd1cb14bf213b8121f6a0deb54e0e66753cc5f0d09bd6778c8f4312bf9111f/worddav127b215053f698ec2c68dfc3308694df-2.png?cb=127b215053f698ec2c68dfc3308694df) Multiple streets limited to ½ linear mile Location Example: Both sides of Olympic Dr from California Ave to Rimpau Ave; Both sides of Rimpau Ave from California Ave to Sunset Park; Both sides of Sunset Park From Rimpau Ave to Mount Baldy Ct; Both sides of Mount Baldy Ct from Sunset Park to Trabucco Park 2. **2 linear mile maximum on freeways or railroad tracks** ![worddav5244a7323d65de67c5436feabec022f7.png](https://docs.digalert.org/__attachments/a_7f76a069f2c5ed7d40f8cf1106c7c26bf74d7baf9226e2a8382b5456061f7f59/worddav5244a7323d65de67c5436feabec022f7.png?cb=5244a7323d65de67c5436feabec022f7) 2 linear miles of freeway Location example: S/bound side of 15 freeway from 91 Frwy to Old Temescal Rd 3. **Intermittent locations** ![worddav127b215053f698ec2c68dfc3308694df.png](https://docs.digalert.org/__attachments/a_8c838ca84c5a58946101d25e35402a22129787a63e13121880316ccbc524d9f6/worddav127b215053f698ec2c68dfc3308694df.png?cb=127b215053f698ec2c68dfc3308694df) Intermitted Locations Location Example: Intersection of Olympic Dr and California Ave; S/E corner of Olympic Dr and Rimpau Ave; Inter of Sunset Park and Rimpau Ave; inter of sunset park and Mount Baldy Ct; S/W coroner of Mount Baldy Ct and Bighorn Park; S/W coroner of Mount Baldy Ct and Santiago Park; S/W corner of Mount Baldy Ct and Trabucco Park 4. **County lines** 1. Tickets will stop at county lines no matter the distance and will be issued a ticket for each county ![worddava3bfb6761fa7858266099927b7aae91c.png](https://docs.digalert.org/__attachments/a_19b511b8146535d764d5621cc4914c95372d25396014b863b92d152649ced430/worddava3bfb6761fa7858266099927b7aae91c.png?cb=a3bfb6761fa7858266099927b7aae91c) Location Example: County = Riverside, City = Corona Inter of Aldergate Dr and Hellman Ave ![worddav09c1c6a50af03c2600f82ac3ae4ff1f7.png](https://docs.digalert.org/__attachments/a_1575fd31a3e7e7724896f1bf40d371e1cf8f6de30d969061d192ebd7177ecd27/worddav09c1c6a50af03c2600f82ac3ae4ff1f7.png?cb=09c1c6a50af03c2600f82ac3ae4ff1f7) Location Example: County = San Bernardino, City = Chino Inter of Aldergate Rd and Hellman Ave 5. **Bounded areas** 1. Cannot contain any named public roads 2. Internal roads, private roads, driveways, trails or other unnamed roads are exempt ![worddav58b006bc8a79d0e09ecedcefcc3cd726.png](https://docs.digalert.org/__attachments/a_c5ac7e11e377a072762ada9ef7671b57680bebc52c7480096817e7f09bb0296a/worddav58b006bc8a79d0e09ecedcefcc3cd726.png?cb=58b006bc8a79d0e09ecedcefcc3cd726) ½ square mile bounded area, no streets Location example: Working in bounded area n/w by January Ct if extended s/w; n/e by Somerdale if Extended s/e; s/w by approx. ½ mile s/w/of Somerdale; s/e/by approx. ½ mile s/e/of January ct. 6. **Farms** 1. Locations are limited to 1 square mile 7. **Exceptions** * Center supervisory staff may allow exemptions to any rule when warranted by the project, location and/or circumstances * All tickets that fall outside of these rules have been pre-approved by supervisory staff * Existing tickets issued prior to the effective date above are grandfathered in and will not be re-done to comply with these rules * Existing tickets where streets were not present when issued but after a map update appear are grandfathered in and will not be re-done to comply with these rules [Next Page](https://docs.digalert.org/llms-full.txt/1)