131.1 Design Exception Process - Revision history

Hoskir: small format change

2026-07-15T14:48:40Z

small format change

← Older revision		Revision as of 09:48, 15 July 2026
Line 1:		Line 1:
	<div style="float: right; margin-top: 5px; margin-left: 15px; margin-bottom: 15px;">__TOC__</div>		<div style="float: right; margin-top: 5px; margin-left: 15px; margin-bottom: 15px;">__TOC__</div>

	{\| style="margin-left:15px; border:1px solid #a9a9a9; background:#f5f5f5" width="275px" align="right"		{\| style="margin-left:15px; margin-top: 5px; border:1px solid #a9a9a9; background:#f5f5f5" width="275px" align="right"
	\|-		\|-
	\| style="text-align:center;" \| '''<u>Forms</u>'''		\| style="text-align:center;" \| '''<u>Forms</u>'''

Hoskir: eProjects is now MoProjects

2026-07-14T14:11:35Z

eProjects is now MoProjects

← Older revision		Revision as of 09:11, 14 July 2026
Line 83:		Line 83:
	Project managers (consultant, transportation or structural) and their design staff should recognize the importance of an open and transparent decision making process while considering the suitability and appropriateness of a given design element that is not consistent with current policies. Since engineering policy is established through a collaborative effort, it is critical to engage all appropriate staff when making the decision not to meet policy. While completing the form, communication with the appropriate staff, including the DLE, a representative of any affected MoDOT division and FHWA (when applicable), is critical to ensure efficient and effective review and approval. For efficient processing and to avoid delays, this communication should occur prior to the formal submittal. Depending upon the item being excepted and the type of project, the appropriate review staff and signatory parties will vary.		Project managers (consultant, transportation or structural) and their design staff should recognize the importance of an open and transparent decision making process while considering the suitability and appropriateness of a given design element that is not consistent with current policies. Since engineering policy is established through a collaborative effort, it is critical to engage all appropriate staff when making the decision not to meet policy. While completing the form, communication with the appropriate staff, including the DLE, a representative of any affected MoDOT division and FHWA (when applicable), is critical to ensure efficient and effective review and approval. For efficient processing and to avoid delays, this communication should occur prior to the formal submittal. Depending upon the item being excepted and the type of project, the appropriate review staff and signatory parties will vary.

	Central Office staff should be consulted and provide review of the draft design exception prior to district approval. Design exceptions involving safety related items (see [[#131.1.5_Required_Information\|EPG 131.1.5]]) should be reviewed by the District Traffic Engineer and/or Highway Safety and Traffic Division prior to district approval. For design-bid-build projects, a final copy of the design exception is saved in [~~http~~://~~eprojects~~/~~SitePages~~/~~Home.aspx eProjects~~] using the appropriate content type: DE Design Exceptions, with all necessary checkboxes for Type of Exception checked. Staff should include any pertinent information in the Comments Section within the ~~eProjects~~ metadata. For design-build projects, approved design exceptions incorporated into the project are saved in the design-build projects SharePoint site in an Approved Design Exceptions folder.		Central Office staff should be consulted and provide review of the draft design exception prior to district approval. Design exceptions involving safety related items (see [[#131.1.5_Required_Information\|EPG 131.1.5]]) should be reviewed by the District Traffic Engineer and/or Highway Safety and Traffic Division prior to district approval. For design-bid-build projects, a final copy of the design exception is saved in [https://modotweb.modot.mo.gov/MoProjects/Account/Login MoProjects] using the appropriate content type: DE Design Exceptions, with all necessary checkboxes for Type of Exception checked. Staff should include any pertinent information in the Comments Section within the MoProjects metadata. For design-build projects, approved design exceptions incorporated into the project are saved in the design-build projects SharePoint site in an Approved Design Exceptions folder.

	PODI design exceptions are processed through the DLE for the State Design Engineer and FHWA signatures of approval. The DLE provides the electronic copy of the fully approved design exception back to the TPM for placement in ~~eProjects~~.		PODI design exceptions are processed through the DLE for the State Design Engineer and FHWA signatures of approval. The DLE provides the electronic copy of the fully approved design exception back to the TPM for placement in MoProjects.

	FHWA reserves the right to audit the design exceptions of any federal aid project regardless of level of oversight.		FHWA reserves the right to audit the design exceptions of any federal aid project regardless of level of oversight.
Line 120:		Line 120:
	Process 10 - DLE obtains FHWA signature - Go to Process 10		Process 10 - DLE obtains FHWA signature - Go to Process 10
	Process 11 - DLE returns DE to TPM - Go to End		Process 11 - DLE returns DE to TPM - Go to End
	End - TPM stores DE in ~~eProjects~~		End - TPM stores DE in MoProjects
	]]		]]

Line 154:		Line 154:
	Process 12 - DLE obtains FHWA signature - Go to Process 13		Process 12 - DLE obtains FHWA signature - Go to Process 13
	Process 13 - DLE returns DE to TPM - Go to End		Process 13 - DLE returns DE to TPM - Go to End
	End - TPM stores DE in ~~eProjects~~		End - TPM stores DE in MoProjects
	]]		]]

Hoskir: updated per RR4213

2026-07-09T18:25:15Z

updated per RR4213

Show changes

Hoskir: updated links

2023-09-18T17:36:54Z

updated links

← Older revision		Revision as of 12:36, 18 September 2023
Line 202:		Line 202:
	:2 The Design Liaison Engineer emails the Bridge Inventory Analysts and requests the Structure NBI number for box 2 on the Vertical Clearance Design Exception Coordination with SDDCTEA Form.		:2 The Design Liaison Engineer emails the Bridge Inventory Analysts and requests the Structure NBI number for box 2 on the Vertical Clearance Design Exception Coordination with SDDCTEA Form.

	:3. Concurrent with the submission or routing of the Design Exception, the Design Liaison Engineer submits the form to the SDDCTEA and copies FHWA. This may be done electronically using the contact information on the [~~[media~~:131.~~1 Vertical Clearance Coord Form Jul 2018~~.pdf\|Vertical Clearance Design Exception Coordination with SDDCTEA]].		:3. Concurrent with the submission or routing of the Design Exception, the Design Liaison Engineer submits the form to the SDDCTEA and copies FHWA. This may be done electronically using the contact information on the [https://epg.modot.org/forms/general_files/BR/131.1_Vertical_Clearance_Coord_Form.pdf Vertical Clearance Design Exception Coordination with SDDCTEA].

	:4. A response from SDDCTEA should occur within 10 working days following receipt of the coordination request. Receipt of the request can be verified with SDDCTEA via telephone or fax. If there is no response after 10 working days following receipt, it can be determined that SDDCTEA does not have any concerns about the proposed exception.		:4. A response from SDDCTEA should occur within 10 working days following receipt of the coordination request. Receipt of the request can be verified with SDDCTEA via telephone or fax. If there is no response after 10 working days following receipt, it can be determined that SDDCTEA does not have any concerns about the proposed exception.

Hoskir: updated links

2023-09-18T16:18:25Z

updated links

← Older revision		Revision as of 11:18, 18 September 2023
Line 3:		Line 3:
	\|align-"center"\|'''Forms'''		\|align-"center"\|'''Forms'''
	\|-style="background:#f5f5f5"		\|-style="background:#f5f5f5"
	\|valign="top" align="center"\| [~~[media~~:131.~~1 Design Exception 2020~~.docx\|Design Exception Information Form]]		\|valign="top" align="center"\| [https://epg.modot.org/forms/general_files/BR/131.1_Design_Exception.docx Design Exception Information Form]
	\|-		\|-
	\|[~~[media~~:131.~~1 Vertical Clearance Coord Form Jul 2018~~.pdf\|Vertical Clearance Design Exception Coordination with SDDCTEA]]		\|[https://epg.modot.org/forms/general_files/BR/131.1_Vertical_Clearance_Coord_Form.pdf Vertical Clearance Design Exception Coordination with SDDCTEA]
	\|}		\|}

Line 86:		Line 86:
	Requests for design exceptions are submitted when the need first arises; however, they may be submitted at any time and specifically along with the [[:Category:128 Conceptual Studies\|conceptual study]], [[:Category:235 Preliminary Plans\|preliminary plan]], right of way certification, or plans, specifications, and estimate (PS&E). In general, it is best to identify and consider the design exception as early as practical in the design process.		Requests for design exceptions are submitted when the need first arises; however, they may be submitted at any time and specifically along with the [[:Category:128 Conceptual Studies\|conceptual study]], [[:Category:235 Preliminary Plans\|preliminary plan]], right of way certification, or plans, specifications, and estimate (PS&E). In general, it is best to identify and consider the design exception as early as practical in the design process.

	When the need for a design exception has been identified, the project manager, Structural Project Manager or consultant representative is responsible for completing the standard [~~[media~~:131.~~1 Design Exception 2020~~.docx\|Design Exception Information Form]]. The form must include a detailed description of the rationale for the change and the appropriate supporting documentation to satisfactorily justify the decision and document any mitigation efforts associated with varying from the engineering policy. Examples of approved Design Exceptions can be found here<provide link>. (Please note that previous approval of an item should not be considered approval of the item on any future project. Approval for future projects must be sought on a case-by-case basis.)		When the need for a design exception has been identified, the project manager, Structural Project Manager or consultant representative is responsible for completing the standard [https://epg.modot.org/forms/general_files/BR/131.1_Design_Exception.docx Design Exception Information Form]]. The form must include a detailed description of the rationale for the change and the appropriate supporting documentation to satisfactorily justify the decision and document any mitigation efforts associated with varying from the engineering policy. Examples of approved Design Exceptions can be found here<provide link>. (Please note that previous approval of an item should not be considered approval of the item on any future project. Approval for future projects must be sought on a case-by-case basis.)

	Project managers (consultant, transportation or bridge) and their design staff should recognize the importance of an open and transparent decision making process while considering the suitability and appropriateness of a given design element that is not consistent with our current policies. Since our engineering policy is established through a collaborative effort, it is critical to engage all appropriate staff when making the decision not to meet our policies. While completing the form, communication with the appropriate staff, including the Design Liaison Engineer, a representative of any affected MoDOT division and FHWA (when applicable), is critical to ensure efficient and effective review and approval. For efficient processing and to avoid delays, this communication should occur prior to the formal submittal. Depending upon the item being excepted and the type of project, the appropriate review staff and signatory parties will vary.		Project managers (consultant, transportation or bridge) and their design staff should recognize the importance of an open and transparent decision making process while considering the suitability and appropriateness of a given design element that is not consistent with our current policies. Since our engineering policy is established through a collaborative effort, it is critical to engage all appropriate staff when making the decision not to meet our policies. While completing the form, communication with the appropriate staff, including the Design Liaison Engineer, a representative of any affected MoDOT division and FHWA (when applicable), is critical to ensure efficient and effective review and approval. For efficient processing and to avoid delays, this communication should occur prior to the formal submittal. Depending upon the item being excepted and the type of project, the appropriate review staff and signatory parties will vary.

Smithk: /* 131.1.4 The Design Exception Process */ updating broken BR division link

2021-12-17T20:44:42Z

131.1.4 The Design Exception Process: updating broken BR division link

← Older revision		Revision as of 15:44, 17 December 2021
Line 91:		Line 91:
	<div id="A copy of every fully approved"></div>		<div id="A copy of every fully approved"></div>

	Central Office staff should be consulted and provide review of the draft design exception prior to district approval. A link to the electronic copy of every fully approved design exception is provided to the [https://modotgov.sharepoint.com/sites/DE/ Central Office Design Division] and [~~http~~://sharepoint/~~systemdelivery~~/br~~/Pages/default.aspx~~ Central Office Bridge Division], as appropriate. A final copy of the design exception is saved in [http://eprojects/SitePages/Home.aspx eProjects] using the appropriate content type: DE Letting Documents. Staff should include any pertinent information in the Comments Section within eProjects.		Central Office staff should be consulted and provide review of the draft design exception prior to district approval. A link to the electronic copy of every fully approved design exception is provided to the [https://modotgov.sharepoint.com/sites/DE/ Central Office Design Division] and [https://modotgov.sharepoint.com/sites/br Central Office Bridge Division], as appropriate. A final copy of the design exception is saved in [http://eprojects/SitePages/Home.aspx eProjects] using the appropriate content type: DE Letting Documents. Staff should include any pertinent information in the Comments Section within eProjects.

	PODI design exceptions are processed through the Design Liaisons for the State Design Engineer and FHWA signatures of approval. The Design Liaisons provide the electronic copy of the fully approved design exception back to the PM for placement in eProjects.		PODI design exceptions are processed through the Design Liaisons for the State Design Engineer and FHWA signatures of approval. The Design Liaisons provide the electronic copy of the fully approved design exception back to the PM for placement in eProjects.

Smithk: updating broken "Design Division" links

2021-11-24T17:09:24Z

updating broken "Design Division" links

← Older revision		Revision as of 12:09, 24 November 2021
Line 91:		Line 91:
	<div id="A copy of every fully approved"></div>		<div id="A copy of every fully approved"></div>

	Central Office staff should be consulted and provide review of the draft design exception prior to district approval. A link to the electronic copy of every fully approved design exception is provided to the [~~http~~://sharepoint/sites/~~de/Pages~~/~~default.aspx~~ Central Office Design Division] and [http://sharepoint/systemdelivery/br/Pages/default.aspx Central Office Bridge Division], as appropriate. A final copy of the design exception is saved in [http://eprojects/SitePages/Home.aspx eProjects] using the appropriate content type: DE Letting Documents. Staff should include any pertinent information in the Comments Section within eProjects.		Central Office staff should be consulted and provide review of the draft design exception prior to district approval. A link to the electronic copy of every fully approved design exception is provided to the [https://modotgov.sharepoint.com/sites/DE/ Central Office Design Division] and [http://sharepoint/systemdelivery/br/Pages/default.aspx Central Office Bridge Division], as appropriate. A final copy of the design exception is saved in [http://eprojects/SitePages/Home.aspx eProjects] using the appropriate content type: DE Letting Documents. Staff should include any pertinent information in the Comments Section within eProjects.

	PODI design exceptions are processed through the Design Liaisons for the State Design Engineer and FHWA signatures of approval. The Design Liaisons provide the electronic copy of the fully approved design exception back to the PM for placement in eProjects.		PODI design exceptions are processed through the Design Liaisons for the State Design Engineer and FHWA signatures of approval. The Design Liaisons provide the electronic copy of the fully approved design exception back to the PM for placement in eProjects.
Line 198:		Line 198:
	Maintaining the integrity of interstates for national defense purposes has long been recognized. Interstates are intended to be constructed and maintained to meet AASHTO Policy as stated in ''A Policy on Design Standards - Interstate System'', which is incorporated by reference in [http://www.fhwa.dot.gov/legsregs/directives/fapg/cfr0625.htm 23 CFR 625]. Maintaining standard vertical clearances to the extent possible for defense mobilization is considered particularly important and is a focus at the national level. As a result, the [http://www.fhwa.dot.gov/ FHWA] has agreed that all exceptions to a 16 ft. vertical clearance standard for the rural interstate and certain single routings on the urban interstates be coordinated with the Surface Deployment and Distribution Command Transportation Engineering Agency (SDDCTEA) of the Department of Defense. This coordination applies whether it is a new construction project, a project that does not provide for the correction of an existing substandard condition, or a project that creates a substandard condition at an existing structure. The steps involved are:		Maintaining the integrity of interstates for national defense purposes has long been recognized. Interstates are intended to be constructed and maintained to meet AASHTO Policy as stated in ''A Policy on Design Standards - Interstate System'', which is incorporated by reference in [http://www.fhwa.dot.gov/legsregs/directives/fapg/cfr0625.htm 23 CFR 625]. Maintaining standard vertical clearances to the extent possible for defense mobilization is considered particularly important and is a focus at the national level. As a result, the [http://www.fhwa.dot.gov/ FHWA] has agreed that all exceptions to a 16 ft. vertical clearance standard for the rural interstate and certain single routings on the urban interstates be coordinated with the Surface Deployment and Distribution Command Transportation Engineering Agency (SDDCTEA) of the Department of Defense. This coordination applies whether it is a new construction project, a project that does not provide for the correction of an existing substandard condition, or a project that creates a substandard condition at an existing structure. The steps involved are:

	:1. For a vertical clearance over any interstate highway that will be less than 16 ft. meeting the above criteria, the district submits to the [~~http~~://~~wwwi~~/~~design~~/~~default.htm~~ Design Division] a completed SDDCTEA Interstate Vertical Clearance Coordination Form along with a Design Exception for vertical clearance.		:1. For a vertical clearance over any interstate highway that will be less than 16 ft. meeting the above criteria, the district submits to the [https://modotgov.sharepoint.com/sites/DE/ Design Division] a completed SDDCTEA Interstate Vertical Clearance Coordination Form along with a Design Exception for vertical clearance.

	:2 The Design Liaison Engineer emails the Bridge Inventory Analysts and requests the Structure NBI number for box 2 on the Vertical Clearance Design Exception Coordination with SDDCTEA Form.		:2 The Design Liaison Engineer emails the Bridge Inventory Analysts and requests the Structure NBI number for box 2 on the Vertical Clearance Design Exception Coordination with SDDCTEA Form.

Kleins1: /* 131.1.1 When to Complete a Design Exception */

2020-11-18T14:08:20Z

131.1.1 When to Complete a Design Exception

← Older revision		Revision as of 09:08, 18 November 2020
Line 15:		Line 15:
	An approved exception simply documents the engineering-based determination that variance from MoDOT’s engineering policy is necessary and appropriate. It is the primary tool to detail not only the decision itself, but also what was considered when the decision was made.		An approved exception simply documents the engineering-based determination that variance from MoDOT’s engineering policy is necessary and appropriate. It is the primary tool to detail not only the decision itself, but also what was considered when the decision was made.

	When there is doubt whether a design exception is required, the ~~Engineering Policy Administrator~~, Assistant State Bridge Engineer or the Design Liaison Engineer (DLE) for the district should be consulted.		When there is doubt whether a design exception is required, the Assistant State Design Engineers, Assistant State Bridge Engineer or the Design Liaison Engineer (DLE) for the district should be consulted.

	A design exception is encouraged whenever it is feasibly or technically impossible to reasonably meet the preferred design criteria or wherever there is potential for additional value outside of written engineering policy. Design exceptions should not be considered breaches of policy as much as opportunities to add practicality or value to the design.		A design exception is encouraged whenever it is feasibly or technically impossible to reasonably meet the preferred design criteria or wherever there is potential for additional value outside of written engineering policy. Design exceptions should not be considered breaches of policy as much as opportunities to add practicality or value to the design.

	An approved exception is not a request for permission; rather, it simply documents deliberate variances from engineering policy.		An approved exception is not a request for permission; rather, it simply documents deliberate variances from engineering policy.

	==131.1.2 The 10 Controlling Criteria==		==131.1.2 The 10 Controlling Criteria==

Smithk: Updated the missions statement on the Design Exception Information Form

2020-01-15T14:42:58Z

Updated the missions statement on the Design Exception Information Form

← Older revision		Revision as of 09:42, 15 January 2020
Line 3:		Line 3:
	\|align-"center"\|'''Forms'''		\|align-"center"\|'''Forms'''
	\|-style="background:#f5f5f5"		\|-style="background:#f5f5f5"
	\|valign="top" align="center"\| [~~http~~:~~//epg.modot.org/forms/DE%202017%20Forms/DELiaison/~~131.~~1_Design_Exception~~.docx Design Exception Information Form]		\|valign="top" align="center"\| [[media:131.1 Design Exception 2020.docx\|Design Exception Information Form]]
	\|-		\|-
	\|[[media:131.1 Vertical Clearance Coord Form Jul 2018.pdf\|Vertical Clearance Design Exception Coordination with SDDCTEA]]		\|[[media:131.1 Vertical Clearance Coord Form Jul 2018.pdf\|Vertical Clearance Design Exception Coordination with SDDCTEA]]
Line 86:		Line 86:
	Requests for design exceptions are submitted when the need first arises; however, they may be submitted at any time and specifically along with the [[:Category:128 Conceptual Studies\|conceptual study]], [[:Category:235 Preliminary Plans\|preliminary plan]], right of way certification, or plans, specifications, and estimate (PS&E). In general, it is best to identify and consider the design exception as early as practical in the design process.		Requests for design exceptions are submitted when the need first arises; however, they may be submitted at any time and specifically along with the [[:Category:128 Conceptual Studies\|conceptual study]], [[:Category:235 Preliminary Plans\|preliminary plan]], right of way certification, or plans, specifications, and estimate (PS&E). In general, it is best to identify and consider the design exception as early as practical in the design process.

	When the need for a design exception has been identified, the project manager, Structural Project Manager or consultant representative is responsible for completing the standard [~~http~~:~~//epg.modot.org/forms/DE%202017%20Forms/DELiaison/~~131.~~1_Design_Exception~~.docx Design Exception Information Form]. The form must include a detailed description of the rationale for the change and the appropriate supporting documentation to satisfactorily justify the decision and document any mitigation efforts associated with varying from the engineering policy. Examples of approved Design Exceptions can be found here<provide link>. (Please note that previous approval of an item should not be considered approval of the item on any future project. Approval for future projects must be sought on a case-by-case basis.)		When the need for a design exception has been identified, the project manager, Structural Project Manager or consultant representative is responsible for completing the standard [[media:131.1 Design Exception 2020.docx\|Design Exception Information Form]]. The form must include a detailed description of the rationale for the change and the appropriate supporting documentation to satisfactorily justify the decision and document any mitigation efforts associated with varying from the engineering policy. Examples of approved Design Exceptions can be found here<provide link>. (Please note that previous approval of an item should not be considered approval of the item on any future project. Approval for future projects must be sought on a case-by-case basis.)

	Project managers (consultant, transportation or bridge) and their design staff should recognize the importance of an open and transparent decision making process while considering the suitability and appropriateness of a given design element that is not consistent with our current policies. Since our engineering policy is established through a collaborative effort, it is critical to engage all appropriate staff when making the decision not to meet our policies. While completing the form, communication with the appropriate staff, including the Design Liaison Engineer, a representative of any affected MoDOT division and FHWA (when applicable), is critical to ensure efficient and effective review and approval. For efficient processing and to avoid delays, this communication should occur prior to the formal submittal. Depending upon the item being excepted and the type of project, the appropriate review staff and signatory parties will vary.		Project managers (consultant, transportation or bridge) and their design staff should recognize the importance of an open and transparent decision making process while considering the suitability and appropriateness of a given design element that is not consistent with our current policies. Since our engineering policy is established through a collaborative effort, it is critical to engage all appropriate staff when making the decision not to meet our policies. While completing the form, communication with the appropriate staff, including the Design Liaison Engineer, a representative of any affected MoDOT division and FHWA (when applicable), is critical to ensure efficient and effective review and approval. For efficient processing and to avoid delays, this communication should occur prior to the formal submittal. Depending upon the item being excepted and the type of project, the appropriate review staff and signatory parties will vary.

Kleins1 at 14:35, 5 March 2019

2019-03-05T14:35:09Z

← Older revision		Revision as of 09:35, 5 March 2019
Line 5:		Line 5:
	\|valign="top" align="center"\| [http://epg.modot.org/forms/DE%202017%20Forms/DELiaison/131.1_Design_Exception.docx Design Exception Information Form]		\|valign="top" align="center"\| [http://epg.modot.org/forms/DE%202017%20Forms/DELiaison/131.1_Design_Exception.docx Design Exception Information Form]
	\|-		\|-
	\|[[media:131.1.7 Vertical Clearance ~~Design Exception Coordination with SDDCTEA~~.pdf\|Vertical Clearance Design Exception Coordination with SDDCTEA]]		\|[[media:131.1 Vertical Clearance Coord Form Jul 2018.pdf\|Vertical Clearance Design Exception Coordination with SDDCTEA]]
	\|}		\|}

Line 202:		Line 202:
	:2 The Design Liaison Engineer emails the Bridge Inventory Analysts and requests the Structure NBI number for box 2 on the Vertical Clearance Design Exception Coordination with SDDCTEA Form.		:2 The Design Liaison Engineer emails the Bridge Inventory Analysts and requests the Structure NBI number for box 2 on the Vertical Clearance Design Exception Coordination with SDDCTEA Form.

	:3. Concurrent with the submission or routing of the Design Exception, the Design Liaison Engineer submits the form to the SDDCTEA and copies FHWA. This may be done electronically using the contact information on the [[media:131.1.7 Vertical Clearance ~~Design Exception Coordination with SDDCTEA~~.pdf\|Vertical Clearance Design Exception Coordination with SDDCTEA]].		:3. Concurrent with the submission or routing of the Design Exception, the Design Liaison Engineer submits the form to the SDDCTEA and copies FHWA. This may be done electronically using the contact information on the [[media:131.1 Vertical Clearance Coord Form Jul 2018.pdf\|Vertical Clearance Design Exception Coordination with SDDCTEA]].

	:4. A response from SDDCTEA should occur within 10 working days following receipt of the coordination request. Receipt of the request can be verified with SDDCTEA via telephone or fax. If there is no response after 10 working days following receipt, it can be determined that SDDCTEA does not have any concerns about the proposed exception.		:4. A response from SDDCTEA should occur within 10 working days following receipt of the coordination request. Receipt of the request can be verified with SDDCTEA via telephone or fax. If there is no response after 10 working days following receipt, it can be determined that SDDCTEA does not have any concerns about the proposed exception.