Taming the Time Card

At some point, most of us have been required to submit time cards. To most professionals the task often seems maddeningly trivial, especially when the card is due in ten minutes, we've forgotten how we actually spent our time for a few days, and the whole thing is just a piece of fiction.

In accounting or law, where time spent determines client billing, time reporting is obviously necessary. For many other professions, expended-effort data seems to have no real purpose. But expended-effort data can be an indispensable management tool for project-oriented organizations.

Why is this data so important? Projects are supposed to end. Often there's much more project work to be done than people to do it, which creates pressure to complete successfully any existing projects. That's one reason why project sponsors always ask, "When will it be done?"

To answer such questions, project managers need to know roughly how long each task should take, and how much effort has been expended so far. They estimate the former and measure the latter.

Management would rather estimate than guess time to completion. Lacking historical effort data, estimates cannot be based on data; lacking current effort data, actuals are little more than hunches. By tracking the time of project team members, project managers can control projects better because they can base their estimates on real data.

The primary requirements
of any time-card system
for professionals:
respect their time
and respect themIf your organization is project-oriented, and you don't yet collect expended-effort data, you might consider starting. But whether a system is in place, or you're considering one, take care that it meets your needs without burdening or insulting professionals. A well-designed system can be minimally intrusive and still yield useful data.

Here are some criteria for a time card system that doesn't put the corporate culture at risk:

• Gather effort data only from the people who work on projects.
• Include all overtime.
• Don't bother with supervisor's signatures. Any professional inept enough to get caught lying that way is not to be trusted with important project work.
• Collect data weekly. This helps keep people fairly current.
• Don't try to account for 100% of a person's time — focus on the time spent on project work.
• Put the system on the Intranet. Make it easy to use from anywhere.
• Provide a separate account for each project task, so you can compare actuals with estimates.
• Pick a minimum resolution: 15 minutes or more. Any finer than that is fiction.
• Report all work done, no matter where — even at home or on travel.

If people understand the need for the data you collect — and if you use that data — your time reporting system will be a tool, not a target.  Top    Next Issue

The article you've been reading is an archived issue of Point Lookout, my weekly newsletter. I've been publishing it since January, 2001, free to all subscribers, over the Web, and via RSS. You can help keep it free by donating either as an individual or as an organization. You'll receive in return my sincere thanks — and the comfort of knowing that you've helped to propagate insights and perspectives that can help make our workplaces a little more human-friendly. More

Your comments are welcome

About Point Lookout

Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.

Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.

Related articles

More articles on Personal, Team, and Organizational Effectiveness:

The Hypothetical Trap

Politicians know that answering hypothetical questions is dangerous, but it's equally dangerous for managers and project managers to answer them in the project context. What's the problem? Why should you be careful of the "What If?"

Decisions, Decisions: I

Most of us have participated in group decision making. The process can be frustrating and painful, but it can also be thrilling. What processes do groups use to make decisions? How do we choose the right process for the job?

Working Lunches

To save time, or to find a time everyone has free, we sometimes meet during lunch. It seems like a good idea, but there are some hidden costs.

Guidelines for Sharing "Resources"

Often, team members belong to several different teams. The leaders of teams whose members have divided responsibilities must sometimes contend with each other for the efforts and energies of the people they share. Here are some suggestions for sharing people effectively.

You Might Be Stressed If…

A little stress once in a while keeps us sharp, but chronic intense stress shortens lives. Stress can build gradually, out of our awareness. Here are some indicators of chronic intense stress.

See also Personal, Team, and Organizational Effectiveness and Personal, Team, and Organizational Effectiveness for more related articles.

Forthcoming issues of Point Lookout

Coming June 4: White-Collar Contractor Sabotage

Modern firms in competitive, dynamic markets draw on many types of employer/employee relationships, including contractors. By providing privileges and perks preferentially among these different types, they risk creating a caldron of resentments that can reduce organizational effectiveness. Available here and by RSS on June 4.

And on June 11: More Things I've Learned Along the Way: VI

When I gain an important insight, or when I learn a lesson, I make a note. Example: If you're interested in changing how a social construct operates, knowing how it came to be the way it is can be much less useful than knowing what keeps it the way it is. Available here and by RSS on June 11.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenubcqSvusyBsQaEDwner@ChacfhuriyFKgDguTpuYoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

• Get 2001-2 in Geese Don't Land on Twigs (PDF, )
• Get 2003-4 in Why Dogs Wag (PDF, )
• Get 2005-6 in Loopy Things We Do (PDF, )
• Get 2007-8 in Things We Believe That Maybe Aren't So True (PDF, )
• Get 2009-10 in The Questions Not Asked (PDF, )
• Get all of the first twelve years (2001-2012) in The Collected Issues of Point Lookout (PDF, )

Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info