Tracking Your Own Hours and Pay

Why this matters

Payroll mistakes are rarely dramatic. A ticket closes a day late and its flag hours land in nobody's week. A shop meeting gets left off the clock. A spiff gets paid on the wrong job. Each one is a fraction of a day's pay, and without your own record you cannot tell a mistake from a slow week, so you shrug and move on. Over a year those shrugs add up to real money, and if you ever do need to dispute something, the shop's records are the only ones in the room unless you kept your own.

A personal log takes about two minutes a day. This article covers what goes in it, how to keep it so it holds up, and how to check every check against it in five minutes a week.

What your log is for, and what it is not

It is for checking pay. Every number on your stub (hours, flag hours, overtime, spiffs, commission) should be reproducible from your log. If you cannot rebuild the check from your own notes, the log is missing a column.

It is evidence if it comes to that. Under the Fair Labor Standards Act the employer must keep accurate time and pay records (29 CFR Part 516), and since the Supreme Court's 1946 decision in Anderson v. Mt. Clemens Pottery, when the employer's records are missing or inaccurate an employee can show hours worked by reasonable evidence, which a contemporaneous log is. A log written at the time, day by day, carries far more weight than a reconstruction done after a dispute starts.

It is not a surveillance project. Do not record conversations with your boss to "prove" anything. A handful of states require every party's consent before a conversation is recorded, and a recording made in one of them can expose you rather than the shop. Write down what was said instead, with the date.

Step 1: Pick a medium that will still exist in three years

Use a pocket notebook, a notes app, or a simple spreadsheet on your own phone or account, not the company tablet or the field-service app.

Why: the company device and the company login go away the day you leave, which is exactly when a final-pay or overtime dispute shows up. Federal wage claims can reach back two years, and three for a willful violation (29 U.S.C. 255); many state wage claims reach back further. A log you lost access to protects nothing.

What breaks if you skip it: your evidence lives on a device the employer controls and can wipe, and you are left estimating from memory.

Step 2: Log start and stop, not totals

Write the actual time you started work and the actual time you stopped, plus each unpaid meal break with its start and end. Do not write "worked 9.5."

Why: a total cannot be checked and cannot be argued with. Start and stop times let anyone, including a labor agency investigator, recompute the day. They also catch the quiet stuff: a 7:00 start when the stub says 7:30, or a 30-minute lunch automatically deducted on a day you ate in the truck between calls. Under federal rules a meal period only comes off the clock if you were completely relieved of duty for it, generally 30 minutes or more (29 CFR 785.19); eating while driving to the next job is not a meal break.

What breaks if you skip it: auto-deducted breaks and rounded start times disappear into the total, and the total looks right.

Step 3: Log every block of clock time by type

Between start and stop, note what each block was: a job (with the ticket number), drive between jobs, a parts run, waiting at the shop or a supply house, a meeting, training, loading the truck.

Why: these blocks are all hours worked under federal rules, whether or not your pay plan pays them separately. Travel between job sites during the day counts (29 CFR 785.38), and so does time you are required to wait. If you are paid hourly, this column tells you whether all of it was paid. If you are on flag rate or commission, it tells you where the gap between your flag hours and your clock hours went, which is the number your real hourly earnings ride on. See related: How Flat-Rate Pay Works From the Tech's Side for what that gap means.

What breaks if you skip it: you know you were busy but cannot show where three hours went, so you cannot tell whether the shop shorted you or the board did.

Step 4: Log what each job should pay you

For each ticket, write the number, the customer's last name or street, and whatever earns you money on it: the flag hours, the sold amount your commission is based on, any spiff or bonus item, and its status (done, waiting on parts, recall).

Why: this is the column the stub is built from, and it is where most errors live. A ticket that sat open waiting on a part, or was closed by the office after the pay period ended, may pay you a week or a month late. A recall usually flags at zero; a callback on a new problem should flag normally. If your log says which was which, you can see when a job was coded wrong.

What breaks if you skip it: a missing ticket looks exactly like a slow day.

Step 5: Close each day with two totals and one note

At day's end write total clock hours (stop minus start minus real breaks) and total flag hours or sold amount. Add one line for anything unusual: "kept late for inspector," "told to clock out then finish the invoice," "Saturday on-call, 1 call."

Why: two totals a day make the weekly check a matter of adding seven numbers. The note is the part that gets forgotten fastest and matters most, because instructions like "clock out and finish up" are exactly the kind of thing that turns into an unpaid-hours dispute months later.

The week, written out

Here is one tech's Monday to Friday, written the way it should look. This tech is on flag rate with a weekly overtime premium, and the pay week runs Monday through Sunday.

WEEK OF 3/9   (pay week Mon-Sun)
DAY  IN    OUT   MEAL         CLOCK  FLAG  TICKETS
Mon  7:00  17:15 12:00-12:30  9.75   7.5   4410 4413 4415
Tue  7:00  16:00 none (truck) 9.00   6.0   4419 4422
                 note: lunch auto-deducted? check
Wed  6:30  18:00 12:30-13:00 11.00   8.5   4427 4430 4431
                 4431 waiting on part, not closed
Thu  7:00  17:30 none (truck)10.50   5.0   4433 R4415
                 R4415 = recall on Mon job, 2.0 clk
Fri  7:00  15:30 12:00-12:30  8.00   5.5   4440 4441
                 note: shop mtg 7-8, unpaid on plan?
TOTAL                        48.25  32.5

Note what the artifact already shows before the stub arrives. Clock hours are 48.25, so there are 8.25 overtime hours in the week. Flag hours are 32.5, and 1.5 of those belong to ticket 4431, which is not closed. Two days had no real meal break, so if the system deducts 30 minutes automatically, 1.0 clock hour will be missing. Thursday's recall consumed 2.0 clock hours and flagged nothing, which is normal under most plans, but those 2.0 hours still belong in the clock total.

Step 6: Check the check, every payday

When the stub arrives, put it beside the week.

For the week above, the stub showed 47.25 hours worked, 31.0 flag hours, and an overtime premium figured on 7.25 hours.

• Hours: 48.25 in the log minus 47.25 on the stub leaves 1.0 hour, which matches the two auto-deducted lunches on Tuesday and Thursday exactly. That points to the cause before anyone has to argue about it.
• Flag hours: 32.5 minus 31.0 leaves 1.5, which is ticket 4431. Closed late is normal; the check is to look for those 1.5 flag hours on the next stub, not to assume they are gone.
• Overtime: the stub's 7.25 overtime hours equal 47.25 minus 40, so the premium is consistent with the stub's own hours. Restore the missing 1.0 hour and overtime becomes 8.25 hours, and since every added hour lands past 40, the whole correction is overtime.

What you end up with is a two-line, specific question: "Tuesday and Thursday show a lunch deduction, but I ate between calls both days; that is 1.0 hour, which puts me at 48.25 for the week. And 4431 should come through next period at 1.5 flag." See related: Raising a Paycheck Error for how to bring it up.

What would change this check. If this tech were paid hourly, the flag column would not drive pay and the whole check would be clock hours times rate, plus overtime at one and a half times the regular rate. If this tech worked in California, the check grows: daily overtime after 8 hours in a workday applies under state law, so Monday's 9.75, Tuesday's 9.00, Wednesday's 11.00 and Thursday's 10.50 each carry daily overtime, and California requires piece-rate workers to be paid separately for rest periods and nonproductive time (Labor Code 226.2). If the shop pays the meeting and drive time separately at an hourly rate, those blocks become their own line on the stub to check.

Keeping it up

Write it the same day. A log reconstructed on Sunday from memory is the weakest version. If you miss a day, write the late entry and mark it as written later; do not backfill as if it were current.

Keep a year of stubs beside it. Year-to-date figures on the stub become a running audit: if your log's flag hours for the year and the stub's year-to-date flag pay drift apart, something went missing and you can bracket when.

Keep it for at least three years after you leave, matching the longest federal look-back. Some states give longer, so keep it longer if yours does.

Keep it yours. Do not post it, do not share customer details from it beyond a street or last name, and do not use it to argue about other techs' pay.

References

• 29 CFR Part 516 (employer recordkeeping) and 29 CFR Part 785, including 785.19 (meal periods) and 785.38 (travel between job sites)
• 29 U.S.C. 255 (two-year and three-year limitations on FLSA wage claims)
• California Labor Code 226.2 (piece-rate pay for rest periods and nonproductive time)
• See related: How Flat-Rate Pay Works From the Tech's Side; Reading Your Pay Stub as a Technician; Raising a Paycheck Error