01Three dates decide whether an hour exists
The first is the effective date on the agreement your school holds with the site, which is not the date you signed anything and not the date somebody told you it was fine to begin. The second is the date your programme approved that specific preceptor, which is a separate approval with its own paperwork. The third is the date the term's logging window opens, because many systems will not accept an entry outside it.
An hour that falls outside any of the three is unpaid in every sense of the word. Get all three in writing before the first shift and put them at the top of your own record, because when a total is disputed at the end of a term this is the layer everybody argues about and almost nobody documented at the time.
02Reconciliation at three checkpoints
Your school's system holds the number that counts. Your own parallel record is the only instrument that can correct it, and it can only do so while the term is open. That asymmetry is the whole reason for keeping a second record, and it is why the checkpoints matter more than the format.
- First week: confirm the system holds the right start date, the right preceptor and the right site
- Mid-term: compare your running total against the system's and resolve the difference that week
- Before the evaluation is signed: reconcile once more, because a signature closes the record
- Any week an entry is rejected: fix it immediately, since rejections do not queue politely
- After any correction is accepted: re-read the running total, because a repaired entry sometimes replaces rather than adds
- Keep the parallel record somewhere you can export, as access to a school system ends with the term
03What a defensible entry contains
Date, start and end times, the site, and the person who supervised you. Then the part people skip: a description of what you did, written in the vocabulary your programme uses for its objectives or competencies. At the end of the term that log gets read against those objectives, not against your memory of a Tuesday, and an entry saying you saw patients tells a reviewer nothing they can map.
Write the entry the same day, while the shift is still specific. A log filled in on a Sunday to cover five shifts is a reconstruction, and reconstructions round the times, merge two encounters into one and describe the competency you can remember rather than the one you actually met. It shows: five rows in near-identical phrasing, every one of them ending on the hour. A reviewer reading a whole term of entries at once sees that pattern before anything else.
Learn the exclusions before week one rather than in week ten. Programmes differ on orientation, on documentation time, on travel and on hours spent in activities that are not direct care, and every one of those rules lives in a handbook sentence you can find in ten minutes. Logging excluded time is not a small error; it inflates a total you are relying on, and the correction always arrives late.
04When the totals disagree at the end
Send one message containing your record, the three dates and the preceptor's evaluation, and ask for a specific correction rather than a review. A request naming the entries, the dates and the difference is something an administrator can act on that afternoon. A request asking somebody to look into it goes into a queue behind everything else that is also unclear.
If the deficit turns out to be real, no argument recovers it and the only remedy is more hours inside a window that is still open. That is precisely why the mid-term checkpoint exists, because a shortfall found halfway through is a scheduling problem and the same shortfall found at the end is a delayed graduation.
Where the paperwork rather than the clinical work is what is failing, the whole administrative layer can be handed over on its own, and that is the shape placement ops normally takes.
FAQQuestions to control
Can I log hours before the agreement is finalised?
You can write them in your own record, and you should, but do not expect them to count. The effective date on the agreement is what an auditor reads, and a countersignature does not reach backwards. If a site invites you to start early, the useful reply is to ask for the effective date in writing first, then treat anything before it as observation rather than as banked hours.
What should the parallel record actually be?
Anything you control and can export, which for most people means a spreadsheet with a row per shift. It needs the same fields the school's system asks for, plus the three governing dates at the top. Screenshots of submitted entries are worth keeping alongside it. The format matters far less than the fact that it exists outside a system whose access ends with your term.
My preceptor changed halfway through. What breaks?
The approval attached to the first preceptor does not transfer, so a new approval and often a new agreement have to be in place before hours under the second one begin. Hours already logged under the first remain valid. The risk sits in the gap: shifts worked while the second approval is still being processed, which is the same effective-date problem in a different coat.
Who signs off the final total?
Usually your preceptor attests to the hours and your faculty accepts them, which means two people have to agree with a number that your record and the school's system have already agreed on. Reconcile before you ask anyone to sign, because a signature on a total you later want to change turns a five-minute correction into a formal request.
