Engineering Project Delivery

A scope and work breakdown you can measure against, a critical path schedule, an interface register, weekly progress by rules of credit, change control, honest forecasts and reports, through to engineering close-out.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Engineering Project Delivery, and click Install. It goes into your own files, and works offline from then on.

Before you start: this plan is general information to help you organise your own work. It does not replace your professional judgement, the rules of your regulator or professional body, your firm's policies, or advice from a qualified lawyer, accountant or other adviser. Where a law, code or standard applies, use the current official version for your country, and get qualified sign-off on regulated or safety-critical work.

What it installs.

1

Pillar

1

Area

50

Projects

200

Starter tasks

🔧 Engineering Practice

Engineering Project Delivery

Running an engineering project from scope to handover: work breakdown, schedule, interfaces between disciplines, progress measurement, change control and reporting.

  1. Project charter and agreed scope statement
  2. Contract obligations digest for the delivery team
  3. Work breakdown structure to deliverable level
  4. Master deliverables register with hour budgets
  5. Rules of credit for each deliverable type
  6. Responsibility matrix for disciplines and client
  7. Engineering project execution plan
  8. Baseline critical path schedule
  9. Interface register between disciplines and contractors
  10. Project risk register and first risk workshop
  11. Kick-off meeting with client and discipline leads
  12. Weekly deliverable progress measurement
  13. Weekly schedule update and three-week look-ahead
  14. Earned value tracking with CPI and SPI
  15. Monthly client progress report
  16. Hours and cost-to-complete forecast
  17. Scope change control and trend log
  18. Weekly interface coordination call
  19. Action log and decision register
  20. Technical query tracking with the client
  21. Vendor data and long-lead item tracker
  22. Monthly risk and opportunity review
  23. Quarterly lessons learned capture
  24. Critical path method and float by hand
  25. Earned value fundamentals for engineers
  26. Contract models for engineering work compared
  27. Scheduling tool proficiency in P6 or Project
  28. Writing escalations and bad-news updates
  29. Reviewing a contractor's schedule for realism
  30. Choosing a project controls toolset
  31. Recovery plan for a slipping engineering schedule
  32. Shortening client review cycles on deliverables
  33. Make or buy decision for a discipline's scope
  34. Design and procurement overlap decision
  35. One-page project dashboard for leadership
  36. Resource loading and levelling across disciplines
  37. Design freeze and scope freeze milestone
  38. Issue for construction drawing push
  39. Client project controls audit preparation
  40. Independent mid-project health check
  41. Engineering close-out and final document handover
  42. First project as a discipline lead
  43. Stepping up from design engineer to project engineer
  44. Taking over a project mid-stream
  45. Manager overseeing a portfolio of small projects
  46. Plant engineer delivering minor brownfield projects
  47. Work-share execution across two engineering offices
  48. Schedule risk analysis with P50 and P80 dates
  49. Contemporaneous records for delay and change disputes
  50. Productivity norms from completed projects

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Project charter and agreed scope statement

Most engineering projects start with a purchase order, a few emails and a client who assumes far more is included than the proposal said. A two-page charter that states the objective, what is in and out of scope, the key dates, the budget authority and who signs off gives everyone one reference point before the first hour is booked.

First tasks

  • Pull the scope, exclusions and assumptions out of the winning proposal
  • Draft the two-page charter with in-scope and out-of-scope columns
  • Walk the draft through with the client's project representative
  • File the approved charter in the project document register

Contract obligations digest for the delivery team

Engineers rarely read the contract, then discover in month four that the client has 15 working days to review every drawing, that liquidated damages attach to one milestone, or that overtime is not reimbursable. A plain-language digest of the obligations that affect delivery puts those clauses in front of the people who actually trigger them.

First tasks

  • Read the scope of work, schedule and special conditions in one sitting
  • List every review period, milestone and notice requirement with its clause
  • Ask the commercial lead to check the digest for misreadings
  • Brief the discipline leads on the five clauses most likely to bite

Work breakdown structure to deliverable level

Schedules, budgets and progress reports are only as good as the structure underneath them. Breaking the scope down by area, discipline and deliverable, with a numbering code that the timesheets, the schedule and the document register all share, means hours, dates and documents finally add up to the same answer.

First tasks

  • Sketch the top two WBS levels on one page by area and discipline
  • Decompose each branch to packages one person can own
  • Check every charter scope item against the breakdown
  • Ask finance to load the WBS codes into the timesheet system

Make it yours.

Install Engineering Project Delivery, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.