A work log that
leads somewhere.

Start with the rules you actually work under.

Set up a pay profile with your hourly rate and payroll timezone. Confirm optional overtime, Sunday premium, callout-minimum, and per-diem rules only when they apply. An unconfigured rule is not silently guessed.

Rules vary by agreement, contractor, and assignment. LinePaycheck is not an automatic union-contract interpreter, and no verified agreement library is promised at launch.

Keep the work and its context together.

The planned work log covers adding, editing, and deleting work intervals, callouts, and overnight work. Preserve the relevant timezone and the rule snapshot behind a calculation rather than applying today's settings to yesterday's record.

Read the Pay Ledger, not a black box.

Expected gross wages are broken into hours, rates, multipliers, and amounts. Open the explanation to see how a component was calculated. Keep reimbursements such as per diem distinct from gross wages and net take-home pay.

Compare, then investigate.

Planned paycheck checks compare confirmed paystub information with expected pay. A difference is a prompt to review the inputs, not proof of underpayment. Paystub scanning is intended to run on-device; uncertain extracted fields need your confirmation.

History and shareable audit reports are part of the planned Pro offering. Availability must be confirmed in the released app.

Keep the architecture personal.

No LinePaycheck account or central paycheck database is planned. Device-local work, platform-managed purchases, and explicit sharing keep the basic workflow simple.