How much internal effort and resources will I need to make a timesheet work?

First, let's talk about the effort to implement TimeControl when it is first deployed. This is highly dependent on several factors including the number of users on TimeControl and the number of external system to which TimeControl will be integrated.

The TimeControl QuikStart program was designed for a mid-sized organization doing a basic deployment of TimeControl with only a couple of interfaces to create.

This is a 5-day effort by HMS and requires internal support of a TimeControl Administrator for 3-5 days prior to making the timesheet available to the end-users.

If you are deploying TimeControl for 10-200 people and making a simple link to a project management tool and another export link to a finance tool, then this is probably sufficient.

Of course some people have much more complex environments and wish to integrate TimeControl to numerous internal processes and tools. Depending on the level of complexity, a multi-thousand person deployment covering numerous countries systems, internal payroll rules and more could take a team several months to complete the deployment.

Next, let's talk about time to administer and support TimeControl once it is in use. The technical time to support TimeControl is negligible. You have to make sure data is being backed up, but that's probably being done anyway as part of the DBA's responsibilities.

Upgrades and updates take very little time and are done only a couple of times a year typically.

Administrators are often not full-time on TimeControl unless it is a system with thousands of users.

The work each week Administrators focus on is making sure new employees are onboarded and that employees who have left are made inactive and looking to do regular clean ups of old data.