Civil, Structural and Construction Engineering

01Purpose and scope

• This manual supports the course Civil, Structural and Construction Engineering. It describes how the work is actually carried out from early site assessment through design, procurement, construction oversight and handover, so that a practitioner can use it as a reference during day-to-day tasks.
• The scope covers buildings, bridges, retaining structures, roads, drainage and utility corridors, and the temporary works that support them. It treats the engineer as one participant in a team that includes owners, architects, contractors, inspectors and regulators. It does not teach the underlying mechanics or the detailed code equations, which are covered in design texts and in the adopted standards themselves.
• This guidance does not replace qualified professional judgment, approved procedures or required authorization. Structural and geotechnical decisions carry life safety consequences, and the licensed engineer of record, the building official or the owner's representative holds responsibility for them. Where local rules differ, the current adopted code and the agency with jurisdiction are the authoritative sources.

02Core principles

• Load paths must be traceable. Every element that carries load should have a clear route down to the ground, and every connection on that route should be designed, detailed and built to transfer the forces assigned to it. Most serious failures trace back to a path that was assumed rather than confirmed.
• Design intent must survive the drawing set. A specification, a shop drawing or a site modification can quietly change an assumption such as a bearing capacity, a concrete strength or a rebar spacing. Engineers treat every issued document as a statement that must be reconciled with the others.
• Ground conditions are a measured input, not a guess. Foundation and earthwork decisions rest on borings, test pits, groundwater observations and laboratory results. Where the data are thin, the design should say so and carry an explicit contingency.
• Constructability and durability are part of the design. A structure that is correct on paper but cannot be formed, placed, compacted or inspected in the field will generate requests for information, rework and schedule pressure. Good practice tests the design against the means and methods the contractor is likely to use.
• Uncertainty is managed, not eliminated. Tolerances, safety factors, load combinations and inspection hold points exist because inputs vary. The practitioner documents what is assumed and what would change the conclusion.

03Planning and preparation

• Start by defining the project boundary, the governing codes, the owner's performance requirements and the basis for compensation and schedule. Confirm which jurisdiction applies and which edition of the adopted code governs the permit. For public works, the agency's own design manual often adds requirements beyond the model code, and those additions usually control.
• Collect existing information before proposing anything. This includes record drawings, prior geotechnical reports, survey control, utility locates, hazardous material surveys for demolition, and photographs or condition assessments of any existing structure to be retained. Missing records are themselves a finding that should be reported to the owner in writing.
• Set the design basis early and keep it on one page. The design basis lists design life, occupancy or traffic classes, live and environmental loads, seismic or wind parameters, material strengths, exposure conditions, serviceability limits such as deflection and crack width, and any acceptance criteria the owner has set. Each item should cite its source.
• Decide the deliverables and their levels of completion. A concept package, a permit set, a bid set and a construction set differ in detail and in the level of risk they carry. Agree with the project team which decisions are frozen at each stage and which remain open.
• Identify stakeholders and their approval roles. Typical roles include the engineer of record who seals the documents, a peer reviewer for complex or high-risk elements, the geotechnical engineer, the contractor's engineer for temporary works, the special inspector and the authority having jurisdiction. Write these roles down so that nobody assumes another party has checked a detail.

04Recommended workflow

1. 1
   : Confirm scope, site access and the design basis with the owner, then record any open questions as formal items with owners and due dates. Do not begin detailed calculations until the governing loads and performance criteria are written and accepted.
2. 2
   : Review existing documents and conduct or commission a site reconnaissance. Note visible distress, drainage paths, adjacent structures, buried services and access constraints. Photograph conditions and log them with location references.
3. 3
   : Establish geotechnical parameters from the available investigation. If the investigation is incomplete, define the additional borings or probes needed, their cost and schedule impact, and the conservative assumption used until results are in.
4. 4
   : Develop the structural or civil concept. Compare at least two realistic options on cost, constructability, durability, maintenance and risk. Keep the comparison short enough to be read by the owner and the contractor, and record why the preferred option was chosen.
5. 5
   : Perform analysis and sizing using accepted methods and software that have been verified for the problem type. Keep hand checks for key members and for the governing load cases. Save input files, version numbers and output summaries with the project record.
6. 6
   : Prepare drawings and specifications in a coordinated set. Cross-check dimensions, levels, bearing elevations, reinforcement schedules, anchor locations and utility crossings across disciplines. Issue a clear list of assumptions that the contractor must verify in the field.
7. 7
   : Run internal review at the stages defined in the quality plan. A reviewer who did not prepare the calculations should trace the load path, check the governing combinations, and confirm that drawings match the calculations. Record comments and their resolution.
8. 8
   : Support procurement and submittals. Review shop drawings, mix designs, steel mill certificates, precast details and temporary works designs against the intent of the design. Respond to requests for information within an agreed time and in writing.
9. 9
   : Provide construction phase oversight at the hold points set in the specification. These typically include foundation bearing verification, reinforcement placement before concrete, post-tensioning or anchor installation, backfill compaction and critical connection tightening. Observe, measure and record, and do not accept verbal approvals.
10. 10
    : Close out the project by collecting as-built information, issuing record drawings, documenting deviations and their approvals, and handing over operation and maintenance requirements. Confirm that inspection and testing records are complete before releasing the final certificate or sign-off.

05Quality checks, risk controls and compliance

• Quality checks should be planned, not improvised. A typical quality plan defines which calculations are independently checked, which drawing sheets receive a second review, which field tests are required, and who signs each record. The plan should also state the acceptance criteria for each test, such as minimum concrete compressive strength at a given age, compaction percentage relative to a laboratory maximum density, or required bolt pretension.
• Risk controls focus on the events that could cause harm or major cost. For structures these include progressive collapse, overturning during erection, excavation instability, settlement of adjacent buildings, flooding of work areas, and failure of temporary shoring. For a deep excavation, for example, the engineer should identify the shoring system, the monitoring points on adjacent structures, the trigger levels for movement and the response plan if a trigger is reached.
• Temporary works need the same discipline as permanent works. Formwork, falsework, shoring, cranes and lifting plans should be designed or reviewed by a competent person, and the design should state the loads, the sequence of removal and the conditions under which the work must stop. Many site incidents come from removing supports before the concrete has reached the required strength.
• Compliance is jurisdiction specific. Building codes, road design standards, environmental permits, worker safety rules and utility clearance requirements each come from different authorities and change over time. Use the current adopted version and confirm any amendments with the authority having jurisdiction. Where an alternative method is proposed, document the basis for equivalence and obtain approval before relying on it.
• Materials and workmanship need traceable evidence. Keep certificates, test reports and inspection records linked to the element they describe. Nonconforming material should be marked, isolated and dispositioned by the engineer, and the decision should be recorded rather than handled informally on site.

06Collaboration and documentation

• Good collaboration depends on clear documents and short decision loops. Use a single issue register for drawings and specifications, a request for information log with response times, and a change register that shows the reason for each change, its cost and schedule effect, and the approving party. Each entry should be traceable to the source document.
• Calculation records should be complete enough that another engineer could reproduce the result without asking the author. Include the design basis, the load cases, the method, key assumptions, the software version, the governing result and the reviewer's initials and date. Store calculations in the project record, not in personal folders.
• Site communication benefits from a regular cadence. A weekly coordination meeting with the contractor, the inspector and the designer, supported by a short written action list, prevents many small misunderstandings from becoming disputes. When a site problem arises, record what was observed, what was proposed, who approved it and what drawing or note was updated.
• Drawings should show intent, not just geometry. Notes that state the design assumptions, the tolerance expected, the inspection required and the sequence where it matters help the contractor build the right thing. Avoid general notes that conflict with specific details, and resolve conflicts before issue.
• Be cautious about informal changes. A verbal instruction from the owner, a phone call with the contractor or a marked-up photograph may be useful, but it is not a design change until it is documented, checked and issued. Clear records protect the engineer, the owner and the public.

07Measures and continuous improvement

• Track indicators that show whether the work is controlled. Useful measures include the number of open requests for information and their average age, the percentage of calculation packages checked before issue, the count of design changes after construction starts, inspection hold points passed on first presentation, and the number of nonconformance reports closed within the agreed period. Interpret these as signals rather than targets, since a low count can also mean issues are not being reported.
• Measure field outcomes as well. Concrete test results, survey movement readings, settlement records, punch list counts and warranty calls each show how well the design and construction matched. Compare them against the criteria set during planning, not against memory of how the project felt.
• Use lessons from each project to update templates, checklists and standard details. After a project closes, hold a short review with the design, construction and inspection teams. Record what the design assumed, what the field found, which drawing notes were misread and which checks caught real errors.
• Recognize the limits of local data. A small firm may have too few projects to draw statistical conclusions, and a single failure is rarely representative. Use external guidance and peer experience with care, and state the basis when a change in practice is proposed.

08Common mistakes and how to prevent them

• Designing to a load case that was never confirmed is a frequent error. Prevent it by writing the design basis early, getting it accepted, and checking that the analysis uses the agreed values rather than defaults left in a template.
• Assuming soil bearing without a site investigation leads to settlement and cracking. Prevent it by requiring a minimum investigation for the structure type and by documenting the conservative assumptions used until data arrive.
• Allowing drawings to disagree is common when disciplines work in separate files. Prevent it with a coordination meeting before each issue, overlay checks of foundations, embedded items and utility crossings, and a clear rule that the most recent approved revision governs.
• Neglecting temporary works leads to collapse during construction even when the permanent design is sound. Prevent it by requiring a designed temporary works plan, a named competent person for each high-risk activity and a documented stop-work trigger.
• Accepting substitutions without analysis causes many field problems. Prevent it by requiring the contractor to submit the proposed change with calculations and drawings, and by refusing approval until the equivalence is demonstrated.
• Closing out without as-built information leaves the owner with incomplete records for future work. Prevent it by building as-built capture into the construction schedule and by making record drawings a condition of final payment where the contract allows.
• Relying on verbal approvals creates disputes later. Prevent it by confirming every site decision in writing on the same day and filing it with the relevant drawing or inspection record.

09Practical checklist

• Confirm the jurisdiction, the governing code edition and any agency amendments before starting design.
• Record the design basis with loads, materials, exposure, serviceability limits and source references, and obtain acceptance from the owner.
• Review existing records and conduct a site reconnaissance with photographs and location notes.
• Confirm that the geotechnical investigation is adequate for the structure type, or define the additional work and the interim assumptions.
• Compare at least two realistic concept options on cost, constructability, durability and risk.
• Assign an independent checker for governing calculations and for high-risk elements.
• Cross-check drawings across disciplines for levels, bearings, embedded items, anchors and utility crossings.
• Confirm that temporary works are designed or reviewed by a competent person, with removal sequences and stop-work triggers stated.
• Verify that submittals, substitutions and field changes are analyzed and approved in writing before use.
• Hold inspections at the defined hold points and record results, measurements and acceptance decisions.
• Track requests for information, design changes and nonconformances in registers with owners and dates.
• Collect as-built information, issue record drawings and confirm that all test and inspection records are complete at closeout.
• Review the project with the design, construction and inspection teams and update templates and checklists with the lessons learned.

10

★Learning sources

• Micro Degree: Civil, Structural and Construction Engineering
• Micro Degree: Data Analytics Applications
• Micro Degree: Azure Cloud Fundamentals
• Micro Degree: Google Cloud Platform Basics