Internal auditing

Internal auditing is a workflow for wind, solar and storage assets, and it works differently from the others: nothing runs when a document arrives. You hold a checklist, you point it at an asset, and Aevy answers each question from the documents on that asset, citing what it read. What it cannot answer is the gap, and the gap is the output.

Availability

Analyses are a separate module, run and read on an asset. They are part of Due Diligence, and switched on per organization in other modes. If an asset shows no Analyses view, switch mode from your account menu at the bottom of the sidebar, or ask your Aevy contact to turn it on.

From a checklist to answered questions

The two outputs matter equally. An answered question with a citation is evidence you can hand to an auditor. An unanswered one is either a document you do not hold or a thing you have not done, and telling those apart is the work.

An audit checklist can cover whatever you audit against: technical condition, HSE, compliance and permits, insurance, commercial terms. The same machinery runs a due diligence review, which is the same job with a different checklist and a deadline.

Set it up

Step	What happens	Who
1 The checklist	Your questions, as you already ask them. Bring the spreadsheet or the audit protocol you use today rather than inventing one.	You
2 Turned into a template	Aevy builds it into a reusable template, so the same audit runs on the next asset without being rewritten.	Aevy
3 Documents	The asset’s documents are in Aevy. An audit reads the whole asset, so completeness matters more here than elsewhere.	You
4 Run it	You start a run against an asset. This is on demand: it happens when you say so, not when a document arrives.	You
5 Review	Read the answers, check the citations, and raise the gaps you want tracked as work.	You

Decide before it runs

Decision	What it changes	Where portfolios land
What the questions ask	A question that asks whether a document exists gets a cheap answer. One that asks whether the thing was actually done gets a useful one.	Written as the auditor would ask them, not as a filing check. “Was the annual inspection carried out and by whom” beats “is there an inspection report”.
What an unanswerable question means	Whether no evidence is treated as a fail or as a gap to chase. The two lead to very different lists.	A gap, with the fail reserved for a question the documents answer badly rather than not at all.
How often you run it	A run is a snapshot of what the asset’s documents said that day, so the cadence is yours to choose.	Annually per asset, plus before any event that will be scrutinized: a refinancing, a sale, a regulator’s visit.

Read a run

An analysis opens on three tabs: 1. Conclusion, 2. Findings, and 3. Checks. The checks tab lists every question with its answer and the passage behind it, so a disputed answer is settled by opening the document rather than by arguing. The coverage bar above it filters to the questions Aevy could not answer, since that list is usually the point of the exercise.

Aevy drafts findings from the answers on the findings tab. Add all to findings moves them into your findings list, where each gets an owner and a date, so it leaves the audit and joins the work. A run you do nothing with is a report. A run whose gaps became findings is an audit.

Limits

An audit reads the documents on the asset. It cannot see practice that was never written down, so it tells you what your paperwork can prove rather than what your team actually does.

A run is a snapshot. It does not update itself as new documents arrive, which is deliberate: an audit is a statement about a date. Run it again to see what changed.

What’s next

• How workflows work: the set, and what each needs before it runs.
• Document handover: the same machinery asking only whether the file is complete.
• Industry standards: the published guidelines many audit checklists are built from.
• Findings: what a raised gap becomes.