Audit Plan Template Excel: Build a Usable Workbook

How-to basics · Updated November 19, 2026

An audit plan template in Excel is a workbook for recording an audit’s objectives, scope, risks, procedures, owners, schedule, and results. Build one with separate sheets for the audit overview, work program, timetable, and findings; tailor the fields to the audit’s purpose and the standards or policies that apply.

What an Excel audit plan should do

An audit plan is a working document, not just a calendar or a list of questions. It connects what the audit is intended to establish with the work the team will perform and the evidence it will collect. A useful spreadsheet makes those connections visible and gives the audit lead a way to monitor progress, changes, and unresolved issues.

The appropriate content depends on the audit. An internal review of purchasing, for example, may focus on approval controls, supplier setup, and payment records. A financial statement audit follows its applicable professional standards and engagement requirements. A regulatory or quality audit may use prescribed criteria and evidence rules. A generic Excel template can help organize work, but it does not establish compliance with a particular standard or replace professional judgment.

Keep the plan proportionate. A small, low-risk review might need one work-program sheet and a short schedule. A multi-location audit with several reviewers may need separate tabs, version control, and more detailed tracking. In either case, a reader should be able to tell what is being examined, why, by whom, and what remains to be done.

A practical workbook structure

Start with a small number of clearly named worksheets. Avoid making one enormous sheet that mixes background, test steps, evidence references, and findings; that layout is difficult to filter and maintain. A practical starting structure is:

  • Overview: audit name or identifier, audit lead, sponsor, purpose, objectives, scope, criteria, locations or processes, planned dates, and approval or review details.
  • Work program: one row per procedure, with a procedure ID, objective or risk link, test description, population or sample details where relevant, assigned person, target date, status, and evidence reference.
  • Schedule: key milestones such as planning, opening meeting, fieldwork, review, draft reporting, and closeout, with owners and planned or actual dates.
  • Findings and actions: finding ID, condition, applicable criterion, supporting evidence reference, impact or risk assessment, agreed action, owner, due date, and follow-up status.
  • Lists or instructions: definitions for status values, instructions for users, and any controlled dropdown choices. Keep this sheet simple and remove it from circulation if it contains internal setup notes that recipients should not see.

For example, a work-program row might read: “AP-03; verify a sample of purchase orders against approval limits; risk R-02; reviewer J. Lee; due 15 May; status Planned; evidence reference WP-03.” The example illustrates a tracking format, not a required audit test or sample size. Define what a status such as “Complete” means so that different reviewers do not use it inconsistently.

Set up the template in Microsoft Excel

In Excel for Microsoft 365 on Windows, create a blank workbook and add the worksheets you need. Put one field name in each column of the work-program sheet and keep each procedure on its own row. Select the range, then choose Home > Format as Table and confirm that the table has headers. Excel tables make it easier to filter by owner, due date, risk, or status as the plan grows. On Mac, the Format as Table command is also on the Home tab; names or placement can vary slightly by build. Excel for the web has table formatting as well, though some advanced workbook controls differ.

Use short, consistent status labels, such as Not started, In progress, Ready for review, Complete, and Blocked. If you want users to choose from a fixed list, select the entry cells and choose Data > Data Validation, then select a list and enter the allowed values. For a list stored on another sheet, define a named range and use that name as the validation source; this is more maintainable than repeatedly typing choices. Do not use status color as the only indication of meaning: retain readable text for accessibility and for printing.

Freeze the header row with View > Freeze Panes > Freeze Top Row when a sheet is long. Adjust column widths, wrap long descriptions, and use date formats consistently. Avoid merged cells in the middle of data tables because they interfere with sorting and filtering. Use a separate title area above the table if a prominent heading is needed.

Define the objective, scope, and criteria

Write an objective that states the question the audit is meant to answer. “Review purchasing” is too broad to guide testing. A more useful objective might be “Assess whether purchase approvals for the selected business unit followed the organization’s approval policy during the defined review period.” This makes the process, control concern, and period more apparent, while leaving room to specify the exact procedures later.

Record scope boundaries explicitly. Include the period examined, business units or sites, systems, transaction types, and any exclusions. An exclusion should be explained and approved where the engagement’s governance requires it; otherwise, readers may mistake an unexamined area for one that passed testing. Identify the criteria used to evaluate the activity, such as a named policy, contract requirement, regulation, or control framework, with a version or effective date when relevant.

Separate the audit objective from the procedure. The objective describes the intended result; the procedure describes the work used to reach it. For example, “determine whether access is appropriately authorized” is an objective, while “compare a defined sample of active accounts to approved access requests” is a procedure. The auditor should determine whether that test is suitable for the system and risk under review.

Connect risks to procedures and evidence

A work program is more useful when each procedure links to a risk or objective. Add an identifier such as R-01 or OBJ-02 and reuse it consistently in the overview and work program. A risk entry can describe what could go wrong and why it matters; a procedure should say what the reviewer will inspect, compare, observe, or reperform. Avoid vague entries such as “check invoices.” State the relevant criterion and the intended evidence, while keeping sensitive details out of broadly shared cells.

For a simple completion count, suppose procedure statuses are in H2:H21 and the summary formula is placed in H23. If 14 of those 20 cells contain the exact text “Complete,” =COUNTIF(H2:H21,"Complete") returns 14. This counts labels only; it does not establish that the work was adequately performed or reviewed. If you change the status wording, update the formula’s criterion too.

Evidence references should point to an approved, controlled location or workpaper identifier rather than embedding confidential files in the plan. Record enough information to locate the evidence and understand which procedure it supports. The plan itself should not claim that a control is effective merely because a test was marked complete. Test results, exceptions, review notes, and conclusions belong in the appropriate workpapers and reporting process.

Schedule owners, review, and changes

Give every procedure a responsible owner and a realistic target date. If another person must review the work, record that reviewer or include a review-status field. Distinguish planned dates from actual dates so schedule changes do not erase the original plan. The schedule tab can show milestones, while the work-program sheet tracks the more detailed tasks; these dates should agree.

Plans often change when access is delayed, a system changes, evidence is unavailable, or early results reveal a new risk. Record material changes with the date, reason, decision-maker, and effect on scope or timing. Do not silently delete a procedure that was dropped or overwrite an approved plan without retaining a record of the revision. Follow the organization’s approval and documentation rules, especially where the audit is regulated or externally reviewed.

Excel can sort and filter a schedule, but it is not automatically a project-management or audit-management system. It will not reliably notify every owner unless additional tools and processes are configured. Agree how the team will communicate overdue work and how often the audit lead will review status rather than assuming the workbook will manage those tasks by itself.

Common template problems and quality checks

A template can look polished and still produce weak audit documentation. Before using it, check for practical problems such as:

  • Scope is too vague: state the period, process, population boundaries, locations, and exclusions.
  • Procedures are not traceable: link procedures to objectives or risks and identify the evidence location.
  • Statuses are ambiguous: define them and distinguish completed work from reviewed work.
  • Dates and owners are missing: assign responsibility and make deadlines visible.
  • Changes overwrite history: preserve approved versions or use a controlled change log.
  • Too much sensitive data is copied into cells: use approved storage and access controls instead.

Before release, check that filters work, dates sort as dates rather than text, dropdowns contain the intended choices, and formulas cover the correct ranges. Review the workbook for hidden rows or sheets, stale examples, comments, and test data. If it will be shared outside the immediate team, confirm the recipient is authorized and remove unnecessary confidential information. A spreadsheet password should not be treated as a substitute for approved file-storage permissions.

When Excel is the right choice—and alternatives

Excel is a reasonable option for a small or straightforward engagement when the team needs a familiar, adaptable tracker and can manage access, revisions, and evidence separately. It is also useful for developing a draft template before deciding whether a more controlled tool is warranted. Its flexibility is a trade-off: users can alter cells, formulas, and layouts, and a workbook can become difficult to govern when many people edit separate copies.

For recurring audits, multiple teams, formal approval workflows, or extensive evidence management, consider whether an organization-approved audit-management or work-management platform better supports permissions, version history, review, and reporting. A shared document platform may help with controlled collaboration, but it does not by itself supply audit methodology. Follow organizational requirements for data retention, confidentiality, and approved software; do not move workpapers to a consumer file-sharing service simply for convenience.

Frequently Asked Questions

Is there a built-in audit plan template in Excel?
Excel does not provide one universal audit plan that fits every audit. Templates may be available through Microsoft template sources or an organization’s own files, but check the source and adapt its fields to the engagement. A downloaded workbook is a starting point, not evidence that its procedures meet applicable requirements.

What columns should an audit plan spreadsheet have?
Common fields include procedure ID, objective or risk link, procedure description, owner, planned date, status, reviewer, and evidence reference. The overview should capture purpose, scope, criteria, period, and key contacts. Add fields only when they serve a clear tracking, documentation, or governance need.

Can I use Excel for an internal audit?
Yes, Excel can organize an internal audit plan, particularly for a limited engagement. Whether it is suitable depends on the organization’s policies, complexity, confidentiality needs, collaboration, and recordkeeping requirements. The workbook does not replace the organization’s audit methodology or any applicable professional standards.

How do I track audit progress in Excel?
Use a consistent status list, an owner, and a target date for each procedure, then filter the table to review open or overdue work. Keep completion separate from review and from the final conclusion. A status count can summarize activity, but it cannot measure evidence quality or confirm that audit objectives have been achieved.

Should audit evidence be stored in the Excel file?
Usually, use the organization’s approved evidence repository and record a stable workpaper or file reference in the plan. Embedding evidence can make the workbook large and expose sensitive information to people who only need the schedule. Follow the engagement’s access, retention, and confidentiality rules.

Related

Try it: the Date Difference Calculator: days, months, years and weekdays between two dates, with the DATEDIF formulas.

More in How-to basics

Sources: Function behaviour and menu paths: Microsoft Support documentation for Excel. Method & sources

Spotted an error in this guide? Let us know.