Resource Planning for Internal Projects: Realistic and Smart Planning

Your project team is working at the limit, deadlines are being pushed back, overtime is piling up. According to the dashboard, utilization is at 95 percent. All good? Not quite. What the system does not show: the 8.7 hours per week your employees spend on unnecessary meetings, rounds of coordination and internal tasks. Internal projects fly under the radar while capacity planning only sees client projects. The result: artificially high utilization, distorted forecasts and decisions based on the wrong data. Resource planning for internal projects closes this gap.

Companies that integrate internal projects into their resource planning gain transparency about their actual capacity. They avoid overbooking, make better prioritization decisions and improve the planning quality of their projects for the long term. This article shows you in practical terms how to record internal effort systematically, include it in your capacity planning and arrive at realistic resource transparency.

Why internal work distorts your capacity planning

The invisible time sink in project business

Meetings, coordination, recruiting, training, internal initiatives: at IT companies, consultancies and agencies, there are many activities that do not flow directly into client projects. This invisible work inside the company can reach considerable proportions. Studies show that employees in Germany spend an average of seven hours per week in unproductive meetings, managers as many as twelve hours.

The problem: if this internal effort is not reflected in resource planning, a dangerous gap opens up between planned and actual availability. A developer who is 100 percent assigned to client projects on paper may in reality spend 20 percent of their time on administrative work, team meetings and special assignments.

What happens when internal projects are not reflected

Without systematic recording of internal effort, several problems arise at once. Utilization looks artificially high, even though employees feel permanently overloaded. Forecasts regularly fall apart because the calculated capacity is never actually available. Priority decisions are not made on the basis of data but on political factors or gut feeling.

In practice, this shows up as recurring patterns: frequent ad hoc switches between tasks, chronic lack of time despite a constant project load, recurring overtime without visible peaks in client projects. These early warning signs indicate that internal work needs to be made visible.

Typical internal time sinks in project-based companies

The range of internal activities is wide. Regular coordination such as jour fixes, team weeklies or department meetings ties up time structurally. Special tasks such as preparing proposals, pitches or proofs of concept often come on top. Internal initiatives for process optimization, tool rollouts or quality assurance need dedicated capacity.

Then there are enablement activities such as onboarding new colleagues, knowledge transfer or mentoring. Recruiting processes with job interviews and assessments tie up senior resources in particular. Events such as team workshops, training sessions or company events block entire days. All these activities are legitimate and necessary, but they have to be taken into account in capacity planning.

Defining terms clearly: the foundation of resource planning

Understanding capacity, availability and utilization correctly

In discussions about resource planning for internal projects, terms are often used loosely. Capacity refers to the theoretically available working time of a resource, typically expressed in FTE (full-time equivalent). A full-time employee with a 40-hour week has a capacity of 1.0 FTE.

Availability is the working time that can actually be used after deducting vacation, illness, public holidays and other absences. It reduces theoretical capacity to a more realistic value. Utilization measures how much of the available capacity is actually tied up by projects and tasks. It is expressed as a percentage and should ideally be between 70 and 85 percent to leave room for the unexpected.

What counts towards the utilization calculation?

Calculating utilization is not only about billable client projects. Realistic capacity planning must take into account all work activities that tie up resources. This includes client projects (billable), internal projects with defined deliverables, recurring administrative tasks, meetings and coordination, and time for training and development.

According to various surveys companies should plan with a realistic capacity of around 80 percent per employee, as around 20 percent of working time disappears into recurring administrative tasks. This rule of thumb is a starting point but should be validated for your own company.

Forecast: what it is good for and why data quality is decisive

The resource forecast is a planning instrument for predicting future capacity requirements and availability. It helps identify bottlenecks early and make capacity decisions: Do we need new employees? Can we take on more projects? Where do we need to prioritize?

The quality of the forecast stands and falls with the quality of the data. If internal effort is not recorded, available capacity is systematically overestimated. The forecast suggests free resources that do not exist in reality. This leads to wrong decisions with expensive consequences: projects accepted that cannot be delivered, or hiring processes of the wrong size.

Recording internal projects: categorization as the first step

Internal projects versus internal activities

Not all internal work is the same. Internal projects have a defined goal, a deliverable and typically a limited duration. Examples include introducing a new CRM system, developing an internal tool or reorganizing processes. These projects should be treated like client projects and planned in full.

Internal activities, on the other hand, are ongoing, recurring activities without a specific end date. They include weekly team meetings, vacation cover, ad hoc support for other teams or maintaining the knowledge base. These activities can often be represented better by capacity blocks than by individual tasks.

Recurring work versus one-off peaks

The timing characteristics of internal work influence the planning strategy. Recurring work such as jour fixes, monthly reports or regular customer service slots is predictable and can be scheduled as fixed capacity blocks. A weekly two-hour team meeting structurally corresponds to about five percent of working capacity.

One-off peaks such as company events, trade fair participation or year-end closing activities require a temporary capacity reservation. These should be explicitly visible in the project calendar as internal projects with a defined period, to avoid overbooking during these phases.

Making work under the radar visible

Spontaneous, unstructured activities are particularly challenging: the developer who quickly helps a colleague from another team; the project lead who steps into the pitch team at short notice; the consultant who has ad hoc coordination with other projects. These context switches and spontaneous discussions add up.

A pragmatic approach is to plan a buffer for unforeseen internal tasks. Many companies reserve five to ten percent of total capacity as "flex time" or "special tasks" for this, without tracking every single activity. This creates realism without administrative overhead.

Three models for resource planning for internal projects

Model 1: Fixed capacity blocks

The simplest model works with flat capacity deductions. Each role is assigned a fixed percentage for internal work. A developer, for example, has 15 percent reserved for internal tasks, a team lead 25 percent, a head of department 40 percent. These blocks reduce the capacity that can be planned for client projects accordingly.

The advantage lies in its simplicity and low maintenance effort. The model is suitable for smaller teams or as an entry point into systematically accounting for internal work. The disadvantage: it does not reflect fluctuations and does not differentiate between actual activities. In phases with many internal projects, utilization still ends up too high.

Model 2: Task- and activity-based planning

The most detailed model treats internal projects like client projects. Each internal initiative is set up as a separate project with tasks, time estimates and resource assignments. An internal development project appears in the resource plan exactly like a client order. Meetings are managed as recurring tasks with assigned participants.

This approach offers maximum transparency and enables precise capacity decisions. The effort, however, is considerable: someone has to set up, maintain and track internal projects. The model is suitable for larger organizations with a professional PMO and established project management maturity. The risk is bureaucracy and a perception of micromanagement.

Model 3: Hybrid solution for pragmatic planning

Most successful implementations use a hybrid approach. Recurring, predictable internal work is represented by capacity blocks: 15 percent for meetings and administration, five percent for ad hoc coordination. Larger internal projects with a genuine project character are planned explicitly: the CRM rollout as a separate project, the process optimization initiative with a dedicated team.

This approach combines simplicity for routine tasks with transparency for strategic internal initiatives. It avoids both the inaccuracy of pure flat rates and the overhead of full task planning. The balance can be adjusted individually depending on project complexity and the company's planning maturity.

Decision guide: when each model makes sense

Choosing the right model depends on several factors. For small teams of under 20 people, fixed capacity blocks are often enough. The overview is good, and adjustments can be communicated informally. Mid-sized organizations with 20 to 100 project staff benefit from the hybrid model: background workload through blocks, strategic projects explicitly.

Large companies with several hundred employees and complex multi-project environments often need task-based planning for transparency across departments. Maturity is also decisive: organizations without established time tracking should start with model 1 and evaluate after six to twelve months whether more granularity is needed.

Planning stability also plays a role. In dynamic environments with frequent changes, detailed plans are hard to maintain. Here, a simpler solution can be the better choice despite lower precision, because it is actually used.

Practical rules: internal planning without overhead

Which internal activities must be included in the plan?

Not every five-minute coffee break has to be recorded. What matters is defining clear categories. Larger internal projects with a total effort of around 40 working hours or more should be planned as mandatory. Regular meetings of 30 minutes or more with more than three participants belong in the plan. Training sessions, workshops and events that take up a full day or several days must always be visible.

Training should be accounted for with at least five percent of annual working time. Vacation cover and longer-term special assignments lasting a week or more need explicit planning. Everything below these thresholds can disappear into the general capacity buffer. These rules create clarity and avoid case-by-case discussions.

Minimum granularity: where detail pays off

The question of the right granularity divides teams. As a rule of thumb, internal activities should be planned with the same granularity as client projects, but not finer. If client projects are estimated on a daily basis, that is enough for internal projects too. Planning a two-hour meeting in half-hour steps is excessive.

It makes sense to distinguish between strategic and operational internal tasks. Strategic initiatives that affect several teams or departments deserve detailed planning. Operational routine tasks can be recorded more roughly. An internal development project for process automation justifies task-level planning; weekly team meetings do not.

Clarifying responsibilities: who plans, approves and maintains?

Without clear ownership, any planning logic peters out. Planning internal projects requires defined responsibilities. The project lead or initiative owner plans internal projects in the same way as client projects: scope, tasks, resource requirements. Team leads or heads of department plan recurring team activities such as weeklies or department meetings.

Approval of larger internal projects should lie with the PMO or portfolio management, to allow prioritization across all initiatives. Smaller activities that are purely internal to a team can be approved by the team lead. Plans are maintained decentrally by the respective owners, with central monitoring by the PMO.

Timeboxing versus tracking everything

A common mistake is trying to track every single action. This leads to acceptance problems and administrative overhead. Pragmatic timeboxing works better: fixed time budgets are planned for defined activities, and actual usage is not recorded to the minute. A team weekly is blocked with two hours per week; whether the meeting sometimes takes 90 minutes or 2.5 hours is secondary.

This model creates planning certainty without control fantasies. It communicates: we recognize that this work takes time, but we trust you to use it efficiently. The balance between accuracy and acceptance decides whether the implementation succeeds or fails.

How ZEP brings together resource planning for internal and external projects

Central transparency instead of Excel chaos

Integrating internal projects into Resource Planning requires a system that connects both worlds: client projects and internal effort on one data foundation. As Professional Services Automation, ZEP provides exactly this central platform, on which working time tracking, Project Planning and resource management come together.

What sets it apart: internal projects are treated in ZEP exactly like client projects. You can create work packages for the CRM rollout in the same way as for a client order. Bookings in ZEP do not distinguish between external and internal, but cover all productive activities. This creates the data foundation for realistic utilization analyses.

Dynamic utilization planning with a real-time overview

Resource Planning in ZEP, available as an add-on and included in ZEP Business, shows at a glance where your capacity is tied up. The utilization row for each person makes overloads visible immediately: overplanning above 100 percent is marked red. This visual transparency enables proactive countermeasures before employees become structurally overloaded.

Particularly valuable: regular working hours, public holidays and approved absences flow into capacity automatically. The planned-vs-actual comparison shows the plan and the booked hours side by side, including for internal projects. This makes the typical discrepancy between plan and reality visible.

Mapping internal work precisely

ZEP offers flexible options for the different models of internal planning. Recurring internal activities can be scheduled as an internal project with a value per day or as a total for the period: this spreads the weekly team meeting evenly over the period. Larger internal projects are created as projects in their own right and scheduled at project level.

Resource Planning allows both percentage-based scheduling for capacity blocks and hour values for individual projects. This supports the hybrid approach: background workload through percentage reservation, strategic initiatives through detailed project planning.

Forecasting with a realistic data foundation

The planned capacity utilization and planned revenue in Resource Planning are based on the complete planning basis, including internal projects. When internal effort is scheduled and booked systematically, the plan no longer shows fantasy figures but the capacity actually available for new client projects.

The booked hours provide the data basis for insights at employee and project level: What percentage of working time goes structurally into internal versus external work? Which teams have unusually high internal shares? This transparency enables data-based optimization decisions.

Integration creates added value

The decisive advantage lies in end-to-end integration. Employees book their hours once, whether for client projects, internal initiatives or meetings. The system uses this data for project controlling, Invoicing and Resource Planning. There are no parallel Excel lists for internal projects and no manual consolidation of different data sources.

The GDPR-compliant solution, developed and hosted in Germany, also offers integrations with DATEV and other systems common in the DACH region. This makes ZEP the central platform for professional services companies that need resource transparency across all project types.

Table: types of internal effort and their planning logic

This table serves as a decision matrix for categorizing and planning internal effort. It can be adapted and extended for your company.

Reporting and management: KPIs for better decisions

Planned versus actual internal effort

Monitoring the deviation between planned and actual internal effort is central to continuous improvement. If systematically more internal hours are recorded than planned, either the planning is too optimistic or there are unplanned activities that should become structural. If actual usage is well below plan, capacity blocks can possibly be reduced.

A monthly review of these deviations helps improve planning quality. The target should be a deviation of under ten percent. Larger differences indicate planning problems or a lack of discipline in recording hours. Both points have to be addressed to get reliable capacity data.

Breaking down utilization by type of work

Instead of only looking at overall utilization, a breakdown into external (client projects) and internal is valuable. A team with 90 percent overall utilization, of which 60 percent is external and 30 percent internal effort, has a different profile from a team with 85 percent external and five percent internal.

The first team is effectively working at its capacity limit, while the second team would have room for more client projects. This transparency enables better resource allocation and portfolio decisions. It also shows which teams structurally have too much internal work and may need to be relieved.

Forecast accuracy as a management metric

The accuracy of the capacity forecast can be measured objectively. Compare the capacity forecast three months ago with the capacity actually available. Without taking internal projects into account, deviations of 20 to 30 percent are not unusual. After implementing systematic internal planning, the deviation should fall below ten percent.

This metric is particularly relevant for management reporting. It proves the value of the measure in quantifiable terms and builds trust in the planning data. The PMO can argue on a sounder basis why certain projects should not be accepted or why additional resources are needed.

Recognizing conflict indicators

Certain metrics point to structural problems. Frequent overbooking of individual people shows that their capacity is systematically overestimated or that they are assigned to too many projects at once. High multitasking with more than three parallel projects per person reduces efficiency through context switching. Bottleneck roles that are constantly over 90 percent utilized block the project flow.

A good reporting dashboard makes these conflict indicators visible at a glance. The PMO can take proactive countermeasures: postpone projects, adjust priorities, bring in additional resources or build skills internally.

{{blog-cta}}

Implementation checklist for realistic capacity planning

This roadmap leads to a working system in two weeks:

Week 1: analysis and concept

Days 1 to 2: define categories. Create a list of all relevant types of internal effort in your company. Use the examples in this article as a starting point and add categories specific to your company. Decide which activities must be planned as mandatory.

Days 3 to 4: define roles and typical capacities. For each role in the company (developer, consultant, project lead, etc.), determine typical shares of internal work. To do this, interview team leads and analyse existing time tracking data, if available.

Day 5: choose a planning model. Based on team size, complexity and maturity, decide on one of the three models presented. Document the decision and the reasoning for later evaluation.

Week 2: pilot and rollout

Days 6 to 7: select a pilot team and communicate the rules. Choose a team of 5 to 15 people as a pilot. Train team leads and project leads in the new planning rules. Set up the technical requirements in the resource planning system.

Days 8 to 9: enter internal projects and capacity blocks. The pilot team enters all relevant internal activities: ongoing internal projects, recurring meetings, blocked time for administration. Check plausibility together.

Day 10: define the reporting standard and carry out the first review. Decide which KPIs will be reported weekly/monthly. Carry out the first review with the pilot team: How realistic does utilization look now? Which adjustments are needed?

Days 11 to 12: document learnings and scale. Collect feedback from the pilot team. Adjust rules and processes based on practical experience. Communicate the extension to further teams.

Days 13 to 14: establish governance. Define a review rhythm (weekly/every two weeks) for utilization overviews. Set escalation paths for overbooking. Establish a regular meeting for quality assurance of the planning data.

After this pilot phase, you should start scaling to the entire organization, team by team over three to six months.

Overcoming common objections: how to win over your team

"This is micromanagement and control"

This objection often comes up when time tracking or detailed project planning is introduced. The answer lies in the purpose: it is not about monitoring employees but about making their work visible. Internal projects are real work that creates value. If it stays invisible, only the utilization figure is embellished; productivity does not increase.

Communicate clearly: the goal is protection against overload, not control. Only if management and the PMO know the actual utilization can they plan realistically and push back on excessive expectations. The alternative is that employees silently work overtime or projects fail.

"Too much admin effort"

If planning internal projects takes more time than the projects themselves, something is wrong. The key lies in the right granularity. Recurring activities are set up once and then run automatically. Larger internal projects justify the planning effort through better manageability.

A pragmatic approach reduces the overhead considerably. Use templates for typical internal projects. Work with capacity blocks instead of individual tasks where it makes sense. Delegate planning to the respective owners instead of managing everything centrally. With the right setup, the additional effort is less than 30 minutes per week.

"We can't plan internally anyway"

This objection suggests that internal work is too spontaneous and unpredictable to plan. That is only partly true. A large share of internal activities is structural and recurring: weekly meetings, annual planning rounds, quarterly retrospectives. These can certainly be planned.

Even for spontaneous activities, a flex buffer helps. Instead of claiming "we can't plan", explicitly plan time for the unplannable. This is more honest and more realistic than pretending that all employees have 100 percent availability for client projects.

"Reality keeps changing"

True, and that is exactly why you need transparency. If priorities shift every week, you need to know all the more urgently where your capacity is tied up. A well-maintained resource plan lets you see quickly which internal projects can be paused when an important client order comes in.

The focus is not on perfect prediction but on transparency and adaptability. A "wrong" plan that is updated promptly is more valuable than no plan at all. It enables informed decisions instead of gut feeling and makes the consequences of changes in priority visible.

Conclusion: internal work is real work

Companies that ignore internal projects in their resource planning work with fantasy figures. Their utilization looks good on the dashboard while teams are overloaded in reality. Their forecasts promise capacity that will never be available. Their capacity decisions are based on incomplete data.

Integrating internal projects into capacity planning creates realism. It makes visible what employees actually spend their time on. It enables data-based prioritization between client projects and internal initiatives. It protects teams from structural overbooking caused by artificially high utilization targets.

Getting there does not require a revolution. With clear categories, pragmatic planning rules and the right model for your company size, you can create a reliable foundation within a few weeks. The result: better forecasts, avoidable overbooking and capacity decisions you can trust.

Internal work is not waste that has to be eliminated. It is an investment in processes, people and future viability. But it has to be visible, planned and included in decisions. Only then does resource planning become truly realistic.