Item 308(a) sets out what the annual report must carry: a statement of management's responsibility for establishing and maintaining adequate internal control over financial reporting, identification of the framework used, management's assessment of effectiveness as of the end of the most recent fiscal year, and disclosure of any material weakness. It then closes off the evasion the rest of the item would otherwise invite: "Management is not permitted to conclude that the registrant's internal control over financial reporting is effective if there are one or more material weaknesses." There is no partial verdict available, and no threshold below which a known weakness can be carried quietly.
Instruction 2 is where an AI-assisted control becomes a documentation problem. "The registrant must maintain evidential matter, including documentation, to provide reasonable support for management's assessment of the effectiveness of the registrant's internal control over financial reporting." For a control a person operates, the supporting matter is largely a by-product of operating it — the reviewed schedule, the initialled exception. For a control a model operates, the by-product is a result with no visible derivation, and the support has to be constructed deliberately: which model version was in force, how it was configured and prompted, on what basis items were sampled, and how exceptions were resolved. COSO's 2026 paper on internal control over generative AI reaches the same list from the control side, describing the evidence expectations that follow once management depends on an AI-produced output; here they are the practical content of a filing requirement.
The item is also the point at which management's file meets somebody else's judgement. What Instruction 2 obliges the registrant to hold is what an auditor will later have to reach a conclusion from — see evidence sufficiency for AI controls, which states the problem from the other side of the table. The two are not the same duty and neither discharges the other: a registrant whose file is thin has failed Instruction 2 whether or not anyone has yet tried to audit it.
The usable test is self-sufficiency. Evidential matter provides reasonable support if it supports the assessment without recourse to the person who did the work, because that person may be unavailable, may have moved on, and in any event is not what the instruction asks for. Applied to AI-assisted controls this is unforgiving: a great deal of what finance functions know about their tools lives in the head of the analyst who configured them. Writing it down is most of the compliance, and it is the same discipline the year-end evaluation itself depends on — see an AI tool inside a control you must evaluate.