How to Use IRAC to Answer a Law School Problem Question
IRAC is useful because it forces a law student to do four different jobs in a visible order: identify the Issue, state the relevant Rule, Apply that rule to the facts, and reach a Conclusion. The framework does not create the legal analysis for you. It helps you show the analysis you have already built from the problem and the authorities.
Treat IRAC as a flexible writing framework, not as a universal University of the Punjab marking formula. Teachers may prefer a different structure, may combine stages, or may expect several linked IRACs inside one answer. Follow the instructions for the actual course and assessment. The value of IRAC is that it makes a common weakness easy to diagnose: a student may know the rule but never apply it, or may jump to a conclusion without showing why the facts matter.
I: Turn the story into a legal issue
A problem question usually gives you a story. Your first task is to convert that story into a legal question. A useful issue is specific enough to guide the rule and application. "Is Ali liable?" is often too broad. "Whether the notice requirement was satisfied when the message was sent after the stated deadline" is more useful because it identifies the rule and the fact that needs analysis.
Do not copy the whole problem into the issue sentence. Pick the legally significant uncertainty. If the facts raise three separate legal questions, you may need three smaller IRACs rather than one oversized answer. The issue should help the reader predict what the next paragraph will resolve.
R: State the rule at the level the facts require
The rule section should give the legal standard you need to analyze the issue, supported by the authorities required for the course. State the general rule, then any element, exception, definition, or limitation that becomes important on these facts. Do not turn the rule section into a textbook chapter if only one part of the doctrine is in dispute.
This is where accurate research matters. If the rule comes from legislation, check the current provision. If a case supplies the proposition, make sure the judgment supports the sentence you attribute to it. PLC's guide to citing Pakistani cases and statutes can help you keep the authority identifiable while you focus on the reasoning.
A: Make the application the longest thinking part
Application is where many problem answers either become analytical or remain descriptive. Take the words of the rule and connect them to the facts. Do not write, "The rule applies to the facts, therefore the claimant will succeed." Explain which fact supports which part of the rule, which fact points the other way, and what interpretation would be needed for each argument.
A useful application sentence often has three components: a fact, a legal significance, and a comparison or inference. For example: "The demand was sent in writing, which supports the notice requirement; however, it was sent after the contractual date, so the timing condition remains disputed." The sentence does not merely repeat the fact. It explains why the fact matters under the rule.
Where the facts support both sides, show both. Problem questions are often designed to contain uncertainty. A strong answer can say that one argument is stronger while still explaining the competing interpretation. Do not manufacture a counterargument when none reasonably arises, but do not hide an awkward fact just because it weakens the conclusion you prefer.
C: Conclude at the same level of certainty as the analysis
The conclusion should answer the issue you framed. It can be brief when the application has done the work. Avoid writing "clearly" or "definitely" unless the law and facts truly justify that level of certainty. A qualified conclusion such as "On these facts, the stronger argument is..." may be more accurate when the result depends on interpretation.
The conclusion is not a new section for extra rules or facts. If a point is important enough to change the result, it belongs in the rule or application before the conclusion.
A worked IRAC with a fictional rule
The following example uses a deliberately fictional rule so that the structure can be practiced without presenting made-up law as Pakistani law. Assume the fictional Student Equipment Rule says: "A borrower who keeps college equipment after a written return demand, without a reasonable excuse, must pay the stated late charge." The facts say that Sana borrowed a recorder, received a written demand on Monday, and returned it on Thursday after a hospital visit on Tuesday and Wednesday.
Issue: Whether Sana must pay the late charge when she kept the recorder after the written demand but says the hospital visit was a reasonable excuse.
Rule: Under the fictional rule, the charge applies when a borrower keeps equipment after a written return demand unless there is a reasonable excuse.
Application: The written Monday demand and Thursday return satisfy the first part of the rule because Sana retained the recorder after receiving the demand. Her hospital visit, however, creates the central question under the exception. If the visit made return impracticable during the relevant period, it supports a reasonable-excuse argument. The facts do not say whether she could have arranged a return on Monday before the visit or through another person, so both the duration and practicality of the excuse need analysis.
Conclusion: Sana may avoid the charge if the hospital visit falls within the rule's reasonable-excuse exception, but the result depends on facts about whether return was realistically possible after the demand.
Notice what the example does not do. It does not add facts about the hospital, invent a definition of "reasonable," or cite an authority that does not exist. In a real answer, the applicable statute, case law, course materials, and teacher's instructions would control the rule.
Use several small IRACs when the problem has several issues
A long problem may require an issue map before drafting. Write each disputed element or legal question on a separate line. Then decide which issues deserve full analysis and which can be resolved briefly. If one issue depends on the outcome of another, order them accordingly.
This prevents a common structural problem: one large Rule section followed by one large Application section covering several doctrines. Smaller units let the reader see which rule is being applied to which facts. The headings do not need to say "IRAC" unless your teacher wants that format; the logical sequence can remain visible without mechanical labels.
Do not confuse application with fact repetition
After drafting, highlight every sentence in the application that merely repeats a fact. Beside it, add the question "So what?" If the next sentence explains the legal significance, the fact belongs. If nothing changes when the fact is removed, it may be background rather than analysis.
Then highlight the words from the rule that you actually apply. If the rule has four elements but the answer discusses only two, decide whether the other elements are undisputed and can be dealt with briefly, or whether they were accidentally ignored. This rule-to-fact check is one of the fastest ways to see whether the IRAC is complete.
Use authority inside the analysis, not as decoration
A problem answer is stronger when authority is connected to the proposition it supports. If a case helps explain how a court interpreted a term or treated a similar fact, state that relevance. Do not attach several case names to a sentence simply to make the paragraph look researched.
If the assessment allows or requires citations, use the required style and pinpoint references where appropriate. If it is a timed examination with different citation expectations, follow the teacher's instructions. IRAC does not determine citation format.
Practice IRAC with past papers after checking relevance
Once you understand the framework, practice it on questions that match the current course. PLC's past-paper practice guide explains why an older paper should first be checked against the current syllabus and assessment context. For an IRAC drill, you do not always need to write the full answer: spend five minutes identifying issues and mapping rule-to-fact links, then compare the map with your notes.
When you review the attempt, diagnose the stage that failed. A vague issue suggests problem-reading needs work. An inaccurate rule suggests research or recall needs work. A thin application suggests you did not connect facts to legal criteria. An overconfident conclusion may show that the qualification in the application was ignored.
Run a four-question IRAC self-check
Before you finish, ask four questions in order. Issue: can I state the precise legal question without retelling the whole story? Rule: does every rule sentence come from an authority or course source I can identify? Application: have I explained why the important facts help or hurt each side under that rule? Conclusion: does my level of certainty match the analysis rather than exceed it?
If one answer is weak, revise that stage instead of rewriting the entire response. This turns IRAC into a diagnostic tool rather than a rigid template.
Keep the framework invisible enough to sound natural
IRAC is a scaffold. The finished answer should still read like legal analysis rather than a form filled with labels. Start with a precise issue, give the rule the reader needs, spend real effort applying that rule to the facts, and conclude with the degree of certainty the analysis earns. If the teacher requires a different analytical structure, use it.
The framework is most valuable when it exposes what is missing. If you cannot write the Issue, you may not have understood the problem. If you cannot state the Rule accurately, you need the authority. If the Application is two sentences long, you may not have analyzed the facts. If the Conclusion is stronger than the reasoning, revise the claim. Used that way, IRAC is not a shortcut; it is a check on whether the legal thinking is actually visible.
