Example Achievement Log for a Civil Engineer
Below is a Civil Engineer's running log across a single review year, tracking design revisions, site inspections, budget challenges, and one significant setback that led to a process change. This example shows how specific project names, failure modes, and named feedback make the difference between a credible record and a blank memory at review time.
A year in the life of a Civil Engineer's log
- Jan - task: Started on Riverside Drive widening survey. GPS-based cross-section data collected for 2.4 km stretch, but discovered 0.6 m vertical discrepancy between county records and field reality at chainage 1100. Had to backtrack and retake levels manually.
- Feb - feedback: Email from Caltrans reviewer Maria Chen: 'Your revised drainage calcs caught an issue we'd have missed. Good eye on the shoulder infiltration rates.' Said it in a routine compliance call but worth noting.
- Feb - achievement: Riverside Drive design progressed to 60% PS&E. Reduced concrete volume 18% by optimizing slab thickness per soil bearing capacity from Phase II geotechnical, saving ~$340k without compromising design life.
- Apr - task: Attended six contractor pre-construction meetings for Riverside. Coordinated utility relocations with PG&E and water district; flagged three coordination conflicts in the baseline schedule that would have delayed mobilization.
- May - achievement: Permit package for Riverside Drive submitted. CEQA Initial Study approved first review cycle. City planning sign-off took two rounds but final conditions met; no major rework needed on traffic or archaeology sections.
- May - task: Spent 8 days on foundation condition assessment for retrofit project on 3rd Avenue. Inspected 24 piers, documented spalling and reinforcement exposure. Report flagged 3 critical and 7 moderate defects needing urgent repairs.
- Jul - feedback: Spoke with project architect James Wu after the 3rd Avenue foundation inspection. He said, 'That pier report was thorough. You caught the chloride contamination issue we'd have addressed too late.' Included in design memo.
- Aug - achievement: Riverside Drive construction commenced. Final inspection of site prep, grade control, and utility clearances passed. Only one minor RFI during first four weeks of concrete pours; zero change orders yet.
- Oct - task: Seized up mid-review of as-built drawings for Bay Street project. AutoCAD file corruption lost two days of revisions; realized our team had no backup protocol. Rebuilt drawings from PDFs and implemented automated daily saves with shared folder.
- Nov - achievement: 3rd Avenue retrofit construction phase kick-off. Prepared detailed repair sequencing plan. Coordinated with structural specialist to stage concrete removal around existing occupancy; zero lane closures during phase 1.
- Dec - task: Year-end site inspection of Riverside widening. Pavement at 94% complete. Encountered unexpected settlement in fill zone near chainage 840; worked with contractor to investigate and adjust compaction protocol for final section.
What makes a strong entry
What most people write: Reduced concrete costs on Riverside Drive project through design optimization.
What went in the log: Reduced concrete volume 18% by optimizing slab thickness per soil bearing capacity from Phase II geotechnical, saving ~$340k without compromising design life.
The strong version names the specific method (slab thickness optimization tied to actual geotechnical data), the percentage savings, and the dollar figure, making it verifiable and credible instead of vague credit-taking.
What most people write: Conducted foundation inspection for retrofit project and identified defects.
What went in the log: Inspected 24 piers, documented spalling and reinforcement exposure. Report flagged 3 critical and 7 moderate defects needing urgent repairs.
The strong version specifies the count of elements surveyed, the damage types observed, and the severity breakdown, giving a reviewer concrete evidence of rigor and letting them judge the significance themselves rather than relying on assertion.
How this becomes your review in November
This year I delivered two major projects from design into construction. On Riverside Drive, I reduced concrete volume 18% through slab thickness optimization based on Phase II geotechnical data, saving approximately $340,000 without compromising design life, and brought the project through permitting in two rounds with no major rework. On the 3rd Avenue retrofit, I completed a foundation condition assessment across 24 piers and flagged 3 critical and 7 moderate defects, which the project architect credited as thorough work that prevented delayed repairs downstream. I also learned from a failure: after AutoCAD file corruption cost two days on the Bay Street project, I implemented automated daily backups and a shared folder protocol that the team now uses across all active jobs.
Starting your own log
Don't try to reconstruct a year you have already had. Start from today, one line whenever something happens, and let it build. The Perform Review Achievement Log does this for you and can capture wins straight from Slack, and how to start an achievement log covers the wider playbook.
Example Logs for Related Roles
Ready to start your own? Start your Achievement Log free, see how the Perform Review Achievement Log works, or browse performance review phrases for Civil Engineer.