Skip to content
CEGR 493
Investigation
Week 3
general
Site Investigation Lab
Not graded — practice
Capstone II dashboard

This deliverable is not counted toward your grade

Project Start and Technical Implementation (site, data and investigation) pages are required practice but are not counted toward your final grade. Your engineering grade comes from Chapter 4 and Chapter 5.

Existing Conditions Assessment

Students document existing site conditions (structures, utilities, drainage, hazards) into a baseline report that will bound the design scope.

Section progress

0% of the workflow complete

Field & Laboratory · Plan, execute and document field and laboratory data collection to a defensible quality standard.

Deliverable: Existing conditions assessment report with condition ratings and hazard flags.

How to complete this section

0 words saved

Do this next: Read the Existing Conditions Assessment lecture and the worked example so you know what "Existing conditions assessment report with condition ratings and hazard flags." 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.

Site Investigation Lab — what this workspace teaches

Plan, execute and document field and laboratory data collection to a defensible quality standard.

  • Planning a subsurface, structural or traffic field investigation
  • Instrumentation selection, resolution, accuracy and calibration records
  • GPS/GNSS positioning: datums, projections, RTK vs. handheld accuracy
  • GIS data capture, attribute schemas and coordinate metadata
  • Land surveying: traverses, levelling, closure and error adjustment
  • Sampling strategy: representative sampling, spacing, depth intervals, replicates
  • ASTM/AASHTO laboratory testing procedures and reporting requirements
  • Chain of custody, sample labelling and preservation
  • QA/QC: duplicates, blanks, repeatability and data validation rules

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.
Week 3
general

Existing Conditions Assessment

Students document existing site conditions (structures, utilities, drainage, hazards) into a baseline report that will bound the design scope.

Section B

Engineering story

A real project situation that frames this module

Week 3: existing conditions assessment is the item standing between the team and a reviewable project record. Students document existing site conditions (structures, utilities, drainage, hazards) into a baseline report that will bound the design scope. Review stalls on a single line: the team cannot show the record behind visual condition assessment rating scales for existing infrastructure elements.

Recording a condition rating without a photo reference that lets a reviewer verify it. Because distinguishing conditions requiring immediate safety action from those to be addressed in design, the error does not stay local: it is carried into the data foundation every later calculation silently depends on, and every downstream product inherits it before anyone notices.

The owner, the reviewing agency and the engineer of record carry the consequence. On this module specifically, the exposure runs through coordinating existing-conditions findings with the data inventory and gap analysis, and the cost of correction rises every week the project record moves closer to issue.

Decisions the engineer must make

  • What record establishes visual condition assessment rating scales for existing infrastructure elements, and is that record in the project data inventory?
  • Does ASCE 11-99 (1999 (R2016)), Sec. 2, govern here — and is that the edition adopted by the jurisdiction?
  • What is the acceptance criterion for distinguishing conditions requiring immediate safety action from those to be addressed in design, and was it written before the result was known?
  • Is the documented procedure valid for the conditions this project actually presents?
  • If the check fails, does the team revise the project record or raise a change request against the locked baseline?
Water ponding in a street gutter and flowing into a curb storm drain inlet during rain.

Photo 1. Inlet capture during rainfall: gutter spread and inlet capacity decide whether the lane floods.

Capstone Studio instructional photograph

Section C

Why this matters

Professional

A licensed engineer defending existing conditions assessment cites ASCE 11-99 (1999 (R2016)), Sec. 2, and shows the record behind each input. Your existing conditions assessment report with condition ratings and hazard flags. is reviewed the same way — traceability is assessed before arithmetic.

Technical

Visual condition assessment rating scales for existing infrastructure elements controls the numbers this module hands forward. Distinguishing conditions requiring immediate safety action from those to be addressed in design determines whether those numbers remain valid once conditions change.

Safety

The failure mode this module guards against is a decision made without a traceable basis. It reaches people through documenting non-conforming or legacy conditions relative to current code (grandfathering), which is why the safety check is recorded explicitly here rather than inferred from a passing strength or performance check.

Economic

The data foundation every later calculation silently depends on is priced from this work. Quantities, unit costs and schedule float all trace to visual condition assessment rating scales for existing infrastructure elements; a late correction here is paid for as a change order, not a redline.

Environmental

Environmentally, this module fixes material use, land disturbance and the waste stream generated by rework. 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

The residents and agencies who inherit the completed work inherit whatever this module decides — performance, accessibility, cost of ownership and resilience are set here, not at the ribbon-cutting.

Section D

Learning objectives

By the end of this module you will be able to:

  1. 1.Apply visual condition assessment rating scales for existing infrastructure elements, using this project's own conditions rather than a textbook case.
  2. 2.Compare distinguishing conditions requiring immediate safety action from those to be addressed in design, using this project's own conditions rather than a textbook case.
  3. 3.Analyze coordinating existing-conditions findings with the data inventory and gap analysis, using this project's own conditions rather than a textbook case.
  4. 4.Justify documenting non-conforming or legacy conditions relative to current code (grandfathering), using this project's own conditions rather than a textbook case.
  5. 5.Apply ASCE 11-99 (1999 (R2016)), Sec. 2, and cite the section that governs your acceptance decision.
  6. 6.Produce existing conditions assessment report with condition ratings and hazard flags. at a standard the advisor of record would accept without a second revision cycle.

Section E

Instructional content

Full lecture notes with figures and governing equations

Reading existing conditions assessment as a practising engineer

Students document existing site conditions (structures, utilities, drainage, hazards) into a baseline report that will bound the design scope. That single sentence hides the substance of the module: visual condition assessment rating scales for existing infrastructure elements, and distinguishing conditions requiring immediate safety action from those to be addressed in design. Both must be established from project evidence before anything downstream is credible.

In civil engineering practice, this work is the input to the project record. Coordinating existing-conditions findings with the data inventory and gap analysis — which is why this page asks you to record the source of every quantity, not just its value. The data foundation every later calculation silently depends on depends on it.

  • Visual condition assessment rating scales for existing infrastructure elements
  • Distinguishing conditions requiring immediate safety action from those to be addressed in design
  • Coordinating existing-conditions findings with the data inventory and gap analysis
  • Documenting non-conforming or legacy conditions relative to current code (grandfathering)
FIGURE 1InputAnalyzeCheckDecideDocument1Condition rating2Location3Hazard flag4Code non-conformance5Photo ID6Recommended action
Figure 1. Existing Conditions Assessment — annotated engineering schematic showing the governing quantities carried through this module.Read this figure alongside the theory block: every labelled quantity must appear in your calculation package with a unit and a source.
Water ponding in a street gutter and flowing into a curb storm drain inlet during rain.

Photo 1. Reading existing conditions assessment as a practising engineer in practice — Inlet capture during rainfall: gutter spread and inlet capacity decide whether the lane floods.

Capstone Studio instructional photograph

Decision logic: the procedure that replaces a closed-form solution

Existing Conditions Assessment is governed by a documented procedure rather than a single expression, so the decision logic is the deliverable: what you accept, what you reject, and on what evidence. Visual condition assessment rating scales for existing infrastructure elements.

Write the acceptance criterion before you look at the result. Distinguishing conditions requiring immediate safety action from those to be addressed in design — recording the criterion afterwards lets it be shaped to fit the number you happened to get.

Three engineers in hard hats and safety vests reviewing drawings on a truck tailgate.

Photo 2. Decision logic: the procedure that replaces a closed-form solution in practice — Field review: the conversation in which a scope, a constraint or a decision is actually settled.

Capstone Studio instructional photograph

Constraints, adopted standards and the safety case for existing conditions assessment

ASCE 11-99 (1999 (R2016)), Sec. 2, governs this module: Guideline for structural condition assessment of existing buildings FHWA-NHI-16-064 (2018), Ch. 4, adds the second constraint: Highway bridge inspection condition rating reference

The safety case is explicit here. The failure mode is a decision made without a traceable basis; the people exposed are the owner, the reviewing agency and the engineer of record; the control that prevents it is documenting non-conforming or legacy conditions relative to current code (grandfathering) together with an independent check by someone who did not perform the work.

  • Controlling criterion for this module: visual condition assessment rating scales for existing infrastructure elements.
  • Adopted reference: ASCE 11-99 (1999 (R2016)) — cite Sec. 2 by number.
  • Failure mode guarded: a decision made without a traceable basis.
  • Evidence produced: Existing conditions assessment report with condition ratings and hazard flags..
FIGURE 2Confirm inputs and sourcesSelect governing standardAnalyze / designCheck units and equilibriumIndependent checkAccept or revise
Figure 2. Existing Conditions Assessment — professional workflow from inputs through acceptance.The revise loop is normal. Reviewers expect to see it in your version history.
Dense peak-hour traffic queued on an urban arterial at dusk.

Photo 3. Constraints, adopted standards and the safety case for existing conditions assessment 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

Every method has a domain of validity. State the range of geometry, loading, material behaviour or flow regime over which your approach holds, and state what you would do instead beyond it.

For this project, the boundary you are most likely to push is documenting non-conforming or legacy conditions relative to current code (grandfathering). 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.

Concrete cylinder under axial load in a compression testing machine.

Photo 4. Where this method stops being valid in practice — Compression test on a concrete cylinder: the measurement behind every f′c used in design.

Wikimedia Commons, public domain

Section F

Engineering workflow

Steps

  1. 1. Assemble the inputs this module needs — visual condition assessment rating scales for existing infrastructure elements; distinguishing conditions requiring immediate safety action from those to be… — each with a unit and a source record.
  2. 2. Confirm ASCE 11-99 (1999 (R2016)) is the adopted edition and locate Sec. 2.
  3. 3. State the assumptions and the acceptance criterion for visual condition assessment rating scales for existing infrastructure elements.
  4. 4. Execute the documented procedure, recording each judgement and the evidence behind it.
  5. 5. Test the result against coordinating existing-conditions findings with the data inventory and gap analysis.
  6. 6. Audit units and run an order-of-magnitude check by hand before the number leaves your desk.
  7. 7. Obtain an independent check from a teammate who did not perform the work, and record their name and date.
  8. 8. Assemble existing conditions assessment report with condition ratings and hazard flags. and submit it to the advisor of record for review.

Decision points

  • Is every input behind visual condition assessment rating scales for existing infrastructure elements traceable? If not — stop and collect the record.
  • Does the result satisfy distinguishing conditions requiring immediate safety action from those to be addressed in design? If not — revise the work, never the criterion.
  • Would the correction change the data foundation every later calculation silently depends on? If yes — raise a change-control request before proceeding.
  • Have you ruled out the most common error on this module — recording a condition rating without a photo reference that lets a reviewer verify it?

Quality checklist

  • Documented: visual condition assessment rating scales for existing infrastructure elements
  • Documented: distinguishing conditions requiring immediate safety action from those to be addressed in…
  • Documented: coordinating existing-conditions findings with the data inventory and gap analysis
  • ASCE 11-99 Sec. 2 cited by section number
  • Procedure steps recorded in order with evidence
  • Acceptance criterion recorded before the result
  • Independent check signed and dated
  • Existing conditions assessment report with condition ratings and hazard flags. attached and named per the course convention

Section H

Interactive visualization

Existing Conditions Assessment — step-through

Advance one frame at a time. Each frame adds one engineering decision to the previous state.

Stepwise reveal

Step 1 of 6

Walk the site systematically, documenting each element's condition.

Section I

Applicable codes and standards

ASCE 11-99

1999 (R2016) · Sec. 2

Adopted design/analysis reference governing this module.

Relevance: Guideline for structural condition assessment of existing buildings

Reference the section number and edition in your calculation package. Do not reproduce code text.

FHWA-NHI-16-064

2018 · Ch. 4

Adopted design/analysis reference governing this module.

Relevance: Highway bridge inspection condition rating reference

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

  • Recording a condition rating without a photo reference that lets a reviewer verify it.
  • Failing to immediately escalate an observed life-safety hazard rather than saving it for the final report.
  • Treating visual condition assessment rating scales for existing infrastructure elements as a given instead of establishing it from a project record.
  • Producing existing conditions assessment report with condition ratings and hazard flags. without showing how distinguishing conditions requiring immediate safety action from those to be addressed in… was satisfied.
  • Recording the outcome of this module without recording the judgement and evidence that produced it.
  • Missing documenting non-conforming or legacy conditions relative to current code (grandfathering), which is exactly the path to a decision made without a traceable basis.
  • Collecting data before defining what decision the data has to support.
  • Accepting a laboratory or field value without its method, date, operator and uncertainty.
  • Ignoring constructability: a design that cannot be built safely is not a completed design.
  • Omitting the safety check because the strength check passed.
  • Referencing figures, tables, or sources that never appear in the reference list.

Section L

Industry case study

Documented failure related to existing conditions assessment

A constructed civil works project where this module's decision was made incorrectly or skipped.

Official findings

  • Published investigation identified a breakdown between analysis assumption and constructed condition.

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

  • Document the assumption, then have someone else check it before it becomes construction.

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 — civil engineering practice section (record the section number from your handbook edition).

Exam topics

civil engineering practice fundamentals

Handbook formulas

    Weak results here feed your FE Civil Academy weak-area queue for targeted practice.

    Question 1 of 2

    Score: 0/2

    In existing conditions assessment, which item must be established BEFORE the analysis is run?

    Section N

    Apply it to your project — Existing Conditions Assessment

    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.

    QuantityValueUnitSource / record

    Assumptions and consequences

    AssumptionBasisConsequence if wrong

    Self-check before submission

    Section O

    Design challenge

    Consulting challenge — Existing Conditions Assessment

    Your firm has been retained to deliver the existing conditions assessment 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

    Loading editor…
    0 words

    Section Q

    File uploads

    Accepted: PDF, DOCX, XLSX, CSV, PNG, JPG, ZIP

    No files uploaded yet.

    Section R

    Deliverable and advisor review

    Existing conditions assessment report with condition ratings and hazard flags.

    Data quality
    Safety
    Documentation
    Professionalism

    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

    SO 2
    CE-PC1
    CE-PC4
    reinforced

    Existing conditions assessment report with condition ratings and hazard flags. with advisor review and dual scoring.

    Assessment: Faculty rubric score and administrator rubric score on this module's submission.

    Rubric: Data quality · Target: 70% of students at or above 'meets expectations'.

    SO 4
    CE-PC1
    CE-PC4
    reinforced

    Existing conditions assessment report with condition ratings and hazard flags. with advisor review and dual scoring.

    Assessment: Faculty rubric score and administrator rubric score on this module's submission.

    Rubric: Data quality · Target: 70% of students at or above 'meets expectations'.

    Section T

    References and further study

    standard

    ASCE 11-99 (1999 (R2016))

    Adopted reference — cite section numbers, do not reproduce text.

    standard

    FHWA-NHI-16-064 (2018)

    Adopted reference — cite section numbers, do not reproduce text.

    template

    Existing Conditions Assessment — instructor design procedure

    Course template for the calculation package format expected in the final report appendix.

    manual

    NCEES FE Reference Handbook

    Locate the equations used here and note the handbook section for exam recall.

    template

    Advisor meeting agenda item

    Bring the unresolved decision from this module to your next weekly advisor meeting.

    Week 3 · Existing conditions assessment report with condition ratings and hazard flags.
    © 2026 Dr. Steve Efe. Civil Engineering Capstone Studio. All rights reserved.