Following on from my earlier blog on booking time in 15 minute blocks to ease and speed up entry, this time I want to look at your protocol.
This refers to the in-house rules you have for time recording, and is often overlooked or taken for granted.
To keep it simple, I recommend at least the following four rules need to be considered when building a protocol for timesheeting in any organization.
The first protocol: what am I doing?
Perhaps the best place to start is with Activities.
If Projects represent the goal of either a specific job or commission (or in the service sector – the provision of an ongoing service perhaps to a specific customer/client), then an Activity is the type of effort that contributes to achieving that goal.
Against each Activity you can specify in free-text exactly what you expect your Staff to use each Activity for. This avoids confusions of generic items like ‘MEETINGS’ – is that in-house meetings AND professional customer consultations or are they separate?
Get that wrong from the start and sooner or later you’ll have people booking to the wrong Activity. So why not make it clear by specifying the type of Activity covered by a specific Activity Code.
Place your spec in the Setup > Activities > Maintain Activities {select your Activity and click Change to edit it}: Description of Work field.
When communicating your protocol (either in at least an e-mail to everyone but perhaps in a protocol document which you might place on your Intranet or whatever), why not then include as an appendix a pdf print of report Administration > Lists > Activity Listing – it offers a print of the Description of Work against each Activity?
The second protocol: how much detail do I have to go into?
This refers back to my earlier 15-minute article, but you might have a situation where other time-units apply be it more (30 minute blocks) or less (6 minute blocks is typical of legal settings, for example).
The third protocol: great, yeah but no but how do I do it?
Our contention is that day-to-day end-user use of Time Manager should be so easy that no end-user training is required. Especially if your Administrators have got their configuration right.
But Pillar can’t be responsible for the communication of the basics, such as distribution of the URL, what each individual’s Login will be and exactly what constitutes your protocol for time recording.
Rather, this is best communicated in a single, easy-to-use document that ideally details both the initial steps to access the software in your environment with all the relevant credentials and clearly states your rules and expectations of use (the protocol itself).
Most importantly, give Users the means to help themselves – give them the links to our support area, this blog and, in particular the videos. Tell them how they can access the in-system Help and where all else fails, who to discuss things with internally (they’re the Supervisor/Administrator who might then, in turn, contact our Helpdesk).
The fourth protocol: when should it be there?
All the above is naught without the fourth protocol which refers to when timesheets should have been Submitted. Unless you tie this down you could be chasing forever.
This is often looked upon as merely a practical administrative problem, but without the full set of time records, your reporting is incomplete. That means the business decisions you make may not be based on the full extent of evidence that ought to be available to you. And therein lies the risk.
Wrapped up in the fourth protocol is the process by which you then extrapolate information from the data garnered. This is the point of the entire system.
It therefore requires management and stakeholder buy-in to the whole reason d’être for deploying a time management system in the first place.
Ordinarily, I find most enterprises opt for about 2-8 monthly standard reports which could be a mix of statements and progress reports as well a bit of forecasting. If stakeholders don’t know what information they want out of the system, how can Administrators build a data structure which will reflect their needs?
And this is why the fourth protocol is the most important.
CHANGE
Sometimes those needs change – perhaps the business has changed or the way a service is to be provided requires a re-structure of the organistations resources. If this is the case, then it is a good time to look again at your protocol. And don’t forget – we’re here to help and offer on-site business consultancy on this very matter.
If you’d like to discuss any of the above, e-mail me on carl@profess.co.uk or login to WordPress and post you comments here.