---
title: "Why did we create EasyTime?"
canonical: "https://www.techtime-initiative.com/space/EasyTime/4554939/Why%20did%20we%20create%20EasyTime%3F"
format: markdown
---
We found that humans are quite bad at keeping up-to-date realistic timesheets. Moreover, we have been spending way too much time on, hmm... recording time – reverse-engineering the flow of our days using various forensic methods.

Our support receives and resolves only 34.7 requests on average per week, but reports from our Tempo Timesheets tell us that within the 8h working day a support engineers on our team on average records time against 25.6 issues, every day.

They might triage a new ticket, spend some time reviewing and trying to come up with the solution on the spot, reading KB articles on Confluence, searching the Internet. If the problem requires swarming, the engineer then leaves an internal comment to escalate the issue to other team members or Technical Leads. There is a lot of back and forth with the customers, and a lot of switching to another request while waiting for a response. Somewhere between all this fun the engineer will be pulled in for a morning quiz, quarterly review, important discussion, will be distracted by the latest cat meme or will get a phone call. 

There is a very high chance that time won't be logged when the engineer is switching context so much and so fast.

And that is why EasyTime was born.

[EasyTime](https://www.techtime-initiative.com/space/EasyTime) records time **instantly** when tracked events occur, **automatically** aligning and merging resulting work logs and making it easier to **visually** review your day.

EasyTime records time when a user [views an issue](https://techtime-website.atlassian.net/wiki/spaces/EasyTime/pages/4883003), comments or resolves the issue, creating work logs with distinct messages, automatically [resolving conflicts](https://techtime-website.atlassian.net/wiki/spaces/EasyTime/pages/4882953), [performing merging](https://techtime-website.atlassian.net/wiki/spaces/EasyTime/pages/4981121) and recognising relative [priority of events](https://techtime-website.atlassian.net/wiki/spaces/EasyTime/pages/4882936) so the resulting timesheets accurately reflect the reality of what the user was doing.

Work logs created will have distinct [messages that can be configured](https://techtime-website.atlassian.net/wiki/spaces/EasyTime/pages/5046769) to your liking – to produce timesheets that require [minimal review](https://techtime-website.atlassian.net/wiki/spaces/EasyTime/pages/4948091) and [manual editing](https://techtime-website.atlassian.net/wiki/spaces/EasyTime/pages/5046349) and can be send to customers as part of your billing right away.

We've been using and testing it for a year, before going public. It seems to work well for us. Will it work for you?