How to prepare a factory timesheet: example with shifts, overtime and leave days

Monday, 06:10: on the paint line the night shift is leaving and the morning shift is arriving. The line supervisor is trying to settle two questions with the list in hand. Which day does the shift that started Saturday at 22:00 belong to? Why does the operator who was on leave on Friday show as “absent”? On top of that, three people on the morning shift stayed two hours longer than planned; how many had approved overtime, and how many were just waiting at the machine? This is why timekeeping in a factory is harder than in an office. This article gives a sample timesheet for shift-based production and the steps for reading it correctly.

A factory timesheet is a monthly work sheet that shows, on a single row, each employee’s planned shift, actual clock-in and clock-out, overtime and leave days in a business running shift-based production.

Why is a factory timesheet different from an office timesheet?

• Shifts run into the next day. On a night shift, clock-in belongs to one day and clock-out to the next; without a rule, the same shift gets split across two days.
• The plan changes. Shift swaps, team moves and urgent production orders update the plan often; if the timesheet closes against the old plan, it will be wrong.
• Overtime is common. When orders peak, overtime rises line by line; who stayed, at what time and with which approval must be on record.
• There is more than one recording point. The turnstile, the line terminal and the shift supervisor’s list can show the same person at different times.

Factory timesheet example: one employee’s weekly table

The table below is fictional. It shows how Employee A’s plan, actual punches and other records turn into a timesheet code. “O2” is a sample code meaning two hours of approved overtime on that day.

Two points stand out in the table. No punches on Wednesday is not absence but approved leave; you can only make this distinction if the leave record is matched with the timesheet. Because Friday night’s clock-out falls on Saturday, Saturday may look “not worked”, but that morning’s punch is the end of the shift that belongs to Friday. Decide once, as a company rule, which day a night shift is recorded on; the common practice is the day the shift starts.

Monthly timesheet example: summary by line

Daily rows are too detailed for a manager. At month end, a summary table by line shows both the data going to accounting and the open issues at a glance. The figures below are fictional; the aim is to show the logic of the columns.

The “Open exceptions” column is the real checkpoint for closing. Every non-zero value means that a late arrival, a missing clock-out or an unexplained absence is still waiting for an answer. The period should not be locked until this whole column is zero. Otherwise the figure that goes to payroll preparation becomes an estimate that will have to be corrected again next month.

How do you keep timesheets in a shift-based factory? Six steps

1. Publish the plan at the start of the period. Without a daily, weekly or monthly shift plan, you cannot tell who was late or who left early.
2. Collect actual punches in one place. Turnstile, terminal and manual entries should be merged under the same employee ID.
3. Enter shift changes in the plan. If swaps and moves are not recorded, at month end anyone can say “I wasn’t there that day”.
4. Link overtime to a request and an approval. Time spent outside the plan should be recorded as overtime if there is an approved request, and as an open exception if not.
5. Enter leave and sick notes. Do not mark a day without punches as absent before matching it with leave records.
6. Close weekly. Each line supervisor should close their own team’s exceptions every week, so nothing piles up at month end.

In a small factory there is no need to set up everything at once. Start by publishing the plan and comparing it with actual punches; even this single step makes the question “is the plan wrong or is the record missing?” visible. In the second stage, link overtime to requests and approvals; in the third, match leave records with the timesheet. Each stage prepares the ground for the next and gives employees time to adjust. It is also important to involve line supervisors from the start; even if they do not keep the records, they interpret the exception list with knowledge from the floor and know which record a correction should start from.

For line supervisors, these questions make a sufficient checklist during the weekly close: Is there a difference between the planned shift and the actual punches? Is the reason for the difference written down? Is every day without punches matched with a leave or sick record? Is there an overtime request for every period spent outside the plan? Is the night shift’s clock-out linked to the right day? A week that gets “yes” to these five questions brings no surprises at month end.

How do I show overtime and leave in a factory timesheet?

Defining in advance how each situation appears in the timesheet, and which record backs it up, stops arguments. The table below is a starting suggestion; adapt your policy to your own workflow.

Where do Excel and paper factory timesheets work, and where do they break down?

In a small, single-shift workshop, a paper list and Excel are often enough. With multiple shifts, problems snowball: the shift supervisor keeps their own list, HR pulls the turnstile report separately, leave stays in e-mail. Three different results come out for the same person, and at month end there is an argument over whose record counts. In Excel, formulas that split the night shift in two, columns that miss a swapped shift and cells that change quietly after the period is closed make this mess even less visible.

How do factory timesheets work with YazSis KurumsalPortal?

• Plan: Shift & Overtime Planning creates daily, weekly and monthly shifts, assigns the team, checks for conflicts, notifies changes and links overtime requests to approval.
• Actual: Time & Attendance Control merges punches on one screen, matches them with employees and sends late arrivals, early departures and absences for approval as exceptions.
• Leave: with Mobile Leave Management, employees create leave requests from their phone browser without installing an app; the request goes through manager and HR approval, and approved leave is entered in the calendar.
• Result: because attendance records are matched with leave records, leave days are separated from absences, and the timesheet is produced from this clean data.

If you want to see how the modules work together for a shift-based site, start with the KurumsalPortal page and look at the plan and attendance flow on the related module pages.