A sick call log is a simple record of when someone reports an illness-related absence, who received the notice, and what follow-up is needed. Use the printable template below to track notifications consistently without recording unnecessary medical details.
What a Sick Call Log Records
In many workplaces, “calling in sick” means notifying a supervisor or designated contact that an employee will miss work or arrive late because of illness. A sick call log records the notification and its administrative details; it is not a medical record, a diagnosis list, or proof that a person is ill. The term can also be used in other settings, such as a school office recording a guardian’s absence notification. The exact fields should fit the organization and its existing attendance process.
A log is most useful when several people might receive absence calls, messages, or emails. Without a shared record, one person may assume someone else notified the schedule coordinator, or a return-to-work question may be left unanswered. A consistent entry creates a basic timeline: notice received, absence period reported, action taken, and current status. It can also help an authorized manager review attendance records, subject to the organization’s policies and applicable requirements.
Who Uses the Log and When
Supervisors, office administrators, shift leads, and attendance coordinators may keep a log, depending on how an organization handles absences. It is especially practical for teams with rotating shifts or more than one person responsible for receiving calls. A small team might keep one paper sheet in a controlled office file; a larger organization might use an approved internal record system. In either case, establish who may enter information and who may review it.
Record a contact when it concerns an absence or late arrival and the organization’s process calls for it. If a worker calls before a shift to say they cannot attend, the receiver can document the time and the dates or shift affected. If the person later updates their expected return, add the update as a new note or follow-up entry rather than silently overwriting the original information. The log should support communication, not replace the organization’s official timekeeping or leave process.
Sick Call Log Template
Use one row per notification. Leave fields blank when they do not apply, and follow your organization’s rules for storing completed records.
| Date and time received | Employee or person reporting | Contact method | Absent date or shift | Reason category | Expected return or update | Received by | Follow-up or status |
|---|---|---|---|---|---|---|---|
Sample (fictional): Jordan Lee; phone; evening shift, 14 May; illness; update expected before the next scheduled shift; received by Casey Morgan; coverage coordinator notified, awaiting update. The names and dates are invented.
Choosing Useful Fields
A log should capture enough information to manage the notification without turning into an informal health questionnaire. Start with the operational basics and add fields only when they serve a clear purpose. Useful fields commonly include:
- Date and time received: Record when the organization received the notice, not merely the date the form was completed.
- Person reporting: Identify the employee or, where appropriate, the person who contacted the organization on their behalf.
- Contact method: Note whether notice came by phone, message, email, or another approved channel.
- Absence period: Record the affected date, shift, or stated duration. If the end date is unknown, say so instead of guessing.
- Reason category: A neutral label such as “illness-related absence” may be sufficient. Avoid requesting a diagnosis unless a separate, authorized process specifically requires information.
- Expected update or return: Enter what the caller actually reported, or note that no estimate was provided.
- Receiver and follow-up: Identify who took the notice and whether a practical task remains, such as informing the scheduling contact.
Labels should be neutral and consistent. “Reported illness; update expected tomorrow” is more useful and respectful than an opinion such as “probably not really sick.” If the caller gives no expected return date, record “not stated” rather than filling in a date based on assumption. A short, factual entry is easier for another authorized person to understand later.
How to Complete and Maintain It
Use the same basic sequence each time so different receivers capture comparable information. A straightforward process is:
- Confirm the caller’s identity using the organization’s normal process, without asking for extra personal information.
- Write down the time and channel through which the notice arrived.
- Clarify which date or shift is affected and whether the caller has an expected return or update time.
- Enter only the details needed to route the notice and manage attendance or coverage.
- Pass on any required operational update to the designated person, then mark that follow-up in the log.
- Add later updates as dated entries so the sequence remains clear.
For example, suppose a fictional employee calls at 6:40 a.m. to report they will miss the 8 a.m. shift and will contact the supervisor again by the following afternoon. The receiver can record the notification time, the affected shift, the caller’s stated update plan, and who was informed about coverage. If the employee later says they expect to return the next day, add the time of that update. Do not change the first entry to make it appear that the initial call contained information that arrived later.
Privacy and Appropriate Detail
Health information deserves careful handling. A routine attendance log generally needs to show that an illness-related absence was reported, not describe symptoms, treatment, medications, or a diagnosis. Collecting extra detail can create avoidable privacy and recordkeeping concerns. If an organization has a separate process for documentation or accommodation requests, keep that process distinct and limit access according to its policies.
Store completed logs where only people with a legitimate work-related need can access them. Do not leave a paper sheet visible to visitors or place sensitive notes in a shared calendar. For electronic records, use the organization’s approved storage and access practices rather than an informal personal account or an unsecured shared document. Retention periods and specific obligations can depend on the setting and applicable rules, so do not assume one schedule fits every organization. For a situation requiring legal, medical, or other professional guidance, ask a qualified professional.
Common Mistakes to Avoid
- Writing down a diagnosis: A call log is usually for notification and coordination. Avoid adding health details that are not needed for that purpose.
- Recording assumptions as facts: Distinguish what the caller said from what the receiver inferred. Use “expected return not stated” when that is accurate.
- Leaving out the affected shift: A date alone can be ambiguous for overnight, split, or rotating schedules. Include the shift or relevant time period.
- Overwriting updates: Replacing an original entry can obscure when information arrived. Add dated updates or use a clear correction method.
- Mixing the log with timekeeping: A notification record does not necessarily establish hours worked, leave approval, or payroll treatment. Use the designated systems and procedures for those matters.
- Keeping duplicate, conflicting copies: Decide which log is authoritative and how receivers should update it. Multiple uncontrolled versions can create mismatched records.
Another common misconception is that a log proves whether an absence was justified. It documents what was reported and what administrative steps followed; it does not independently verify a person’s health or decide how an absence should be treated. Keep those decisions within the organization’s established process.
Paper, Spreadsheet, or Other Record
A printed log is straightforward and works when a small number of authorized staff share a physical office. It is easy to use during a phone call, but handwriting may be hard to read, pages can be misplaced, and access is harder to control if the sheet is left out. Use a designated storage location and a consistent method for adding corrections.
A spreadsheet can make sorting by date or person easier, but it also introduces version and access questions. If several people need to update it, establish a single approved location, clear permissions, and a simple rule for recording later updates. A formal attendance or leave system may be more suitable where one already exists. The best format is the one that fits the organization’s workflow and privacy controls; moving the same unnecessary medical detail into a digital file does not make it more appropriate.
Frequently Asked Questions
What is a sick call log?
A sick call log is a record of illness-related absence notifications. It typically notes when the notice arrived, who reported it, the affected shift or date, and any follow-up required. It is an administrative record, not a diagnosis or medical chart.
What should I write when the person does not know when they will return?
Record that no expected return date was provided, or enter the time of the next update if the caller stated one. Do not invent an estimate. Add a dated entry if the person later provides new information.
Should a sick call log include symptoms or a diagnosis?
For a routine notification log, usually record only the minimum information needed to manage the absence. Follow any separate, authorized process for documentation when one applies, and do not use the call log as a place to collect unnecessary health details.
Can one log be used for several employees?
Yes, if the format provides a separate, legible entry for each notification and access is appropriately limited. Use one row per call or update so a later reader can tell which information belongs to which person and when it was received.
Is a sick call log the same as an attendance or leave record?
No. The log records the notification and related follow-up. An attendance, scheduling, leave, or timekeeping record may serve a different purpose and may be maintained through a separate procedure. Follow the organization’s established process for each record.
How long should a sick call log be kept?
There is no single retention period that fits every workplace or setting. Follow the organization’s records policy and applicable requirements, and ask a qualified professional if the correct period is unclear for a particular situation.
Making the Template Work
Before using the form, decide who receives calls, where the completed log is kept, which fields are necessary, and how updates are added. Share those instructions with anyone expected to take notifications. Review the form occasionally: remove fields no one uses, clarify confusing labels, and make sure the log still supports the actual attendance process. A concise, consistently maintained record is generally more useful than a longer form filled with details that do not help the next person take action.