Staff Record & Development Log

In this browser, on this device, and nowhere else. There is no account, no upload and no server copy — the tool has no way to send anything anywhere. That is deliberate: a record holding absence, capability concerns and formal warnings is the last thing that should be sitting on somebody else's server, and the honest way to promise that is not to build the upload path at all. The trade is that the log lives on one machine, so use "Back up" regularly and keep the file wherever your school keeps staff records.

"Download as PDF" opens your browser's print dialogue — choose "Save as PDF" as the destination. It prints whatever the current filters show, so you can produce one person's full year, or every formal warning across the department, or a single term, without editing anything. Each printed log carries the department, the date it was printed, who keeps it, and a signature line for both the head of department and the member of staff.

That is what the print layout is for. Filter to one member of staff, print the log, and it comes out as a dated, ordered record with the observation and training entries in place — which is the part of a teacher's evidence folder that is hardest to reconstruct in June if nobody wrote it down in October. Entries you have marked as shared with the member of staff are labelled as such, since an unshared concern and a discussed one are not the same evidence.

That is a decision for your school's policy, not for this tool — but the tool assumes the answer is usually yes. There is a "shared with the member of staff" tick on every entry, it is printed, and the entry form says plainly that what you write may be read back in a formal process. Write it as though it will be, because it may be.

Once the page has loaded, yes. Everything runs in the browser and nothing calls out, so you can keep a log in a classroom with no signal, on a train, or during an inspection week when the school wifi is being used by four hundred people at once.