Claim Settlement Capacity in an EPFO Regional Office
An EPFO regional office in a Tier-2 city settles claims through 24 dealing assistants. Each assistant is effectively available for 7.5 hours a day over 22 working days a month; the rest of the day goes to meetings and file movement. A time study shows that each claim needs 36 minutes of scrutiny and 12 minutes of data entry, and the two stages cannot be run in parallel. Average monthly inflow over the last quarter was 6,400 claims. Of last month's 6,400 claims, 12.5% were returned to employers for incomplete KYC and never became 'settled'; of the remaining, 70% met the 20-day service standard and 30% did not. The zonal office has now fixed a target of 85% of admissible claims within the standard. The Regional PF Commissioner must pick one lever for the coming year: sanction 8 new posts, outsource data entry, or fund a rework-reduction drive. Finance will fund only one.
1. Using the time-study data, how many dealing assistants are actually required to clear an average month's inflow of 6,400 claims? Is the sanctioned strength of 24 adequate?
Read the worked answer
Step 1 - Convert the process into standard minutes per claim. Scrutiny 36 min + data entry 12 min = 48 minutes per claim. The two stages are sequential, so they add; there is no parallelism to exploit.
Step 2 - Convert one assistant-month into minutes. 7.5 hours × 60 minutes × 22 days = 9,900 productive minutes per assistant per month.
Step 3 - Claims per assistant per month. 9,900 ÷ 48 = 206.25 claims.
Step 4 - Requirement. 6,400 ÷ 206.25 = 31.03 assistants.
Since a fraction of a person cannot be posted, the requirement must be rounded up to 32 assistants.
Conclusion. The sanctioned strength of 24 is short by 8 posts. Note the direction of the rounding: rounding 31.03 down to 31 would leave roughly 6 claims of the month's load undone, and the figure of 32 is itself a floor, because it assumes 100% attendance, zero training days and zero rework. Any month with leave, peak inflow or returned claims will breach it. That is precisely why the 8-post demand looks arithmetically justified - and why it must be compared against the cheaper levers before being accepted.
2. For the 6,400 claims of last month, how large is the gap against the new 85% service-standard target, and what does closing it demand in operational terms?
Read the worked answer
Step 1 - Admissible claims. 6,400 × 0.875 = 5,600 claims (the 800 returned for KYC are excluded from the denominator because they were never settled).
Step 2 - Present performance. Within the standard: 5,600 × 0.70 = 3,920. Beyond the standard: 5,600 × 0.30 = 1,680.
Step 3 - Target performance. 85% of 5,600 = 4,760 claims within 20 days.
Step 4 - Gap. 4,760 − 3,920 = 840 claims must move from the late tail into the 20-day window.
Step 5 - Interpretation. 840 ÷ 1,680 = 0.50, i.e. half of all late claims must be pulled inside the standard. This is not a marginal tightening. An office that is already 30% late cannot reach 85% compliance by exhortation or by a marginal rise in throughput; it needs either a step change in capacity or a structural reduction in the number of claims that enter the pipeline. Also note that the 800 returned claims still consumed staff time and still delayed the member, so they belong in any diagnosis even though they are outside the service-standard denominator.
3. Quantify each of the three levers and recommend one, setting out the assumptions on which your recommendation would fail.
Read the worked answer
Lever A - Outsource data entry. Data entry is 12 of 48 minutes, i.e. 25% of the workload, worth 24 × 0.25 = 6 full-time equivalents. If it is removed, capacity per assistant becomes 9,900 ÷ 36 = 275 claims; the office could clear 24 × 275 = 6,600 claims against 6,400 - a headroom of only 200 claims (about 3%). That headroom evaporates in any peak month and does nothing about the 800 rework claims, which still need re-scrutiny.
Lever B - Sanction 8 posts. 32 × 206.25 = 6,600 claims, the same 200-claim headroom, but at a permanent recurring cost and after a recruitment lead time of several months.
Lever C - Attack rework. The 800 returned claims are 800 × 48 = 38,400 minutes = 3.9 assistant-months of capacity already burnt, plus member delay and repeat handling. Eliminating most of the cause at source (a standard KYC checklist, employer-side validation before upload, rejecting incomplete ECR uploads at the gateway) recovers close to that capacity without a new post.
Recommendation. Fund the rework-reduction drive first, with a three-month measurement of the return rate, and hold the 8 posts in reserve. The reasoning is that Lever C is the only option that both frees capacity and shrinks the load, and it costs a fraction of the alternatives.
Where this recommendation fails: if the return rate is driven by employer behaviour that the office cannot influence within three months; if the 6,400 average conceals a peak of 7,500 in March; or if the leakage is at scrutiny rather than data entry, in which case the 36-minute figure itself is understated and only Lever B creates durable headroom. State the trigger explicitly: if the return rate is not below 5% by the end of the quarter, sanction the posts.