Fill in your timesheet

Personas: Employee (books their month and submits it, from the Personal shell) · Modules: Timesheets Your month on a project arrives pre-generated — one 8-hour day per working day. You adjust the days that differ, then submit; your manager approves. The unchanged month is literally one click.

Before you start: you sign in to the Personal shell at /services/web/personal/ — it needs an Employee record whose Username equals your login (that is what every personal page resolves you by). You must be assigned to the project's team; otherwise no timesheet line is generated for you. An administrator who has no Employee record of their own can still reach the flow by acting as an employee.

1. Your month is waiting — Employee (Personal shell)

1. On the 1st of the month, your timesheet line is created automatically for every active project you are assigned to, and a Submit task appears in your Inbox — the Personal shell's home page. The task is yours alone, not a group queue.
2. Your line is named after the project-month plus you — e.g. "2026 July - Acme Website Redesign - Ivan Petrov" — status DRAFT, already filled with an 8-hour billable allocation on every working day.

2. Adjust the days — Employee (My Employee Timesheets)

1. Open My Employee Timesheets in the sidebar and click your line. Only your own timesheets are listed — you cannot see or touch anyone else's time.
2. The day allocations are the document's line items, and they render as a month calendar on your personal page exactly as they do in the back office — each booked day an entry titled with its hours and coloured by its billable flag; click an empty date to add a day (the date comes prefilled), click an entry to edit it. The difference on your own page is not the widget: it is what is hidden (the rate and the money, see step 4) and the strict own-records scope. Starting from an empty month, Fill Month creates an 8-hour billable line for every working day (Mon–Fri) in one step, skipping any day that already has a line — then you only tweak the exceptions.
3. Per day you set the hours (0 is fine), the Billable flag (on by default — untick for non-billable time), and optionally the project Task the day was spent on. Delete days you did not work.
4. What you will not see: the billing rate, each day's amount and the timesheet's rolled-up billable amount are held back on your personal pages — they never even leave the server for the Personal shell. You do see your total hours, recomputed as you edit.

3. Submit — Employee (Inbox)

1. Open the Submit task in your Inbox (it is also shown inline on the timesheet itself). The task form shows the number (still a temporary placeholder), the project-month, your total hours and the status — no money fields.
2. Click Submit. The status moves to SUBMITTED and the timesheet goes to your manager for approval.

What happened behind the scenes

• Each day you add snapshots your billing rate from your project assignment, server-side — days keep the rate they were booked at; the day's amount is hours × rate.
• Every edit rolls up twice: to your line's total hours / billable amount, and through it to the project-month's totals.
• Status path of your line: DRAFT → SUBMITTED (your submit) → APPROVED (manager), or REJECTED if the manager sends it back. The real TS-number from the "Project Timesheet" series is stamped only at approval.

Variations and refusals

• Rejected? If the manager rejects, your timesheet turns REJECTED — clearly distinguishable from a fresh draft — and the Submit task comes straight back to your Inbox: correct the days and resubmit; it is the same flow, not a new one.
• Approved = locked. Once your timesheet is APPROVED it is payroll/invoicing input — editing or deleting it refuses. If something is wrong after approval, talk to your manager.
• No timesheet arrived? Either the project is not ACTIVE or you were not on its team when the month was generated — ask your project manager.
• Booking for someone who is away. The Personal shell is strictly your own records, so there are two routes: a manager books the days on the regular (back-office) pages, or an entitled user acts as that person (see How it works) and books from the Personal shell in their name — the entry is recorded as theirs, while the audit log keeps the real login.

See also

• Timesheets module · Plan a project · Approve and invoice a project timesheet