Initial Professional Development (IPD)

Build the right experience. Develop sound judgement. Put yourself in a position to pass.

Initial Professional Development is the stage where you move from being an engineer who follows guidance to one who makes decisions and stands behind them.

It is not a period of passive experience. It is an active process where you build the capability, judgement, and professional awareness expected of a Chartered Engineer.

If approached properly, IPD does two things:

• it develops you into a competent professional

• it puts you in a position to pass the Professional Review first time

You can find formal guidance on IPD on the ICE website, and it is worth reading that alongside this page. What follows is a practical interpretation based on real reviews and mentoring experience.

A Note on Perspective

This guidance reflects the view of someone who has reviewed and mentored a large number of candidates through to Professional Review.

It is not official ICE wording, and it should not replace direct guidance from ICE or your Supervising Civil Engineer.

Use it to sharpen your understanding, but always discuss your approach with your Supervising Civil Engineer and agree a plan that works for your specific situation.

What IPD Actually Is

IPD is the structured process of developing your competence against the ICE attributes.

It is the most common route to becoming Chartered. Once your IPD is complete and signed off, it unlocks your ability to sit the Professional Review.

There are three main routes:

• an ICE-approved training scheme

• mentor-supported training

• career appraisal after self-managed development

The first two involve structured IPD, where your development is tracked and guided over time.

The career appraisal route is different. It is used when you have already built sufficient experience independently. Instead of completing structured IPD, you submit evidence to show that you already meet the required level and are ready to attempt the Professional Review.

Regardless of the route, the standard is identical. ICE is not interested in how you got there. It is interested in whether you can demonstrate the required competence clearly and convincingly.

The Purpose of IPD

IPD exists to bridge the gap between academic learning and professional responsibility.

At university, you learn theory and methods.

In industry, you are expected to:

• apply those methods in real situations

• deal with incomplete information

• balance competing constraints

• take responsibility for outcomes

The purpose of IPD is to build your ability to do this consistently.

It is about developing judgement.

The Shift in Thinking

The defining change during IPD is how you think.

Early in your career, you are focused on:

• getting calculations right

• following standards

• completing assigned tasks

As you develop, the focus shifts to:

• selecting appropriate approaches

• understanding why decisions are made

• considering risk, cost, safety, and sustainability together

• taking responsibility for decisions and their consequences

You move from answering questions to asking them.

You move from doing work to shaping it.

How Engineers Actually Develop

Workplace learning is not structured like education. You are expected to drive it yourself.

Most learning comes from:

• observing experienced engineers

• discussing decisions and approaches

• asking questions

• working through real problems

• reflecting on outcomes

Strong engineers are deliberate about this.

They do not just complete tasks. They try to understand:

• why a decision was made

• what alternatives were considered

• what risks were involved

• what the consequences were

They also pay attention to how experienced engineers think, not just what they do.

Over time, this builds instinct and judgement.

Reflection Is Where Growth Happens

Experience on its own does not lead to development.

The key step is reflection.

After a piece of work, you should be able to explain:

• what happened

• why it happened

• what went well

• what could have been done differently

• how it will influence your future decisions

Without this, experience is quickly forgotten and difficult to use later.

With it, even small tasks become valuable evidence of competence.

Using the Attributes Properly

The ICE attributes are not just an assessment tool at the end.

They are a development framework.

Each attribute must be demonstrated at three levels:

• knowledge, what you understand

• experience, what you have done

• ability, what you can decide and justify

Strong candidates use the attributes from the start to:

• plan their development

• identify gaps early

• choose the right opportunities

• track their progression

Weak candidates leave this until they start writing their report, which makes everything harder.

What You Should Be Developing

Technical competence is expected. It is not what sets you apart.

You are developing the ability to balance multiple factors at once, including:

• technical performance

• cost and programme

• safety and risk

• sustainability and environmental impact

• buildability and maintenance

• stakeholder and public expectations

Real engineering decisions sit at the intersection of these.

You need to show that you understand this and can operate within it.

Responsibility and Progression

A clear sign of development is increasing responsibility.

Over time, you should move from:

• assisting with tasks
  to

• taking ownership of defined elements
  to

• influencing decisions and outcomes

This does not require a specific job title. It is about the level of responsibility you take and the decisions you contribute to.

Reviewers are looking for evidence that you:

• made decisions

• understood their implications

• took responsibility for outcomes

Breadth and Awareness

Breadth is often misunderstood.

It does not mean doing every type of role.

It means understanding how your work connects to the wider system, including:

• design and analysis

• construction and delivery

• operation and maintenance

• clients, contractors, and stakeholders

• environmental and societal impacts

You should be aware of how decisions made in one stage affect others.

This is what demonstrates professional awareness.

Managing Your Development

IPD requires structure.

You should have:

• a development action plan

• regular reviews of progress

• a clear understanding of your gaps

• a strategy to address those gaps

You are also expected to carry out Continuing Professional Development alongside IPD.

This includes formal and informal learning such as:

• training courses

• reading and research

• industry events

• discussions with colleagues

• mentoring relationships

The expectation is not just that you learn, but that you plan, record, and review your learning.

Recording Evidence Properly

Your records are critical.

You should regularly capture:

• your role on a project

• the challenges you faced

• the options you considered

• the decisions you made

• the outcomes

• what you learned

Good records are:

• specific

• clear

• reflective

They focus on your contribution, not the project as a whole.

If you do this consistently, preparing your Professional Review Report becomes straightforward.

If you do not, it becomes a struggle to reconstruct your experience later.

The Role of Mentors and SCEs

If you are on a structured route, your Supervising Civil Engineer or mentor plays an important role.

They help you:

• interpret the attributes

• plan your development

• identify gaps

• challenge your thinking

• stay on track

But they do not carry you through the process.

You are still responsible for your own development.

This is why regular discussion and agreement with your Supervising Civil Engineer is essential. Alignment early on avoids problems later.

Common Mistakes

There are a few consistent issues that slow candidates down:

Describing tasks instead of decisions
You need to explain what you decided and why.

Waiting for opportunities
You need to actively seek experience that fills your gaps.

Ignoring reflection
Without it, experience does not translate into competence.

Poor record keeping
This leads to weak, vague submissions later.

Treating IPD as a formality
It is the core of your preparation, not a box to tick.

When IPD Is Complete

IPD is complete when you can demonstrate that you are operating at the level of a professional engineer.

This means you can:

• make sound engineering decisions

• explain and justify those decisions clearly

• understand wider implications of your work

• integrate technical, commercial, and environmental considerations

• show how your judgement has developed over time

At that point, you are ready to sit the Professional Review.

This is not based on time served. It is based on capability.

Final Thought

IPD is where most candidates either set themselves up properly or create problems that surface later.

If you take control of your development, use the attributes properly, reflect on your experience, and build clear evidence as you go, the Professional Review becomes a natural next step.

If you drift through it, you will find yourself trying to fix gaps at the last minute.

Treat IPD seriously, and everything that follows becomes easier.