One work record from clock-in to payday

Clock in when work begins, pause for a break, resume when you return, and clock out at the end. The active shift stays close through HoursKit, widgets, Live Activities, and shortcuts, giving you several natural ways to keep the timer in sight during a busy day.

If the day did not go to plan, the record is still yours to correct. Add a missed shift, move the start or end time, change the job, or update a break so the entry reflects what you actually worked rather than what the timer happened to capture.

An unpaid break belongs with the shift it changed. Record it inside the entry instead of trying to reconstruct lunch, travel, or an interrupted pause at the end of the week. A reminder can bring you back when a paused break reaches the duration you chose.

The same principle applies to the rest of the day. Notes, job context, additions, and deductions remain attached to the relevant work, making the total easier to understand when an unusual shift needs a second look.

Choose the rate and rules that match each job: regular hours, daily or weekly overtime, double time, weekends, holidays, night work, or another special rate you need to model. HoursKit applies those settings to the shifts you record, so a demanding week does not collapse into one flat hourly total.

The estimate becomes a practical question you can inspect: which hours were regular, which crossed a threshold, and which shift carried a different rate? Because the answer stays linked to the underlying entries, you can correct the source instead of adjusting a mystery number.

Open the current day, week, month, or pay period to see recorded hours and estimated gross pay building together. A biweekly worker can follow the whole two-week window; someone with several jobs can narrow the view to the work that matters right now.

This is most useful before the period feels settled. Spot a missing day while you still remember it, notice when a weekend rate did not match your setup, or see that one heavy week is carrying most of the expected total.

When payment information arrives, compare it with your own HoursKit record rather than relying on memory. Paid status lets you mark which shifts you consider paid and keep the remaining entries visible for follow-up; it does not decide whether money was received for you.

A difference becomes easier to investigate when the dates, breaks, jobs, and rate categories are already organised. Return to the relevant shift, make a correction if your record was wrong, and keep the rest of the period intact.

Choose the job, date range, pay period, task, tag, or paid status you want to include, then preview a report before exporting it. PDF works well when the reader needs a clear finished document; XLSX keeps the rows available for further sorting or calculation.

The report comes from the same shifts you reviewed, so you do not have to rebuild the week in a separate spreadsheet. Share it when you choose, keep it for your own records, or return later with the path from summary to detail still intact.