Estimating hours for an audit or review file

A task-by-task method for estimating hours on an audit, review or similar file, then checking the estimate against actual time and updating it.

Country-neutral · Updated November 20, 2026

A good estimate is a list of tasks with hours beside each, built from your own records, then checked against what happened. This guide shows that method for audit, review and similar files. It gives no standard hours for any engagement type, because hours depend on the file, the client's records and your own speed.

Country-neutral: the estimating method. For the standards that set which procedures an engagement needs, use the standard-setter that governs the engagement, such as the AICPA for US engagements. Check your own regulator if you work to different standards.

Why estimates miss

Estimates fail in predictable ways:

  • They count the work you can picture and leave out the rest: opening the file, reading prior-year papers, questions to the buyer, waiting for answers, review notes, final tidy-up.
  • They assume complete records on day one.
  • They use the best case from memory. People remember fast files better than slow ones.
  • They do not separate your hours from calendar time. A file may take 8 hours of work across 10 days.

Fixing these needs a structure, not more effort.

Step 1: define what the file is

Write one paragraph that says what you are asked to do and what you are not. State the engagement type as the buyer or the firm describes it, the period, the entity or entities, the set of records you will receive, the output you will produce, and who reviews it. If you cannot write that paragraph, you cannot estimate yet; ask questions.

You are not the one who decides which procedures an engagement requires. The firm that signs, working under the standards for that engagement, does. Estimate the hours for the tasks you are given. If the scope seems too thin to meet the standards, raise it with the firm in writing before you price, and do not shrink the work to fit a price.

Step 2: break it into tasks

Use a standard task list and edit it for each file. A starting list for a review of financial statements or an audit file, to be adapted:

  • Intake: open the file, check what has arrived against what was promised, log gaps.
  • Reading: prior-year papers, the client's records, anything the firm tells you about the entity.
  • Core procedures: the tasks you are actually assigned, one line each. For example, tie the trial balance to the statements, review a reconciliation, test a sample, review a disclosure checklist.
  • Documentation: write up what you did and the result so another person can follow it.
  • Queries: questions to the firm or the client, and time to process the answers.
  • Review: a final read of your own work, and time to answer notes from the reviewer.
  • Close: delivery, administrative steps and updating your time record.

Give each task its own line. A single line called "the review" will be wrong; seven lines will be wrong by much less.

Step 3: put hours on tasks from your own data

For each task, use your own recorded hours on similar work if you have them. If you do not, time the next three files by task and use those. If you have nothing, estimate a range, not a point: a best case, a likely case and a worst case.

Then add a simple three-point figure for each task, or for the whole file:

Estimate = (best + 4 x likely + worst) / 6

Illustrative example, labelled as such. For one file you put best 6 hours, likely 9 and worst 18. The estimate is (6 + 4 x 9 + 18) / 6 = (6 + 36 + 18) / 6 = 60 / 6 = 10 hours. The weighted figure sits above the likely case because the worst case is far from it, which is how a long tail should show up.

If you are not comfortable with the formula, a plain range with a stated likely figure is fine. The aim is a number you can defend, and a note of how uncertain it is.

Step 4: add the items people forget

Check the total for these before you quote:

  • Waiting is not billable time but may cost you other work. If the file will be open for weeks, price the carrying cost of having it open.
  • A margin for rework. Choose it from your history: the usual ratio of actual to estimated hours on your last files of this type.
  • Communication. Calls and messages are real hours on a file.
  • Set-up time for a new buyer or a new file layout, which falls on the first file and shrinks after.

Step 5: convert the estimate to a price or an hourly cap

For an hourly engagement, give the estimate as a range and agree a point at which you pause and report. For a fixed or per-file fee, divide the price by your estimate and compare the result with your required rate, built as in the main rates guide. If the equivalent is below it, change the price, the scope, or decline.

Illustrative continuation. A price of 1,000 units against a 10-hour estimate is 100 units an hour. If your required rate is 120 units, you need a price of 10 x 120 = 1,200 units, or an estimate of 1,000 / 120 = 8.3 hours that you can honestly defend, which usually means a narrower scope.

Step 6: record actuals and close the loop

After the file, record actual hours by task against the estimate. Compute actual divided by estimate for the file and for each task. Over a few files, patterns show up: intake that always runs long, a task you always underestimate, a buyer whose files always carry gaps. Update your standard task hours and your rework margin from these records. This is how an estimate becomes accurate: by feeding your own experience back in, not by guessing harder.

Professional standards still set the floor

Estimating is about your time, not about the procedures. The AICPA Code's General Standards Rule (ET 1.300.001) requires professional competence and due professional care, and the engagement standards for audits, reviews and compilations say what the engagement requires. A short deadline or a low price does not lower those requirements. If a quote leaves too few hours to do the assigned work to the standard the firm needs, say so in writing and let the firm decide whether to change the scope, the date or the price.

Frequently asked questions

How many hours does an audit file take?

There is no sound general answer. It depends on size, complexity, the state of the records, and the part of the work you are asked to do. Build the estimate from tasks and your own records.

Should I tell the buyer my estimate?

For hourly work, yes, as a range with a point at which you will pause and report. For fixed fees, you can share the scope and price without the internal hours.

What if my estimate is wrong halfway through?

Tell the buyer when you see it, with the reason and the revised range. Early notice keeps the relationship; a surprise at the invoice does not.

Is a three-point estimate required?

No. It is one method. A range with a likely figure serves the same purpose if you record actuals.

Sources

Last verified November 20, 2026. Sources checked by the editorial team; not yet reviewed by a named professional. General information, not legal, tax or accounting advice.

Related pages

Join the CORAA CPA network waitlist

CORAA prepares audit files for US CPA firms. Network members are independent contractors who clear what the software flags, with evidence and a note, paid per file under a contractor agreement.

  • Files are offered to you; you accept or decline
  • No exclusivity: you can work for others
  • The firm reviews and signs; CORAA never does

* required