Time logging examples

Basic Life/Work admin

This comes up, this is just very basic stuff such as planning out your day in the morning, getting a cup of tea, stretching out your back etc. Generally, these will be small chunks of time, but time worth logging nonetheless.

Drupal events

Events and event expenses

Every member may take up to 5 days per year as paid training or community days. For further guidance see the training and personal development policy.

Internal mandatory events

Such as company away weekends, Agile Collective will pay the normal working hours, tickets, accommodation, fares and expenses for such an event.

External non-mandatory

Events that fall outside of normal working hours (but are work related), you can log up to 2hrs per month as part of your contractual hours. This is of course negotiable if you feel the event has wider benefits, but will need to be included in Forecast if you plan to use this.

Examples of suitable events:


If you take any paid holiday, this needs to be accounted for in Harvest by logging the time against the Holidays & Leave project.



Check with the PM, but generally ALL time on a project (whether unbillable or billable) should get logged against the project. Speak with the PM about how detailed to be on the notes

If you are working on something a project will use, but is ultimately part of R&D speak with the PM about where to log the time best.

Research and development

We are able to claim a proportion of time (and therefore costs) spent on R&D work that is either billable to a project or unbillable. For more information on R&D tax credits, please read the overview.

This applies to direct technical R&D work. We can also claim for supporting workers like project management and admin in general. This time should be logged as normal and will be calculated as part of the reporting process after year end.

Support tickets

You should ALWAYS use the widget on the support ticket, this helps to understand how much time each ticket has “cost” the client.

If there is no ticket, it is not a meeting, and it should still be billable, consider whether creating a new ticket for the work is worthwhile.


There is a “Training and Personal Development” project in Harvest, log all training time to this.


In general and where possible, we encourage using travel time constructively, but understand that this may not always be possible.

We will endeavour to enable all our employees to work online whilst travelling through the purchase of wifi tokens on trains or using mobile phones as internet hotspots for laptops.

Overtime and TOIL

Sometimes you will work overtime and then need to take this time off as TOIL.

We do not log TOIL as this time has already been logged, in effect, by doing the overtime.

Unbillable time

Unlogged time

Logging large chunks of time against the unlogged is generally discouraged. It is important that time is meaningfully logged so that we can assess our time.

It is inevitable that we will lose some time, but using unlogged too much skews valuable reporting on our activities.

Working groups and temporary circles

From time to time, working groups and temporary circles are set up and time spent on these should be logged on the appropriate project in Harvest. There is an AC Working Groups client in Harvest that should be used when creating a new time logging project for a working group.


If something is not covered in the above examples, please ask someone relevant, or the people circle rocket channel if there is nowhere relevant.

Last updated: