Pike
  • Pricing
  • Contact us
Log in
  1. Home/
  2. Glossary/
  3. Unplanned work

Glossary

Unplanned work

Unplanned work is any task that arrives after the plan is set and must start before the next planning cycle, such as an urgent client request or production incident.

What counts as unplanned work

At an agency or consultancy, the common sources are urgent client requests, incidents on work that has already been delivered, rework after late feedback, and cover for a colleague who is unexpectedly absent.

The amount is predictable even though the content is unknown. A team can know from its time entries that it loses about six hours per person each week to interruptions without knowing which client those hours will go to.

Unplanned work vs a forecasting miss

A forecasting miss is planned work that was estimated wrongly. If a project needed 60 hours and the plan said 40, the extra 20 hours were knowable in advance and a better estimate would have caught them.

Unplanned work could not have been named in advance. Improving project estimates does not reduce it. The fix is to hold back capacity that is assigned to no project.

How unplanned work affects allocation and utilization

When every available hour is allocated, an interruption displaces planned work, goes into overtime, or gets rushed. Each outcome shows up later as a late delivery, a tired team, or rework.

Planned utilization drops when a team reserves hours for unplanned work. Actual utilization usually stays about the same, because the interruptions were already consuming those hours.

How to size a capacity buffer

Log interruptions against a dedicated task or tag for four to six weeks, total the hours per role, and divide by the available hours for that role. Reserve that share of each week as unallocated time.

Size the buffer per role. Teams that support live client work usually need a larger share than teams working on scheduled projects.

Buffer % = (Unplanned Hours / Available Hours) × 100

Example: a team with 160 available hours that logs 24 hours of unplanned work in a week needs a 15% buffer.

Example

A four-person development team has 160 available hours per week. Over four weeks the team logs 20, 28, 22, and 26 hours against an unplanned work task, an average of 24 hours or 15% of available time. The business caps planned allocations for that team at 136 hours per week and leaves 24 hours open. When a client reports a broken checkout page that takes six hours to fix, the time comes out of the open hours and no planned project moves.

Related terms

  • Resource allocation
  • Resource forecasting
  • Utilization rate
  • Available capacity
  • Bench time

FAQ

Your business runs better on Pike.

Contact sales
  • ISO 27001 CertifiedISO 27001
  • GDPR CompliantGDPR
  • AICPA SOC 2 Type IISOC 2 Type II

Built to keep sensitive client data secure and private.

Pike box logoPike
Features
ProjectsResourcing & capacityFinance & invoicingDashboardsCustomers & salesTime & absencePike MCPIntegrations
Company
BlogOur storySwitch playbookMigration guideGet in touch
Industries
Creative agenciesMarketing agenciesDigital agenciesConsulting firmsIT consultanciesArchitecture firms
Resources
DocsChangelogPrivacy policyTerms and conditionsGlossaryFree toolsFAQ
All systems operational

Engineered around the 🌎

© 2026 Pike. All rights reserved.