Yes, you read that right. Monthly reporting is here which should explain why our reports have been seeing some adjustments and tweaks lately 😁.

It's probably our most requested feature and we've been working away on this for a while now, so I'm really happy to be able to share it with you all.

You can now, finally, find out how many days off were taken in a specific month. Either by a user or by a specific leave type. If the booking crosses over multiple months that's fine, you'll get the numbers for the month you requested.  You'll see a brand new monthly report in Settings > Reporting & Backup which follows our usual reporting format.

Data is available for all of your bookings as far back as the start of your user's current leave year and all future bookings from now on and this is available for everyone on all Timetastic plans - we're not making this Pro only.

We're updating the help centre with more details on reporting in the coming days with full explanations but hopefully this will make your lives easier.

You'll notice we've renamed and moved some columns in the reports on the Leave sheets - apologies if this breaks your macros/integrations but it's for good reason, we promise.

We've collected up some bugfixes around allowances being recalculated wrongly if they finish at midnight and some speed improvements to reporting and allowance calculations.

Small update that hopefully improves your reporting a bit - we've added booking ID to "leave" sheets in reports and added a user's department name too. 

Keep an eye out for future reporting updates!

We've had this one requested by a few people and it's always been a good idea. So today we're solving a pain point with the API. 

Who is absent on x day?

Previously you'd need to query the bank holidays, work schedules, holidays endpoint for every user to get a nice list of who is off. Then merge them all together at your side. 😱

Now?

Just query api/absences with your dates and what type of absences you want and you'll get a list broken down by day and by user with everyone's absences. 👌

You can query for just public holidays, bookings, all types of absence (public holidays, non working days, bookings) or if you've got an external dashboard/app to update and want to get everything you see on the wallchart  then query "AllEvents" and you'll get work anniversaries, birthdays, locked dates and all absences. We include some basic data and the associated record ID so you can query for more data if you need it.

We limit the endpoint to 31 days so you can query for a whole month at a time and we've had to rate limit this to 1 request per second.

Full details are in our API docs: https://app.timetastic.co.uk/api-docs/index.html 

Show us your integrations - we'd be keen to see how this is being used! https://x.com/timetastic 

Small but important update today. We've updated and moved the API docs 🔧. There are no changes to the underlying API so you can rest easy, but the postman collection has now been replaced with a nice OpenAPI specification document.

https://app.timetastic.co.uk/api-docs/

We'll be improving these over the coming months so if you spot anything wrong/missing let us know.

All your old links to API docs should still work and any future updates will be made to the OpenAPI spec rather than the postman collection.

We’re introducing a new feature: you can now schedule user archiving for the future! 🎉

Instead of archiving users immediately, you can now set a future end date, giving you better control over when employees are archived. We’ve also added the option to pro rate leave balances up until their final working date, ensuring that leave data stays accurate.

There’s more on the help centre:
📖 Pro rata calculations

 Stay tuned for more updates! 🚀

This one came directly from a few recent feature requests and made so much sense to us we got straight on it.

Say hello to working hours on your work schedules:

We now count up the working hours for the week in your business hours, work schedules and custom schedules so you know how many hours people are working in that week when you set it up.

Small, simple, effective - just how we like it. Keep your feature suggestions coming, we read and discuss them all 🙂

A small but important update to our reporting today. 📊

We've got some new fields, moved some fields to more sensible places and made report generation faster.

Full backup report:

The users tab has Accrual data just before the allowance summary columns (AD->AF if you're a Pro user) and we've moved the Accrual flag to not be at the end of all the leave types.

Annual summary report

Columns K,L and M now hold accrual details for users who have accrued leave:

Column T has Unused Carry forward

User Report

A user's "personal" report that they can download at anytime now has new branding and the accrual columns added on the UserData sheet in Columns AD to AF. 

In addition unused carry forward is on the Allowance Breakdown sheet on Column I

Apologies if we have broken your macros or integrations, but hopefully you'll appreciate the improvements!

Happy new year, happy new feature 🥳

We've got an improvement to our booking history today. From now on we track more detail about everything that's happened to a booking so as well as "who approved it and when" we can show when recalculations happened, when the reason or attachment was changed/updated and even the source (Slack, Teams, Mobile, etc).

Existing bookings we don't have this information for will show the data we do have.

Bookings made from today will show as much detail as we collect. If something's missing or you'd like to include something specific, reach out and let us know and we'll add it to the suggestions list.

While in there we've fixed some timezone issues and hopefully improved the design.

It looks like this:

You'll have probably noticed we've updated our UI colours and leave type colours recently. These align better with WCAG standards and make life easier for people with vision impairments.

Also you'll now get a notification if someone's changed a reason or changed an attachment after a booking has been made (Anyone using the API will note this raises a new webhook event type)