Technical Competency 1.8: The Project or Asset Life Cycle

Every engineering project, whether an asset-specific project focused on a particular component or a multi-year public infrastructure program, moves through a recognizable sequence of stages. This sequence begins when an idea is first proposed and continues through implementation and the eventual review of its results. An engineer who has only ever worked inside one of these stages, always doing detailed design, for instance, can struggle to see how their own contribution fits into a larger sequence involving budgets, tenders, contractors, regulators, and end users. Technical Competency 1.8 asks engineers to demonstrate that they understand this broader life cycle: not that they have personally led every stage, but that they are aware of what happens at each one, who is involved, and what concerns typically arise along the way.

Description of Technical Competency 1.8

Technical Competency 1.8 requires an engineer to demonstrate exposure to, and awareness of, the stages that a typical engineering project or process passes through, along with the project concerns and stakeholder roles associated with each one. The competency, as outlined in the Competency-Based Assessment (CBA) guidelines published by most Canadian professional engineering regulators using the 34-competency framework, describes an applicant who has:

"been exposed to the stages of a process or project life cycle"

The regulators that use the 22-competency framework, such as APEGA, frame the same underlying idea around a somewhat longer arc. Their definition asks an engineer to demonstrate exposure to a project or process life cycle that carries on

"through design, implementation, operation, and maintenance, and on to decommissioning and retirement,"

extending well past the point where a project is completed and handed over, into how it is operated, maintained, and eventually retired. Whichever version an applicant is assessed against, the underlying expectation is the same: an engineer should be able to place their own work within the bigger picture of a project's life, rather than only within the task directly in front of them. At its core, this competency is built around six identifiable stages, illustrated in Figure 1.

1. Identification is where a project begins, as an initial idea is generated and shaped into a preliminary design.
2. Preparation follows, translating that idea into a detailed design that addresses both the technical requirements and how the project will actually be operated once complete.
3. Appraisal tests the project from several angles at once, weighing its technical, financial, economic, social, institutional, and environmental merits. Once a project clears appraisal,
4. specifications and tender document preparation packages the design into a form that contractors and suppliers can bid on, covering everything from preparing tender documents to evaluating bids and awarding the work.
5. Implementation and monitoring is where the project is actually carried out, with progress tracked and fed back into decisions along the way. Finally,
6. Evaluation closes the loop, reviewing what happened and feeding lessons into the next project cycle.

Figure 1: The Six Stages of an Engineering Project or Process Life Cycle

Identification and Preparation: How a Project Takes Shape

The first two stages of the life cycle are where a project takes form before a single dollar is spent on construction or fabrication. Identification is deliberately open-ended: someone recognizes a need, a gap, or an opportunity, and turns that recognition into an initial project idea, usually accompanied by a rough, preliminary design that establishes scale and feasibility. Preparation narrows that idea considerably. It is where an engineer develops a detailed design, working through technical requirements such as loads, capacities, materials, and layouts, alongside operational aspects: how the finished project will actually be run, staffed, and maintained once it exists.

At this stage, an engineer's role is not only to produce drawings and calculations but also to understand who else has a stake in the outcome. Owners are concerned with cost and schedule. Operators are concerned with maintainability and day-to-day usability. Regulators are concerned with compliance. Recognizing these differing concerns early, before a design is locked in, is part of what this competency is assessing.

Example # 1 – Municipal Civil Engineering Application

Consider a mid-sized municipality where population growth has pushed an existing wastewater treatment plant close to its licensed capacity. Identification begins when the utility recognizes this constraint and commissions a preliminary study, a rough estimate of future flows, a high-level look at expansion options, and an early cost range, enough to justify moving forward. Preparation follows once council approves further work. Here, the engineering team develops a detailed design for the plant expansion, sizing new treatment trains and specifying equipment, while addressing how existing operations will continue safely during construction. Throughout preparation, the design has to account not just for hydraulic and process requirements, but also for how operators will run the expanded plant, how maintenance access will work, and how the utility will meet its provincial discharge approval once the new capacity is online.

Notice what this example actually does. It does not simply state that the engineer "was involved in a plant expansion." It names the two stages separately, states specifically what happened in each one, a preliminary study with rough numbers during identification, a detailed design addressing both process requirements and future operability during preparation, and connects those actions to the people who would eventually run the plant. When you draft your own response for this stage, the same structure works: identify which of the six stages your experience actually falls under, then describe your specific contribution within it rather than the project as a whole.

Why Appraisal Looks at More Than the Engineering?

Once a detailed design exists, it still has to prove itself worth building. Appraisal is the stage where a project is tested from technical, financial, economic, social, institutional, and environmental perspectives, often at the same time and sometimes against conflicting priorities. A design can be technically excellent and still fail appraisal if it is not affordable, if it does not deliver enough economic benefit relative to its cost, if it draws serious community opposition, if it does not fit the mandate of the agency that would operate it, or if its environmental impact cannot be adequately mitigated.

For an engineer, participating in appraisal means being able to step outside a purely technical frame and contribute to, or at least understand, an analysis built on more than one discipline's criteria. It also means recognizing that a project can be redesigned, delayed, or cancelled at this stage for reasons that have nothing to do with whether the engineering itself is sound.

Example # 2 – Renewable Energy Engineering Application

Consider a proposed run-of-river hydroelectric project on a river system shared with several other users. The technical appraisal confirms that the site has sufficient head and flow to support the proposed turbine capacity. The financial appraisal tests whether projected power sales can cover construction financing and operating costs over the project's life. The economic appraisal looks more broadly at regional benefits, such as local employment during construction, weighed against the opportunity cost of the capital involved. The social appraisal involves consultation with nearby communities and Indigenous groups whose traditional use of the river may be affected. The institutional appraisal confirms that the developer holds the regulatory approvals and operating agreements needed to proceed, and the environmental appraisal assesses impacts on fish passage, downstream flow, and aquatic habitat. Only once all six lenses are satisfied, sometimes after redesign, does the project move forward to procurement.

From Design to Contract: Specifications and Tendering

With a project appraised and approved, the design has to be translated into a package that contractors and suppliers can actually bid on. This stage involves preparing specifications and tender documents, inviting qualified bidders, opening submissions, and often conducting pre-qualification to confirm that bidders have the capacity and experience to do the work safely and competently. Bids are then evaluated, not always on price alone, and the work is formally awarded.

This stage carries its own set of stakeholder concerns. Owners want fair, transparent competition and value for money. Bidders want clear, unambiguous specifications so they can price the work accurately without excessive contingency. Regulators and, in the public sector, oversight bodies want a procurement process that can withstand scrutiny. An engineer preparing tender documents is effectively translating a design into a legal and commercial instrument, where an ambiguity that seemed harmless on a drawing can turn into a costly dispute once construction begins.

Example # 3 – Transportation and Structural Engineering Application

Consider a provincial transportation authority preparing to rehabilitate an aging highway bridge. The engineering team prepares tender documents that specify the scope of work, required materials, quality standards, and schedule constraints, including lane closures that must be minimized during peak travel periods. Prospective contractors are pre-qualified based on their experience with similar structural rehabilitation work and their safety record. Once tenders are opened, bids are evaluated against both price and technical merit, since the lowest bid is not automatically the one best able to deliver the specified quality within the stated timeline. The contract is ultimately awarded to the bidder judged best able to meet the technical specifications, schedule, and budget together.

For this stage in particular, a reviewer is looking for evidence that the applicant understood tendering as more than paperwork, since an ambiguity in a specification tends to become someone else's problem, and possibly someone else's dispute, later on. A strong response names a specific decision made during specification writing or bid evaluation, such as why a pre-qualification criterion was set a certain way, or why the lowest bid was not the one recommended, rather than simply stating that tender documents were prepared.

Implementation, Monitoring, and Evaluation: Closing the Loop

Implementation is where the project moves from paper to reality. Activities proceed according to the awarded contract, but rarely without some deviation from plan, so monitoring runs alongside it: tracking progress against schedule and budget, inspecting work for quality and safety, and feeding any problems back into decisions in real time rather than discovering them only at completion. This is also where an engineer's role often shifts from design authority to field oversight, reviewing contractor submissions, responding to site conditions that were not fully anticipated, and confirming that what gets built matches what was specified.

Evaluation is the final stage, and the one most often skipped in practice. It involves a periodic, and ideally a final, review of how the project performed against its original objectives, cost, schedule, and quality, with the findings fed back into how the next similar project is planned. Without this step, an organization risks repeating the same avoidable problems on every subsequent project.

Example # 4 – Power Utility Engineering Application

Consider a substation upgrade undertaken to accommodate projected load growth in a service area. During implementation, the engineering team monitors construction progress, quality, testing, and commissioning to confirm that the upgraded facilities are completed and energized as designed.

Following energization, the team monitors transformer and substation loading over the approved revenue horizon to assess whether the expected demand materializes. A subsequent cost true-up compares the actual project costs and resulting utilization against the assumptions used to justify the investment, confirming whether the costs have been appropriately recovered from the customers for whom the investment was made. The results are documented and used to inform future load forecasts, investment decisions, and project justification.

Conclusion

Competency 1.8 is less about mastering project management as a discipline and more about developing situational awareness: recognizing which stage a project is in, what is expected during that stage, and who else is affected by decisions made there. An engineer does not need to have personally led identification, appraisal, tendering, and evaluation on the same project to satisfy this competency. What matters is being able to describe, from direct experience, how a project moved through some of these stages, and showing an understanding of the concerns that owners, operators, regulators, communities, and contractors bring to each one.

In practice, this awareness shows up in an engineer who can explain why a design decision made during preparation has consequences during tendering, or why a compromise reached during appraisal shapes what gets monitored during implementation. Seeing the project life cycle as a connected whole, rather than a series of disconnected assignments, is what this competency is ultimately asking engineers to demonstrate.

Disclaimer:

The information provided in this blog is for general informational purposes only. While every effort has been made to ensure the accuracy of the content, the author does not guarantee the technical precision or completeness of any project details mentioned. The views expressed in this blog are based on publicly available information and personal insights and may not reflect the latest developments or technical changes. Readers should verify all technical information and consult relevant professionals before making any decisions based on the presented content.