Templates

30-60-90 day plan for civil engineers

On this page
  1. Set up before the first design task
  2. Licensure and site safety rules to confirm
  3. The 30-60-90 day plan
  4. What to measure
  5. A filled example
  6. What "on track" looks like
  7. The field and the reviewer: two relationships to build early
  8. What the firm owes the new engineer
  9. Common mistakes
  10. Adapting the plan
  11. Questions people ask

A civil engineer usually arrives knowing the engineering: hydraulics, grading, pavement design, structural checks, the software that goes with them. What they do not know is how this firm or agency turns a design into a plan set that a reviewer will approve and a contractor can build. Sheet standards, the QA/QC process, which jurisdictions review the work, how hours are charged to a project budget and who is in responsible charge are different everywhere. A 30-60-90 day plan for civil engineers should teach those conventions on redlines and small tasks, then hand over a real piece of design under a licensed engineer's review, then a submittal package to own through agency comments.

This plan is for the project manager or engineering lead hiring a civil engineer, licensed or an engineer in training, at a consulting firm, a public works department or a design-build contractor. The general structure is in the 30-60-90 day plan template for new hires. If the role is still open, the civil engineer phone screen questions cover design judgment and software experience before the offer.

Set up before the first design task

A new engineer cannot produce a usable sheet until the basics are in place. Name an owner for each item and set up as much as you can before day one.

ItemOwnerNeeded before
CAD and design software licenses, the firm's templates and project folder accessCAD manager or ITOpening any project drawing
Plan set standards and the QA/QC checklist, in writingEngineering leadThe first sheet submitted for internal review
Project codes, task budgets and time entry rulesProject managerThe first timesheet
Site safety orientation and PPESafety lead or construction managerThe first site visit
Accounts on agency submittal and permit portalsProject managerThe first submittal they prepare
Design manuals and standard details for the main jurisdictionsEngineering leadAny design in that jurisdiction

Licensure and site safety rules to confirm

Engineering licenses are issued by state boards. According to NCEES, whose members are the state engineering and surveying licensing boards, licensure candidates typically pass the FE and PE exams, most states require four years of acceptable, progressive and verifiable work experience, and only a licensed engineer can prepare, sign, seal and submit engineering drawings. NCEES also notes that many states offer other paths, so check the board in each state where the firm works. If the hire is not yet licensed, name the PE in responsible charge of their work in the plan itself. If they are licensed, confirm the license on the state board's lookup before the start date.

Civil engineers who design or inspect excavations should also know where OSHA's construction rules put engineering judgment. Under 29 CFR 1926.651(k), a competent person must inspect excavations, adjacent areas and protective systems daily, before work starts and after every rainstorm or other hazard-increasing event, when employee exposure can be reasonably anticipated. Under 29 CFR 1926.652, sloping, benching and support systems that do not use the other permitted options must be approved by a registered professional engineer, and tabulated data used for a design must identify the engineer who approved it and be kept at the jobsite during construction. This is current as of October 2026 and is not legal advice; confirm state rules with counsel or the safety lead.

The 30-60-90 day plan

30-60-90 day plan — [Name], Civil Engineer, [group]
Reports to: [project manager / engineering lead]   Start: [date]
License: [PE state(s) / EIT]   PE in responsible charge: [name]
Main clients/jurisdictions: [list]   Software: [CAD / design tools]
Buddy: [senior engineer]

DAYS 1-30 — Learn the conventions on real work
Goals:
- Tools, templates and project folders working
- Read the plan set standards, QA/QC checklist and the design
  manuals for the two main jurisdictions
- Pick up redlines, quantity takeoffs or a cost estimate on a
  live project (example: update a grading sheet after review)
- Visit at least one active site with the project engineer
- Sit in on a project kickoff and a client or agency meeting
Deliverables by day 30:
- First sheets through internal QA/QC, findings logged by type
- Time charged correctly to project codes every week
Check-in: day 30, with project manager

DAYS 31-60 — A design piece under review
Goals:
- Take one design element end to end (example: a storm sewer
  layout with hydraulic calculations, or a site grading plan)
- Write the calculations to the firm's format so a reviewer
  can check them without asking
- Prepare the response letter for one round of agency comments
- Answer RFIs on an active construction job, reviewed first
Deliverables by day 60:
- Design element reviewed by the PE, comments closed
- QA/QC findings on new sheets falling against the first ones
Check-in: day 60

DAYS 61-90 — Own a submittal
Goals:
- Own a submittal package (example: a site plan or a utility
  permit) from assembly through the first agency review
- Track hours against the task budget and flag overruns early
- Present their design at an internal design review
Deliverables by day 90:
- Submittal made with a clean QA/QC record and a comment log
- Written status of the owned package with risks and dates
Check-in: day 90 — full review

What to measure

Sheet counts say little on their own. Measure quality, review cycles and budget, and set targets from the firm's own project history. The standards below are examples only.

MeasureWhy it mattersExample standard (example only)
Internal QA/QC findings per sheetShows whether the standards are learnedFewer findings on later sheets than on the first ones
Agency review rounds per submittalEvery extra round delays the client's scheduleEach comment answered in full in the first response
Hours against task budgetOverruns found late cannot be billed or recoveredOverruns flagged before they happen, not after
RFI turnaround on construction jobsSlow answers stop work in the fieldWithin the time the contract or the PM sets
Calculation package completenessThe PE has to be able to check and seal itReviewer has no questions about inputs or sources

A filled example

Civil engineer: Marcus Bell (invented), an engineer in training with two years at a site contractor, joining the land development group of a mid-size consulting firm.

Day 30: Completed redlines on two grading sheets and a quantity takeoff for a bid set. QA/QC findings were mostly about sheet conventions: label styles, north arrows and note numbering. Visited a subdivision under construction and met the contractor's superintendent.

Day 60: Designed the storm sewer for a small commercial site, with calculations reviewed by the PE in responsible charge. Drafted the response to the county's first review comments and answered three RFIs with the project engineer's review.

Day 90: Assembled the site plan submittal and tracked it through the first county review. Flagged a likely overrun on the drainage task two weeks before it would have happened, and the PM agreed a change with the client. Licensure plan agreed: PE exam once the state's experience requirement is met.

What "on track" looks like

CheckpointOn trackWorth a direct conversation
Day 30Sheets through QA/QC; site visited; time coded correctlyStill asking where the standards are; no field time
Day 60A design element the PE could check without reworkCalculations the reviewer cannot follow; comments reopened
Day 90A submittal owned with a comment log and budget statusOverruns discovered at invoice time; status unclear

The field and the reviewer: two relationships to build early

Most rework in civil design comes from two places: the field, where something drawn cannot be built as shown, and the agency reviewer, whose checklist the engineer did not know. Both are cheap to learn early. Send the new engineer to a site where their group's design is being built and ask them to bring back three things that differed from the plans and why. Then have them read the last set of review comments from each main jurisdiction before their first submittal. Patterns show up quickly: a county that always asks for the same detail, a city that wants calculations in a specific order. Engineers who learn these patterns early write submittals that pass in fewer rounds.

What the firm owes the new engineer

  • A named PE in responsible charge who reviews their work on a set schedule, not when there is time.
  • Budgeted hours for learning, such as redlines and site visits, so the engineer is not penalized for ramp-up.
  • Agency and client introductions before they have to answer comments alone.
  • A clear licensure policy: whether the firm supports exam fees, study time and experience documentation.

Common mistakes

MistakeResultFix
Starting with a full design packageMany QA/QC comments on basic conventionsRedlines and takeoffs first
No field timeDesigns that cannot be built as drawnSite visits in the first two weeks
Hours not tracked by taskBudget overruns found after the factWeekly budget check with the PM
Unclear responsible chargeWork that no PE has properly reviewedName the PE in the plan

Adapting the plan

  • Public agencies: replace the submittal with plan review on the agency side, such as checking a developer's drainage report against the design manual, and add the agency's procurement and capital project process.
  • Design-build contractors: add estimating, submittal review and field engineering, and coordinate with the construction project manager on RFIs and change orders.
  • Transportation, water or structural groups: swap the examples for that discipline's work, such as a signal timing plan, a pump station calculation or a connection design, and its design standards.
  • New graduates: extend the redline phase, add weekly reviews with the buddy and plan the FE exam timing if the firm supports licensure.

For engineers who will also work on mechanical systems, the 30-60-90 day plan for mechanical engineers shows how a change process ramps. If you are still sourcing, the boolean search strings for civil engineers help find candidates with the right discipline and license.

Questions people ask

What should a new civil engineer do in the first week?

Get the CAD templates, project folders and time codes working, read the firm's plan set standards and QA/QC procedure, and visit at least one active job site with the project engineer. Then pick up a set of redlines or a quantity takeoff on a live project so they learn the firm's conventions on real work with low risk.

Does a new civil engineer need a PE license?

Not always on day one, but someone on the project does. NCEES, whose members are the state engineering and surveying licensing boards, notes that only a licensed engineer can prepare, sign, seal and submit engineering drawings. Many new civil engineers start as engineers in training working under a PE in responsible charge. Check the rules with the board in each state where the work is done. This is not legal advice.

How do you measure a civil engineer's first 90 days?

By QA/QC redlines per sheet falling over time, agency review comments answered in fewer rounds, hours on assigned tasks tracked against the budget, and one design package or submittal owned with a clear status. Set targets from the firm's own project history rather than an industry figure.

When should a new civil engineer go to the job site?

In the first two weeks, with the project engineer or construction manager. Seeing how a grading plan, a storm sewer or a pavement section is actually built teaches more about constructability than any review comment, and it gives the engineer contacts in the field before they have to answer RFIs.