Only classroom hours are counted
A two-hour session for 40 people is 80 learner hours before anyone designs the material, schedules coverage, or answers questions the following week.
IT project training costs
Training is usually the largest hidden business cost on an internal software change. Estimate it before approval by counting who must learn the new work, who must teach it, and what else stops while they do.
For department managers, operations leads, and IT partners who approve software work but do not have a dedicated training budget analyst.

A usable training estimate includes
A technical estimate can be honest and still leave leadership with a false total. Internal training is not a course catalog purchase. It is staff time, materials, backfill, and a temporary drop in throughput after go-live. If that work is invisible at approval, it shows up later as overtime, delayed adoption, or a “successful” launch that nobody uses correctly.
A two-hour session for 40 people is 80 learner hours before anyone designs the material, schedules coverage, or answers questions the following week.
The person who writes the job aid, runs the sessions, and sits with the first week of tickets is usually a supervisor or SME already carrying a full load.
When training is planned after sprint planning, the organization has already committed people and dates without knowing whether the change is affordable to absorb.
Do this after the request has a clear problem, affected people, and first-release outcome—and before anyone treats a developer sprint plan as a commitment. You do not need a precise dollar to make a better decision. You need a range with named assumptions.
Record the training range on the same request that entered software project intake, so adoption cost is visible before anyone treats a sprint date as a commitment.
Name who must learn the new work in requirements gathering software while the first-release outcome is still being reviewed—not after tickets exist.
List roles, not a headcount guess. Separate people who will use the system daily from people who only approve, audit, or support it.
A new client intake path may touch front-line staff, supervisors, a records team, and a small group of reviewers. Each role has a different learning load. If you cannot name the roles, the project is not ready to estimate training.
Creating the training is a different cost from sitting through it. Count both, or the estimate will look cheap and then slip.
Design includes outlining the change, writing or revising procedures, building examples, and rehearsing. Delivery includes live sessions, office hours, and one-to-one walkthroughs. Learner time is every hour a person is in training instead of doing their job.
Use a simple loaded rate the finance partner already accepts. A range is better than a false exact number.
Internal training cost is mostly time. Multiply design hours, trainer hours, and learner hours by a loaded hourly rate for that role. Add vendor invoices, materials, travel, and temporary coverage. State the rate and the date you used it.
The expensive part is often not the session. It is coverage during training and slower work while people are still learning.
Ask what work will wait, who will cover phones or queues, and how long supervisors expect questions. A conservative first-month support allowance prevents the “we trained them, why is output down?” surprise.
An estimate without exclusions will be reused later as if it covered everything.
Write down the audience, session length, whether historical data cleanup is included, whether contractors are already budgeted, and whether refresher training is out of scope. That list is as important as the number.
Practical template
Use this as a worksheet. If a row does not apply, write “none” and why. Blank rows are how costs disappear.
| Category | What to count | Example |
|---|---|---|
| Training design | Hours to outline, write, review, and revise procedures, job aids, and examples. | One trainer and one supervisor spend 16 hours preparing a new intake walkthrough. |
| Training delivery | Hours trainers spend in sessions, office hours, and floor support. | Four 90-minute sessions plus two office hours: 8 trainer hours. |
| Learner time | Every hour staff spend learning instead of producing regular work. | 36 staff × 1.5 hours = 54 learner hours. |
| Backfill or overtime | Coverage so the queue, phones, or service window does not stall. | Two people cover the desk during sessions: 6 hours of overtime. |
| Materials and vendors | Outside help, LMS updates, printing, or a vendor revising existing courses. | Vendor revises an existing module for $2,000; procurement still confirming. |
| Launch support | The first weeks of questions, corrections, and shadowing after go-live. | Supervisor budget: 4 hours/week for four weeks after launch. |
Worked example
A department wants a new client intake path. Development has a technical estimate. Leadership still needs the internal training cost before saying yes. The numbers below are illustrative, not a benchmark.
| Estimate input | Value |
|---|---|
| Audience | 36 front-line staff, 6 supervisors, 1 trainer |
| Design and delivery | 16 design hours + 8 trainer delivery hours |
| Learner time | 36 staff × 1.5 hours + 6 supervisors × 2 hours = 66 hours |
| Coverage | 6 overtime hours so the public window stays open |
| Loaded rate used | $55/hour staff, $75/hour supervisor and trainer |
| Illustrative total | About $6,900 in internal time, plus $2,000 vendor materials still unconfirmed |
The technical build can still be the larger cash number. The training estimate is what tells leadership whether the organization can absorb the change in the same quarter—or whether the launch window is the real constraint.
| What the build estimate counted | What the training estimate must add |
|---|---|
| Developer and vendor hours to ship the change | Design hours, trainer hours, and every learner hour |
| A license, classroom invoice, or “training TBD” | Backfill, overtime, and first-month support after go-live |
| A go-live date the technical team can hit | Who cannot do their job while they learn, and for how long |
| A single cash number with no audience named | Assumptions, loaded rates, and exclusions written next to the range |
“We will train 40 people” is not an estimate. Forty people for 90 minutes is 60 hours, plus design, plus coverage.
Supervisors attend, then re-train their teams, then handle exceptions. Omitting them understates both cost and calendar time.
A license or a recorded video is a delivery method. The cost is still the time people spend creating and consuming it.
Once dates are public, training becomes a scramble. Estimate it with the rest of the business effort, before the organization commits.
In Precision Foundry
Precision Foundry asks for a Business Effort estimate beside the technical estimate. Training is a named area—who needs it, who will create it, and how long it will take—so leaders see adoption cost before they approve the build.
Common questions
Identify the roles that must change how they work. Estimate design hours, trainer hours, and learner hours separately. Convert those hours with a loaded rate, then add backfill, vendor or material costs, and first-month support. Write the assumptions and exclusions next to the number.
A loaded rate is the internal cost of an hour of staff time, including wages and the overhead finance already uses for planning. Ask finance for the rate they want used on project estimates so every proposal uses the same basis.
Internal training, procedure changes, communication, and launch support belong in the business estimate. The technical team estimates build, configuration, data movement, and technical testing. Leaders need both before they approve the work.
When the audience, session approach, calendar window, and major unknowns are named. A range with assumptions is more useful than a precise figure that hides who still has to confirm coverage or vendor cost.
Precision Foundry keeps this guide attached to the request so the template does not live in a forgotten doc.
Join the private alpha waitlistOptional cookies
We use optional technologies only with your choice. Strictly necessary cookies for sign-in and security always run. Cookie Policy