Technical information to pass on.

[HappyAdmin]

Having taken over here about 6 months ago, and having been fortunate enough to have a short overlap with my predecessor during which I was able to ask many questions and make copious notes, I'd say that the most important things are passwords (which you clearly have covered) and "foibles." All those weird, non-standard things that resulted from a peculiar set of circumstances requiring something weird to be done - like the licence manager for a piece of software that requires a certain server to have a user logged in for that software to work anywhere in the school because it won't run as a service... For all the standard stuff the documentation is helpful, for the weird, site-specific things it is a lifesaver!

Good for you for doing this!

[kennysarmy]

Any specific software installation notes.

 

Locations of software where only a specific number of licences have been purchases.

 

List of jobs you had on your to do list, short, medium and long term.

 

Warranty information and when key kit was planned to be replaced.

 

End of year procedures?

Start of year procedures?

 

Imaging procedure.

[hardtailstar]

Thanks all,

 

I have all of the above some in greater detail then others.

 

Anymore to add?

[timbo343]

Which members of staff are the ones to avoid/whiney ones or the ones who are actually really friendly and understand.

[Trapper]

This is my performance management task for this year.

 

I've always wanted, and after inheriting two networks with no information, known it's just good cricket to provide a full, and proper documented network to your successor. Especially if you have the time to do it.

 

I'll admit to laziness over the past four years as the reason why I haven't, when I handed my seconded school over I just gave him my office number. Yes, he figured it out very quickly but it wasn't right. That's why I've set it as my PM task, if I don't do it I don't get a payrise next year!