IR capacity benchmarks: the real cost of ad hoc data requests

What 50+ interviews with IR teams reveal about how much time ad hoc requests actually consume, by team size

CRT
Clema Research Team
July 7, 2026
Updated October 2, 2026
7 mins read
Share:
Table of Contents

Introduction

IR leaders asking for budget to invest in conversational AI need a defensible number for what the status quo costs. Our data request workflows whitepaper, based on 50+ interviews with IR and IE professionals across 19 US states, quantified the ad-hoc request burden by team size. This post is the benchmark table pulled out of the research so you can use it in a cabinet memo or a budget case. For why the gap keeps widening (national AIR staffing data, and where the extra demand comes from), read why IR office staffing has not kept up with data demand.

The headline benchmarks

MetricBenchmarkSource
Capacity consumed by ad hoc requests40 to 60% of team capacity50+ IR/IE interviews
Institutions reporting request management challenges91.2%50+ interviews, 19 states
Teams citing vague or unclear requests73.5%50+ interviews
Teams needing extensive follow-up or clarification52.9%50+ interviews
Clarification cycles per ad hoc request2 to 5 cycles50+ interviews
IR teams operating with 1 to 3 staff50%50+ interviews
Hours reclaimable annually with AI-enabled workflows220 to 3,200 hours50+ interviews

Benchmarks by team size

Team sizeAvg utilizationPeak utilizationGross ad hoc hours/yrPrimary challenge
Small (1 to 3 staff)47.6%90%~550 (69 days)Resource scarcity; doing everything with minimal capacity
Medium (4 to 7 staff)40%75%~1,584 (198 days)Process transition; formalizing workflows as team grows
Large (8+ staff)62.9%85%~5,333 (667 days)Scale and complexity; managing breadth across the institution

Hours reclaimable

Gross hours consumed by ad hoc requests run 550 to 5,333 per year depending on team size (roughly 69, 198, and 667 workdays for small, medium, and large teams respectively), per the same 50+ interview research. That is the full cost of the status quo; the 220 to 3,200 hours annually reclaimable range is the portion of that gross figure an AI-enabled workflow can realistically recover. The low end reflects small teams (1 to 3 staff) with lower absolute request volume but the highest proportional capacity drag; the high end reflects large teams (8+ staff) where the absolute hours consumed by repeat questions compound across more analysts. Medium teams (4 to 7 staff) land in between, at 634 to 950 hours a year.

To put that in budget terms: 1,000 reclaimed hours is roughly half an FTE. At a fully loaded IR analyst cost of $80,000 to $120,000 per year (an illustrative range; use your own), that is $40,000 to $60,000 of capacity redirected from repeat question answering to strategic analysis. Clema is free to start, with published plans from $99 per month (the Pro plan, $1,188 per year). The math is the budget case.

The hours come back from intake and repeat work, not from analysis. Clema's data request management takes requests as a conversation, asks the clarifying questions before an analyst sees them, and answers repeat questions from your data with sources attached. If you want the process side first, the data request best practices post covers intake rules and when to automate a repeat request.

How to use these benchmarks

  • Cabinet memo: cite the 40 to 60% capacity figure and your team size to put a number on the ad-hoc request burden. Pair with the 220 to 3,200 reclaimable hours range to size the investment case.
  • Budget case: hours reclaimable times your analyst fully loaded cost gives the dollar value of the status quo; set that against the published price (free to start, $99 per month for the Pro plan, or $1,188 per year) for the ROI calculation.
  • Accreditation: the 2 to 5 clarification cycles per request benchmark is a process-quality signal. Track your own cycle count before and after an intake change, and cite the measured drop in a self-study.
  • Team-size peer comparison: if you run a small IR office (1 to 3 staff), the 90% peak season impact benchmark is the figure that explains why your team feels underwater during IPEDS or accreditation cycles.

See the benchmarks on your team

Book a demo and we will map these benchmarks to your institution size and request volume. Published pricing, free to start, from $99 per month, no implementation fee.

Book a Demo

Frequently asked questions

How much IR capacity do ad hoc data requests consume?

40 to 60% of team capacity on average, based on 50+ interviews with IR and IE professionals across 19 US states. The burden is highest proportional to capacity at small teams of 1 to 3 staff, where peak season impact reaches 90%.

How many hours can an IR team reclaim with AI-enabled workflows?

220 to 3,200 hours annually, out of a gross 550 to 5,333 hours per year that ad hoc requests consume across team sizes. Small teams (1 to 3 staff) reclaim 220 to 330 hours, medium teams (4 to 7) 634 to 950, and large teams (8+) 2,133 to 3,200. As a rule of thumb, 1,000 reclaimed hours is roughly half an FTE.

Where do these IR capacity benchmarks come from?

The benchmarks are drawn from the Clema data request workflows whitepaper, based on 50+ interviews with IR and IE professionals across 19 US states. The full research is available as a free download at clema.ai/data-request-workflows.

Ready to get started?

Reclaim Your Team's Capacity

See how Clema can help your IR team handle routine requests automatically