Fully agree, AFAIK the only time you'd ever be asked to show something like a logbook is as evidence of CPD, and soft copy is definitely ok for that.

Don't bring it to interview, the interviewers will want to talk to you, not sit there reading a logbook!!! ? 

Use it for your own benefit, the most important thing by far is to use a format which is easy to use so that you can keep it up to date and find stuff in it. Soft logbooks are definitely the way to go for this. Provided they are maintainable - make sure it is in a format that can be transferred (even if it's just exporting as a text file) as software systems become obsolete.

Regarding helping you move towards CEng, the benefit of keeping a logbook is that when you come to build your application you should be able to look back on it and remind yourself of what projects you did and when, technical issues you encountered and resolved, training courses etc you took (it's very easy to lose track of these), other pieces of experience you gained that may not be directly related to projects you worked on, etc. It isn't "evidence", because in the end you could write anything in there, but it really should help you when you are trying to remember what you did five years earlier. Include names of key people who you might want to go back to to support parts of your application (and contact details if they offer them, but mostly it's better to find them on LinkedIn when you need to - apart from data protection issues, phone numbers and email addresses go out of date quickly). You will want to carry it with you as you move companies, so don't put anything in, particularly technical details, that are company confidential. 

Besides helping your application, it will also help with creating your CV, and when starting work on a project which relates to work you may have done several years earlier. So good thing to do anyway.

Thanks,

Andy

Fully agree, AFAIK the only time you'd ever be asked to show something like a logbook is as evidence of CPD, and soft copy is definitely ok for that.

Don't bring it to interview, the interviewers will want to talk to you, not sit there reading a logbook!!! ? 

Use it for your own benefit, the most important thing by far is to use a format which is easy to use so that you can keep it up to date and find stuff in it. Soft logbooks are definitely the way to go for this. Provided they are maintainable - make sure it is in a format that can be transferred (even if it's just exporting as a text file) as software systems become obsolete.

Regarding helping you move towards CEng, the benefit of keeping a logbook is that when you come to build your application you should be able to look back on it and remind yourself of what projects you did and when, technical issues you encountered and resolved, training courses etc you took (it's very easy to lose track of these), other pieces of experience you gained that may not be directly related to projects you worked on, etc. It isn't "evidence", because in the end you could write anything in there, but it really should help you when you are trying to remember what you did five years earlier. Include names of key people who you might want to go back to to support parts of your application (and contact details if they offer them, but mostly it's better to find them on LinkedIn when you need to - apart from data protection issues, phone numbers and email addresses go out of date quickly). You will want to carry it with you as you move companies, so don't put anything in, particularly technical details, that are company confidential. 

Besides helping your application, it will also help with creating your CV, and when starting work on a project which relates to work you may have done several years earlier. So good thing to do anyway.

Thanks,

Andy