Write clear, concise, audience-fit Day 3 responses.
Clear writing on CFE Day 3 means the intended reader can understand the issue, analysis, implication, and recommendation quickly. Concision matters because Day 3 is time-constrained, but concision does not mean writing fragments or unsupported conclusions. It means using only the words needed to answer the case request.
The goal is professional usefulness. A board member, partner, manager, owner, or client should be able to act on the answer without guessing what the candidate meant.
This lesson focuses on response clarity, concise structure, audience fit, and plain-language professional communication. It is not about cosmetic style. It is about making the analysis easier to mark and more useful to the reader.
| Writing quality | What it looks like |
|---|---|
| Clear issue | The first sentence shows what problem is being addressed. |
| Relevant analysis | Case facts are linked to the rule, calculation, risk, or decision criterion. |
| Stated implication | The response explains why the analysis matters. |
| Direct recommendation | The answer says what should be done. |
| Audience fit | Technical detail and tone match the reader and purpose. |
| Concision | The response avoids filler, repeated facts, and unnecessary background. |
A useful Day 3 paragraph often follows this pattern:
| Move | Function |
|---|---|
| Issue | State the problem or decision. |
| Analysis | Use the relevant rule, calculation, evidence, or criteria. |
| Implication | Explain the effect on reporting, cash, risk, compliance, control, or decision making. |
| Recommendation | State the action, correction, procedure, disclosure, or follow-up. |
| Caveat | Add only if an assumption or missing fact changes the conclusion. |
This is not a mandatory template. It is a discipline for avoiding vague writing. If the paragraph has no implication or recommendation, it may read like notes. If it has a recommendation without analysis, it may read like a guess.
Audience affects how much technical detail belongs in the answer. A partner or controller may need concise technical reasoning. A board may need risk, governance, and decision consequences. An owner-manager may need practical cash and tax implications. A client may need plain-language advice and next steps.
| Reader | Better emphasis |
|---|---|
| Board or audit committee | Governance, risk, accountability, approvals, and monitoring. |
| Owner-manager | Cash, tax, feasibility, controls, and practical consequences. |
| Controller or CFO | Reporting treatment, calculations, documentation, and process changes. |
| Assurance partner | Risk, evidence, materiality, procedures, and reporting implications. |
| Tax advisor or manager | Compliance, documentation, filing position, exposure, and follow-up. |
Audience fit does not mean changing the technical conclusion. It means choosing the explanation that helps the reader use the conclusion.
A concise answer still needs evidence. The most efficient writing links one fact to one consequence. For example:
| Weak sentence | Stronger sentence |
|---|---|
| “There are cash flow issues.” | “The expansion creates a $40,000 cash shortfall before customer collections arrive, so management should secure short-term financing before committing.” |
| “The control is weak.” | “The same employee approves purchases and records invoices, so unauthorized purchases could be processed without review.” |
| “The tax treatment should be considered.” | “The shareholder loan terms should be reviewed because an imputed benefit or repayment issue could create personal tax exposure.” |
| “Management should be careful.” | “Management should disclose the conflict and have disinterested directors approve the supplier contract.” |
The stronger sentences are not necessarily longer; they are more specific.
Common vague endings include “more analysis is needed,” “management should consider,” “this could be an issue,” and “the company should be careful.” These phrases may be acceptable as part of a caveat, but they are weak as conclusions.
Replace them with action:
| Vague ending | Actionable ending |
|---|---|
| “More analysis is needed.” | “Obtain the missing lease terms before signing because the cancellation clause could change the cost comparison.” |
| “Management should consider the risks.” | “Delay the launch until privacy controls and vendor due diligence are complete.” |
| “This may not be appropriate.” | “Adjust revenue because control has not transferred under the stated delivery terms.” |
| “The client should be careful.” | “Disclose the related-party relationship and obtain approval from independent directors.” |
Professional writing should be calm and precise. Avoid alarmist wording unless the facts support serious risk. Avoid casual phrasing, sarcasm, and overconfidence. When facts are incomplete, state the assumption and its effect. When the issue is serious, be direct without exaggerating.
The answer should sound like professional advice, not a study note. “Because the lender relies on the forecast, omitting the likely covenant breach would be misleading” is stronger than “This is bad ethics.” It identifies the user, the problem, and the reason.
Use this review checklist before moving to the next issue:
This checklist should take seconds, not minutes. Its purpose is to catch vague conclusions and unsupported assertions before they repeat across the case.
| Pitfall | Correction |
|---|---|
| Repeating case facts without explaining them. | Link each fact to the conclusion it supports. |
| Writing technically correct but unreadable paragraphs. | Use shorter sentences and state the implication plainly. |
| Overexplaining basic rules. | Include only the rule detail needed to answer the case request. |
| Using vague recommendations. | State the action, owner, condition, or follow-up. |
| Ignoring the reader. | Match the level of technical detail to the audience named in the case. |