Hours you can put in front of a client

You can run a timer somebody has to remember to start and remember to stop. Or you can fill in a timesheet on Friday from memory. One undercounts because people forget; the other guesses because a week is long.

Both end with a number in front of a client that nobody in the room can actually defend when it is questioned.

Deskly already knows when you were here, which room you were in, and whether you were active - not because it watches you, but because a virtual office has to know where people are to work at all.

So the only thing left to ask is what you were working on, and that is one tap from wherever you are standing. What it opens is a window, not a stopwatch. There is nothing to stop.

• The hours are the intersection of that window with real, active presence.
• Idle, away and offline never count - a browser left open in an empty room is not work.
• Task time can therefore never exceed office time. Correct one and you have corrected the other.
• The gap is shown, not hidden: "Not attributed" is hours somebody was here for and never put against anything.

Presence-derived hours are useful inside the office and meaningless outside it. A sprint review, an invoice or a contract runs on what is in Jira.

So we show both columns - what the office saw, and what the tracker was told - with the difference between them and a button. Nothing is ever written into somebody else's system of record without a person pressing it, and it is written with their own credentials so the worklog honestly says who it belongs to.

That is the whole design rule: Deskly measures, the tracker decides, and a human presses the button between them.