Auditing Tick Mark Legend: Symbols, Electronic Workpapers, and Retention

An auditing tick mark legend is the reference key at the front of an audit workpaper file that defines every symbol the auditor uses on the schedules inside. Each symbol is shorthand for a specific procedure the auditor performed on a figure, and the legend translates that shorthand so a second reviewer, a quality control partner, or a peer review team years later can tell exactly what was done. Without the legend, a workpaper covered in checkmarks, letters, and triangles is unreadable.

What the Legend Contains

Each entry pairs a symbol with a plain-language description of the procedure it represents. “✓ = Verified amount to supporting invoice.” “C = Confirmed balance directly with third party.” The description has to be specific enough that someone who was not on the engagement can understand precisely what the auditor did with the figure the mark sits beside.

The legend is typically placed at the front of the electronic workpaper file or the beginning of a physical binder, so it’s the first thing a reviewer encounters. Many firms also require a localized version of the legend at the bottom of each individual schedule. That way, any single schedule pulled out of the file still stands on its own as a complete, interpretable document.

Some firms add the preparer’s initials and the date alongside each legend entry to document who performed the work and when. This is a firm-level practice rather than a regulatory mandate, but it strengthens the audit trail. When a reviewer can trace a mark back to a specific auditor on a specific date through the legend, the documentation is far more defensible.

Symbols You Will Commonly See

No universal standard governs which symbols mean what, but certain conventions appear often enough that most experienced auditors recognize them:

  • ✓ (checkmark): the amount has been checked and verified for accuracy.
  • √√ (double checkmark): the figure was cross-referenced with another document or working paper.
  • F (or P): the column was footed, meaning the auditor verified that the column totals add up correctly.
  • C: confirmed with an external party, such as a bank confirmation for a cash balance.
  • R: the auditor recomputed the calculation independently to verify accuracy.
  • A: the figure was agreed to the general ledger or financial statements.
  • T: traced to a supporting source document like an invoice or receipt.
  • Δ (triangle): a variance or difference was identified that needs further investigation.

These are conventions, not rules. A symbol that means “traced to source document” at one firm can mean something different at another, or on a different engagement within the same firm. That is why the legend is authoritative and general familiarity is not.

How Marks and the Legend Work Together on the Page

Placement matters. The tick mark goes immediately next to the specific figure it applies to. A checkmark confirming recalculation of a total sits right beside that total, not in the margin or at the bottom of the column. When marks drift away from their target figures, reviewers waste time guessing which item was tested, and the documentation loses its value.

Tick marks work alongside the cross-referencing system that threads an audit file together. A mark indicating that a balance agrees to the general ledger is often paired with a workpaper reference number, linking the reader to the exact schedule where that balance was independently tested. The tick mark shows what was done; the cross-reference shows where to find the supporting work.

Reviewers use tick marks too, but for a different purpose. A preparer’s mark says “I performed this procedure.” A reviewer’s mark says “I checked the preparer’s work and agree with the conclusion.” Firms commonly distinguish the two through color, with reviewers working in red ink, for instance. In electronic systems, the software tracks the distinction automatically.

Firm-Wide Versus Engagement-Specific Symbols

Large firms maintain proprietary tick mark libraries that apply across all engagements. The firm’s internal methodology manual defines the approved symbols and their meanings, which speeds up training and cross-office collaboration. Beyond that firm-wide set, engagement teams frequently create additional symbols for procedures unique to a particular client or industry. A manufacturing audit might add a mark for “agreed to physical inventory count.” A financial institution audit might add one for “confirmed derivative position with counterparty.” Those marks live in the legend for that file and nowhere else.

This is why the legend on the specific engagement is what governs, even within the same firm. Assumptions carried over from other engagements lead to misreadings. Check the legend on the file in front of you.

Tick Mark Legends in Electronic Workpaper Systems

Most audit work today happens in platforms like CaseWare, TeamMate, or the proprietary systems the largest firms have built. The underlying concept is the same, but the mechanics change.

In CaseWare, auditors create and manage tick marks through a centralized tickmarks worksheet inside the engagement file. Each entry has a graphic symbol, a short alphanumeric identifier, and a description of the procedure. Auditors apply the marks by dragging them from a toolbar onto figures in the workpapers, and hovering over any mark shows who placed it and when.

Electronic systems close some of the gaps that paper-based tick marks used to leave open. The legend stays linked to the marks, so a symbol cannot appear on a schedule without a corresponding definition in the file. The software logs the identity of the person who applied each mark and timestamps the action, doing automatically what preparer initials and dates used to do by hand. Reviewer sign-offs are tracked separately from preparer marks inside the system, so color coding is no longer necessary.

Documentation and Retention Rules That Apply to the Legend

Tick marks and their legends fall under broader audit documentation standards. For audits of publicly traded companies, the PCAOB requires auditors to prepare documentation “in sufficient detail to provide a clear understanding of its purpose, source, and the conclusions reached.”1Public Company Accounting Oversight Board. AS 1215: Audit Documentation The standard does not prescribe symbols or require a legend by name, but a workpaper full of unexplained marks would plainly fail the “clear understanding” test.

Retention is strict. Under PCAOB standards, audit documentation must be kept for seven years from the date the auditor grants permission to use the audit report in connection with the company’s financial statements. If no report is issued, the seven-year clock starts when fieldwork was substantially completed. Auditors have 14 days after the report release date to assemble the final set of documentation for archiving.1Public Company Accounting Oversight Board. AS 1215: Audit Documentation The SEC’s parallel regulation imposes the same seven-year retention period for workpapers, memoranda, correspondence, and any records containing conclusions, opinions, or analyses related to the audit.2eCFR. 17 CFR 210.2-06 – Retention of Audit and Review Records

Destroying audit records, including workpapers and their tick mark legends, carries criminal consequences. Federal law makes it a crime for an accountant who audits a public company to fail to maintain audit or review workpapers for the required retention period.3Office of the Law Revision Counsel. 18 USC 1520 – Destruction of Corporate Audit Records The legend, as part of the workpaper file, sits squarely inside those retention obligations. If the workpapers survive but the legend does not, the tick marks become meaningless symbols and the documentation fails to support the auditor’s conclusions.

For audits of non-public entities, state boards of accountancy set their own retention requirements, which typically range from five to seven years depending on the jurisdiction. The principle is the same either way: keep the legend with the file, for as long as you keep the file.