How to automate time entries
Some work repeats every week: a fixed hour package on a client, an on-call shift, an internal allocation. If the team re-logs that by hand, time entry becomes form-filling — and the real hour of the day competes with the “table” hour.
Hour logging automation puts those rules in Rabbiit: you define what is entered automatically and when the rule runs. You can adjust it on screen and import rules in CSV to get started faster. Recurring hours are entered while the team works, not while they fill a spreadsheet.
Automation does not invent hours in the future: it only generates what already makes sense on the calendar. The report still shows work from the period, not a forecast.
💡 The menu path is Settings > Timesheet automation — that is the hour logging automation screen. Whoever configures it is an administrator (or whoever runs the account operations). Whoever feels the effect is whoever logs hours and whoever reads the report.
Who it is for
Administrator / operations — writes the rule: who, which project, what volume, at what time automation runs. Also imports the CSV when the account already has an allocation table.
Manager — stops chasing the “default log” every Monday. Still responsible for reviewing and approving the submitted week — automation does not replace a human look.
Team member — sees the recurring hour already in the log and only adjusts exceptions (absence, project change, overtime). Day-to-day is left for work that changes.
Finance — gets a more complete period at close, as long as the rules are right. A wrong rule scales the error: review in the first month.
Where to find it
Timesheet automation rules
Settings > Timesheet automation
This is different from logging reminders. A reminder notifies whoever has not logged. Automation logs what is repeatable. Many accounts use both: the rule covers the fixed package; the reminder covers the rest.
How to get started without getting lost
- List what actually repeats every week (not what “would be nice” to automate).
- Open Settings > Timesheet automation and create the rule on screen — or import the CSV if operations already have the table.
- Set the time automation runs, in the company time zone. The team needs to know when the hour appears, so they do not think it “vanished” in the morning.
- Run one week in parallel: look at the week log of the people affected. Adjust the rule before rolling it out to the whole account.
- Ask for the week to be submitted and approved as usual. Automation fills the board; the manager still validates.
When to use — and when not to
Use for recurring hours, stable internal allocation, agreed on-call.
Do not use for a project that changes every week, or to “fill capacity” automatically. That hides who did not really log and breaks capacity.
Do not use in place of the timer. Variable work still goes manual or on the timer.
What gets easier
The team spends the weekly ritual on exceptions, not on what was already agreed. The manager receives a fuller week. Operations stops keeping a sister spreadsheet just for allocation.