Direct answer
Add the paid setup meeting to the shift total, then subtract only unpaid breaks.
Setup time matters only when the employer treats it as paid work.
Tie the answer to the record you are using: a time clock export, pay stub, PTO system, company calendar, or policy note. That is where most wrong results start.
Open Hours Worked CalculatorFormula and worked example
Formula: Paid hours = setup meeting time + shift span - unpaid breaks.
Example: Example: a 20-minute paid setup meeting before an 8-hour shift turns into 8.33 paid hours if lunch is still unpaid.
Keep the example visible while you replace the numbers. It is easier to catch a wrong lunch rule, date rule, or deduction period when the clean example is still on the page.
Comparison table
| Part | Value | Why it matters |
|---|---|---|
| Question | counting paid time when a shift starts with a setup meeting | Defines the calculation |
| Formula | Paid hours = setup meeting time + shift span - unpaid breaks. | Keeps assumptions visible |
| Example | Example: a 20-minute paid setup meeting before an 8-hour shift turns into 8.33 paid hours if lunch is still unpaid. | Shows the number in context |
| Calculator | Hours Worked Calculator | Tests real inputs |
Step-by-step method
Key checks
- Write down the raw punch times, corrected times, unpaid breaks, paid breaks, schedule date, workweek boundary, and rounding rule before calculating.
- Calculate the ordinary version first. Add the exception only after the baseline is clear.
- Apply the rule: Paid hours = setup meeting time + shift span - unpaid breaks.
- Adjust for missed punches, meal breaks, paid rest breaks, overnight work, multiple shifts, rounded punches, holidays, and custom schedules only when those details apply.
- Compare the result with your time clock export, schedule, manager correction, payroll note, or written timekeeping message before using it for a real timesheet correction, payroll question, work-hours estimate, invoice, or schedule check.
What can change the answer
The answer can change when missed punches, meal breaks, paid rest breaks, overnight work, multiple shifts, rounded punches, holidays, and custom schedules are part of the real situation.
The calculator is still useful; the important step is matching the inputs to the record, schedule, paycheck, or policy you are checking.
If the number will go into a payroll question, PTO request, resignation note, invoice, or deadline message, save the assumption that changed the result.
Real-world check
Keep the setup meeting as its own paid block if it sits outside the normal shift. That explains why the day is longer than the schedule.
Subtract lunch once after adding the meeting. The meeting should not create a second unpaid break unless the time record says so.
Keep setup time visible
A paid setup meeting should not be hidden inside the normal shift span if it happened before the shift. Put it on its own line so a manager or payroll reviewer can see why the day is longer than the schedule.
If the meeting happened during the normal shift, do not add it again. In that case it is already inside the clock-in and clock-out span.
Key checks
- Copy format: setup meeting 20 minutes, shift 8.0 hours, unpaid lunch already deducted.
- Review question: was the setup meeting outside the normal clocked shift?
Common mistakes
Key checks
- Do not count every meeting as paid automatically.
- Do not forget to subtract unpaid lunch after the meeting.
- Do not double count setup time and the normal shift.
Use the related calculator
Use Hours Worked Calculator when you want to test this question with real inputs instead of doing the math from memory.
Copy the result with the assumptions beside it: dates, hours, pay rate, break treatment, deduction period, or policy detail.
Run a second scenario when one input changes the result sharply. That is usually where the real decision sits.
Open Hours Worked Calculator