Some organisations approve time entry by entry; others expect a person to submit a complete week and a manager to sign it off in one go. TimeSheets supports both, chosen site-wide.
1. Switching to weekly mode
Set Approval mode to *Weekly* in Admin Settings. This changes how everyone works, so it is a site-wide decision rather than a per-project one.
In weekly mode individual entries are no longer approved on their own. They move as a week.
2. Submitting a week
A week starts on Monday. While it is open, entries are drafts — yours to change freely. Submitting hands the whole week to your approver at once.
- Fill in the week — as normal, from the Calendar or the Log time dialog.
- Check the totals — the submit bar shows the week's hours before you commit.
- Submit — every draft entry in that week becomes pending together.
The bar appears in two places: on the Dashboard for the current week, and on the Calendar's week view for whichever week you are looking at. Use the calendar to submit an older week.
A log spanning two weeks needs two submissions — a week is the unit, so each one is submitted on its own.
3. Recalling a submission
Made a mistake? Recall pulls the week back, provided nobody has decided it yet. The entries return to draft and you can edit them.
Once a week has been approved or rejected it cannot be recalled — that would rewrite a decision someone already made.
4. After a rejection
A rejected week goes back to you rather than being final. Fix what the comment asked for and submit it again — a week can move from rejected straight back to submitted, as many times as it takes.
An approved week is the end of the line. Correcting one means an unlock request, or voiding the invoice if it has been billed.
5. Approving a week
Approvers see submitted weeks in the Approvals queue as a single item with the week's total. Approving accepts every entry in it; rejecting sends the whole week back with a comment.
Weekly mode has its own automatic-approval sweep, using the same timeout as per-entry mode. A week left undecided long enough is approved and marked as system-decided.
6. Being told the outcome
When a week is decided you are emailed, with the approver's comment if they left one — the same message a per-entry decision sends.
In the app it shows in the My week submissions gadget on the Dashboard, including the reason if it was rejected, and on the submit bar for that week. A rejection also raises a sent back alert at the top of the Hub.
7. Weeks carried over from per-entry mode
Switching a site to weekly leaves whatever was already awaiting approval in an odd position: those entries were never part of a submitted week, because weeks did not exist when they were logged.
They are grouped onto their Monday and shown to approvers marked carried over, so it is clear nobody chose to submit them — the mode changed underneath. Deciding one works exactly like deciding any other week.
Submitting a week whose entries are already awaiting approval simply records the submission. There is nothing to move, and it is not an error.
8. What locks while a week is out
A submitted or approved week cannot be edited. Attempting to change an entry in one gives a message saying whether it is submitted (recall it) or approved (it is final). This is separate from, and additional to, the lock window.