How to submit hours for approval

Closing the week should not be a “I already logged it” in the group chat. Whoever logs hours needs to say, on the Timesheet itself, that the week is ready for the manager to review. In Rabbiit that is submit for approval.

This article is for the teammate — the profile that logs their own hours. Whoever receives the queue and gives the OK is in how to approve submitted hours.

💡 Plan: the approval flow is part of Ultimate. The submit button only appears if the account enabled approval and your user (or your team) is on the list of who must submit. You also need a manager set on the profile.

Who it is for

Teammate (regular user) — reviews their own week, submits when it is complete, and, if the manager rejects it, corrects and resubmits. Submission already notifies the manager: you do not need to “tell the group”.

Whoever logs hours and also manages people — submits their own week here. Other people’s queue is the other article.

If the account does not use the weekly grid yet, start with weekly and daily timesheet.

Where to find it

Week timesheet with the submit-for-approval buttonWeek timesheet with the submit-for-approval button Time tracking > Timesheet, Week view. The button is Submit for approval.

It is not the Approvals screen. That queue is the manager’s.

Before you submit

  1. Confirm that the administrator turned the flow on and that you are among the people (or teams) who must submit.
  2. Confirm that your profile has a manager. Without a manager, Rabbiit warns you and the submission does not go out — ask the administrator to define who approves your hours.
  3. Open Week and look at totals by day and by project. A gap in the grid is cheaper to fix now than after a rejection.

Time-entry reminders exist so this ritual does not depend on informal chasing.

How to submit the week

  1. Open Time tracking > Timesheet and choose Week.
  2. Review the entries. Without time logged, there is nothing to submit.
  3. Click Submit for approval. The system confirms the name of who will receive it.
  4. Done: that week enters the manager’s queue and the status changes.

Submission applies only to the week period you submitted — it does not lock the entire account. The following week stays open.

A submitted week is locked

While the week is pending approval or already approved, that period locks for time entry:

  • you cannot create an entry on those days;
  • you cannot edit or delete what was already in the week.

The agreement is what you submitted. To log time on that week again, the submission needs to be undone (Undo submission, if the manager has not decided yet) or the manager needs to reject it. Without that, the period stays closed.

The goal is not bureaucracy. It is you saying “this week is ready”, instead of the manager hunting for an incomplete entry.

If the manager rejects it

Rejection returns the week to you so you can correct and resubmit. The walkthrough is in the week was rejected — what to do.

Undo the submission

Submitted too early or forgot a project? Undo submission cancels the submission for that week. The period unlocks: you can create and edit entries again, without opening a ticket. The administrator can also undo a submission made by mistake.

Do not use this as “save a draft all the time”. Submit when the week is complete.

When the account submits automatically

The administrator can turn on automatic submission on the weekly deadline. Then the week goes up on its own at the agreed time. Your job is still to leave the grid correct before the deadline — automatic submission does not invent hours you did not log.

What gets easier

You and the manager share the same status. Finance does not bill a week that was “almost submitted”. A rejection with a comment avoids the “but I had already said so” conversation.

In this article