All outcomes
Skills

Civil Structural Analysis and Design

8 weeks · 0 milestones

Perform structural analysis and design of a real or representative civil structural element — a beam, column, slab, or simple frame — to a named structural code (Eurocode 2/3, ACI 318, AS 3600, or equivalent). The analysis must include: load combination calculations to the applicable standard (dead, live, wind, and/or seismic loads as applicable), section design or section adequacy check with documented calculation steps and code clause references for each check, deflection calculation and verification against code limits, a summary table of all utilisation ratios (capacity used / capacity available) for the governing failure modes, and a statement of the critical failure mode. Preferred proof: structural analysis for a real project (academic, professional, or community). Accessible alternative: SkyCiv free tier (browser-based structural analysis software) for a published worked example or standard structural design scenario — input file and output results required, not screenshots alone; OR a complete hand calculation using documented methodology with free reference material (Eurocode and ACI 318 are available through university open access). Proof artifacts: the loading diagram and calculation (analysis artifact) and the design summary with code clause references (documentation artifact). Verification: a structural engineer reviews the governing failure mode — 'you checked flexure but not lateral-torsional buckling; under what conditions would that govern?' — requiring you to reason beyond your submitted calculation.

Milestone map

Milestone map

3 milestones

Define the Civil Structural Problem and Loading

1–2 weeks (2–3 hrs/week)

Define a civil structural analysis problem: a reinforced concrete beam or slab, a steel portal frame, a masonry wall, a retaining wall, or a bridge girder. Specify the geometry (span, section dimensions), material properties (concrete grade, reinforcement, steel grade), and loading to Eurocode or equivalent: permanent loads (self-weight), variable loads (imposed floor load, wind, snow), and the relevant load combination. State which failure mode governs the design check: bending (ULS flexure), shear (ULS shear), deflection (SLS), or cracking (SLS). Civil structural analysis is load-combination-driven — a single load case without the governing combination is incomplete.

Proof required

Submit your problem definition document (≥500 words): structural description with geometry and material grade, permanent and variable loads with Eurocode load combination applied (e.g. 1.35G + 1.5Q), and the governing failure mode stated for the design check.

What gets checked

  • Load combination is applied using the named standard (e.g. Eurocode EN 1990 combination 6.10 or equivalent)
  • Geometry and material grade are stated specifically — not 'a typical beam'
  • Governing failure mode is identified before calculation — yield, shear, or serviceability

Common mistakes

  • Loading defined without applying a code load combination — structural design is not based on characteristic loads alone; the factored combination (ULS) or unfactored (SLS) must be explicitly applied
  • Material grade omitted — 'concrete' and 'steel' are not material specifications; C30/37 and S275 are

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

  • Confirm load combination cites the standard and applies the correct factors — flag unfactored loads used for ULS check.
  • Confirm material grade is specified — flag 'concrete' or 'steel' without a grade.
  • Confirm governing failure mode is identified before M2 analysis begins.

Perform Section Design and Verify Capacity

3–4 weeks (4–5 hrs/week)

Design the critical section to resist the governing failure mode at ULS and check a serviceability limit state. For a reinforced concrete beam: calculate the required tension reinforcement area using the rectangular stress block method (EC2), then check shear capacity and deflection. For a steel beam: calculate the design moment resistance (plastic or elastic), check shear, and verify lateral-torsional buckling. For a retaining wall: check sliding, overturning, and bearing capacity. Show all calculations with the design code equation references and material partial factors applied.

Proof required

Submit your section design calculations: design equation cited with EC2/EC3 clause number (or equivalent), all material partial factors applied, required reinforcement area or section size, and a ULS check plus one SLS check with utilisation ratios.

What gets checked

  • Design code clause number is cited for each design equation — not just the formula without attribution
  • Material partial factors are applied correctly (γc = 1.5 for concrete, γs = 1.15 for reinforcement in EC2)
  • Both ULS and one SLS check are performed — not just the ultimate limit state

Common mistakes

  • Using characteristic material strength without applying the partial factor — EC2 uses design strength fd = fk/γm; using fk directly in the design equation is unconservative
  • Checking ULS but not SLS — serviceability (deflection, crack width) is always required for civil structures and often governs residential and light-commercial floor design

Resources

Foundationstart here

Depthgo deeper

What a verifier looks for

  • Confirm design code clause number is cited for each equation — flag any equation used without a code reference.
  • Confirm material partial factors are correctly applied — flag characteristic strengths used as design strengths.
  • Confirm both ULS and at least one SLS check are performed.

Write the Structural Design Report

2–3 weeks (2–3 hrs/week)

Write a complete civil structural design report (1,500–2,500 words plus calculations appendix) covering: structure description and loading, applied load combinations, design method and code references, section design results (reinforcement area, section size, or wall dimensions), utilisation ratios for ULS and SLS, and a construction note (what information would a contractor need from this report to build the element). Have the report reviewed by a structural engineer or civil engineer and respond to Q&A on the design decisions and code compliance.

Proof required

Submit your structural design report (1,500–2,500 words plus calculations appendix) and review record: reviewer name, role, ≥3 challenge questions about design decisions or code compliance, and your responses.

What gets checked

  • Report includes a construction note specifying what a contractor needs — reinforcement arrangement, cover, concrete grade, or equivalent
  • Utilisation ratios for both ULS and SLS are reported — not just a pass/fail statement
  • Reviewer has structural or civil engineering experience and challenged the design decisions or code compliance specifically

Common mistakes

  • Report without a construction note — a structural design report is not complete until it contains the information a contractor needs to build the element; 'provide adequate reinforcement' is not a construction instruction
  • Reviewer without structural engineering experience — EC2/EC3 Q&A on partial factors, load combinations, and SLS checks requires domain knowledge

Resources

Foundationstart here

What a verifier looks for

  • Engineering Design Triad check: M1–M3 together produce a design artifact (section design + construction note), an analysis artifact (ULS/SLS calculations with code equations and utilisation ratios), and a documentation artifact (structural design report + review record) — confirm all three types are present.
  • Confirm construction note is present and specifies contractor-actionable information.
  • Confirm utilisation ratios for both ULS and SLS are reported numerically.
  • Confirm reviewer has structural or civil engineering experience.
  • The Proof Accessibility Rule applies — MIT OCW (free), Eurocodes portal (free excerpts), Concrete Centre free guides, Steel Construction Institute free resources, and ICE free materials are all accessible without commercial licence.

We use analytics to improve Powstik. No ads, ever.