Timeline for At the end of contracting work (IT/Programming), what steps need to be taken to protect myself from any technical issues company might have
Current License: CC BY-SA 3.0
18 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 23, 2016 at 2:58 | comment | added | nigelhanzo | I have a checklist of items to be handed over for many of my freelance projects Such as codes, documents(password, usernames, user guides etc)... In my agreement i also stated that upon handing over all the items, i am required to be paid within 10 working days.. the project manager will usually check and sign the checklist.. so far no issues.. | |
| Aug 23, 2016 at 1:23 | comment | added | Anthony | Why is it necessary for you to even ask in the first place? This should be unnecessary in an well run company... | |
| Aug 23, 2016 at 1:21 | answer | added | Anthony | timeline score: 1 | |
| Mar 3, 2016 at 10:39 | vote | accept | joshuaty | ||
| Feb 29, 2016 at 23:01 | comment | added | ChrisLively | Fact of life: you're no longer working with them. Of course you are going to be blamed for everything from a light bulb going out to the new guy being late to work. Doesn't matter if you're a contractor or an ex employee; it's still going to be your fault. | |
| Feb 29, 2016 at 22:45 | answer | added | mcknz | timeline score: 1 | |
| Feb 29, 2016 at 22:03 | history | tweeted | twitter.com/StackWorkplace/status/704426691469426688 | ||
| Feb 29, 2016 at 19:50 | comment | added | mcknz | @joshuaty companies typically disable user accounts at the end of the contract, so changing your password may not be necessary. Your only obligation is to notify/confirm the end date with your employer, and not attempt to access your account after that date. | |
| Feb 29, 2016 at 19:36 | history | edited | joshuaty | CC BY-SA 3.0 |
added 283 characters in body
|
| Feb 29, 2016 at 19:30 | comment | added | joshuaty | I think as well as actually changing the critical passwords, my thinking was to inform everyone that we are changing them, this is purely to deter blame. | |
| Feb 29, 2016 at 15:41 | answer | added | gnasher729 | timeline score: 1 | |
| Feb 29, 2016 at 14:59 | comment | added | Brandin | If you've memorised your password already and want to forget it, you could change your password to a randomly generated one, and then don't record that password anywhere else. Use copy/paste to avoid unintentionally memorising the new password. | |
| Feb 29, 2016 at 14:22 | answer | added | Old_Lamplighter | timeline score: 0 | |
| Feb 28, 2016 at 16:10 | comment | added | keshlam | How do you know passwords haven't already been changed? Also, you have absolutely no business checking, and you should destroy all record of the old oassword so it can't be stolen from you - or at the vety least put it behind extremely strong encryption -- or you haven't done your part in maintaining security. If you do your job right, whether they do theirs right is not your problem. | |
| Feb 27, 2016 at 23:32 | answer | added | Kilisi | timeline score: 5 | |
| Feb 27, 2016 at 23:26 | answer | added | paparazzo | timeline score: 6 | |
| Feb 27, 2016 at 23:18 | review | First posts | |||
| Feb 28, 2016 at 18:10 | |||||
| Feb 27, 2016 at 23:18 | history | asked | joshuaty | CC BY-SA 3.0 |