Transportation Design Overview
Establish the scope, functional classification, and design controls that govern the transportation design chapter.
Section progress
0% of the workflow complete
Highway & Traffic Engineering · Geometric design, traffic analysis, pavement, intersections and roadway safety to AASHTO and MUTCD.
Deliverable: Transportation design basis memo with functional classification, design controls, and design-year traffic.
Minimum tables, figures and equations for Transportation Design Overview
Tables — at least 6
- Table — trial sections or sizes considered, with the capacity of each and the selection decision
- Table — final selected geometry for every element: dimensions, thickness, grade, spacing, elevation
- Table — slab, beam, column and shear wall schedule with governing demand
- Table — ultimate limit state check summary: demand, capacity, ratio, pass or fail, governing clause
- Table — serviceability check summary: deflection, crack width, settlement, freeboard or velocity against its limit
- Table — factors of safety achieved against the factor required, per failure mode
Figures — at least 4
- Figure — free body diagram of each isolated element, fully labelled with loads, reactions, dimensions and axes
- Figure — shear and moment (or pressure and velocity) diagrams for each force-carrying element
- Figure — dimensioned section or plan of each designed element
- Figure — capacity versus demand plot, interaction diagram, or rating curve as applicable
Equations — at least 8
- Equation — equilibrium equations written out for each free body (sum of forces and sum of moments, or continuity and energy)
- Equation — the internal force relations V(x) and M(x), or the momentum/thrust relation, used to compute each element's demand
- Equation — the resulting demand at the critical section of each element, with numeric substitution
- Equation — the capacity expression for each element type, shown with full numeric substitution and units
- Equation — the sizing criterion that sets the final dimension (for example required area, depth or diameter)
- Equation — each limit state check written as demand over capacity with numbers substituted
- Equation — the factor of safety calculation for each failure mode checked
- Equation — punching shear, drift and deflection checks with limits
Number every table and figure (Table 4.x, Figure 4.x), caption it, and refer to it by number in your text. Number displayed equations and show the substitution with units. These counts are minimums — add whatever else your design needs.
Engineering documentation standard — required in every Chapter 4 subsection
These rules are graded on every subsection. Work that misses them is capped on technical accuracy, exhibits, codes and communication, whatever the quality of the prose.
Code and standard references
- Every requirement, factor, coefficient, limit and allowable you apply cites the governing document AND the exact section, article or sub-article number — e.g. ACI 318-19 §22.5.5.1, AISC 360-22 Chapter J, Section J3.6, AASHTO LRFD 10th Ed. Article 3.6.1.2.2, ASCE 7-22 §12.8.1, ASTM D2487, state DOT manual section, local stormwater manual chapter.
- Give the edition or year of every document the first time it appears, then use a consistent short form.
- Where a code equation is used, quote the equation number (e.g. Eq. 22.5.5.1) next to your displayed equation.
- Where you depart from a code provision, state the clause you are departing from and the engineering justification.
- List every code, standard and manual actually used in a Codes and Standards table at the start of the subsection.
Citations for statements
- Every statement of fact, value taken from elsewhere, material property, soil parameter, rainfall depth, unit cost or published method carries an in-text citation (APA) to its source.
- Field and lab data cite the report, boring log, gauge, survey file or test number and its date.
- Manufacturer data cites the product literature and revision date; software results cite the program, version and model file name.
- Uncited assertions are treated as assumptions and must appear in the assumptions table with a justification.
- Every in-text citation resolves to a full entry in the reference list.
Step-by-step calculations
- Structure every calculation the same way: (1) objective, (2) governing code clause, (3) equation in symbolic form with the equation number, (4) definition of each symbol, (5) numerical substitution, (6) result with units, (7) comparison against the limit and the pass/fail statement.
- Show the substitution line — never jump from the formula to the answer.
- Number displayed equations sequentially (Eq. 4.1, 4.2, …) and refer to them by number in the text.
- State the load or flow combination governing each calculation by name.
- Carry consistent significant figures and round only at the reported result; state the rounding convention once.
- Present repetitive element checks in a calculation table with one row per element and the same column order throughout.
Free body diagrams and figures
- Draw a separate free body diagram for each isolated element — no combined sketches standing in for several members.
- Dimension every FBD: span, depth, thickness, cover, eccentricity, embedment, slope, pipe diameter, wall height — with the dimension lines and values shown.
- Label every force, pressure, reaction and moment with its symbol, magnitude and units, and show the sign convention and coordinate axes.
- Show supports and boundary conditions explicitly (pin, roller, fixed, elastic, buoyant, hydrostatic).
- Accompany each FBD with its shear, moment, thrust, pressure or hydraulic grade diagram at the same scale reference.
- Number and caption every figure (Figure 4.x) and refer to it by number in the narrative; add a scale or north arrow to plans.
Units and notation
- Every number in text, tables, figures and equations carries its unit — no bare numbers.
- Use one unit system throughout (US customary or SI); if both appear, give the converted value in parentheses consistently.
- Check dimensional homogeneity of each equation and say so — the units of both sides must match.
- Provide a nomenclature table defining every symbol with its unit.
Checking and verification
- Every calculation is checked by an independent route — hand check against software, alternative method, order-of-magnitude estimate, or a published worked example — and the check is shown, not just claimed.
- Report demand-to-capacity ratios and factors of safety against the required values, with the source clause for each required value.
- Include a verification/checking table: item, method of check, expected, obtained, difference, accept or revise.
- Sanity-check every result (magnitude, direction, plausibility) and state the conclusion.
- Record who checked the work and on what date; flag anything still unverified as an open item.
- State limitations and the range over which the result is valid.
How to complete this section
Do this next: Read the Transportation Design Overview lecture and the worked example so you know what "Transportation design basis memo with functional classification, design controls, and design-year traffic." has to contain.
Not sure how to start or how much depth is expected? Read the fully written model example for this deliverable first — it shows the structure, tables and level of justification your advisor grades against.
Transportation Design Office — what this workspace teaches
Geometric design, traffic analysis, pavement, intersections and roadway safety to AASHTO and MUTCD.
- AASHTO Green Book design controls: design speed, functional class, design vehicle
- Traffic data: AADT, DHV, K and D factors, truck percentage, growth projection
- Horizontal alignment: curve radius, superelevation, side friction, transitions
- Vertical alignment: grades, crest and sag curves, K-values
- Sight distance: stopping, decision, passing and intersection sight distance
- Cross sections: lane and shoulder widths, side slopes, clear zone
- Pavement design: ESALs, subgrade support, layer thicknesses (flexible and rigid)
- Intersection design, roundabouts, turn lanes and capacity
- Traffic signals: warrants, phasing, cycle length, timing (MUTCD/HCM)
- Roadway drainage and safety: crash analysis, barriers, clear zone
End-of-term milestones
- Tuesday, November 17, 2026 — Poster printed and ready. 36 in × 48 in poster finalized and printed one week before the November 24 showcase.
- Wednesday, November 18, 2026 — Final document package uploaded for scoring. Chapters 4–5, calculation package, drawings and appendices uploaded in the app for advisor scoring.
- Wednesday, November 18, 2026 — Poster presentation to faculty and industry. Wednesday poster session — printed 36 in × 48 in poster presented in person; industry reviewers score communication and impact.
- Wednesday, November 25, 2026 — Oral presentation and defense (scored). Scored oral presentation and defense held on Wednesday, November 25.
Transportation Design Overview
Establish the scope, functional classification, and design controls that govern the transportation design chapter.
Section B
Engineering story
A real project situation that frames this module
A transportation engineering team hits transportation design overview in week 4, with the roadway geometry, control plan and operational analysis already promised to the owner. Establish the scope, functional classification, and design controls that govern the transportation design chapter. The reviewer starts at the end and works backwards, and the chain breaks at functional classification (arterial, collector, local) drives design speed, access spacing, and cross-section.
Adopting a functional classification without confirming it against the current MPO/DOT map. Because design controls, the error does not stay local: it is carried into the design of record that drawings, quantities and cost are generated from, and every downstream product inherits it before anyone notices.
Drivers, pedestrians, cyclists, transit riders and the agency that owns the facility carry the consequence. On this module specifically, the exposure runs through context-sensitive design balances mobility, access, and multimodal needs, and the cost of correction rises every week the roadway geometry, control plan and operational analysis moves closer to issue.
Decisions the engineer must make
- What record establishes functional classification (arterial, collector, local) drives design speed, access spacing, and cross-section, and is that record in the project data inventory?
- Does AASHTO Green Book (7th Ed.), Ch. 1–2, govern here — and is that the edition adopted by the jurisdiction?
- What is the acceptance criterion for design controls, and was it written before the result was known?
- Is DDHV = AADT × K × D valid over the parameter range this project actually occupies?
- If the check fails, does the team revise the roadway geometry, control plan and operational analysis or raise a change request against the locked baseline?
Photo 1. Peak-hour demand: the flow rate that drives capacity, delay and level-of-service analysis.
Wikimedia Commons, CC BY 2.0
Section C
Why this matters
Professional
A licensed engineer defending transportation design overview cites AASHTO Green Book (7th Ed.), Ch. 1–2, and shows the record behind each input. Your transportation design basis memo with functional classification, design controls, and design-year traffic. is reviewed the same way — traceability is assessed before arithmetic.
Technical
Functional classification (arterial, collector, local) drives design speed, access spacing, and cross-section is what makes DDHV = AADT × K × D usable on this project rather than a formula copied from a reference. Get it wrong and every quantity derived from it is wrong by the same factor.
Safety
The failure mode this module guards against is a geometric or control element that puts drivers in a conflict they cannot resolve. It reaches people through coordination points with geotechnical (subgrade), water resources (drainage), and structural (bridges/culverts) chapters, which is why the safety check is recorded explicitly here rather than inferred from a passing strength or performance check.
Economic
The design of record that drawings, quantities and cost are generated from is priced from this work. Quantities, unit costs and schedule float all trace to functional classification (arterial, collector, local) drives design speed, access spacing, and cross-section; a late correction here is paid for as a change order, not a redline.
Environmental
Environmentally, this module fixes vehicle delay emissions, pavement material demand and stormwater from added impervious area. Choosing conservatively without justification is not free — the excess shows up as material, energy and land that the project consumes for no measurable gain.
Community
Design controls and load assumptions must be revisited whenever project scope, traffic, or standards change. Everyone who walks, rides or drives the corridor every day live with that outcome long after the semester ends.
Section D
Learning objectives
By the end of this module you will be able to:
- 1.Justify functional classification (arterial, collector, local) drives design speed, access spacing, and cross-section, using this project's own conditions rather than a textbook case.
- 2.Evaluate design controls, using this project's own conditions rather than a textbook case.
- 3.Evaluate context-sensitive design balances mobility, access, and multimodal needs, using this project's own conditions rather than a textbook case.
- 4.Apply design year selection (typically 20 years) and traffic growth rate assumptions, using this project's own conditions rather than a textbook case.
- 5.Compute the governing quantity from DDHV = AADT × K × D, with a unit audit on every term.
- 6.Apply AASHTO Green Book (7th Ed.), Ch. 1–2, and cite the section that governs your acceptance decision.
- 7.Reproduce the worked example for a collector roadway carries AADT = 12,000 vpd with K = 0.10 and D = 0.55 and defend the interpretation of the result.
- 8.Produce transportation design basis memo with functional classification, design controls, and design-year traffic. at a standard the DOT design reviewer would accept without a second revision cycle.
Section E
Instructional content
Full lecture notes with figures and governing equations
Transportation Design Overview: from proposal statement to engineering product
Establish the scope, functional classification, and design controls that govern the transportation design chapter. That single sentence hides the substance of the module: functional classification (arterial, collector, local) drives design speed, access spacing, and cross-section, and design controls. Both must be established from project evidence before anything downstream is credible.
In transportation engineering, this work is the input to the roadway geometry, control plan and operational analysis. Context-sensitive design balances mobility, access, and multimodal needs — which is why this page asks you to record the source of every quantity, not just its value. The design of record that drawings, quantities and cost are generated from depends on it.
- Functional classification (arterial, collector, local) drives design speed, access spacing, and cross-section
- Design controls: design vehicle, design speed, design hour volume (DHV), K and D factors
- Context-sensitive design balances mobility, access, and multimodal needs
- Design year selection (typically 20 years) and traffic growth rate assumptions
- Coordination points with geotechnical (subgrade), water resources (drainage), and structural (bridges/culverts) chapters
Photo 1. Transportation Design Overview: from proposal statement to engineering product in practice — Peak-hour demand: the flow rate that drives capacity, delay and level-of-service analysis.
Wikimedia Commons, CC BY 2.0
Governing relationships and how they are applied here
The relationships below govern transportation design overview. DDHV = AADT × K × D — each is valid only inside the parameter range this project occupies, so state that range before substituting.
Design controls sets the values you place into these expressions. Any code-prescribed factor must match AASHTO Green Book (7th Ed.); a factor lifted from a different edition silently changes the answer.
DDHV = AADT × K × D
- DDHV = directional design hour volume (veh/h)
- AADT = annual average daily traffic
- K = proportion of AADT occurring in design hour
- D = directional distribution factor
Photo 2. Governing relationships and how they are applied here in practice — Peak-hour demand: the flow rate that drives capacity, delay and level-of-service analysis.
Wikimedia Commons, CC BY 2.0
Constraints, adopted standards and the safety case for transportation design overview
AASHTO Green Book (7th Ed.), Ch. 1–2, governs this module: Design controls and functional classification MUTCD (11th Ed.), Ch. 1, adds the second constraint: Uniform traffic control device basis of design
The safety case is explicit here. The failure mode is a geometric or control element that puts drivers in a conflict they cannot resolve; the people exposed are drivers, pedestrians, cyclists, transit riders and the agency that owns the facility; the control that prevents it is coordination points with geotechnical (subgrade), water resources (drainage), and structural (bridges/culverts) chapters together with an independent check by someone who did not perform the work.
- Controlling criterion for this module: functional classification (arterial, collector, local) drives design speed, access spacing, and cross-section.
- Adopted reference: AASHTO Green Book (7th Ed.) — cite Ch. 1–2 by number.
- Failure mode guarded: a geometric or control element that puts drivers in a conflict they cannot resolve.
- Evidence produced: Transportation design basis memo with functional classification, design controls, and design-year traffic..
Photo 3. Constraints, adopted standards and the safety case for transportation design overview in practice — Peak-hour demand: the flow rate that drives capacity, delay and level-of-service analysis.
Wikimedia Commons, CC BY 2.0
Where this method stops being valid
The worked example — a collector roadway carries AADT = 12,000 vpd with K = 0.10 and D = 0.55 — holds only while its assumptions hold. This directional volume, not AADT, sizes the number of through lanes needed at the design hour. Outside that envelope the arithmetic still returns a number, and the number is wrong in a way no unit check will catch.
For this project, the boundary you are most likely to push is coordination points with geotechnical (subgrade), water resources (drainage), and structural (bridges/culverts) chapters. If you cross it, say so in writing, bound the error, and carry the limitation into your results chapter. A disclosed limitation is professional practice; a silent extrapolation is not.
Photo 4. Where this method stops being valid in practice — Peak-hour demand: the flow rate that drives capacity, delay and level-of-service analysis.
Wikimedia Commons, CC BY 2.0
Section F
Engineering workflow
Steps
- 1. Assemble the inputs this module needs — functional classification (arterial, collector, local) drives design speed, access spacing,…; design controls — each with a unit and a source record.
- 2. Confirm AASHTO Green Book (7th Ed.) is the adopted edition and locate Ch. 1–2.
- 3. State the assumptions and the acceptance criterion for functional classification (arterial, collector, local) drives design speed, access spacing, and cross-section.
- 4. Evaluate DDHV = AADT × K × D term by term, carrying one extra significant figure.
- 5. Test the result against context-sensitive design balances mobility, access, and multimodal needs.
- 6. Audit units and run an order-of-magnitude check by hand before the number leaves your desk.
- 7. Obtain an independent check from a teammate who did not perform the work, and record their name and date.
- 8. Assemble transportation design basis memo with functional classification, design controls, and design-year traffic. and submit it to the DOT design reviewer for review.
Decision points
- Is every input behind functional classification (arterial, collector, local) drives design speed, access spacing, and cross-section traceable? If not — stop and collect the record.
- Does the result satisfy design controls? If not — revise the work, never the criterion.
- Would the correction change the design of record that drawings, quantities and cost are generated from? If yes — raise a change-control request before proceeding.
- Have you ruled out the most common error on this module — adopting a functional classification without confirming it against the current MPO/DOT map?
Quality checklist
- Documented: functional classification (arterial, collector, local) drives design speed, access spacing, and cross-section
- Documented: design controls
- Documented: context-sensitive design balances mobility, access, and multimodal needs
- AASHTO Green Book Ch. 1–2 cited by section number
- Units audited on every expression
- Acceptance criterion recorded before the result
- Independent check signed and dated
- Transportation design basis memo with functional classification, design controls, and design-year traffic. attached and named per the course convention
Section H
Interactive visualization
Transportation Design Overview — step-through
Advance one frame at a time. Each frame adds one engineering decision to the previous state.
Step 1 of 6
Confirm project limits and adjacent network context
Section I
Applicable codes and standards
AASHTO Green Book
7th Ed. · Ch. 1–2
Adopted design/analysis reference governing this module.
Relevance: Design controls and functional classification
Reference the section number and edition in your calculation package. Do not reproduce code text.
MUTCD
11th Ed. · Ch. 1
Adopted design/analysis reference governing this module.
Relevance: Uniform traffic control device basis of design
Reference the section number and edition in your calculation package. Do not reproduce code text.
Section J
Worked examples
Full engineering solution format
Section K
Common mistakes and how to avoid them
- Adopting a functional classification without confirming it against the current MPO/DOT map
- Using AADT directly for lane design instead of the directional design hour volume
- Skipping coordination with drainage design until construction documents
- Treating functional classification (arterial, collector, local) drives design speed, access spacing, and cross-section as a given instead of establishing it from a project record.
- Producing transportation design basis memo with functional classification, design controls, and design-year traffic. without showing how design controls was satisfied.
- Substituting into DDHV = AADT × K × D outside the range where it is valid, and reporting the number anyway.
- Missing coordination points with geotechnical (subgrade), water resources (drainage), and structural (bridges/culverts) chapters, which is exactly the path to a geometric or control element that puts drivers in a conflict they cannot resolve.
- Designing to the average condition when the governing condition is the controlling one.
- Freezing a design before the constructability and access review that would have changed it.
- Confusing results (what the analysis produced) with conclusions (what the engineer decided).
- Ignoring constructability: a design that cannot be built safely is not a completed design.
- Omitting the safety check because the strength check passed.
Section L
Industry case study
I-35W Mississippi River Bridge Collapse
Minneapolis, MN, 2007
Official findings
- NTSB found an undersized gusset plate detail was never re-checked as the bridge's use and dead load changed over decades.
Field observations
- The controlling assumption was documented nowhere in the design record.
- No independent check existed at the stage where the error entered the work.
Engineering interpretation
- Interpretation below is student analysis for instructional purposes, not an official finding.
- Map the failure to a step in your own workflow and state where your process would have caught it.
Lessons learned
- Design controls and load assumptions must be revisited whenever project scope, traffic, or standards change.
Source: Summarize the published investigation; cite it in your reference list. Do not reproduce copyrighted report text.
Section M
FE Civil exam connection
Handbook FE Reference Handbook — transportation engineering section (record the section number from your handbook edition).
Exam topics
Handbook formulas
- DDHV = AADT × K × D
Weak results here feed your FE Civil Academy weak-area queue for targeted practice.
Question 1 of 2
Score: 0/2In transportation design overview, which item must be established BEFORE the analysis is run?
Section N
Apply it to your project — Transportation Design Overview
Complete this using your own capstone project data. Every field is saved to your project record and routed to your advisor with this module's submission.
Inputs and sources
Every value needs a traceable source.
| Quantity | Value | Unit | Source / record |
|---|
Assumptions and consequences
| Assumption | Basis | Consequence if wrong |
|---|
Self-check before submission
Section O
Design challenge
Consulting challenge — Transportation Design Overview
Your firm has been retained to deliver the transportation design overview scope for a municipal client on a compressed schedule. Produce the technical position your firm would defend at a public meeting.
Client request: The client wants a defensible recommendation, the basis of design, and an honest statement of what remains unresolved.
Constraints
- Adopted local code edition governs; no exceptions without written variance.
- Budget and schedule are fixed; scope changes require change control.
- Public safety and accessibility requirements are non-negotiable.
Deliverables
- One-page basis of design
- Supporting calculation extract
- Risk and limitation statement
Evaluation
- Technical correctness
- Standard compliance
- Clarity of engineering judgment
- Honest treatment of uncertainty
Section P
Documentation workspace
Write the report section for this module in the academic editor
Section Q
File uploads
Accepted: PDF, DOCX, XLSX, CSV, PNG, JPG, ZIP, DWG, DXF, Civil3D
No files uploaded yet.
Section R
Deliverable and advisor review
Transportation design basis memo with functional classification, design controls, and design-year traffic.
Submissions route to your assigned faculty advisor and are scored independently by faculty and administrator rubrics.
Reflection
What was the hardest engineering judgment in this module, and how did you resolve it?
Section S
ABET outcome mapping
Transportation design basis memo with functional classification, design controls, and design-year traffic. with advisor review and dual scoring.
Assessment: Faculty rubric score and administrator rubric score on this module's submission.
Rubric: Engineering design · Target: 70% of students at or above 'meets expectations'.
Transportation design basis memo with functional classification, design controls, and design-year traffic. with advisor review and dual scoring.
Assessment: Faculty rubric score and administrator rubric score on this module's submission.
Rubric: Engineering design · Target: 70% of students at or above 'meets expectations'.
Section T
References and further study
AASHTO Green Book (7th Ed.)
Adopted reference — cite section numbers, do not reproduce text.
MUTCD (11th Ed.)
Adopted reference — cite section numbers, do not reproduce text.
Transportation Design Overview — instructor design procedure
Course template for the calculation package format expected in the final report appendix.
NCEES FE Reference Handbook
Locate the equations used here and note the handbook section for exam recall.
Advisor meeting agenda item
Bring the unresolved decision from this module to your next weekly advisor meeting.