Use exhibits, source documents, and evidence trails to support Day 2 analysis.
Exhibits are not attachments to be copied into the answer. They are evidence sources. A Day 2 exhibit may contain the fact that identifies an issue, the input for a calculation, the contradiction that changes a risk assessment, or the source document that supports a recommendation. Strong responses interpret exhibits through the declared role.
Exhibit work is especially important because the long case may separate narrative facts from schedules, contracts, emails, reports, forecasts, or management data. The candidate must connect them.
CFE Day 2 often uses exhibits to test whether the candidate can find and use evidence under time pressure. The exhibit may be relevant to role depth, a common issue, or a limitation on the conclusion. The task is not simply to mention that the exhibit exists. The task is to determine what the exhibit changes.
An assurance role may use exhibits to identify risk, procedure design, evidence quality, or reporting implications. A finance role may use them for cash flows, valuation inputs, covenant analysis, or sensitivity. A performance-management role may use them for metrics, costs, pricing, process gaps, or incentive effects. The same exhibit can support different conclusions depending on the role.
A useful exhibit-reading sequence is:
This sequence helps prevent two common errors: copying too much data and missing the inconsistency that matters.
| Exhibit type | What to look for | Possible role use |
|---|---|---|
| Financial schedule | Trends, unusual amounts, margins, working capital, cash flow, debt. | Finance, reporting, audit risk, performance analysis. |
| Forecast | Assumptions, growth rates, sensitivity, missing costs, financing needs. | Valuation, capital budgeting, going concern, decision support. |
| Contract excerpt | Obligations, rights, timing, penalties, renewal terms, related parties. | Revenue, leases, tax, assurance procedures, transaction risk. |
| Email or memo | Management intent, bias, decision pressure, approval process. | Governance, ethics, audit evidence, professional skepticism. |
| Control description | Approval gaps, segregation, monitoring, IT reliance, documentation. | Assurance, risk, data reliability, implementation advice. |
An evidence trail connects assertion, source, analysis, and conclusion. If management asserts that a forecast is reliable, the evidence trail might include historical performance, signed contracts, market data, capacity analysis, and sensitivity testing. If management asserts that a control is operating effectively, the evidence trail might include policy documents, samples, approval records, system logs, or exception reports.
The response should not accept management assertion when the case gives reason to question it. It should state what evidence supports the conclusion or what additional evidence is needed before relying on it.
For example: “Management’s forecast assumes a 20 percent sales increase, but the exhibit shows customer churn has risen for three consecutive quarters. The recommendation should therefore be qualified until management supports the growth assumption with retention evidence or signed customer commitments.”
Inconsistencies deserve attention because they affect reliability. A narrative may say sales are growing, while an exhibit shows margin erosion. Management may say a control is strong, while a process exhibit shows no independent review. A forecast may assume stable costs, while the supplier contract shows a price escalation clause.
When an inconsistency appears, write it directly:
This is stronger than choosing one source and ignoring the other.
Do not paste an exhibit table into the conclusion. Instead, convert the exhibit into a role-specific implication. A finance conclusion should not merely list forecast figures; it should explain whether the figures support investment, financing, valuation, or risk advice. An assurance conclusion should not merely state that a schedule exists; it should explain what risk, procedure, or reporting point follows.
Good exhibit language often uses verbs such as indicates, supports, contradicts, limits, increases, reduces, or qualifies. These verbs force interpretation.
| Pitfall | Why it weakens the response | Better approach |
|---|---|---|
| Copying exhibit data into the answer. | The response describes evidence without analyzing it. | State the exhibit implication for the role issue. |
| Ignoring source reliability. | The conclusion may rely on weak evidence. | Identify whether evidence is internal, external, complete, current, and corroborated. |
| Missing contradictions. | The response may accept a flawed assumption. | Compare narrative claims with exhibit data. |
| Using every exhibit equally. | Time is lost on low-value details. | Prioritize exhibits that affect the role conclusion. |