Common Case Facts, Entity Context, and Relevant-Information Filtering

Relevant-information filtering is the skill of turning a long Day 2 case into usable evidence. The case may contain company history, financial data, board concerns, management preferences, exhibits, stakeholder comments, operational problems, and technical cues. Not every fact deserves space in the final response.

A fact is relevant when it affects issue identification, analysis, calculation, risk assessment, recommendation, or the caveat attached to a conclusion. A fact is background when it helps understand the entity but does not change the assigned role’s advice.

Exam Focus

Day 2 tests depth, but depth does not mean copying more case facts. Depth means selecting the facts that matter and using them to support a conclusion. A response that repeats a long paragraph from the case may look detailed while still failing to analyze. A response that selects three decisive facts and explains their implications is usually stronger.

Fact filtering should be tied to the declared role. The same fact may be relevant in different ways depending on the role. A decline in gross margin may be a valuation input in a finance role, a performance issue in a performance-management role, a risk factor in an assurance role, or a tax-planning constraint in a tax role.

Background Versus Evidence

Use this distinction when reading the case:

The key is not the type of fact. The key is what the fact does in the analysis.

Filtering The Case

A practical filtering method is to tag facts during reading:

1. Role facts: facts that define the assignment, audience, responsibility, or deliverable.
2. Issue facts: facts that identify a problem, decision, risk, or opportunity.
3. Evidence facts: facts that support analysis or calculation.
4. Constraint facts: facts that limit or qualify the recommendation.
5. Background facts: facts that explain context but do not need detailed discussion.

This tagging method protects time. It also prevents a common Day 2 error: using the first interesting fact instead of the most decision-useful fact.

Missing Information

Relevant-information filtering also includes recognizing what is missing. A role-specific conclusion may be limited by absent data, unsupported assumptions, unavailable source documents, unclear management estimates, missing tax attributes, incomplete control information, or insufficient market evidence.

Missing information should not freeze the response. State the limitation, explain its effect, and identify the follow-up needed. For example: “The customer retention rate is not provided, so the valuation conclusion is sensitive to the revenue forecast. Before relying on the forecast, management should support the retention assumption with historical churn data or signed contracts.”

That wording is stronger than simply saying “more information is needed” because it identifies the missing fact and explains why it matters.

Using Exhibits As Fact Sources

Exhibits often carry the most important role evidence. They may contain financial statements, forecasts, contracts, schedules, emails, control descriptions, tax details, valuation data, or operational metrics. Do not copy the exhibit. Interpret it.

Ask three questions:

• What does this exhibit prove or suggest?
• Which role issue does it affect?
• Does it support, contradict, or qualify management’s narrative?

If the exhibit and narrative conflict, say so. Inconsistency is often more important than either fact alone because it affects reliability and professional judgment.

Generic Knowledge Versus Case Evidence

Technical knowledge is necessary, but Day 2 answers should not read like textbook summaries. The response must use the case facts. A financial reporting answer should explain how the case facts affect recognition, measurement, presentation, or disclosure. An assurance answer should identify the risk and the evidence needed. A finance answer should connect inputs and assumptions to the recommendation.

If a paragraph could be pasted into any case without changing the wording, it is probably too generic. Add case evidence or shorten it.

Common Pitfalls

Key Takeaways

• Relevant facts are facts that affect the role conclusion.
• Background facts should be used sparingly and only to explain context.
• Missing information should be communicated as a limitation, not as a vague request for more work.
• Exhibits should be interpreted and connected to the role issue.