AbenAudit / List of Potential Findings (LoPF)

Topic · LoPF

List of Potential Findings (LoPF)

From fieldwork notes to agreed findings: what a LoPF is, why internal audit teams keep one, and how AbenAudit handles potential findings.

What is a List of Potential Findings?

A List of Potential Findings (LoPF) is the working register of issues an audit team has spotted during fieldwork but not yet confirmed. Each line is a candidate finding. It gets evaluated, discussed with management and then either becomes a reported finding or is dropped, with the reason recorded.

The idea comes straight from the IIA's Global Internal Audit Standards. Standard 14.2, Analyses and Potential Engagement Findings, says that a difference between the evaluation criteria and the condition indicates a potential engagement finding that must be noted and further evaluated. Standard 14.3, Evaluation of Findings, then requires each potential finding to be evaluated for significance. That evaluation is done with management, to identify root causes where possible and to consider likelihood and impact. (The IIA, Global Internal Audit Standards, 2024.) A LoPF is how many teams keep track of that step.

What a LoPF usually records

The columns vary by methodology. A typical register holds:

  • a reference and a short title;
  • the work-programme step or working paper it came from, and who prepared it;
  • on a group audit, the company or entity it concerns;
  • the criteria (what should be) and the condition (what is), and later the cause and effect;
  • a preliminary rating;
  • its status: open, under evaluation, discussed with management, agreed, merged or dropped;
  • the date it was discussed with the auditee, and the outcome.

Why keep one

  • Nothing gets lost between fieldwork and the report. Every candidate has a status and an owner.
  • No surprises at the closing meeting. Management sees potential findings while they can still be discussed and the facts checked.
  • A clean audit trail. A dropped item shows why it was dropped, which matters for supervisory review and quality assessment.

Many teams keep their LoPF in a spreadsheet next to the working papers. That works until two people edit it at once, or a finding's wording in the report drifts away from the evidence behind it.

How AbenAudit handles potential findings

In AbenAudit the potential finding is a record from the start, not a row in a separate file:

  • A finding is raised from a work-programme step, or directly from a test's conclusion, so it always links back to the work that produced it.
  • The engagement's Findings page groups findings by stage. The fieldwork group lists those not yet reported, each with a link to its step. That group is the engagement's live list of potential findings.
  • Criteria, condition, cause, effect and the recommendation are separate fields. On a group audit the finding also records which company it is about.
  • The residual risk is derived from the risk matrix in force (materiality × likelihood), with the version of the scale shown. A director's override is recorded with who, why and what the matrix produced.
  • Findings are grouped into evidence sheets, one problem for one company and risk type. Each sheet is reviewed as a unit, and its findings are frozen while it is in review.
  • Each finding is then put to the auditee, who answers with a comment. Internal audit records the auditee's agreement. The stages run Drafted → With the auditee → Agreed → Reported, and after the report Upheld, Amended or Withdrawn.
  • Every step goes into the engagement's history and the hash-chained ledger, with who and when.

Not there yet

ItemStatus
Potential findings listed per engagement, linked to their work-programme stepAvailable
A downloadable List of Potential Findings built from the work papers, with company and preparer columnsPlanned
Filter and search on the Findings pagePlanned
Evidence sheets per company by default, chosen from the engagement's companies (company is free text today)Partly available

Sources: The IIA, Global Internal Audit Standards (Standards 14.2 and 14.3; summaries are ours). AbenAudit user manual, verified November 2026.