How do I account for a Workers time spent on meetings and calls?

Hi: We handle it a couple of ways: 1) If it is a recurring meeting, we create a part of the plan (at the bottom) where we use WorkFront’s ability to create recurring tasks. Then, the PM regularly closes past meetings each week; 2) For ad hoc meetings, we have a bucket of time that we put people on. Depending on how well things are understood, we might have more or less hours. It’s a guess, really. People can put their time in that bucket. I don’t like this alternative generally, because people will start dumping their time against this bucket rather than take the time to apply their time to the correct tasks. I frown on timesheet buckets; If the essence of the project labor is spent in meetings, then planning the meetings by deliverable, and planning who should be involved might be time well spent. In this alternative, people would have tasks that represent the various meetings they would attend. For example: Deliverable: Print Ad · Meeting to discuss client key messages, tone, talent; · Meeting to storyboard / mock up ads; · Meeting to get final agreement on approach and look/feel; · Meeting to review short list of talent; · Meeting to mock up ads using PhotoShop; · …you get the idea. If the tasks are REALLY meetings, then model them that way. If the goal is resource planning, more detail is better. More detail, however, is more difficult to manage, both for the PM and the person filling out their timesheet. Does this help at all? Let me know. Thanks, Eric

Eric - thank you for the approaches, they are certainly helpful. These types of meetings and calls are not necessarily related to specific projects which make them hard to work into a project plan. They often happen same day or a couple days in advance. The goal here is having a Worker's weekly resource allocation include unplanned meetings, calls, overruns, misc etc. not part of any project task list. These Worker users are not filling out timesheets. Have a General Meeting Project and allocate, say 4 hours a week, for Workers so that the resource allocation is more accurate. I would have to give all workers Manage rights to the project so they can modify hours as needed (adding more or less hours spending on how week looks). But I don't think that will be an issue for them to have 'sync up' weekly meetings time by adding or removing time. I think it has to be user-managed vs a project manager tracking this information down. Thanks for the ideas! -----End Original Message-----

We track meeting hours three ways. 1. In a project as a meeting task. 2. As a hour entry in the General Hours section on the timesheet 3. We have a quarterly "Cost of Doing Business" project where we track time for things like that (certain meetings, demos, reporting, participating on the WF community forum =). Adina

Hi: Okay, I see what you mean. Here is something else we do: I have two Demand Plans. These are simply project plans where we plan two kinds of demand - future projects that are in the pipeline, will likely be approved but aren't yet, and Support. The Support Demand plan accounts for the average amount of time we expect someone to spend working on support work. You could create a project plan and model the generic meeting time in there. I do think it will prove problematic allowing everyone access to that plan to modify tasks to represent meetings. You also need PLAN licenses for everyone to modify tasks. Yes, a WORK license can be authorized to create tasks, but to perform maintenance, you'll need a PLAN license. Another approach would be to let people create issues of type Action Item. Issues look and feel a lot like tasks inasmuch as they have the same essential attributes available - start time, end time, planned hours, assigned resources. You can charge time to issues, which means they will appear in their timesheet. If you configure it right, you can even set it up so they can send an email to WorkFront, which becomes an issue. If you want to be clever, you can set up a request type that ends up in a common demand plan. A request is really an issue in WorkFront. Using emailed issues or requests really makes it easy for them to create an object specific to their meeting that can be charged against. I assume you really don't want a generic bucket that spans a long period of time. You really lose a lot of the detail - a lot of the variance that occurs throughout time. Any good idea there you can steal? :-) Eric

Hi, Tony. We use meetings and calls as a task within a project.

We created a project called "Administrative Tasks" and then created individual tasks for the various things that occupy time but are not attributable to a specific project. We have tasks for "Internal Meeting", "Company Activities" (to cover things like birthday celebrations, community service days, etc), and others. This project appears on the time sheet and associates simply enter time to each task as appropriate. The down side of this is each task occupies a lot of space in the scheduling screen. I am considering changing the availability of each team member to reduce their number of available hours by their estimated time spend on "Admin" tasks so the time simply fails to show as available for assignment Craig

We've gone a few directions on this. While we are sill currently using general hours, we are looking to pare that back for the primary reason that these show up in many reports as "NO VALUE". Additionally, it is time that is not forecast / planned. We're moving to the idea of "operational projects" or "cost of doing business" model (Love that terminology, Adina). I've also seen these as "corporate citizenship". In any case, we have each area define what the high-level pieces are (we have 2000 users) and assign their staff and allocate a certain amount of time. This allows us to look at the pie-chart breakdown of work as it is recorded, as well as have a better view of availability.

Has anyone done or had success with this approach: Group timesheet is based on an 8 hour day, 5 days a week. BUT...on Project Preferences, the hours per work day is set at 6. This globally makes each user available for 6 hours a day for resource planning. The problem I'm having is with managers who want to know what portion of non-project time is being spent on say meetings, self-improvement/research, training classes, etc. Those managers are setting up the "bucket" projects as sited here. So in effect, those users are showing as unavailable up to ~ 4 hours per day. Makes it hard to find resources when this is happening! Any help advice with the work day idea?

Srini, you sited "set the role level capacity lower". Where/how are you setting capacity at the role level? I'm unfamiliar with this. Thanks!