Legal analysis is organised when each issue leads the reader through a conclusion, governing rule, authoritative support, application to material facts, counterargument, and result[cite: 1]. Document-level structure orders the issues; section-level structure proves one proposition at a time; paragraph-level structure keeps every sentence tied to that proof[cite: 1].
Choose IRAC or CRAC according to the reader
IRAC begins with the issue, then rule, application, and conclusion[cite: 1]. CRAC leads with the conclusion, followed by rule, application, and a closing conclusion[cite: 1]. A reader who needs a decision quickly often benefits from CRAC; an examination or prescribed format may require another sequence[cite: 1].
The labels are tools, not content[cite: 1]. The application must do the analytical work[cite: 1]. A draft that spends three pages summarising law and one sentence applying it has structure in appearance only[cite: 1].
Build an issue tree before writing prose
List the ultimate question, threshold issues, elements, exceptions, factual dependencies, adverse points, and remedies[cite: 1]. Place threshold questions first when they may dispose of the matter[cite: 1]. Separate issues with different standards or sources[cite: 1].
- Ultimate conclusion: the answer or position the document must support[cite: 1].
- Controlling questions: the legal findings required to reach that result[cite: 1].
- Sub-propositions: the rules, facts, and comparisons that prove each finding[cite: 1].
- Dependencies: issues that must be resolved before another can arise[cite: 1].
- Consequences: the remedy, risk, or next action flowing from each answer[cite: 1].
Use headings as propositions
A heading should tell the reader why the section matters[cite: 1]. “Limitation” labels a topic[cite: 1]. A proposition heading states the position and key reason[cite: 1]. Ensure the heading does not overstate what the section can prove[cite: 1].
Read only the headings[cite: 1]. They should reveal the argument's order and destination[cite: 1]. Then read the first sentence under each heading[cite: 1]. It should deliver the promised conclusion or roadmap[cite: 1].
State the rule with hierarchy and limits
Begin with current, controlling authority[cite: 1]. Explain the test and genuine exception in language faithful to the source[cite: 1]. Persuasive authority and commentary can help, but identify their role[cite: 1]. Do not turn a fact-specific holding into a universal rule[cite: 1].
The Supreme Court of India's 2025 Handbook for Law Clerks provides official guidance on brief preparation, research, and writing[cite: 1]. Its requirement that clerks distinguish the status of facts and focus on relevant material illustrates the inputs a sound application section needs[cite: 1].
Make the application compare, not repeat
Application explains why the rule produces this result on these facts[cite: 1]. Identify the decisive legal criterion, the relevant record fact, and the connection[cite: 1]. Use precedent through analogy and distinction: compare facts and reasoning, not merely outcomes[cite: 1].
| Component | Question |
|---|---|
| Proposition | What conclusion does this paragraph prove? |
| Authority | What source supplies the criterion? |
| Fact | What record detail activates the criterion? |
| Reasoning | Why does that comparison support the conclusion? |
| Consequence | What follows for the issue or relief? |
Handle counterarguments where they arise
Place a counterargument beside the proposition it challenges rather than collecting every adverse point at the end[cite: 1]. State the strongest version fairly, then answer with the correct rule, factual distinction, authority weight, procedural limit, or missing element[cite: 1].
If the adverse point changes the conclusion, revise the answer and describe the uncertainty[cite: 1]. Analysis is not advocacy when it suppresses a material risk[cite: 1].
Use transitions to show logical relationships
A transition should explain whether the next paragraph adds a reason, provides an example, distinguishes an authority, concedes a point, or states a consequence[cite: 1]. Avoid mechanical connectors that hide a missing relationship[cite: 1].
The legal drafting overview places issue analysis within the broader workflow of instructions, structure, language, and review[cite: 1]. The appellate briefs guide shows how standard of review and procedural posture reshape the same analytical method[cite: 1]. For overall litigation structure, see the litigation process[cite: 1].
Organise advisory analysis around decisions
A client opinion should not imitate a brief if the client needs options[cite: 1]. Lead with the answer, assumptions, and confidence[cite: 1]. Organise the body around legal risks and choices, then assign practical consequences, owners, or next steps[cite: 1]. Keep unresolved factual questions visible[cite: 1]. Reviewing expert legal drafting services can refine complex multi-issue opinions[cite: 1].
Audit at document, section, and paragraph level
- Document: issues appear in a logical dependency order and lead to the requested outcome[cite: 1].
- Section: each heading states a proposition supported by rule and application[cite: 1].
- Paragraph: each paragraph performs one analytical job[cite: 1].
- Sentence: each sentence advances, supports, qualifies, or connects the proposition[cite: 1].
- Source: each legal and factual claim can be verified[cite: 1].
- Conclusion: each conclusion states the consequence without repeating the section[cite: 1].
Finish by comparing the short answer, headings, section conclusions, and requested relief[cite: 1]. If they do not tell the same story, the problem is organisation rather than wording[cite: 1].