Accurate time entry is a major obstacle at many MSPs. In past decades, industries have radically evolved — but the issue of time management has remained. Clearly, the solution for consistent employee-motivated time entry isn’t at large.
That’s why MSP+OS hosted a webinar unpacking how MSPs can conquer time entry once and for all — for long-term results.
In Part 3 of this recap, we cover:
Let’s dive in.
When employees consistently enter their time during work hours, it streamlines everything.
On one end, employees aren’t coming in after work or on weekends to close tickets when failure to enter time hasn't kept them accountable. Rather, they understand the value of their own time and don’t want to be working after hours. On the other end, when work is consistent, clients get time entries and invoices on time.
After all, the thing about time entry is:
When you put your time in, that goes to an agreement.
That agreement goes to a ticket.
That ticket is attributed to a project.
Finally, the client gets billed.
MSP+ has had clients with engineers who haven’t put time in for months – if you sent a belated invoice like that right now, 2022 books are already closed out. Clients will literally refuse to pay.
You’ve created a collections problem, and that cycle keeps building on itself and trickling down to other levels.
To avoid serious situations like this, ensure you communicate the value of time entry to your whole company. With that tenet established, it’s easier to announce new standards and trainings. Setting honest expectations is akin to gently putting the hammer down.
Here are some tips to follow as you continue to streamline and enforce time entry:
Ultimately, time entry takes time.
But, it can be rewarding to see your wrapup at the end of the week. The organization and efficiency that result from an easily-formed habit are integral company improvements.
If you notice someone is consistently entering giant blocks of time (say, eight hours straight) when you know they took breaks, here are some tactics you can employ: