A senior designer takes two weeks off in August. A developer calls in sick for four days. A project manager starts parental leave for three months. A strategist has a standing medical appointment every Tuesday afternoon. In isolation, each of these is manageable. At an agency running 8–12 concurrent client projects, the cumulative capacity impact of untracked absences is one of the most common causes of missed deadlines and over-committed teams.
Absence management for agencies isn't an HR function. It's a delivery function.
Why Absence Management Is a Delivery Problem, Not an HR Process
Most agencies treat leave management as an HR process: the employee requests time off, the manager approves it, it goes in a shared calendar, and everyone moves on. What this process doesn't do is connect the absence to the project schedule, the resource plan, or the capacity forecast.
The failure mode looks like this: a project manager builds a delivery plan assuming a developer is available for three weeks. Two days before the project starts, the developer's approved annual leave — which has been in the system for weeks — collides with the project timeline. Nobody connected the leave record to the project schedule.
At a 10-person agency, two weeks of unplanned capacity reduction during a major delivery can mean the difference between hitting and missing a client deadline. The absence itself isn't the problem — the invisibility is.
Leave creates real capacity gaps that affect real projects. A team member on annual leave isn't partially available — they're at zero. Resource planning that doesn't subtract leave from availability produces forecasts that are wrong by design. Monton automatically reflects approved leave as unavailable capacity in the staffing timeline, so the gap is visible when you're building the delivery plan, not after you've committed to the client.
Sick leave is unpredictable but manageable in aggregate. Agencies that track sick leave patterns can identify which delivery periods historically see more illness — winter, post-peak periods, after major launches — and build buffer into those timelines rather than running at 100% of theoretical capacity.
Leave loading is a financial liability, not just a scheduling event. Accrued but unused annual leave is a real cost on your balance sheet. Agencies that allow employees to bank large leave balances are accumulating a financial obligation that concentrates risk when multiple people take leave in the same quarter.
The Full Scope of Agency Absence: Beyond Annual Leave
Annual leave is the most visible type of absence, but it's not the only one that affects capacity. A complete absence management approach covers:
Annual leave: Planned holiday allowance. Predictable and plannable when requests are made in advance. The main planning challenges are ensuring coverage during peak leave periods (typically summer and the Christmas–New Year window), managing requests when multiple people want the same dates, and ensuring no team member accumulates a balance large enough to create a financial liability or a single-period capacity shock.
Sick leave: Unplanned and unpredictable by definition. The operational response is coverage: who takes on the person's active work, what can be deprioritised without client impact, and what needs to be communicated externally. Agencies that track sick leave frequency can also identify whether specific roles or individuals have patterns that warrant a welfare conversation.
Public holidays: Variable by country, region, and individual contract. An agency with team members in multiple countries — common for remote-first agencies — needs to track public holidays per person, not just the national calendar of the agency's home country. Getting this wrong means assigning work to someone who was never going to be available.
Part-time and flexible arrangements: A designer working 4 days per week isn't available for scheduling on their day off. A team member on reduced hours post-parental leave has a different capacity than their contract hours suggest. Resource planning tools that don't account for these arrangements systematically overcommit people in ways that appear reasonable until they don't.
Parental leave and long-term medical leave: Extended absences that require structural coverage decisions — typically a contractor hire, reallocation across the team, or temporary scope reduction with clients. These can be anticipated months in advance when the leave management system flags extended requests for resource planning review at the time of approval.
TOIL (time off in lieu): In agencies that work overtime during peak periods, TOIL accrued during one month often gets taken in the next. Without tracking, this creates invisible capacity reductions that appear in neither the holiday calendar nor the resource plan.
How to Build an Absence Policy That Protects Delivery
The operational goal of an absence policy isn't compliance — it's predictability. The policy should ensure the agency has enough notice to plan around upcoming absences before they affect committed delivery.
Establish minimum notice requirements by absence length. A half-day absence can be communicated the morning of. A week requires at least two weeks' notice. Two or more weeks requires a month or more. The minimum notice period should reflect how long it takes to arrange coverage for that duration — not what feels administratively convenient.
Define coverage expectations for extended leave. Who owns a person's active projects when they're out for more than three days? This shouldn't be decided at the time of the absence. The policy should specify either a named backup or a process for assigning one before the leave starts.
Set leave restrictions around critical delivery windows. Some agencies implement blackout periods — windows when leave requests are restricted because of major deliveries or peak client periods. This is legitimate when applied consistently and communicated clearly during hiring. The alternative is discovering that two key people have approved leave during your biggest client launch of the year.
Connect leave approvals to the resource plan as a required step. A leave approval shouldn't happen without checking the project schedule. Most agencies run these as separate processes — the manager approves the leave, the project schedule exists somewhere else, and nobody checks whether they conflict until it's too late. The policy should require a capacity check before approval is granted.
Track leave balances actively. Don't wait for an employee to request leave to discover they have 25 days accrued. Monthly balance reviews let managers proactively encourage leave during lower-demand periods, reducing the concentration of leave in peak delivery windows.
Common Absence Management Mistakes in Agencies
Treating leave as the employee's problem. The agency's job is to plan around absence. When managers respond to leave requests with frustration rather than planning, they create a culture where people feel guilty about taking leave — which leads to burnout, reduced work quality, and higher turnover. The policy does the boundary-setting; managers implement the plan.
Not updating the resource plan when leave is approved. Separate approval and planning processes guarantee mismatches. Leave approval should automatically update the person's availability in the resource plan. If your tools don't connect these automatically, the process must include this as a manual step with a clear owner.
Ignoring public holidays for international team members. A project plan that assigns work to a team member on a national holiday they observe is a broken plan. Building the correct holiday calendar per person into resource planning prevents this category of error entirely — but it requires tracking holidays at the individual level, not just the company level.
Letting leave balances accumulate without monitoring. An employee with 30 days of accrued leave represents both a financial liability and a delivery risk. If they take it consecutively, the agency absorbs a significant capacity shock. Active leave management means monitoring balances and encouraging usage before they reach problematic levels — not reacting when the request comes in.
No visibility for the team. If only the manager knows when people are out, the team can't plan their own work around colleagues' absences. A shared absence calendar — visible to everyone — lets team members self-organise around coverage without requiring management coordination at every step.
Leave & Absence Management with Monton
Monton integrates leave management directly with the resource planning and project management tools, so absence data flows automatically into capacity calculations — no manual sync between an HR system and a project tool required.
Leave requests and approvals in-platform: Employees submit requests in Monton; managers approve or reject them with the project schedule visible in the same view. Approved leave automatically updates the person's capacity in the resource planner — the connection is built in, not a separate manual step.
Public holiday calendars by country and region: Monton supports multiple holiday calendars, so a team member in Spain sees their national holidays while a team member in Italy sees theirs. Capacity calculations reflect actual availability per person, not a single shared company calendar that's wrong for half the team.
Absence visibility in the staffing board: The visual capacity timeline shows approved leave and public holidays as unavailable blocks alongside project allocations. A project manager building a delivery plan can see immediately whether the people they're scheduling are actually available in the dates they're planning for — before the plan is shared with the client.
Leave balance tracking: Monitor accrued and used leave per employee from the same dashboard used for project capacity. Balance reports are available for payroll and compliance use without needing a separate HR tool for the basic tracking.
Sick leave logging and absence reporting: Log unplanned absences as they happen. Over time, the data shows absence patterns by person, team, and time period — useful for capacity planning buffers and for identifying whether specific periods or team members need additional support.
For agencies, absence management isn't about enforcing a policy — it's about keeping the delivery machine running when people are unavailable. The tool that handles this well is the one that makes absence visible before it becomes a delivery problem.