Back to Blog
    audit-evidence-examples
    compliance-evidence-collection
    glba-risk-assessment
    compliance-evidence-management
    collecting-audit-evidence

    Compliance Evidence Collection: A Practical Guide for Wisconsin Businesses

    Dustin CollettNovember 14, 2026

    Compliance evidence collection means gathering dated, attributable records that prove a required control actually operated during a specific period. The firms that pass audits without a scramble do three things: they decide in advance which artifact proves which control, they pull records from the systems that generate them, and they keep them in one governed place. IT is where most of that evidence is born, so we treat it as a standing part of managed IT at Collett Systems, not a once-a-year project.

    This guide is for owners and office leaders at Wisconsin manufacturers, law firms, dental practices and financial firms. You do not need a compliance background. You need to know what an auditor will ask for, what good evidence looks like, and how to keep it current.

    TL;DR

    • Evidence is any record showing a control was performed: a policy, a log, a screenshot, a report, a training roster, a signed approval. If it is not documented, an auditor treats it as not done.
    • Reliable beats plentiful. Evidence needs a date, a source and a link to the requirement it supports.
    • Build a control register first: each control, its owner, how often it runs, and the exact artifact that proves it.
    • Automate technical records such as logs and configurations. Keep people in the loop for approvals, exceptions and judgment calls.
    • Financial firms covered by the FTC Safeguards Rule need a written risk assessment and the records behind it.

    Table of Contents

    What counts as compliance evidence

    Evidence is the documentation that shows your security and compliance controls are working as required. Compliance audits seek objective evidence that supports or contradicts assertions about whether controls are designed and operating effectively. In plain terms, you say "we review user access every quarter," and the auditor asks you to show it.

    Common forms include audit reports, licenses, certifications, policies, training records, monitoring logs and testing results. What separates evidence from ordinary paperwork is purpose: it exists to show a reviewer that something happened when and how it was supposed to.

    Audit evidence examples by business type

    The same categories show up everywhere. What changes is the regulation behind them.

    Evidence typeExampleTypical owner
    Policy or procedureWritten information security program, incident response planOwner or compliance lead
    System configurationScreenshot or export showing multi-factor authentication enforcedIT
    System-generated reportBackup success report, patch status report, access review exportIT
    Log recordsAuthentication and administrative activity logsIT
    Training recordSecurity awareness roster with datesOffice manager or HR
    Test resultVulnerability scan or penetration test reportIT or outside tester
    Approval recordSigned change request, risk acceptance sign-offManagement
    WalkthroughDated notes of how a process was demonstrated, with who attendedProcess owner

    A Wisconsin dental practice might use the same table to show how patient records are protected. A manufacturer might use it to show access controls on engineering files for a customer's security questionnaire. A law firm might use it to answer a client's outside-counsel guidelines.

    What makes evidence audit-ready

    Auditors judge evidence on two tests. It must be sufficient, meaning enough to support the finding, and appropriate, meaning relevant, valid and reliable. When it falls short, they ask for corroborating evidence, which means more of your time.

    Two points matter most in practice.

    Volume does not rescue weak evidence. Both ReliabilityFirst and ACCA make the point that a pile of unreliable records does not become reliable. Ten undated screenshots are worth less than one dated system export.

    Source matters. ACCA notes that audit evidence is generally more reliable when it comes from an independent external source, is subject to effective internal controls, is documentary rather than oral, or is an original document. A report exported directly from your backup platform beats a spreadsheet someone typed by hand.

    The detail an assessor looks for

    Forvis Mazars advises that source documentation identify what was tested and where support came from, with dates, scope, participants and the relevant document or report. For a policy, capture the document name, version, approval or effective date and the relevant section. Confirm it was in effect during the period being assessed, and name the requirement it maps to.

    A simple standard for every artifact: what it is, when it was produced, who or what produced it, and which control it proves.

    A step-by-step routine for collecting audit evidence

    The approach below follows the control-register method described by AuditSuisse. At each step we note where it usually goes wrong.

    1. Build a control register

    List every control in scope: its owner, how often it runs, the criterion it meets and the exact artifact that proves it. "Access reviews" is not an entry. "Quarterly user access review, exported from the directory, approved by the office manager" is.

    Where it goes wrong: controls with no named owner. Evidence for them is the first thing missing when the auditor arrives.

    2. Map each control to its requirement

    Tie each artifact to the specific rule or contract clause it satisfies. One record often serves several requirements, so map once and reuse it.

    Where it goes wrong: collecting by framework instead of by control, which produces duplicate requests to the same people.

    3. Collect from the authoritative system

    Pull the record from the system that generated it, not from an email summary of it. Direct exports carry timestamps and system names that retyped versions lose.

    Where it goes wrong: screenshots with no date, no user and no scope. If you capture one, include the date and the system in the frame or the file name.

    4. Check that the population is complete

    If an auditor samples from a list of users, devices or changes, the list has to be whole. Confirm that the export covers every in-scope item and the full period.

    Where it goes wrong: a report filtered to the current month presented as if it covered a year.

    5. Review before you submit

    Have someone other than the collector check each artifact for date, source, scope and mapping. Strong programs also keep a record of this monitoring, as ReliabilityFirst recommends.

    6. Store it in a governed repository

    Use stable file naming, version control and permissions limiting who can edit or delete. Evidence that anyone can overwrite is weak evidence. Our IT documentation checklist shows how we approach documentation ownership for small businesses.

    7. Repeat on the control's schedule

    A quarterly control needs four dated records a year, not one. This is why evidence collection is a routine, not a project.

    What to automate and what needs a person

    Repeatable technical records are good candidates for automation: configuration exports, backup reports, patch status, and logs. They arrive on schedule, carry system timestamps and need no retyping.

    People still need to handle exceptions, approvals, risk acceptance, compensating controls, physical security, vendor decisions and judgments about whether the record set is complete, as AuditSuisse outlines. A tool can export a list of unpatched machines. Someone with authority decides whether to accept the risk and signs it.

    Walkthroughs are the human side of evidence. If you tag equipment or rooms with QR codes so a walkthrough can point to the right records, a secure QR code checklist covers keeping those codes trustworthy.

    Change records and logs

    Two evidence types come up in nearly every audit. The first is proof that changes to systems were approved and tested; a written change management policy creates that record as a by-product. The second is logs. How long you keep them depends on your obligations, and our log retention guide covers the practical side for small businesses.

    Organizing and retaining evidence

    Retention is not one number. A sound approach is risk- and obligation-based: group evidence types into retention classes, keep what you need for audits, investigations, contracts, legal holds and regulatory minimums, and log authorized destruction.

    Some rules do set fixed periods. For example, accountants auditing public-company financial statements must retain audit records for seven years under SEC rules. That rule is aimed at auditors of issuers, so most small businesses will not be directly bound by it. Your own period comes from your regulator, your contracts and your insurer. A lawyer should confirm it for your situation.

    GLBA risk assessment: what to document

    If you are a financial firm, or another business the FTC treats as a financial institution, the Gramm-Leach-Bliley Act (GLBA) Safeguards Rule applies. 16 CFR 314.4(b) requires your information security program to rest on a written risk assessment. That assessment must:

    • identify reasonably foreseeable internal and external risks to the security, confidentiality and integrity of customer information;
    • include criteria for evaluating and categorizing those risks;
    • assess whether your existing safeguards are sufficient to control them.

    The bank regulators' examination procedures, written for banks but useful as a model, expect supporting documents such as asset inventories, threat and vulnerability analyses, control evaluations, risk registers, remediation plans and risk assessment reports. Guidance for auto dealers notes that a defensible record also keeps the criteria for assessing safeguard adequacy and the requirements describing how risks will be mitigated or accepted.

    Evidence for testing and monitoring

    The Safeguards Rule also requires regular testing or monitoring. According to NADA's summary of the rule, without continuous monitoring you need annual penetration testing and vulnerability assessments at least every six months. Keep each report, dated, with the remediation tickets that followed.

    Breach notification records

    Since May 13, 2024, FTC-covered institutions must report certain events to the FTC within 30 days of discovery: unauthorized acquisition of unencrypted customer information involving at least 500 consumers. Your evidence file should show who decides, how you detect and how you document the decision.

    Investment advisers and broker-dealers also fall under the SEC's amended Regulation S-P. Goodwin reports compliance dates of December 3, 2025 for large institutions and June 3, 2026 for others. The amendments call for written incident response procedures, customer notification processes, service provider oversight and records showing compliance. Service providers must notify the institution within 72 hours of detecting a breach. For a step-by-step build of the Safeguards program, see our FTC Safeguards Rule roadmap.

    A worked example: one control, start to finish

    Take multi-factor authentication, a control that appears in almost every framework and questionnaire.

    1. Control register entry: MFA is enforced for all staff on email and remote access. Owner: IT lead. Frequency: reviewed quarterly.
    2. Requirement mapping: the written security program and the access control requirement in your risk assessment.
    3. Artifact: an export from the identity system listing every user and their MFA status, with the export date.
    4. Completeness check: the user count matches the HR roster for that date.
    5. Review: a second person confirms the export, notes two exceptions and records who approved each, with a reason and an end date.
    6. Storage: the file goes into the evidence repository under a consistent name, such as the control ID plus the quarter.

    Four quarters of that gives an auditor a dated trail, and it took minutes each time because the routine was set up in advance.

    Where this goes wrong for small businesses

    The usual failures are mundane. The person who knew where the records lived has left. Logs roll over before anyone saved them. A policy exists but nobody can show it was in force during the audit period. Backup reports exist only in an inbox. Each is a documentation problem more than a security problem, and each is avoided by a routine that runs whether or not an audit is coming.

    For manufacturers, customer security questionnaires add another stream of requests. Our guide to scaling vendor security questionnaires shows how to answer them from one evidence set instead of starting fresh each time.

    Where Collett Systems fits

    We provide managed IT for small and mid-sized businesses in West Bend and Southeastern Wisconsin, with a fixed cost per user, 24/7 monitoring, proactive support, security management, backup and disaster recovery, and compliance documentation. Audit readiness is part of the stack for every client, not an add-on.

    The starting point is the IT & Security Assessment, which gives you a documented picture of your environment and gaps. Our cybersecurity risk assessment work is the natural base for the written risk assessment the Safeguards Rule expects. If you run your own IT staff, co-managed IT lets us carry the monitoring and documentation load alongside them. Explore managed IT services for the full picture.

    Collett Systems LLC

    Book the IT & Security Assessment to see where your evidence stands today.

    Our perspective

    Most compliance pain comes from treating evidence as something you assemble when the auditor calls. By then the logs have rolled over and the person who set up the control has moved on.

    We run IT as infrastructure that documents itself. Monitoring runs around the clock, backups report on schedule, and patching and changes leave records. When the same team owns the stack, evidence is a by-product of operations instead of a separate chore.

    That is also why we price per user with a standardized, fully loaded stack. Audit readiness, strategic planning and automation improvements are included, so a request for proof never turns into a surprise invoice. Owners tell us they want peace of mind, and a dated record is what delivers it.

    Our advice to any Wisconsin business: pick a handful of controls, name an owner for each, and start collecting this quarter. You will be ahead of most of your peers by the next audit.

    Dustin Collett

    FAQ

    What are the three major steps in evidence collection?

    Plan, collect and review. Plan by listing controls and the artifact that proves each. Collect directly from the system that produced the record. Review for date, source, scope and completeness before storing or submitting it.

    How long should we keep compliance evidence?

    There is no single answer. Keep each type for the longest period your regulator, contracts, insurer or legal holds require, and log authorized destruction. Ask your attorney to confirm the periods that apply to your business.

    Is a screenshot good enough as evidence?

    It can be, if it shows the date, the system and the scope, and the population is complete. A system-generated export is usually stronger because it carries timestamps and source details automatically.

    Do we need a GLBA risk assessment if we are a small firm?

    If the Safeguards Rule covers your business, the program must be based on a written risk assessment regardless of size. It should identify foreseeable risks, set criteria for categorizing them and assess whether current safeguards are sufficient.

    Sources