Back to all articlesLead assignment

Weight lead allocation for part-time staff without creating catch-up debt

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A part-time employee should not receive a full-time share of new leads simply because their name appears once in a round-robin list. Nor should someone returning from an absence receive extra leads to repay turns they missed.

Use scheduled available hours to calculate allocation shares for a defined routing period. Recalculate when availability changes, and expire unused entitlement at the end of that period. A returning employee joins at their current share, with no accumulated allocation debt.

The important distinction is between a share of new opportunities and a quota owed to an employee. Weighted lead assignment for part-time staff should establish the first without accidentally creating the second. The worksheet below makes that distinction operational.

1. Define what the weight measures

Use hours scheduled for the lead-handling work covered by the routing pool. Do not automatically use contracted hours if some of those hours are reserved for other duties.

For example, an employee scheduled for a full working day may have only part of that day allocated to handling new leads. Their weight should reflect that planned availability, using the same definition applied to everyone else.

The basic calculation is:

Employee share for a period =
Employee's available lead-handling hours in that period
÷ Total available lead-handling hours in the pool

Hours are a planning input, not a claim that employees work at identical speeds. This design deliberately does not estimate live workload, count open conversations, or predict how difficult an incoming lead will be.

Keep separate pools where employees are eligible for materially different work. Someone who cannot handle a particular lead type should not have their hours included in that pool's denominator. Otherwise, the apparent capacity includes people who cannot receive the work.

Before calculating anything, record three decisions: which leads belong in the pool, which employees are eligible, and what counts as an available hour. Without those definitions, precise percentages can still produce inconsistent assignments.

2. Choose a period short enough to reflect the schedule

A weekly percentage is convenient, but it can hide a schedule that changes substantially by day. An employee who works only on selected days should not gain an allocation entitlement on days when they are absent.

For the fictional worksheet below, the team uses daily allocation periods. It calculates each day's shares from that day's available hours and closes the period at day's end. The weekly view is a summary of those daily decisions, not a separate weekly quota.

This choice has a trade-off. Daily shares reflect changing availability, but weekly totals will also depend on when leads arrive. If more leads arrive on a day when one employee is scheduled, that employee can receive a larger weekly total than a simple weekly-hours percentage suggests.

A weekly period can be reasonable when availability is stable throughout the week. Shorter periods may be needed when availability changes within a day. Select a period that represents the schedule accurately enough for your operation, without pretending this alone resolves real-time presence or shift handoffs.

Most importantly, do not run two conflicting systems: daily shares for routing and weekly targets that later force corrective catch-up.

3. Filled fictional weekly allocation worksheet

Fictional worked example: All names, schedules, lead volumes, and assignment counts below are hypothetical. This is a recommended operating design, not a description of a product control or customer result.

Four employees handle one common pool of new leads. Alex works eight lead-handling hours each weekday. Blake works four hours each weekday. Casey works eight hours on Monday, Wednesday, and Friday. Drew works eight hours on Tuesday and Thursday.

Casey is absent on Wednesday. The absence is known before Wednesday's allocation period opens. For easy arithmetic, the example assumes 30 eligible leads arrive in each daily period.

WEEKLY INPUTS — HYPOTHETICAL

Employee   Planned hours   Absence hours   Available hours
Alex            40               0              40
Blake           20               0              20
Casey           24               8              16
Drew            16               0              16
TOTAL          100               8              92

These weekly hours are a schedule check, not weekly lead quotas.

The actual routing shares come from each day's available hours:

DAILY ALLOCATION WORKSHEET — HYPOTHETICAL

Monday
Available hours: Alex 8 | Blake 4 | Casey 8 | Drew 0
Pool hours: 20
Shares: Alex 40% | Blake 20% | Casey 40% | Drew 0%
30 leads: Alex 12 | Blake 6 | Casey 12 | Drew 0

Tuesday
Available hours: Alex 8 | Blake 4 | Casey 0 | Drew 8
Pool hours: 20
Shares: Alex 40% | Blake 20% | Casey 0% | Drew 40%
30 leads: Alex 12 | Blake 6 | Casey 0 | Drew 12

Wednesday — Casey absent
Available hours: Alex 8 | Blake 4 | Casey 0 | Drew 0
Pool hours: 12
Shares: Alex 66.67% | Blake 33.33% | Casey 0% | Drew 0%
30 leads: Alex 20 | Blake 10 | Casey 0 | Drew 0

Thursday
Available hours: Alex 8 | Blake 4 | Casey 0 | Drew 8
Pool hours: 20
Shares: Alex 40% | Blake 20% | Casey 0% | Drew 40%
30 leads: Alex 12 | Blake 6 | Casey 0 | Drew 12

Friday — Casey returns
Available hours: Alex 8 | Blake 4 | Casey 8 | Drew 0
Pool hours: 20
Shares: Alex 40% | Blake 20% | Casey 40% | Drew 0%
30 leads: Alex 12 | Blake 6 | Casey 12 | Drew 0

WEEKLY ASSIGNMENT SUMMARY
Alex 68 | Blake 34 | Casey 24 | Drew 24
Total: 150 leads
Catch-up carried into next week: 0 for every employee

Without the Wednesday absence, Casey would have had a 40% share that day. That share disappears when Casey's available hours become zero. It does not become a balance owed on Friday.

Notice that Alex's 40 available weekly hours do not translate into exactly 40/92 of the week's assignments. Wednesday has fewer available employees but the same hypothetical lead volume. Daily routing therefore gives Alex and Blake more assignments that day. This is an intentional consequence of using daily availability rather than enforcing weekly totals.

4. Write the no-catch-up rule explicitly

Do not rely on a weight setting alone. A process can calculate sensible shares while a separate counter quietly preserves missed turns.

Use a written operating rule such as:

Allocation shares apply only to new eligible leads during the current allocation period. Absence creates no entitlement to replacement leads. Unused turns, allocation deficits, and fractional remainders expire when the period closes. Returning employees receive their current scheduled share, not additional assignments for missed periods.

In the worksheet, Casey receives 12 hypothetical leads on Friday, not Friday's 12 plus Wednesday's missed 12. The Wednesday absence is recorded as an availability change, not under-allocation.

Also distinguish an unused turn from an actual lead waiting for assignment. Expiring a turn must not delete or conceal a real unassigned lead. If no one is available, place the lead in a visible exception queue with a named person responsible for reviewing it. That queue is outstanding work, not an allocation debt owed to an absent employee.

Existing lead ownership is a separate issue. This rule neither transfers existing leads nor decides who owns a conversation across a shift boundary.

5. Handle whole leads without preserving historical debt

Percentages rarely divide an incoming stream into whole leads perfectly. A small amount of within-period balancing is useful; carrying those balances indefinitely is not.

One recommended design is to track each employee's expected share of assignments within the current period. For each new lead, select the eligible employee furthest below their proportional share after including that lead. Use a documented tie-break rule when deficits are equal.

This is a within-period balancing counter, not a promise to deliver an exact number. Low lead volume can leave employees above or below their mathematical share simply because leads are indivisible.

At period close, retain the counts for reporting but clear the balancing state. Do not erase the audit history; remove its influence on future routing.

If availability changes mid-period, close the current segment, preserve its results, and begin a new segment with revised hours and fresh balancing counters. This prevents the old schedule from generating a debt under the new schedule. Avoid resetting counters repeatedly for trivial edits, which can make tie-breaking disproportionately influential.

For a manual process, the same principle can be implemented with a visible allocation sequence and a fresh sequence for each period. Whatever method is chosen, check that the sequence reflects the intended weights rather than merely repeating every employee's name equally.

6. Treat absences and returns as forward-looking changes

When an absence is known before a period begins, remove the unavailable hours before calculating shares. Wednesday in the worksheet follows this pattern: Casey contributes no hours, so Alex and Blake share the incoming pool.

When an absence becomes known during a period, make the adjustment from a recorded effective time. Do not rewrite earlier assignments to make the day look as though the absence was known all along.

  1. Record the availability change and its effective time.
  2. Stop new assignments to the unavailable employee from that point.
  3. Close the current balancing segment and calculate new shares for the remaining scheduled availability.
  4. Review any actual unassigned leads separately.
  5. On return, restore the employee's current scheduled availability without importing old deficits.

If an employee received leads before an unexpected absence, those leads need an explicit operational decision. Reassigning them, retaining ownership, or arranging cover is outside the weighting calculation. Do not disguise that decision as compensation for missed turns.

Likewise, proportional assignment does not create additional capacity. In the fictional Wednesday example, Alex and Blake receive more leads because fewer people share the pool. If that volume cannot be handled, the team needs a separate coverage or intake decision. Changing percentages alone cannot solve it.

7. Check the failure cases before relying on the scheme

Review a proposed routing process against situations that commonly reintroduce catch-up debt:

  • An unavailable employee retains a positive weight. Compare the routing inputs with the schedule, including planned non-lead duties.
  • A global fairness counter survives every period. Keep historical reporting, but prevent past deficits from increasing future shares.
  • A manager enforces a weekly target after daily routing. Decide which period governs allocation; do not correct legitimate daily differences into a second quota system.
  • An absence is entered late. Check assignments made between the actual absence and the recorded change. Do not silently backdate the routing history.
  • Every employee has zero available hours. Use the exception queue and escalation owner rather than forcing an assignment through invalid weights.
  • Low volume produces uneven totals. Examine the expected share and whole-lead rounding before treating every difference as a defect.

Before enabling any automated version, have an authorised owner confirm how the workspace handles weights, availability changes, counter resets, and exceptions. Verify availability in the current workspace and plan rather than assuming these controls exist.

8. Run one measured week before changing the rule

Start with one pool and publish the completed schedule worksheet before the next routing week. Record each period's available hours, calculated shares, assignment counts, availability changes, and exceptions.

Review proportionality within each unchanged segment, not just across the weekly total. For each employee, calculate:

Expected assignments = Segment lead count × Segment share
Allocation difference = Actual assignments − Expected assignments

Small differences can result from whole-lead rounding. Repeated or large unexplained differences warrant checking eligibility, tie-breaking, manual overrides, or stale counters.

Separately inspect the first assignments after an employee returns. Confirm that their share matches the current schedule and that no assignment was added specifically to repay a missed period. Count leads assigned during recorded unavailability and check that every unassigned lead has a visible owner for review.

The next action is concrete: fill in next week's available hours, choose the expiry boundary, and write the no-catch-up rule beside the worksheet. After the first week, you should be able to explain each allocation difference from the schedule, arrival timing, rounding, or a recorded exception—not from an invisible balance of missed turns.

Lead assignmentCapacity planningPart-time teamsSales operations

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications