Rules and Guidelines
Want to participate in the discussions? Please read our Community Rules and Guidelines. Need some help? Visit Support and Answers.

  • Replies 14 replies
  • Subscribers 20 subscribers
  • Views 999 views
  • Users 0 members are here
Options
You may also be interested in

CPD Declaration Dashboard

Allan Rowan

To satisfy my own curiosity, I recently compared my declared CPD hours with the average CPD hours. For an equivalent Membership Type and EC Type, the average number of CPD hours was 113; however in comparison, the hours I had declared was a paltry 36. I sign up for the seminars and in-house training sessions where my availability allows. My question, borne out of curiosity; what is everyone else doing (which I'm not) to achieve an average of 113 hours within their declared CPD?

  • in reply to Sergio Fernandez

    Thanks Sergio, good idea also. I wasn't sure how everyone else approached their CPDs and hadn't really thought about podcasts.

  • in reply to Allan Rowan
    Allan Rowan said:
    because I want to

    I was thinking after I'd written all the above that this has always been my real motivation for CPD - and indeed for being an engineer - i's just because I'm interested in stuff. So I've never found it a problem justifying CPD time, my frustration (and occasionally in my career my employer's / manager's frustration with me) tends to be the pesky day job getting in the way of wanting to explore the interesting new thing I've just found out!

    The engineers that could struggle are those that see their career as a straight nine to five way of earning enough to retire (which is absolutely fair enough), an occupation rather than a vocation, and I think it's for anyone with that mindset that it's really focussed on - just knowing what you were taught when you were 20 is not going to be good enough when you're 60, or even when you're 25.

  • in reply to Andy Millar

    I tend to find it very difficult to capture on the job training, but as you correctly say, it would probably add up to many hours. Even on a long term project, there is often something new to look at, or a potential process improvement to make (because processes always need refinement).

    But it is remembering to capture those hours which is often the challenge. And often I get stuck on the "well, I'm only doing my day job" aspect.

  • I know my CPD has been depressingly low in years and since I've moved into a new role in a new industry, I have a refreshed approach to it. I've had to learn new things quickly and whilst I haven't logged everything I have "done", I have made a better attempt at it.

    Putting seminars/webinars/training on my calendar makes it easy to go back and retrospectively add it in.

    Reading E+T magazine counts - it has a QR code in the contents page which takes you to a pre-populated page to add in your dates and hours.

    A lot of the advice given here all makes a lot of sense and I do sympathise with you in that if I was logging everything I do that is new, I'd be never off the CPD page!

Community Rules & Guidelines