A weekly time card that speaks decimal hours
This time card calculator takes what a paper timecard holds — seven days of hours and minutes — and produces what payroll wants: a decimal-hours total. Type each day's worked time in either format, 8:30 or 8.5 both work, and the card converts each entry, totals the week, and multiplies by your hourly rate to estimate gross pay. Overtime hours beyond 40 are broken out on their own line.
The reason the split matters is the multiplication step. A week of 7:15, 8:00, 7:45, 8:30, 6:50, 0:00, 0:00 adds up to 38 hours 20 minutes, which most payroll systems store as 38.3333 decimal hours. At $18.50 an hour that is $709.17 gross — a number you can only check by hand if you enjoy dividing minutes by sixty six times in a row. Here the card does each conversion as you type, so the weekly decimal total is on screen before you finish typing Saturday.
Nothing is sent anywhere and no account is required. The hourly rate is remembered in your own browser's local storage so next week's card starts pre-filled, and one tap on reset clears the whole card. On a phone the seven day rows stack comfortably in a single column with full-size inputs — practical for Sunday-night timesheet entry from the couch, which is when most of these actually get filled out.
How a time card turns punches into pay
The card in your hand is only the middle of a chain that starts at a time clock and ends in a bank account, and knowing the whole chain is what lets you find where a number went wrong. First, a punch pair: an in time and an out time. Second, subtraction, which gives elapsed time in hours and minutes. Third, unpaid breaks come off — a 30-minute meal turns 8 hours 35 minutes of elapsed time into 8 hours 5 minutes of paid time. Fourth, the conversion: divide the leftover minutes by 60, so 8:05 becomes 8.0833 decimal hours. Fifth, multiply by the hourly rate. Sixth, split the hours at the overtime threshold and apply the multiplier, 1.5x for the first tier and 2x beyond it where a second tier exists.
Almost every one of those steps is a place where your number and the payroll system's number can part company, and only two of them are arithmetic. Punch rounding happens before the subtraction at all — under the seven-minute rule, an 8:07 punch is recorded as 8:00 before anything else occurs. Break policy happens at step three, where an automatic deduction can remove a meal period you never actually took. The decimal conversion at step four is exact unless someone writes 8.50 for eight hours fifty minutes, which is 8.8333, not 8.5. Steps five and six are where state law and company policy enter, and step six is the one most employees never see, because many stubs collapse the whole split into a single hourly figure and a single total.
Not every premium is overtime. Weekend and evening differentials are employer policy rather than federal law: a hospital might pay $2.50 an hour extra for any hour worked between 23:00 and 07:00, a warehouse might pay Sunday hours at 1.15x, a retailer might add a flat $1 for weekend shifts. Those differentials stack on top of the base rate, and where they sit in the order of operations is usually defined as part of the regular rate, which is why an overtime line sometimes shows a rate higher than 1.5x your base pay. That is normally correct, not an error, and it is worth reading your handbook before assuming otherwise.
Worked example: 8:07 AM to 4:42 PM with a 30-minute lunch
Here is a full day, nothing skipped. Clock in at 8:07 AM, clock out at 4:42 PM, with an unpaid half-hour lunch in the middle. Do the elapsed time first. From 8:07 to 4:07 PM is exactly 8 hours, because the minutes match and only the hour digit moves. From 4:07 to 4:42 is another 35 minutes. So the punches span 8 hours 35 minutes. Now take the meal off: 8:35 minus 0:30 is 8 hours 5 minutes of paid time, which is the number that belongs on the card.
Convert it. Five minutes out of sixty is 5 ÷ 60 = 0.08333, so the day is 8.0833 decimal hours. At $18.50 an hour, break the multiplication into two pieces: 8 × $18.50 = $148.00, and 0.0833 × $18.50 = $1.54. The day pays $149.54. The exact product is 149.54166, so a two-decimal payroll display lands on $149.54 either way.
Now the two errors this example is built to catch. Forget the lunch break and you enter 8:35, which converts to 8.5833 and pays $158.79 — $9.25 too much for one day, and that is exactly the half hour at $18.50, which is how you can spot it without a calculator. Mistake the minutes for decimals instead, write 8.50 beside 8:05, and you claim $157.25, overstating the day by $7.71. Run the same day five times a week and the card reads 40.4167 hours, which is 0.4167 hours past the forty-hour line — a quarter hour of overtime at $27.75, about $11.56, appearing out of a shift that never felt long.
To check the conversion backwards, multiply the decimal by 60: 8.0833 × 60 = 485 minutes, and 485 minutes is 8 hours 5 minutes. Any single day's figure should round-trip that way. If it does not, the error is in the entry, not in the math.
Unpaid meal breaks, paid rest breaks, and the auto-deduction trap
The line between a break you get paid for and one you do not is short and specific. Under the FLSA, rest periods shorter than 20 minutes are compensable — you are still working (29 CFR 785.16), so the 15-minute break, the walk to the time clock, the two minutes your supervisor spends answering a question on your way out, all of that is hours worked. A meal period of 30 minutes or more is unpaid, but only when you are relieved of all duty. Eat at your desk while covering the phones and that half hour is not a bona fide meal period; the deduction has no basis.
The trap is the automatic deduction. Many timekeeping systems subtract a preset 30 or 60 minutes from every shift longer than six hours, whether or not you punched out for it. Convenient for payroll, expensive for you, because the default asserts something that may not have happened. A server working a double who eats standing up, a nurse who takes a working lunch during an understaffed shift, a driver who takes a break at a rest stop and keeps answering dispatch — each can lose 0.5 decimal hours per shift to a deduction nobody verified. Five shifts a week at $16.00 an hour is $40 gone weekly, and just over $2,000 across a year.
Some states go further and attach money to the missed break itself. California is the common example: shifts over 12 hours require a second meal period, rest breaks are 10 paid minutes per 4 hours worked, and a meal period that is missed, late or interrupted earns one additional hour of pay at the regular rate — meal and rest break premium pay. Other states set their own thresholds and their own remedies, so the exact rule depends on where you work rather than on what the handbook claims.
The habit that protects you costs almost nothing: if you worked through a break, note it the same day, with the time. Then compare the meal line on the stub against what you recorded. The question to payroll is not whether the policy exists — it does — but whether the deduction matched the shift.
Decimal precision: 8.5 hours is not 8 hours 50 minutes
8.5 decimal hours is 8 hours 30 minutes. It is not 8 hours 50 minutes, and the gap between those readings is 20 minutes, a third of a pay hour that comes to $6.17 at $18.50 an hour. The confusion is understandable, because the digits after the decimal point look like the minutes you would write after a colon, and they are not: they are fractions of an hour, expressed in hundredths instead of sixtieths.
The scale, in the units payroll actually uses: 0.01 of an hour is 36 seconds. 0.05 is 3 minutes. 0.10 is exactly 6 minutes. 0.15 is 9 minutes. 0.25 is 15 minutes, 0.50 is 30, 0.75 is 45, and 1.00 is a full hour. Two decimal places therefore carry precision to roughly half a minute, which is why most payroll systems stop there — more digits would claim accuracy no time clock has.
That rounding to two decimals is a display decision, not a claim about precision. A day stored as 8.0833 and printed as 8.08 gives away 0.0033 hours, about twelve seconds each time. Multiply that by roughly 250 working days and it is well under an hour for the year, so it will not make or break a check. It does explain a smaller annoyance: adding a year of two-decimal stub figures by hand will drift from the year-to-date total, and the drift is the display, not a missing paycheck.
Night shifts that cross midnight: the 22:00–06:30 shift
The most error-prone entry on any time card is a shift that starts before midnight and ends after it. Take a gas station night shift: clock in at 22:00, clock out at 06:30, with a half-hour unpaid meal break somewhere around 02:00. The elapsed time between the punches is 8 hours 30 minutes, and the unpaid meal takes it to 8 hours 0 minutes of paid time — 8.0 decimal hours on the card.
Get sloppy and the mistakes write themselves. Punch the 06:30 out as 18:30 and the shift doubles to 20.5 hours. Forget to subtract the meal and the card carries an extra 0.5 hours every night — across a five-night week that is 2.5 phantom hours, which at $17.25 an hour is a $43.12 discrepancy big enough to trigger a payroll review. Subtract the break before you write the number down, or compute each night as two blocks: 22:00–24:00 is 2.0 hours, 00:00–06:30 minus the meal is 6.0 hours, total 8.0.
Days of the week matter too. A Monday 22:00 start is a Tuesday-morning end for payroll purposes, so assign the whole shift to whichever day your employer's workweek definition uses — usually the day the shift starts. If your week runs Sunday-to-Saturday and your Sunday night shift bleeds into Monday morning, the hours still belong to Sunday, and they still count toward that week's overtime threshold.
Two-week schedules: nurses on 12-hour shifts, 3-on-4-off
Hospital nursing schedules are the classic case where a single week tells you almost nothing. A common pattern is three 12-hour shifts on, four off, which lands differently in each week of a two-week pay period. Week one might be Monday, Tuesday, Wednesday: three 12s plus a 30-minute unpaid meal each shift, so 11.5 paid hours per shift and 34.5 decimal hours for the week — under 40, no overtime. Week two might be Thursday, Friday, Saturday: another 34.5 hours, also under 40. The pay period total is 69.0 decimal hours, yet the calendar is packed.
The time card handles this by running the numbers week by week. Fill the first week's card, note the total, reset, then fill the second week. The two totals side by side answer the question nurses actually ask: did either week cross 40 and trigger FLSA overtime, or does this schedule stay premium-free all period? With a clean 3-on-4-off at 11.5 paid hours per shift, the answer is no week ever crosses 40 — which is exactly why hospitals like the pattern and why the per-shift math has to be right for it to hold.
Where it gets expensive to be wrong is California and a handful of other states with daily overtime: there, hours beyond 8 or 12 in a single day carry a premium regardless of the weekly total, so a 12-hour shift that runs to 13.5 because of a late handoff is 1.5 overtime hours on the spot. A weekly-only card cannot compute that premium for you, but it keeps the daily decimal values visible so you can flag the overage days and apply your state's rule to them.
Truck drivers and the 70-hours-in-8-days rule
Long-haul and regional drivers in the United States work under a different ceiling: property-carrying drivers may not drive after being on duty 70 hours in any 8 consecutive days (or 60 hours in 7 days). That rule is why drivers who keep their own backup records — paper logs, a notebook on the dash, a spreadsheet at the truck stop — need an 8-day running total, not a weekly one.
The card is built for 7-day weeks, but the 8-day number is two quick card fills away. Run days 1 through 7, write down the total, reset, then run days 2 through 8 and add the two totals minus day 1's hours. Concretely: suppose day 1 was 10.5 hours on duty and days 1–7 total 61.25 decimal hours. To check whether you can drive on day 8, total days 2–8 — if that comes to 58.75, you have 70 − 58.75 = 11.25 hours of room. If it comes to 66.5, you have 3.5, and a 10-hour driving day is not happening until day 2 drops off the window tomorrow.
Drivers' daily entries are rarely round numbers, either. A day of 9:40 on duty, then 11:05, then 8:25 becomes 9.6667, 11.0833 and 8.4167 decimal hours — sums nobody does reliably at the end of a shift. The card converts each entry as typed and keeps four decimal places, which is finer than the 15-minute increments electronic logging devices typically use, so the backup record and the ELD can be reconciled line by line.
One trap worth naming: on-duty hours and driving hours are different counts, and the 70-hour rule runs on on-duty time. A driver who spends 11 hours on duty but only 9 of them driving enters 11:00 on the card, because the window burns on the full shift. Loading, fueling, inspections and waiting at a shipper's dock all count. When a dispatcher asks whether you have hours left tomorrow, the number they want is 70 minus your last 8 days of on-duty totals — which is exactly the running figure this card keeps for you.
Overtime beyond 40: what time-and-a-half actually pays
Under the FLSA, non-exempt employees earn at least 1.5 times their regular rate for every hour worked beyond 40 in a workweek. The overtime line on this card exists so that math is visible instead of buried. A dual-income household running the numbers on a big week — say one partner's warehouse job posts 46:30 on the card, which is 46.5 decimal hours — can see the split immediately: 40 straight hours plus 6.5 overtime hours.
At $19.00 an hour, the straight 40 is $760.00. The 6.5 overtime hours pay at $28.50, another $185.25, for a gross of $945.25 instead of the $883.50 the week would earn at straight time. That $61.75 difference is precisely the amount a payroll system has to compute correctly — and precisely the amount that disappears when a stub shows all 46.5 hours multiplied by the plain rate. Run the numbers here before the direct deposit lands and the discrepancy is a question you can ask on Monday, not a write-off you discover in March.
A note on what counts as 40: hours worked, not hours paid. Paid sick leave, holidays and vacation do not push a week into overtime under federal law, even though they show on the stub. If your card total says 44 because you entered 40 worked plus 4 holiday hours, re-enter just the worked hours — 40 — and the overtime line correctly goes to zero. The card estimates gross pay from the hours you type, so type the hours you actually worked.
Beyond the federal floor: California's daily overtime and the seventh day
Forty hours in a workweek is the federal minimum standard, not the whole rulebook. California Labor Code section 510 requires 1.5x the regular rate for hours over 8 and up to 12 in a single workday, and 2x for hours beyond 12, regardless of how the week totals. It also requires 1.5x for the first 8 hours worked on the seventh consecutive day of a workweek, and 2x beyond 8 on that day. Alaska and Nevada have daily rules of their own, and Colorado applies daily overtime past 12 hours.
The daily trigger changes the arithmetic dramatically on long shifts. Take a 13.5-hour shift at $20.00 an hour. The first 8 hours are straight time: $160.00. Hours 8 through 12 are 4 overtime hours at $30.00: $120.00. The last 1.5 hours are double time at $40.00: $60.00. The day pays $340.00. A weekly-only calculation would pay 13.5 × $20.00 = $270.00, so the daily rule is worth $70 on that one shift, and a worker on a weekly card would never see it.
One caution that trips people up when they audit their own pay: daily and weekly overtime do not both pay on the same hours. If a Tuesday generates 4 daily overtime hours and the week as a whole also crosses 40, the employer pays the greater of the two computations rather than stacking them. That is why a stub can show fewer overtime hours than your own daily tally suggests and still be correct. A weekly time card cannot decide which rule applies, but it does show you which days ran past 8 hours, and that is the input the calculation needs.
Tips, cash and punched hours: restaurant workers
For tipped employees the time card answers a narrower but sharper question: do my punched hours match my schedule, and did the week cross 40? Tips never belong on this card — they are tracked separately, usually in a nightly declaration or a tip-out sheet. What belongs here is the punched record. A server whose week reads Monday 5:30, Tuesday 6:15, Thursday 7:45, Friday 8:30, Saturday 9:10 has 37 hours 10 minutes punched, or 37.1667 decimal hours, and should expect a paycheck built on that number plus reported tips.
The federal tipped minimum wage makes the punched total matter more, not less. Employers may take a tip credit — paying as little as $2.13 an hour in direct wages — as long as tips bring the employee up to at least the full federal minimum wage for every hour worked, and many states cap or refuse the credit entirely. Either way, the employer's obligation is computed per hour worked, so the card's per-day decimal entries are the same numbers a wage claim or a compliance audit starts from. If your stub shows fewer hours than your card, the shortfall multiplies across every hour of the week.
Practical habit for anyone juggling a tip book and a time clock: total your tips per shift in your own records, run your punched hours through this card at the end of the week, and only then look at the stub. Three separate numbers — tips, hours, pay — checked in that order takes about ten minutes and catches the two errors that dominate restaurant payroll complaints: dropped punches and tip-credit math done on the wrong hour count.
How to enter a day's hours
Each day accepts a duration, not clock-in and clock-out times — the cleanest approach when your source is a handwritten card or a memory of the shift. Enter 8:15, 7:45 or a plain decimal like 7.75; the card normalizes everything to decimal hours as you type. A missed day stays blank and counts as zero without breaking the total.
When your source is punches rather than durations, do the subtraction per shift first: end minus start, then minus any unpaid meal. A 07:00–15:30 shift with a 30-minute lunch is 8.0 paid hours; a 09:15–17:00 shift with no break is 7.75. If you would rather the tool handle single conversions — say a 6-hour 20-minute split shift you keep second-guessing — the time to decimal calculator does one value at a time, and the decimal to time converter runs the other way when you need to read a stub figure like 37.1667 back as 37 hours 10 minutes.
If your tracking happens in minutes — a 95-minute task, a 50-minute meeting — the minutes to decimal hours page converts those entries individually. And for a printable reference you can tape inside a cabinet door, the decimal time conversion chart lists every 15-minute increment from 0:15 to 12:00 with its decimal twin, which is faster than any calculator when the value is already on it.
Rounding rules: why your stub shows 7.75 for 7:52
Payroll systems round, and rounding is the number-one source of small discrepancies between your own card and your stub. The FLSA permits rounding to the nearest 5 minutes, the nearest 6 minutes (a tenth of an hour), or the nearest quarter hour, as long as the practice is neutral over time. Under quarter-hour rounding, a 7:52 punch pays as 8.0; under tenth-of-an-hour rounding it pays as 7.9; the exact decimal is 7.8667. All three are legitimate — they are just different numbers, and each one explains a different stub figure.
The pattern to recognize is systematic drift versus one-off noise. If your card says 39.75 for the week and the stub says 39.75, rounding is working and any missing time is a punch problem. If your card says 39.75 and the stub says 38.5 every single week, the gap is not rounding — 15–20 minutes disappearing per week is more likely an automatic meal deduction, a rounding rule stacked against you, or a clock-in buffer, and it is worth $20–$40 a week to have explained.
The card's own totals stay unrounded at four decimal places, so treat them as the exact value and your stub as the policy-adjusted value. Compare the two, expect small differences, and escalate only when the difference has a sign and a schedule — same direction, same days, every week.
It helps to know which increments are legal, because the size of the increment shows up directly in the fractions on your stub. Rounding to the nearest five minutes produces decimals ending in 0.0833, 0.1667 and 0.25. Rounding to the nearest six minutes — a tenth of an hour — produces only 0.1, 0.2, 0.3 and so on. Rounding to the nearest quarter hour produces only 0.25, 0.50 and 0.75. Read three or four daily figures off one stub and the employer's increment is usually obvious: if every value lands on a quarter, you are on the quarter grid; if you see 7.9 or 6.3, you are on tenths and the minutes are being counted in six-minute blocks.
The federal rule behind all of this is 29 CFR 785.48, which allows any of those increments on one condition: the practice must not systematically favor the employer over time. Rounding each punch independently is the usual compliant method, and it tends to even out across a schedule. What does not even out is rounding only at the end of the day in one direction, or rounding clock-in times up while leaving clock-out times alone.
Reconciling a biweekly or semimonthly paycheck against your app export
The shape of your pay period decides what a healthy total looks like before you ever compare it to anything. A biweekly schedule pays 26 times a year, so a full-time stub normally shows 80.00 straight hours. A semimonthly schedule pays 24 times, averaging 86.67 hours per check, since 2,080 annual hours divided by 24 is 86.6667. A monthly schedule pays 12 times and averages 173.33 hours. Seeing 86.67 on a semimonthly stub is not overtime — it is the period being slightly longer than two weeks, and the 40-hour rule is still applied inside each workweek, not to the 86.67 total.
Overtime follows the workweek, not the pay period, and that is the single most important thing to hold on to when a period total looks high. A biweekly stub showing 88.00 hours is not automatically 8 overtime hours. It could be 44 and 44, which pays 8 overtime hours. It could also be 40 and 48, which pays 8 overtime hours, or 39 and 49, which also pays 9 if the high week ran to 49. The period total alone never tells you; the weekly split does, which is why filling two separate weekly cards beats filling one long one.
To reconcile an export against a stub, work in this order and stop at the first mismatch. Export the period from your time app as decimal hours, and add the weekly subtotals rather than the period total. Compare each weekly subtotal with the stub's weekly or period detail, granting the employer's rounding increment. If a week is short, look at the break deductions for that week before looking anywhere else. Then check the rate by dividing regular gross pay by regular hours — the quotient should match your hourly rate exactly. Finally check the overtime line separately, multiplying overtime hours by rate by 1.5. A discrepancy that survives all four checks is worth raising in writing, with the export attached.
Keeping records that win a pay dispute
Most wage disputes are lost for a reason that has nothing to do with the law: the employee cannot produce a contemporaneous record and the employer can. Timekeeping systems retain punch data, and under 29 CFR 516.6 employers must preserve payroll records for at least three years and the underlying time cards for two. You are entitled to ask for that detail, and asking for the punch-level record behind a stub is a reasonable, ordinary request — not an accusation.
Your own record only needs to be good enough to contradict theirs on one specific day. Photograph the paper card before you hand it in. Screenshot the app's weekly summary every pay period, including the date visible in the screenshot. Note breaks when they go wrong, on the day, in whatever you already carry — a note on your phone is fine, and a note made Tuesday about Tuesday is worth far more than a reconstruction made in March. If a manager tells you to clock out and keep working, write down the date and the approximate times the same day.
Keep the calculations too, not just the raw times. A screenshot of this card showing 41.0833 hours for a week whose stub says 39.50 is a far stronger artifact than a memory of having worked a lot. Four dated records from four consecutive weeks, all off by the same half hour, describe a systematic deduction. One record describes a bad day, and one bad day is easy to explain away.
Check your paycheck before you question it
The most common payroll question — my hours look wrong — usually has a boring answer: a decimal conversion done differently than you expected. Enter the hours you actually worked here, compare the weekly decimal total with the one on your stub, and the difference tells you whether the issue is rounding policy, a mistyped punch, or genuinely missing time.
Work through it with real numbers. Your card says 41:05 for the week, which is 41.0833 decimal hours. The stub says 41.0 — that is tenth-of-an-hour rounding on the final total, nothing to chase. The stub says 40.25 — your week may have been split by a payroll cutoff, with the tail of Saturday night landing in next period. The stub says 39.5 — now you are looking for a dropped punch or an auto-deduction, because no neutral rounding rule turns 41 hours into 39.5.
Keep the habit cheap: fill the card once a week, screenshot it, move on. Disputes are easy to win with four dated screenshots and hard to win with a memory. If your week is a single-shift question rather than seven entries — one long night at the plant, one conference day billed to a client — the decimal hours calculator on the home page does the same conversion without the weekly scaffold.
When something does look off, three checks settle most of it in under five minutes. Check the hours line first: does the stub's regular-hours figure match your card's decimal total once your employer's rounding increment is applied? Check the rate second: divide regular gross pay by regular hours and see whether the quotient equals your hourly rate, since anything lower means a deduction, a tip credit or a split rate is in the calculation. Check the overtime third: multiply the overtime hours by your rate by 1.5, and by 2.0 where double time applies. If all three pass, the difference is in taxes or deductions, and payroll can show you that breakdown in a single line.