Biweekly timesheets: how to track two weeks of hours without errors
A biweekly timesheet looks like one form covering fourteen days, and that is where most mistakes start. The pay period is two weeks long, but under the US Fair Labor Standards Act the hours that decide overtime are counted one workweek at a time. A person who works 30 hours in week one and 50 in week two has worked 80 hours, the same as two 40-hour weeks, yet 10 of those hours are overtime. A sheet that only shows a 14-day total hides that.
This article covers how to lay out a biweekly timesheet so each week stands on its own, how to total it, what the federal recordkeeping rules ask employers to keep, where small teams usually go wrong, and when a free template stops being enough. The federal rules quoted here come from the US Department of Labor's Wage and Hour Division fact sheets as read on October 8, 2026. State law can add requirements on top, so check the rules where the team works.
What a biweekly timesheet is, and what it is not
A biweekly timesheet records hours for a pay period of two consecutive weeks. Pay goes out every other week, which works out to 26 pay periods in most years. Because a year is 52 weeks plus a day or two, the calendar occasionally produces a 27th biweekly payday, which matters for anyone who divides an annual salary by 26.
Biweekly is often confused with semimonthly. A semimonthly schedule pays twice a month, typically on fixed dates, for 24 pay periods a year. Semimonthly periods do not line up with workweeks: a period can start on a Wednesday and contain parts of three different weeks. Biweekly periods, by contrast, can be set to contain exactly two full workweeks, which makes the overtime math cleaner if the sheet is built for it.
The other confusion is between the pay period and the workweek. The Department of Labor's Fact Sheet #23 on overtime describes the workweek this way: a fixed and regularly recurring period of 168 hours, seven consecutive 24-hour periods. It does not have to match the calendar week and may begin on any day and at any hour. The same fact sheet states that averaging hours over two or more weeks is not permitted.
That single sentence is the reason a biweekly timesheet needs two weekly totals, not one. Overtime for covered, non-exempt employees is owed for hours worked over 40 in a workweek, at not less than one and a half times the regular rate. The pay period is when the money moves; the workweek is how the hours are judged.
How to lay out a biweekly timesheet
Most downloadable templates follow the same broad shape, and the details below are what separate a sheet that works from one that causes disputes.
Header
- Employee name and an ID if the business uses one.
- The pay period start and end dates.
- The day and time the workweek begins. This is often missing from templates, yet the federal recordkeeping list includes it.
- Manager or approver name.
Body: two blocks, not one
Split the fourteen days into two clearly separated blocks of seven, Week 1 and Week 2. For each day, record:
| Column | Why it is there |
|---|---|
| Date and day | Lets a reviewer match entries to a calendar |
| Time in / time out | Shows when work happened, not just how long |
| Unpaid break | Subtracted from the day's hours |
| Daily hours | In and out minus breaks |
| Project or task (optional) | Needed when hours are billed to clients or cost centers |
| Notes | Explains anything unusual, such as a late start |
At the bottom of each weekly block, show regular hours (up to 40) and overtime hours (over 40) for that week. Then add a pay period summary that sums the two weeks' regular hours and the two weeks' overtime hours separately.
Signatures
Leave space for the employee and the approver to sign or confirm, with dates. A signature does not make the numbers right, but it records that both sides saw them before payroll ran.
Totaling hours: a worked example
Take an employee whose workweek runs Sunday to Saturday, paid hourly, with a 30-minute unpaid lunch each day.
Week 1: Monday to Friday, 9:00 to 17:00 each day. That is 8 hours minus 0.5 for lunch, or 7.5 hours a day, 37.5 hours for the week. Regular hours: 37.5. Overtime: 0.
Week 2: Monday to Thursday, 8:00 to 18:30 each day (10.5 hours minus 0.5, so 10 hours a day), plus Friday 9:00 to 17:00 (7.5 hours). Total: 47.5 hours. Regular hours: 40. Overtime: 7.5.
Pay period: 85 hours worked. Regular 77.5, overtime 7.5.
Now consider what happens if the sheet only kept a 14-day total and assumed 80 hours was the overtime threshold. It would show 85 hours, flag 5 hours of overtime, and underpay 2.5 overtime hours. The error runs the other way too: a two-week total of 78 hours looks like no overtime, but if it splits into 30 and 48, there are 8 overtime hours owed.
Minutes and decimals
Convert minutes to decimal hours before adding them up. Fifteen minutes is 0.25, thirty is 0.5, forty-five is 0.75. Adding clock times directly, such as treating 7:45 as 7.45, is one of the most common sources of small errors that add up across a team. If the business rounds time to the nearest quarter hour or similar, apply the same rule to every entry and write it down in the team's policy so everyone knows how it works.
What federal recordkeeping asks for
The Department of Labor's Fact Sheet #21 on recordkeeping says the law requires no particular form for the records, but requires that they be accurate. Its list of basic records for non-exempt workers includes, among other items:
- Time and day of week when the employee's workweek begins.
- Hours worked each day.
- Total hours worked each workweek.
- Basis on which wages are paid, and the regular hourly rate.
- Total daily or weekly straight-time earnings.
- Total overtime earnings for the workweek.
- Total wages paid each pay period, the date of payment, and the pay period covered.
Note the pairing again: hours are recorded per day and per workweek, wages per pay period. A biweekly timesheet that records only the pay period total does not on its own produce the weekly totals on this list.
On retention, the same fact sheet says payroll records should be kept for at least three years, and records on which wage computations are based, such as time cards, wage rate tables, and work and time schedules, for two years. It also states that employers may use any timekeeping method, including a time clock or having workers write down their own times, as long as the method is complete and accurate.
For a small team, the practical takeaway is simple. Whatever tool is used, it must be possible to pull out daily hours and weekly totals for any past period, and the files must survive at least as long as the retention periods above.
The errors that cost small teams money
The calculator and template pages that rank for this topic explain how to fill in the boxes. The problems that actually cause back pay, disputes, or unhappy staff tend to come from process, not arithmetic.
Treating 80 hours as the threshold
Covered above, and worth repeating because it is the most expensive. Any sheet, formula, or payroll setting that checks "over 80 in the period" instead of "over 40 in each week" is wrong for non-exempt staff under federal rules.
Filling the sheet in at the end of the period
When people reconstruct two weeks from memory on the last Friday, entries drift toward round numbers and planned hours rather than worked hours. Daily entry, or at minimum a weekly entry for each block, keeps the record close to what happened.
Approving the period, not the weeks
A manager who reviews fourteen days at once tends to check the total and sign. Reviewing each week as it closes catches the 50-hour week while there is still time to rebalance the second week, and it spreads the review work evenly.
Changing a submitted sheet without a trail
Corrections happen. The risk is a sheet edited after approval with no record of who changed what. Keep the original, note the correction, and have both sides confirm it.
Mixing employees and contractors on one form
Contractors are often asked for timesheets too, because hours are the basis for their invoices. The rules and expectations are different: overtime under the FLSA applies to covered employees, and whether a worker counts as an employee or an independent contractor is a legal question that depends on the facts. Use separate forms and processes, and get advice when classification is unclear.
Template, spreadsheet, or timesheet tool
A free biweekly template, whether a PDF, Word, Excel, or Google Sheets file, is a reasonable starting point for a team of a few people with stable hours. The question is when it stops being enough.
| Paper or PDF template | Spreadsheet | Timesheet tool | |
|---|---|---|---|
| Weekly and period totals | Calculated by hand | Formulas, if set up correctly | Calculated automatically |
| Daily entry habit | Depends on the person | Depends on the person | Reminders and partial saves help |
| Approval record | Signature on paper | Usually an email or a comment | Built-in submit and approve |
| Corrections | Crossed out by hand | Overwritten unless versioning is on | Sent back for correction, with history |
| Reporting by project | Manual | Possible with pivot tables | Usually built in |
| Retention | Filing cabinet or scans | Shared drive | Stored in the tool; export for archives |
Signs that it is time to move off a template:
- Someone spends more than an hour each pay period chasing missing sheets.
- Hours need to be split by client or project for invoicing.
- Corrections after approval have caused disagreements.
- The team includes contractors on different contract types, such as hourly, per-project, and fixed monthly.
That last point is common in project teams that work with outside specialists. Some project management tools add timesheets to the same place where tasks are tracked, so hours and the work they relate to sit together. One example is an add-on described on the pricing page: a weekly timesheet in half-hour steps with autosave, weekly submission and approval, totals and CSV export by person, project, and work type, and support for hourly, per-project, and fixed monthly contracts. It is priced per person who enters hours, with managers who only view or approve not counted. Because its submissions are weekly, it fits the workweek-first approach described above; a biweekly pay period simply covers two approved weeks. The features page shows how it connects to the boards where the work is planned.
A two-week routine that holds up
Whatever the tool, the same routine keeps a biweekly timesheet accurate.
- Fix the workweek. Write down the day and hour it starts, and use the same definition on every sheet.
- Enter time daily. Hours, breaks, and a short note if anything was unusual.
- Close Week 1 on its last day. The employee confirms the week; the approver reviews it within a day or two.
- Watch Week 2 against Week 1. If Week 1 ran long, plan Week 2 knowing that overtime is judged per week, not per period.
- Close Week 2 and the period. Approve the second week, then check that the period summary shows regular and overtime hours separately.
- Lock and archive. Export or file the approved sheet, and keep it for the retention periods that apply.
The routine adds a few minutes a week and removes most of the end-of-period scramble.
What to change first
If the current biweekly timesheet shows only a 14-day total, add a separate total for each workweek before the next pay period; that one change prevents the most expensive error. If chasing and correcting sheets is taking real time each period, move to weekly submission and approval, for example with the timesheet add-on on the Pinateca pricing page.
Q1. Is overtime calculated on 80 hours in a biweekly pay period?
Not under the federal FLSA. The Department of Labor's Fact Sheet #23 says the Act applies on a workweek basis and that averaging hours over two or more weeks is not permitted. Overtime for covered non-exempt employees is owed for hours over 40 in each workweek, so a biweekly timesheet needs a total for each week.
Q2. What is the difference between biweekly and semimonthly timesheets?
Biweekly means every two weeks, usually 26 pay periods a year, and each period can contain exactly two workweeks. Semimonthly means twice a month, 24 pay periods a year, and periods often split a workweek across two pay periods, which makes overtime tracking more involved.
Q3. How long should biweekly timesheets be kept?
The Department of Labor's Fact Sheet #21 says payroll records should be kept for at least three years, and records on which wage computations are based, including time cards and work schedules, for two years. State rules may require longer, so check local requirements as well.
Q4. Does a timesheet have to use a specific format?
No. Fact Sheet #21 states the law requires no particular form, and any timekeeping method is acceptable as long as it is complete and accurate. The records do need to include items such as hours worked each day and total hours each workweek.
Q5. How should minutes be converted on a timesheet?
Divide minutes by 60 before adding: 15 minutes is 0.25 hours, 30 minutes is 0.5, and 45 minutes is 0.75. Adding clock times as if they were decimals, for example reading 7:45 as 7.45, produces small errors that add up across a team.