Biweekly timesheets: how to track two weeks of hours without errors

Payroll runs every other Friday. The timesheet covers fourteen days, the team fills it in on the last afternoon of the period, and every second cycle something does not add up. A 44 hour week sits next to a 36 hour week, the total says 80, and someone asks whether overtime is owed. Another person worked on three projects but recorded everything under one. The sheet looks tidy and the numbers are still wrong.

A biweekly timesheet is a sensible format. It matches a very common pay schedule and halves the number of approvals a manager does. It also has specific failure points that a weekly sheet does not. This article covers how to lay one out, how to handle the overtime question correctly, and how to keep two weeks of project hours accurate.

What a biweekly timesheet is, and what it is not

A biweekly timesheet records hours for a two week pay period. Pay arrives every other week, so a year normally has 26 pay periods, and occasionally 27 when the calendar falls a certain way. That is different from a semimonthly schedule, which pays twice a month on fixed dates and produces 24 pay periods of uneven length.

The important distinction is between the pay period and the workweek. They are not the same thing.

For employees in the United States, the Department of Labor's Fact Sheet #23 on overtime describes the workweek as a fixed and regularly recurring period of 168 hours, seven consecutive 24-hour periods. It may start on any day and at any hour, and it does not need to match the calendar week. The same fact sheet states that averaging hours over two or more weeks is not permitted.

So a biweekly timesheet is really two workweeks placed side by side, sharing one submission and one approval. If the sheet is designed as a single fourteen day block with one total at the bottom, it hides exactly the information needed to calculate overtime.

Why teams choose biweekly

• It matches the payroll cycle, so the timesheet and the pay run line up.
• Managers approve half as often as with weekly sheets.
• For project reporting, two weeks is often a natural review rhythm.

The trade-off is that people have to remember twice as much when they fill in the sheet late. That trade-off shapes most of the advice below.

The overtime trap in a two week sheet

This is the most common and most expensive mistake with biweekly timesheets, so it deserves its own section.

Consider an employee who is not exempt from overtime and works these hours:

Workweek	Hours worked	Hours over 40 in that week
Week 1	44	4
Week 2	36	0
Pay period total	80	4

The pay period total is 80 hours, which is exactly two times 40. A sheet that only shows the period total suggests no overtime. Under the federal rule described in the Department of Labor fact sheet, overtime is calculated per workweek, so Week 1 contains 4 overtime hours regardless of Week 2 being short.

The fix is structural, not a reminder to be careful:

• Show two weekly subtotals. Each workweek gets its own total line.
• Mark the workweek boundary. A heavy line or a label between day 7 and day 8.
• Calculate overtime per workweek. If the sheet has an overtime field, it should read from the weekly subtotal, never from the period total.
• Write the workweek start in the header. For example, "Workweek begins Sunday 12:00 a.m." The Department of Labor's recordkeeping fact sheet lists the time and day when the employee's workweek begins among the records employers must keep.

State and local rules can add daily overtime or other requirements, and rules outside the United States differ again. The layout above makes it easy to add those calculations, because the daily and weekly figures are already separated.

A layout that works

A biweekly timesheet does not need to be elaborate. The following layout covers what payroll, managers and project reporting need.

Header

• Employee name and role
• Pay period start and end dates
• Workweek start day and time
• Manager or approver

Body

Two blocks of seven days, one per workweek. Each block has:

• One row per project or type of work, with an extra row for work not tied to a project, such as internal meetings.
• One column per day, with the date and weekday shown.
• A daily total at the bottom of each column.
• A weekly total at the end of the block.

If start and end times are recorded, rather than just hours, include in and out columns per day and a break field. Many teams that bill by project only need hours per row. Teams that need exact clock times for payroll need both.

Footer

• Total hours for Week 1 and Week 2
• Overtime hours for Week 1 and Week 2, if applicable
• Total hours for the pay period
• Employee submission date
• Approver name and approval date

Increments and rounding

Pick one entry increment for the whole team, such as quarter hours or half hours, and apply it consistently. Finer is not always better. When the grid is too fine, people guess rather than recall. For payroll, follow the rounding practice that applies in the relevant jurisdiction.

The increment also decides how many rows a person can realistically keep. In half hour steps, four or five project rows per day stay honest. In five minute steps, the same person starts inventing precision that was never observed, and the extra digits give the sheet an authority the underlying memory does not have. Choose the increment that matches how the team actually switches between tasks.

Keeping fourteen days accurate

The core problem with biweekly sheets is memory. Nobody reliably remembers what they did on a Tuesday ten days ago.

Enter daily, submit biweekly

The pay period being two weeks long does not mean entry should happen every two weeks. The most effective single change is asking people to enter hours at the end of each day and only submit at the end of the period. A sheet that saves automatically as numbers are typed, and opens in one step from wherever people already work, makes daily entry realistic.

Carry rows forward

Most people work on the same few projects from one period to the next. A sheet that starts with last period's rows already in place removes typing and reduces the chance of someone inventing a new name for an existing project.

A midpoint check

At the end of Week 1, a quick look at who has entered nothing catches gaps while memory is still fresh. This can be as light as a count of empty sheets, shared with the team lead. There is no need to name people publicly. The point of the midpoint check is not compliance. It is that a gap found on day seven can still be filled from memory, while the same gap found on day fourteen cannot.

Use the calendar as a cross-check

Calendar entries show meetings and client calls. Board or task history shows what moved and when. Neither replaces the timesheet, but both help reconstruct a day that was not entered on time. Keeping the timesheet close to the place where tasks are planned makes this cross-check much faster.

Approval and locking

A biweekly cycle concentrates approval into one moment, which is efficient if the moment is well defined.

Set fixed deadlines

For example: sheets submitted by noon on the Monday after the period ends, approved by end of day Tuesday, payroll processed Wednesday. Written deadlines stop approval from sliding into the payroll deadline.

Approve in one place

Approval by a message in chat is hard to find later. A timesheet with a clear submit step, an approve step and a send back step creates a record that can be checked months afterwards.

Lock after approval

Once a period is approved and paid, the hours should not change silently. If a correction is needed, sending the sheet back and resubmitting leaves a visible trail. This keeps payroll figures and timesheet figures consistent.

Retention

The Department of Labor's recordkeeping fact sheet says records on which wage computations are based, such as time cards and work schedules, should be kept for two years, and payroll records for at least three years. A system of approved, locked sheets makes retention straightforward.

Biweekly sheets for project and client work

Payroll is only one use of the timesheet. Many small teams also use it to see where project time goes and to bill clients.

Hours by project need a shared project list

If projects are planned on a kanban board or Gantt chart and hours are recorded in a separate spreadsheet, the project names in the two places drift apart. Totals by project become unreliable. A timesheet that draws its list of projects from the same place the work is planned avoids that problem.

Two weeks is a useful review rhythm

A biweekly total by project is often the right frequency for checking budgets. It is long enough to show a trend and short enough to act before a project overruns badly. Pairing the biweekly approval with a short look at hours per project turns an administrative step into a planning step.

Contractors on different terms

If some people are contractors rather than employees, the sheet may need to handle different arrangements. Hourly contractors need hours by project for invoicing. Fixed fee contractors may only need to report progress. Forcing fixed fee contractors to enter hours creates numbers nobody uses. The features overview shows one approach that handles hourly, per project and fixed monthly contracts in the same timesheet, and the guide covers setup.

Paper, spreadsheet or software for biweekly timesheets

Each works for some teams.

• Paper is simple for small on-site teams, but weekly subtotals, overtime per workweek and retention all rely on careful manual work.
• A spreadsheet handles subtotals with formulas and is easy to share. The risks are broken formulas, edits after approval and project names typed freehand.
• Software calculates weekly subtotals automatically, supports submit and approve steps, and produces reports by person and project. The cost is usually per user, so check who counts as a user.

Whatever the tool, the test is the same: can it show two workweek totals separately, record approval, and produce hours by project without manual copying? Comparison pages such as Pinateca vs Trello and the full comparison list are a starting point for seeing how board tools differ on those points.

What to change first

Split the biweekly sheet into two clearly marked workweeks with separate totals, and calculate overtime from those totals. Then move entry from the last day of the period to the end of each day. If boards and weekly or biweekly hours in one place would help, Pinateca is free for up to 5 people and offers timesheets as an add-on.

Q1. Can overtime be calculated over a biweekly pay period?

Under the US federal overtime rule, no. The Department of Labor's overtime fact sheet says the law applies on a workweek basis and averaging hours over two or more weeks is not permitted. A biweekly timesheet needs a separate total for each workweek.

Q2. What is the difference between biweekly and semimonthly timesheets?

A biweekly timesheet covers every two weeks, so there are usually 26 pay periods a year. A semimonthly timesheet covers two fixed dates per month, giving 24 periods of uneven length. Semimonthly periods do not line up with workweeks, which makes per-week overtime totals even more important.

Q3. Should employees fill in a biweekly timesheet once or daily?

Daily entry with one submission at the end of the period is the most accurate approach. Filling in fourteen days from memory tends to round hours toward the schedule and lose short tasks and project changes.

Q4. What should a biweekly timesheet template include?

At minimum: the pay period dates, the workweek start day and time, hours per day, a total for each workweek, overtime per workweek where relevant, a total for the period, and fields for submission and approval. A row per project is useful when hours are also used for planning or billing.

Q5. How long should biweekly timesheets be kept?

The US Department of Labor's recordkeeping fact sheet says records used to compute wages, such as time cards, should be kept for two years, and payroll records for at least three years. Other countries and some states can set different periods.