Derived from the time-entry ledger. There is no “currently clocked in” flag anywhere, on the server or on a device.
Today shows who is on the clock and what needs attention. Both are office information and your role does not include either. The office can grant access if you need it.
Field access is the presence of a credential and nothing else. A reset issues a single-use secret shown once — no password is readable by anyone, including the Owner.
Revoking stops the backend trusting a device at its next contact. It states how much unsettled work the device holds; forcing a clearance, which can destroy unsynced work, is Owner-only and separate.
Works owns these records. A customer is the party billed; the property is what equipment and service history belong to, which is why selling a house does not move the water heater.
Only jobs this backend owns appear here. Works 5.x's existing jobs are not in this database and never were — that is what keeps a job from being changeable by two systems at once.
A job is created against a customer and one of their properties. Assigning rides on creation: there is no separate authority to hold. A job with no date is unscheduled, and cannot be dispatched until it has one.
A photograph's record is this row, not its storage location. The bytes can move, be re-uploaded or move to cheaper storage and every link, caption and capture fact survives — which is precisely what Works 5.x cannot do, because it used the Drive file id as the record's identity. That is also why six duplicate photo folders exist there that only a content hash can now untangle.
Nothing on this page can delete a file. The check below corrects the record to match what storage actually holds and reports what it found; a sweep that could delete is a sweep that can lose a photograph through a bug in itself.
This is the weekly payroll handoff. Works 5.x computes payroll from its own time entries, so a technician clocking in on Field would show 5.x zero hours. The office keys these totals into 5.x once a week. There is no adapter, and there never will be one writing into the sheets 5.x treats as authoritative for pay.
Approved time off is a hard scheduling constraint. Works will refuse to create a job for somebody who is away — not warn, refuse — and there is no override here. A clash that appears after a job was scheduled is listed below for the office to resolve; Works never changes a job on its own.
Denying needs a reason. A refused absence with no explanation is the kind of thing people remember for years, so the reason is required and it is kept on the record.
These were scheduled before the leave was approved. Works has changed nothing about them.
Earned PTO accrues at one hour per thirty eligible hours, overtime included, beginning after the first eighty consecutive hours of employment. Running a week twice credits nothing twice. This computes no pay.
The dates Cornerpost does not work — which is not the same list a calendar prints in red. A date recorded here with Cornerpost closes: no says the day exists and is worked, which is worth keeping rather than leaving off.
Leave is not charged for a recognised holiday inside a requested range. Until a date is recorded, Works treats none as holidays — it does not guess at the federal calendar.
A conflict keeps both versions verbatim. Settling one requires a choice and a written reason — the field never adjudicates its own conflict.
Authentication failures, lockouts, revocations and permission changes.