Good documentation lets another person follow what you did without calling you. For a freelancer that is a professional standard and a self-protection: when the file is read months later by a partner, a peer reviewer or a regulator, your notes are all they have. This page sets out what a reviewer's or preparer's notes should show, with pointers to the standards. It is general information, not legal advice. The firm's methodology decides the format.
US rule. The AICPA's auditing standards for non-public entities (AU-C) are the reference. Other engagement types have their own sections, and outside the US you should check your own regulator.
Where the standards sit
AU-C 230 is the AICPA section on audit documentation. It sits in the 200 series, which the AICPA's page for the standards in effect labels general principles and responsibilities. Reviews and compilations of financial statements are covered by the AICPA's separate standards for those engagements. In short, AU-C 230 asks for documentation that would let an experienced auditor with no previous connection to the audit understand what was done, what it found and the significant judgements made, and it asks the file to record who did the work and when, and who reviewed it, when and to what extent (paragraphs .08 and .09). Read the AICPA's text for the exact wording.
For the freelancer, the firm's own documentation policies come first. They tell you which template, which sign-off convention and which cross-referencing system to use. The principles below apply on top of them.
What your notes should let a reader see
An experienced reader should be able to answer these questions from the file, without asking you.
- What was the objective? Which assertion, balance or process was the step meant to address.
- What did you do? The procedure, in enough detail to repeat it: which population, which sample, which criteria, which tools.
- What did you look at? The source: document names, dates, system reports, with a reference to where each sits in the file.
- Who did it and when? Your sign-off and date, and the date you finished.
- What did you find? Exceptions, differences and open points, stated plainly.
- What happened to each exception? Who it went to, what was said, and how it ended.
- What does it feed? A cross-reference to the schedule, memo or conclusion that depends on your step.
If a note cannot answer one of these, the step is not finished.
Habits that make notes usable
- Write for a stranger. Assume the reader has not seen the client.
- Reference, do not paste. Point to the document in the file instead of copying its content into your note.
- Separate fact from judgement. "Two of 25 invoices had no delivery note" is a fact. "This is not significant" is a judgement that belongs to the person who evaluates it.
- Record changes openly. If you correct a note, show the original and the change, with date and initials. Do not overwrite.
- Use the firm's tick-mark legend. Keep a legend on the schedule. A tick mark with no legend is noise.
- Finish before the deadline. AU-C 230 asks for documentation to be prepared on a timely basis, for the final file to be assembled no later than 60 days after the report release date, and for any later change to record why it was made, when and by whom.
- Keep client information inside the firm's system. Do not copy notes to personal drives or messaging apps. See the section 7216 and data-security cluster.
What a reviewer adds
When you review someone else's work, your notes should show:
- What you reviewed, by reference, and the extent of your review (all of it or selected parts).
- Whether you agreed with the preparer's work and conclusion on each point, and why where you did not.
- Questions you raised, the answers you got and whether you were satisfied.
- Items you left for a higher-level review.
A review note that says only "reviewed, ok" does not show what was reviewed.
Independence and other declarations
Documentation is also where you record your independence declaration for the file where the firm requires it, in the form the firm uses. Do not make up your own wording. See the ethics cluster on independence when freelancing.
What not to put in the file
- Opinions about the client's management that are not related to the work.
- Anything you cannot support from the file.
- Conclusions on the engagement as a whole, unless the firm has assigned that to you. That is for the signer. See Who signs and who does not.
- Personal information that is not needed for the step.
Retention and your own copy
Whether you may keep anything after the engagement is a matter of the agreement and the firm's policy. See Who owns the workpapers. Keep your own log of dates, engagement names and hours, not the file.
Two illustrative scenarios
Scenario A. A freelancer tests 25 vendor invoices out of 400 in a payables population. The note shows the population (400 invoices, listed on a referenced schedule), the way the 25 were selected, the criteria (approval, delivery evidence, amount agreed to ledger), two exceptions with references, and a line saying the exceptions went to the senior on a stated date. A reader sees the full path.
Scenario B. A freelancer reviews a preparer's bank reconciliation. The note says which reconciling items were agreed to the bank statement, which were not and why, and that two stale items were passed to the senior for evaluation. It makes no statement that the reconciliation is acceptable overall.
Frequently asked questions
How much detail is enough? Enough that an experienced person with no connection to the file could repeat your step and reach the same result.
Can I use my own template? Only if the firm allows it. Most firms require their own.
Do I sign my workpapers? Follow the firm's sign-off rule. A sign-off records who did or reviewed a step. It is not a report. See Who signs and who does not.
Who decides whether the file is complete? The firm.