If you are paid by the hour, "what will I actually take home" is a question your hourly rate cannot answer on its own. Withholding, overtime, and uneven weeks all sit between the number on your offer letter and the number in your account.
A shift has three lives
Clocked treats a shift as something that changes state over time. It starts scheduled and projected, becomes worked once you record the real hours, and finally finalizes when a paycheck pays for it and locks in the actual money.
- Scheduled: a future shift, projected from your wage and take-home rate.
- Worked: real hours recorded, but the money is still an estimate.
- Finalized: a logged paycheck has paid for it, so the numbers are now real.
Why the loop matters
Until a projection meets a paycheck, it is a guess. Closing that loop is what makes Clocked honest about your pay instead of optimistic about it, and it is what lets every future estimate lean on real history rather than a flat assumption.
Everything stays on your device, with no account to create, so the only thing reconciling your shifts and paychecks is your phone.
Why Clocked learns your take-home instead of guessing it
A flat "you keep 75%" is a fine place to start and a bad place to stop. Here is how Clocked tightens that estimate every time you log a paycheck.
Two jobs, overtime, and unpaid breaks, kept straight
Real hourly work is rarely one clean wage. Clocked models the messy parts - multiple positions, overtime thresholds, and unpaid breaks - so the math comes out right.
What happens when you log a paycheck
Logging a paycheck is the moment Clocked stops projecting and starts proving. Here is exactly what it does to your shifts when a real check comes in.