What Is a Timesheet? Definition, Uses & How to Fill One

A timesheet is a record—paper or digital—that shows when an employee worked during a pay period, including start and end times, breaks, and total hours submitted for payroll.

Search results for timesheet alone often surface calculators, app logins, or vendor homepages—not a clear definition for shift employers. Here we explain the timesheet document itself: what it includes, how to fill decimal hours, and how approval feeds payroll. For capture methods and policy, see employee time tracking; for absences and the full attendance cycle, see time and attendance.

We cover spelling, everyday uses, timesheet vs timecard, paper vs digital options, typical fields, the submit-and-approve workflow, common mistakes, and basic US recordkeeping for hospitality, retail, and healthcare crews. If you are comparing vendors, use our time tracking software guide instead of this glossary entry.

Disclaimer: General HR and payroll orientation only—not legal advice. Federal, state, and local rules vary. Confirm obligations with qualified counsel. US federal recordkeeping: U.S. Department of Labor — Wage and Hour Division.

What is a timesheet?

What is a timesheet? It is an employer-facing record that documents hours worked (and sometimes leave or project codes) for a defined period—usually a day, week, or full pay period. Each row typically ties hours to a person, date, and shift or task so payroll can calculate regular pay, overtime pay, and any premiums.

Timesheets are not the same as a schedule: the rota says who should work; the timesheet shows who did work. When those diverge, managers correct punches before payroll runs.

That distinction matters on busy floors. A published rota might show Maria on close and James on open, but the timesheet proves whether those shifts actually happened—and whether either person picked up an extra hour after the kitchen deep-clean. Payroll, labor reports, and dispute resolution all start from that record, not from the plan alone.

Daily, weekly, and pay-period timesheets

Formats differ by employer:

The label on the PDF matters less than whether totals match your payroll calendar. If your provider runs biweekly payroll, a “weekly” export still needs to roll up into the correct two-week window before you approve.

Timesheet vs time sheet

Both spellings appear in search, but timesheet (one word) is standard in HR, payroll, and most US style guides. Time sheet (two words) still shows up on older paper forms and in casual speech. Pick one spelling in your handbook and stick to it on forms and in your HRIS.

Search snippets may show both variants; consistent internal templates matter more than chasing alternate spellings as separate pages.

In US business writing, one word also matches how payroll systems label exports (timesheet CSV uploads, “approve timesheet” buttons) and how employees search when HR sends a deadline reminder. Standardize labels in email subject lines and mobile notifications so “time sheet” in the body does not fight “timesheet” on the upload button.

For handbook and form design, add a one-line glossary entry—“Timesheet: the record of hours worked for a pay period”—so new hires do not have to infer meaning from software menu labels alone.

What is a timesheet used for?

What is a timesheet used for? Employers rely on timesheets as the pay-period source of truth for hours worked—supporting payroll, compliance, labor reporting, and (when coded) job or department allocation. In payroll specifically, the timesheet is the approved hours file your provider imports before gross wages and deductions are calculated.

Common uses include:

Agencies and freelancers also use timesheets for client billing—that is valid, but we focus here on W-2 shift employers paying crews through payroll, not invoice-only freelancers.

For finance leads, the same document feeds gross pay calculations before deductions appear on the pay stub. When hours are wrong, every downstream number—OT, premiums, PTO balances tied to worked time—drifts. Fixing the timesheet before export is cheaper than reopening payroll after direct deposit.

Operations teams also use approved timesheets to settle disputes—“I worked through lunch” conversations go faster when punch history and manager sign-off exist in one packet. That is separate from performance coaching; the timesheet only proves hours, not quality of work.

Timesheet vs timecard

People use both terms loosely. In practice:

Many digital systems blur the line: one export serves as both punch log and pay-period timesheet. What matters is that payroll receives verified totals for each pay period, not which label your vendor uses in the UI.

When employees ask “is my timecard the same as my timesheet?” the honest answer is often “the system exports both from the same punches.” Use plain language in onboarding so crews do not duplicate hours on two forms.

In payroll, an employee timesheet is the approved packet payroll imports—sometimes a CSV, sometimes rows in your HRIS—not the raw punch log unless your provider maps them automatically. If payroll asks for “the timesheet,” they mean verified period totals with approver sign-off, not a photo of a wall clock strip.

Paper, spreadsheet, and digital timesheets

Timesheet software automates capture and approvals; feature lists and pricing belong in our time tracking software comparison. This article stays on the document and workflow, not vendor roundups.

If you are still on spreadsheets, pair them with a written correction process—the same discipline described in employee time tracking policy essentials.

When teams ask for “the best free timesheet app,” they are usually shopping software—not learning what a timesheet is. Use the software guide for buying decisions; use this page for definitions, fields, and fill-out rules.

Retention and edits follow the same rules no matter the format: store signed paper, locked spreadsheet versions, or HRIS exports where wage-and-hour records live (see recordkeeping below). Employers may correct obvious errors on a timesheet if the change is documented and visible to the employee—never reduce paid time without a recorded reason.

Typical timesheet fields and pay periods

A workable employee timesheet usually includes:

• Employee name and ID
• Pay period dates (aligned with your pay period calendar)
• Date worked and shift start/end (or daily total hours)
• Breaks—paid vs unpaid where your policy requires notation
• Job, department, or cost-center codes (if you allocate labor)
• Regular vs overtime hours (or hours over daily/weekly thresholds your payroll uses)
• Employee signature or electronic attestation
• Manager approval line or digital sign-off

Some forms also capture PTO, sick, or holiday hours so payroll sees one packet per period. For leave rules and balances, see PTO and sick leave; here we only note that those hours can sit on the same form.

Distinguish pay period dates from pay date on the form header: the period is the window you are proving (for example Monday–Sunday or the 1st–15th); pay date is when wages hit accounts. Payroll imports fail when crews enter check date on every row instead of the shift date. If your provider uses earning codes, reserve columns for regular, overtime, double-time, or holiday pay rather than one blended total—premiums stay auditable when OT rules differ by day or role.

Weekly timesheets and biweekly payroll

A weekly timesheet is still common even when payroll runs every two weeks: crews fill a seven-day grid each week, and payroll rolls two approved weeks into one biweekly file. Semi-monthly payroll (twice per month on fixed calendar dates) needs the same discipline—hours must land inside the correct earning window, not “whatever week felt busy.” When you use a timesheet Excel template, name tabs by pay period end date so managers do not approve the wrong sheet after a holiday Monday shuffle.

How does a timesheet work?

How does a timesheet work? Most employers run the same repeatable cycle each pay period—capture, review, submit, approve, then payroll—so hourly totals stay tied to a named approver before wages export.

In more detail, the steps usually look like this:

1. Capture — employee clocks in/out or enters hours per shift
2. Review — employee checks totals before the deadline
3. Submit — timesheet routed to the manager or payroll queue
4. Approve — manager fixes missing punches or flags OT
5. Payroll — approved hours export to payroll; results appear on the pay stub

Digital systems send reminders; paper processes need a published cutoff (for example, Monday 10 a.m. for the prior week). Missed deadlines create guesswork—exactly when wage disputes start.

Part-time and variable-hour staff need the same clarity as full-time crews—band definitions live on part-time hours, but the timesheet still lists actual punches per shift. Split shifts and meal breaks should match how you pay gaps; see split shift if two blocks in one day affect premiums.

When one person wears two hats (GM who also runs payroll), write down who approves versus who exports so hourly staff know whom to ping when a punch is wrong on Sunday night.

How to fill out a timesheet (decimal and quarter hours)

Payroll systems often want decimal hours, not “7:45” text. Convert minutes to decimals by dividing minutes by 60:

• 15 minutes = 0.25
• 30 minutes = 0.50
• 45 minutes = 0.75

Example: 7 hours 45 minutes = 7 + (45 ÷ 60) = 7.75 hours on the timesheet.

If you have wondered what .25 on a timesheet means, it is fifteen minutes (0.25 × 60 = 15). Likewise, .50 is thirty minutes and .75 is forty-five. Never mix clock notation (7:45) and decimals (7.45) on one form; 7.45 decimal hours is seven hours and twenty-seven minutes, not seven hours and forty-five minutes.

Always follow your employer’s rounding rules if punches are rounded to the nearest quarter hour—documented in policy, not invented at payroll. Rounding belongs in written employee time tracking policy; the timesheet should show either raw punches or consistently rounded totals, not both without a legend. Sanity-check weekly totals with our timesheet calculator or time card calculator before you submit.

For unpaid meal breaks, subtract break minutes before you convert to decimals unless your system auto-deducts lunch. A 9:00–17:00 shift with thirty unpaid minutes is seven paid hours (7.00), not eight minus a handwritten note payroll might miss.

Worked examples managers can paste into training

Train crews once on decimals—especially new hires used to “7:45” free text in messaging apps. A single laminated card above the time clock prevents hundreds of payroll edits later.

Overnight shifts that cross midnight need an explicit rule: do the hours belong to the day the shift started, or split across two dates? Payroll systems differ—document your rule once instead of debating it every Sunday close.

Timesheet approval and common mistakes

Strong approval habits:

• Fixed submission deadline communicated in the handbook
• Manager sign-off before payroll cutoff
• Documented corrections with reason and timestamp
• No silent edits that reduce paid time without employee knowledge

Common mistakes: forgetting lunch punches, duplicating hours across two forms, using the wrong pay-period dates, or approving OT nobody authorized. Buddy punching—one employee clocking for another—needs policy plus spot checks, not only trust.

When a manager corrects a timesheet, good practice is a short note in the HRIS or on the paper form: “Added 0.25 — missed clock-out 3/12, confirmed with employee.” That paper trail matters if a later wage claim asks why paid hours changed. Rejecting a timesheet back to the employee is better than silently editing totals the employee never sees.

Exempt salaried staff may submit project or PTO hours only; hourly and non-exempt rows should never be blank while someone clearly worked. Offboarding still requires a final timesheet close-out—see offboarding for lifecycle context.

Multi-site operators should name one approver per location—or one payroll partner who receives exports—so corrections do not bounce between GMs and HR. Ambiguous ownership is how duplicate hours slip through when someone works a shift at a sister store.

Timesheets and US wage-hour recordkeeping

Under the Fair Labor Standards Act (FLSA), covered employers must keep accurate records of hours worked for non-exempt employees. The law does not mandate one paper layout, but records must be complete and available for inspection. Many employers retain time records for at least two years (payroll records often longer); states may require more.

This section is a bridge only—full legal depth on exemptions and state meal or rest rules lives in our FLSA glossary cluster. Timesheets are evidence; they do not replace counsel review when you change pay practices.

Store exports where payroll and HR can retrieve them—shared drive folders with dated filenames, or HRIS attachments—not only on a supervisor’s phone. Audits and wage claims arrive years later; “we deleted it when they quit” is a weak defense.

New hires should see a blank example timesheet during onboarding—completed with fake numbers—so their first real week is not the first time they hear “enter 7.75, not 7:45.” Ten minutes of training prevents recurring payroll tickets.

UK and Ireland employers: working time records and statutory holiday entitlement are framed differently than US FLSA minimums. This page stays US-primary on the timesheet artifact; for UK working time records and the full attendance cycle, use time and attendance—do not duplicate WTR depth here.

Timesheets for shift teams

Restaurants, stores, and care sites share the same pain: Friday night punches, Monday morning payroll. Reliable timesheets need capture at the door or on the floor, manager bandwidth to approve exceptions, and a tight link to the published rota via employee scheduling.

Ordio is not a generic timesheet login portal—we help shift operators combine time tracking with scheduling and employee files so approved hours stay audit-ready. When you outgrow spreadsheets, compare tools in the software guide; when you only need a weekly grid, start with the calculator or template handoffs above.

Seasonal ramps (holidays, summer terraces, flu-season care hours) are when timesheet discipline pays off: temporary staff, borrowed shifts, and overtime spikes all hit the same form. Publish a one-page “how we fill timesheets here” during onboarding week—not only in a PDF buried in the handbook.

Workforce management adds forecasting and labor planning on top of capture; the timesheet itself is still the document that proves hours before those analytics mean anything.

If managers still rebuild hours from text messages every Monday, the problem is usually missing capture at the shift—not “another timesheet template.” Fix the workflow first; templates and calculators help only after everyone agrees what a complete row looks like. Name one payroll or GM contact each period so crews know where to send corrections instead of texting multiple managers.

Summary

A timesheet is the pay-period record that turns worked time into payroll-ready totals—fields, attestation, and approval matter as much as the format. Use definitional clarity for “what is a timesheet,” decimal literacy for fill-out questions, and explicit handoffs for templates, calculators, and software buying guides.

Quick anchors by audience:

For policy and capture methods, read employee time tracking; for absences and UK working-time records, read time and attendance. Before each payroll run, ask three questions: Did every scheduled shift have a matching entry? Do decimals and breaks match policy? Did a named manager approve the packet? When those answers are yes, timesheets stop being paperwork and become the quiet backbone of fair pay on shift teams.