When to use an internal audit template
Internal audits are only valuable if they find the right risks and lead to action. Without a consistent process, audits vary by auditor, evidence is hard to review and agreed actions are forgotten once the report is issued. An audit template gives every audit the same structure and keeps actions visible until they are closed.
Use it for financial, operational or compliance audits of a process or department, or for audits a consultancy runs for clients. It also works for smaller businesses reviewing controls for the first time.
How the template is structured
- Planning. Agree objective and scope, notify the auditee and request documents.
- Risk assessment. Understand the process, identify key risks and controls, and plan the tests.
- Fieldwork. Test controls, interview staff and document workpapers.
- Findings. Draft findings with causes and recommendations, then agree actions with management.
- Reporting. Write, review and issue the report.
- Follow-up. Track actions, verify completion, report progress and close the audit.
The Action overdue label makes late actions easy to report to management.
How to use it in Worklenz
- Create a project for each audit.
- Add the phases and tasks above and attach workpapers and evidence to their tasks.
- Restrict project access to the audit team and relevant managers.
- Create one task per agreed action in the follow-up phase and assign the action owners.
- Track audit hours on the Pro plan and above to plan future audits.
Making audit work visible and billable
Consultancies running audits for clients often sell them at a fixed fee. Time tracking shows the real effort by phase, so fees stay realistic, and on the Business plan project finance compares the budget with the cost of logged time.
Example: auditing the purchasing process
An internal audit team reviews purchasing at a mid-sized company. The risk assessment identifies three key controls: approval limits, supplier set-up checks and three-way matching of orders, deliveries and invoices. Testing a sample of 40 payments finds several paid without an approved order.
The finding is discussed with the finance manager, who agrees to block payments without an approved order from next month. The report rates the issue as high risk. In follow-up, the audit team verifies the new control with a fresh sample and closes the action.
Writing findings people act on
A useful finding has four parts. The condition says what you found, with numbers where possible, such as eight of forty payments made without an approved order. The criteria say what should have happened, usually a policy or control. The cause explains why the gap exists, for example an approval step that the system allows users to skip. The recommendation proposes a practical fix that addresses the cause, not just the symptom. Rate each finding by risk and keep the language neutral: the aim is to fix a process, not to blame a person. Findings written this way are easier for management to agree with, and the agreed actions are more likely to work.
Planning the annual audit programme
Most internal audit teams plan a year of audits at a time. Rank processes by risk, considering size, complexity, past issues and recent changes, and audit the highest-risk areas most often. Leave some capacity for unplanned reviews, such as an investigation or a new system going live. Running each audit from the same template makes the programme easier to manage and the results easier to compare.
Who should be involved
An audit lead owns the plan and the report. Auditors run the tests and write workpapers. A reviewer checks quality before findings are shared. Process owners and managers agree findings and own actions. An audit committee or leadership receives the report.
Common internal audit mistakes
The first mistake is testing everything instead of focusing on key risks. The second is weak workpapers that cannot support the findings. The third is no follow-up, so the same findings appear next year. This template builds each step in.
Tips for effective audits
- Start with risk. Focus testing on what could go most wrong.
- Document as you go. Workpapers written later are weaker.
- Agree findings before reporting. Surprises damage trust.
- Verify, do not assume. Close actions only with evidence.
Related: the security assessment template and the month-end close template.






