Allocate Day 2 depth and time to issues that matter most for the declared role.
Depth allocation is the decision about how much time and analysis each issue deserves. In CFE Day 2, depth is not created by writing more words on every topic. It is created by giving the declared role enough supported analysis on the issues that matter most.
The long case creates time pressure by design. Candidates must decide which issues need full development, which issues need concise treatment, and which issues should be acknowledged only as assumptions, limitations, or follow-up items. This is a professional judgment task, not merely a writing-speed problem.
Day 2 depth depends on role significance. A finance role may require a well-supported capital budgeting recommendation. An assurance role may require a risk assessment, procedures, evidence evaluation, or reporting conclusion. A performance-management role may require operational analysis, metrics, incentives, controls, and implementation advice. The role determines where depth is expected.
Common issues still matter, but they should not consume the time needed for role depth. A candidate can weaken a response by overbuilding a minor common issue while underdeveloping the assigned role.
Use a simple ranking before drafting:
| Rank | Characteristics | Treatment |
|---|---|---|
| Major role issue | Directly tied to the assignment, significant, evidence-rich, and decision-changing. | Full issue-analysis-recommendation treatment. |
| Moderate issue | Relevant to the role but narrower, less significant, or partly constrained by available evidence. | Concise analysis with implication and recommendation. |
| Minor issue | Contextual, follow-up oriented, or only indirectly connected to the role. | Brief note, caveat, assumption, or monitoring point. |
| Background | Useful for understanding the case but not decision-changing. | Use only if needed to explain another point. |
This ranking is not a rigid scoring system. It is a planning tool that prevents equal treatment of unequal issues.
An issue usually deserves depth when it affects the required deliverable, the user’s decision, the reliability of the conclusion, or a material risk. Significance can come from quantitative size, but it can also come from qualitative importance.
For example, a dollar amount may be modest but still significant if it reveals a control breakdown, violates a covenant, creates a tax exposure, affects independence, or changes whether management data can be trusted. Conversely, a large number may not require extensive treatment if the role does not ask for that analysis and the fact only provides context.
Use these significance tests:
The more tests the issue meets, the more depth it likely deserves.
Some issues require calculations. Others require qualitative reasoning. Many require both. The allocation decision is not “numbers or words.” It is “what evidence is needed to support the conclusion?”
A financing recommendation may require cash-flow analysis, covenant assessment, cost of capital, and qualitative discussion of lender expectations. An assurance recommendation may require risk identification, procedure design, and evidence evaluation. A performance-management recommendation may require metrics, root-cause analysis, and behavioral implications.
If a calculation is needed, the response should set it up clearly, use relevant inputs, state assumptions, and interpret the result. If qualitative judgment is needed, the response should connect facts to risk, feasibility, ethics, stakeholders, or implementation.
Time pressure becomes dangerous when the candidate keeps writing because an issue feels familiar. Familiarity is not the same as significance. A candidate with strong technical knowledge may spend too long on a comfortable issue while leaving the role’s main requirement thin.
A useful time habit is to define the depth target before writing:
During review, check whether the response length matches issue significance. If a minor issue is longer than the main issue, the allocation is probably wrong.
| Pitfall | Why it weakens the response | Better approach |
|---|---|---|
| Writing every issue at the same length. | Major issues are underdeveloped and minor issues are overdeveloped. | Rank issues before drafting. |
| Letting technical comfort drive time allocation. | Familiar topics may displace role-critical issues. | Allocate time by role significance, not preference. |
| Treating quantitative work as depth by itself. | A calculation without interpretation does not support advice. | Explain what the result means and how it affects the recommendation. |
| Skipping moderate issues entirely. | The response may look incomplete. | Address them concisely as implications or caveats. |