Skip to content

Using the board portal audit trail as audit evidence

—10 min read

A long thin ribbon of small evenly spaced marks unrolling from a cylinder, with a few marks highlighted and a tiny lock symbol at the ribbon's start

A board portal's audit log can give internal auditors reliable evidence about the board process: who had access, when papers were published and first opened, how votes were cast, and which documents were downloaded or exported. To rely on it, check what the log records, that nobody can alter it, and that your export is complete; then use it next to the minutes and the papers, because the log shows actions, not what the board discussed.

Why is a portal audit log useful evidence?

Because the system writes it automatically, at the time, and the people being audited cannot edit it. That makes it stronger than evidence reconstructed afterwards, such as email folders or recollections. It also lets you test the whole population instead of a sample: every vote, every download, every permission change in the period.

For a review of the board process it answers questions that are otherwise hard to settle. Did all directors have the papers in time? Did anyone outside the board have access? Was a vote cast the way the minutes say? If you are scoping such a review from scratch, start with our guide on how internal audit can review the board process; this post covers the portal log as one source of evidence.

What does a typical audit log record?

It differs by product, so ask for the list of recorded events before you design tests. The Konsaro audit log, as one example, records:

Example of events recorded in a board portal audit log (Konsaro)
AreaEvents
Sign-inSign-ins, sign-outs, failed sign-ins, password and two-factor changes
Membership and accessGuest invitations, membership and permission changes, settings changes
MeetingsAgenda changes, publishing of minutes
DecisionsVotes opened, cast, changed and closed; decisions and tasks
DocumentsDocuments added or deleted; the first time each person opens a meeting paper
Data leaving the portalDownloads and data exports
Context for each entryIP address, browser and device, sign-in session

Acting on someone else's behalf, for example an assistant linked to a director, is also recorded. For a deeper look at what a log should contain in the first place, see what a board portal audit trail should record.

How do you plan the audit step by step?

Treat the log like any system-generated report: agree the objective, define the population, get the data, test it, document it. The owners below are typical; adapt them to your set-up.

Audit steps and owners
StepWhat to doWho
1. ObjectiveWrite down the control you are testing, for example «all directors receive papers by the date the organisational regulations require»Internal audit
2. Event listAsk the board office for the portal's list of recorded events and compare it with the objectiveInternal audit, board office
3. Period and scopeFix the period, the boards and committees, and the meetings in scopeInternal audit, chair
4. ExportHave an organisation admin export the log for the period (CSV or JSON), with you watching or with an independent personOrganisation admin, internal audit
5. CompletenessCheck the first and last entries cover the period, and that counts look plausible against known meetings and votesInternal audit
6. TestsRun the tests in the table below and note exceptionsInternal audit
7. Follow-upAsk the board office to explain each exception, then rate itBoard office, internal audit
8. FileKeep the original export, your filters and your results in the working papersInternal audit

Which tests can use the log?

Several controls in a board process review can be tested directly. The table gives the test, what to compare it with, and what counts as an exception.

Audit tests using the portal log
ControlTestCompare withException looks like
Timely accessFirst-open time of the key papers per directorMeeting date and the distribution rule in the organisational regulationsA director first opened a paper after the meeting started, or never
Access only for entitled peopleMembership, permission changes and guest invitations in the periodBoard and committee membership on each meeting dateA person kept access after leaving, or a guest was invited without a recorded reason
Voting integrityVotes opened, cast, changed and closed per decisionMinutes and decisions registerThe minutes record a decision for which no closed vote exists, or a vote was changed after it was cast
Data leaving the portalDownloads and exports of sensitive papersDepartures, conflict-of-interest declarations, committee membershipA large export shortly before a director left, or a download by someone who should have view-only access
Sign-in securityFailed sign-ins and two-factor changesNormal patterns for the boardRepeated failed attempts, or a two-factor change without a matching request
Acting on behalfEntries where an assistant acted for a directorThe director's written authorisationActions by an assistant who was not authorised

What does this look like at Muster AG? A worked example (invented)

Muster AG is an invented company with a five-member board that meets six times a year. The organisational regulations say papers must be available seven days before a meeting. The internal auditor exports the log for the financial year and finds that, for the March meeting, one director first opened the budget paper two days after the meeting; the other four opened it within the seven days.

The auditor does not conclude that the director failed to prepare. The log shows only the first opening. She asks the board office what happened and learns that the director received the paper by email from the chair's assistant and used the portal copy only afterwards. That is the real finding: papers travelled outside the portal, which the log cannot show and which breaks the confidentiality rules. Sample wording for the report: «For one of six meetings, one of five directors first opened the key paper in the portal after the meeting. Management explained that the paper had been sent by email. We recommend that papers are distributed only through the portal and that the chair confirms this in the regulations.»

How do you make sure the evidence is reliable?

The log is only as good as your confidence in it. Work through these points before you rely on it.

  • Confirm the log cannot be edited or deleted by users, including administrators. In Konsaro it cannot; ask every vendor the same question.
  • Have the export produced in your presence or by a person independent of the board office, and keep the original file (CSV or JSON) unchanged with your working papers. Work on a copy.
  • Check completeness: the export should cover the full period, and event counts should be plausible against known activity such as the number of meetings and votes.
  • Check the clocks: note the time zone of the log and the time zone of the meeting before you compare them, especially around daylight-saving changes.
  • Ask how long the log is kept and whether older entries can still be exported. Do this before the period you want to test has aged out.
  • Record who exported what and when, so your own chain of custody is clear.

What can the log not show?

What happened in the room. The log shows that a director opened a paper, not that they read it; that a vote was cast, not why. It does not show discussions, and it does not cover papers that travelled outside the portal, such as an email attachment or a printout.

A few more limits matter in practice. «First opened» is one timestamp per person and paper, so later reading is not evidence. A shared device or shared account breaks the link between an entry and a person, which is why two-factor sign-in and personal accounts matter. And the log starts when the portal starts: events before go-live, or in a tool the board used before, need other evidence. Use the minutes and the papers as sent for the content, and treat any sign that papers circulated outside the portal as a finding of its own.

What should you ask the board office for?

A short, specific request gets you a complete export. A sample you can adapt:

«For our review of the board process for [financial year], please arrange for an organisation admin to export the audit log for [boards/committees] from [start date] to [end date] as CSV, with me present or with [independent person] confirming the export. Please also send the list of event types the log records, the membership lists with start and end dates, and the list of guests invited in the period.»

How do you handle personal data in the log?

The log contains personal data: names, IP addresses, devices. Use only what the audit needs, store the export securely with restricted access, and delete it in line with your working-paper retention rules. Data protection law requires personal data to be processed proportionately and to be destroyed or anonymised once no longer needed (Art. 6 paras. 2 and 4 FADP). If the log shows conduct that may affect a director personally, take the finding to the chair or the audit committee chair rather than circulating the raw entries.

What do you do when the log contradicts the minutes?

Do not decide which one is right. Describe both, ask the board office and the minute-taker for the underlying facts, and look for a third source such as the papers as sent or the circular resolution text. Common causes are harmless: a vote opened and closed twice, a decision taken orally and entered later, or a meeting that ran in two parts. If the explanation is weak, report it as a gap in the control, not as an accusation. See also how to report to the audit committee.

Where do you find the log in Konsaro?

Organisation admins can view the audit log and export it as CSV or JSON. More on security, our trust centre and decisions and voting. The internal auditor page describes how the log fits an auditor's work.

Frequently asked questions

Can administrators change the audit log?

In Konsaro, no. The log cannot be edited or deleted; organisation admins can view and export it. Ask every other vendor the same question and get the answer in writing.

Does «opened» mean the director read the paper?

No. It means the paper was opened for the first time by that person. It is evidence of access, not of reading or understanding.

Which format should the export be in?

CSV is easy to analyse in a spreadsheet; JSON keeps the full structure. Keep the original export file unchanged in your working papers and work on a copy.

Is the audit log enough to evidence board oversight?

No. It complements the minutes and papers, which show what the board discussed and decided. It proves that actions happened, not that the board exercised judgement.

Can I test every vote instead of a sample?

Usually yes, because the log lists every vote with its opening, casting and closing. Compare the full list with the decisions register and investigate each difference.

Who should be allowed to export the log?

In Konsaro, organisation admins. If the admin is the board office you are auditing, have the export done in your presence or by an independent person and keep the file.

Is the log personal data?

Yes: it holds names, IP addresses and devices. Use it only for the audit, restrict access and delete it under your retention rules (Art. 6 FADP).

Sources

  1. Federal Act on Data Protection (FADP, SR 235.1), Art. 6 (checked 29 October 2026)
  2. economiesuisse: Swiss Code of Best Practice for Corporate Governance (2023) (checked 29 October 2026)
Book in under a minuteSee open times instantly

Interested? Let's talk.

We'll walk you through one full board cycle in Konsaro, from the first board book to signed minutes and assigned actions, and answer your questions live.

Book your demo

30-min video call · Phone call · Email