In My hours, choose a week and record time against your own stop, appointment, job or project. Start and stop a timer or enter start, end and break manually. Minutes are rounded up and breaks deducted. Overlapping and future time are rejected. Entries last at most 24 hours. A forgotten timer remains visible across week boundaries: choose the actual end time yourself. Time is never shortened automatically.
Your planner sees the source, employee, start, end, break and billable flag. Planners review other people’s time once. Rejection requires a reason, visible in your own list. Resubmit rejected time with the requested change. Approved hours remain as a source and cannot be silently overwritten. A running timer is excluded from week totals. Non-billable time is labelled.
Review hours shows the hours of the week in pages of 25, with a filter on status (all, waiting for review, approved, rejected). The figures and bars at the top always count the whole week, including what sits on another page. A link to a single hour (for example from an invoice proposal) opens the page where that hour is.
Export hours downloads your own week as CSV. Planners can export the team week from Review hours, up to 50,000 lines. Export requires the usual authorisation, which may be unavailable during a trial. The CSV labels UTC timestamps and includes source IDs. The screen uses the workspace time zone. Customer text is included in the customer’s privacy export and anonymised on erasure; the employee’s timesheet is excluded from that customer export.
Approved hours provide structured input for an invoice proposal. The invoice proposal selects rates from the existing quote or price list. This step creates or sends no invoice and requires a connection. Offline route status storage does not include time recording.
Via MCP and the director
You can also do your own hours with a key: planning_uren_lezen, planning_uur_schrijven, planning_timer_starten and planning_timer_stoppen (right planning.rooster_eigen). Own means the account that created the key; the person is never input, and a key without a linked account has no own hours. The same rules apply as in the screen: no overlap, no future time, a timer runs on the server clock.
For a planner (planning.beheren), planning_uren_lezen with wie=team reads the hours of the team and planning_uren_beoordelen_lezen shows what is waiting; both work in pages (pagina, 500 and 200 lines) and say totaal, paginas and afgekapt in the answer, so nothing drops silently. planning_uren_beslissen is a proposal: approving or rejecting (with a reason) only happens when a planner signs under Approvals, and that planner is then the reviewer on the hours. A model does not decide on anyone's hours, and you cannot review your own hours.