Skip to main content
Business LibreTexts

13: Introduction to IRAC Writing Structure

  • Page ID
    111041
  • \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \( \newcommand{\id}{\mathrm{id}}\) \( \newcommand{\Span}{\mathrm{span}}\)

    ( \newcommand{\kernel}{\mathrm{null}\,}\) \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\) \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\) \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\id}{\mathrm{id}}\)

    \( \newcommand{\Span}{\mathrm{span}}\)

    \( \newcommand{\kernel}{\mathrm{null}\,}\)

    \( \newcommand{\range}{\mathrm{range}\,}\)

    \( \newcommand{\RealPart}{\mathrm{Re}}\)

    \( \newcommand{\ImaginaryPart}{\mathrm{Im}}\)

    \( \newcommand{\Argument}{\mathrm{Arg}}\)

    \( \newcommand{\norm}[1]{\| #1 \|}\)

    \( \newcommand{\inner}[2]{\langle #1, #2 \rangle}\)

    \( \newcommand{\Span}{\mathrm{span}}\) \( \newcommand{\AA}{\unicode[.8,0]{x212B}}\)

    \( \newcommand{\vectorA}[1]{\vec{#1}}      % arrow\)

    \( \newcommand{\vectorAt}[1]{\vec{\text{#1}}}      % arrow\)

    \( \newcommand{\vectorB}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vectorC}[1]{\textbf{#1}} \)

    \( \newcommand{\vectorD}[1]{\overrightarrow{#1}} \)

    \( \newcommand{\vectorDt}[1]{\overrightarrow{\text{#1}}} \)

    \( \newcommand{\vectE}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash{\mathbf {#1}}}} \)

    \( \newcommand{\vecs}[1]{\overset { \scriptstyle \rightharpoonup} {\mathbf{#1}} } \)

    \( \newcommand{\vecd}[1]{\overset{-\!-\!\rightharpoonup}{\vphantom{a}\smash {#1}}} \)

    \(\newcommand{\avec}{\mathbf a}\) \(\newcommand{\bvec}{\mathbf b}\) \(\newcommand{\cvec}{\mathbf c}\) \(\newcommand{\dvec}{\mathbf d}\) \(\newcommand{\dtil}{\widetilde{\mathbf d}}\) \(\newcommand{\evec}{\mathbf e}\) \(\newcommand{\fvec}{\mathbf f}\) \(\newcommand{\nvec}{\mathbf n}\) \(\newcommand{\pvec}{\mathbf p}\) \(\newcommand{\qvec}{\mathbf q}\) \(\newcommand{\svec}{\mathbf s}\) \(\newcommand{\tvec}{\mathbf t}\) \(\newcommand{\uvec}{\mathbf u}\) \(\newcommand{\vvec}{\mathbf v}\) \(\newcommand{\wvec}{\mathbf w}\) \(\newcommand{\xvec}{\mathbf x}\) \(\newcommand{\yvec}{\mathbf y}\) \(\newcommand{\zvec}{\mathbf z}\) \(\newcommand{\rvec}{\mathbf r}\) \(\newcommand{\mvec}{\mathbf m}\) \(\newcommand{\zerovec}{\mathbf 0}\) \(\newcommand{\onevec}{\mathbf 1}\) \(\newcommand{\real}{\mathbb R}\) \(\newcommand{\twovec}[2]{\left[\begin{array}{r}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\ctwovec}[2]{\left[\begin{array}{c}#1 \\ #2 \end{array}\right]}\) \(\newcommand{\threevec}[3]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\cthreevec}[3]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \end{array}\right]}\) \(\newcommand{\fourvec}[4]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\cfourvec}[4]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \end{array}\right]}\) \(\newcommand{\fivevec}[5]{\left[\begin{array}{r}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\cfivevec}[5]{\left[\begin{array}{c}#1 \\ #2 \\ #3 \\ #4 \\ #5 \\ \end{array}\right]}\) \(\newcommand{\mattwo}[4]{\left[\begin{array}{rr}#1 \amp #2 \\ #3 \amp #4 \\ \end{array}\right]}\) \(\newcommand{\laspan}[1]{\text{Span}\{#1\}}\) \(\newcommand{\bcal}{\cal B}\) \(\newcommand{\ccal}{\cal C}\) \(\newcommand{\scal}{\cal S}\) \(\newcommand{\wcal}{\cal W}\) \(\newcommand{\ecal}{\cal E}\) \(\newcommand{\coords}[2]{\left\{#1\right\}_{#2}}\) \(\newcommand{\gray}[1]{\color{gray}{#1}}\) \(\newcommand{\lgray}[1]{\color{lightgray}{#1}}\) \(\newcommand{\rank}{\operatorname{rank}}\) \(\newcommand{\row}{\text{Row}}\) \(\newcommand{\col}{\text{Col}}\) \(\renewcommand{\row}{\text{Row}}\) \(\newcommand{\nul}{\text{Nul}}\) \(\newcommand{\var}{\text{Var}}\) \(\newcommand{\corr}{\text{corr}}\) \(\newcommand{\len}[1]{\left|#1\right|}\) \(\newcommand{\bbar}{\overline{\bvec}}\) \(\newcommand{\bhat}{\widehat{\bvec}}\) \(\newcommand{\bperp}{\bvec^\perp}\) \(\newcommand{\xhat}{\widehat{\xvec}}\) \(\newcommand{\vhat}{\widehat{\vvec}}\) \(\newcommand{\uhat}{\widehat{\uvec}}\) \(\newcommand{\what}{\widehat{\wvec}}\) \(\newcommand{\Sighat}{\widehat{\Sigma}}\) \(\newcommand{\lt}{<}\) \(\newcommand{\gt}{>}\) \(\newcommand{\amp}{&}\) \(\definecolor{fillinmathshade}{gray}{0.9}\)

    In Legal Research class, you learned to organize your research notes by issue, rather than by legal authority.  One reason is to make the transition into IRAC structure easier. Think of it as assembling a puzzle: You won’t get far just by staring at an individual puzzle piece (a case or a statute).  Your chances for success are much greater if you group related puzzle pieces together, such as all of the edge pieces or all the pieces that have part of a tree on them (all cases or statutes related to a particular legal standard).

     

    IRAC Components

    IRAC is a paragraph-writing structure or framework.  The letters stand for Issue, Rule, Application, Conclusion. There are other ways to analyze a legal problem. But IRAC is easy to learn and is very effective in improving your ability to "apply the law to the facts," the essence of sound legal analysis.

    The Issue.

    The first step of your analysis is to state the issue. The issue defines the problem. It sets out the dispute between the parties. The issue is based upon the legal sgtandard you are analyzing.

    The Rule(s).

    After laying out the issue, you need to set out the applicable rule(s). The reader needs to know what law will be applicable to the problem. Rules can be taken from statutes, cases, regulations or any other appropriate authorities.

    The Application.

    The law is only important as it applies to your client's factual situation. So after you set out the rule, you need to show how the rule applies to your client's situation. In your application section, you will take the facts of your case, and connect them to your rule, to say why each piece of the rule is met/not met, or weighs in favor of your client. 

    The Conclusion.

    In your conclusion, tie your points together to answer the question raised in the Issue. Show the reader where the application of the law to the facts has taken you. Your conclusion is short, but necessary.

    Why Should You Use IRAC?

    Using IRAC gives you the benefit of continuity and clarity of writing; helps to organize your discussion, focusing on the legal issues and rules, rather than authorities; and makes your writing consistent and predictable. More importantly, having a structure to follow can ease writer’s block and ensure you have a complete discussion of the client’s legal question.

     

    Example

    Another person’s perspective on why IRAC is a great writing structure. This podcast transcript discusses law school exams, but it’s equally applicable to the Discussion sections of a legal research memo.

     

    Planning Your IRAC

    Now that you know the IRAC components, the next step is to plan your IRAC for each Question Presented contained in your legal memo. Spending time planning what you are going to write before you begin drafting not only saves you time overall, but also makes it less likely you’ll omit an important part of your IRAC analysis. Here are the recommended steps for planning your IRAC:

     

    Step 1: Review the legal standard from your Question Presented.

    The legal standard should always drive the discussion, so it’s important to have that legal standard front and center as you begin planning your IRAC analysis. For your plan/outline, all you need is the “pure” legal standard from your Question Presented:

    The State must prove beyond a reasonable doubt that Wonka “intentionally damaged” a building with fire.

     

    Step 2: State your conclusion (the answer to the question you just wrote).

    Knowing what your conclusion will be helps you to select appropriate authorities to examine in your Rule component, since you want to include the authorities that support your conclusion. The same is true for the client’s facts that you will describe in your Application component.

     

    Step 3: Review your micro- and macro-synthesis relating to the Question Presented. Then, re-read the legal authorities.

    Take the time to re-familiarize yourself with the analysis you’ve completed so far. Sometimes you gain new knowledge or perspective when you review something. Think of all the times you’ve re-watched a movie or re-read a novel and said to yourself, “I never noticed [xxx] before!”

     

    Step 4: Outline your Rule component.

    Many times, people use an outline or bulleted list for this part of the planning. Start your list with the statute or other legal authority that contains the legal standard in your Question Presented. Then, list the court cases you found that interpreted/applied the legal standard. Make sure to include the cases that you determined were most similar to your client’s facts when you did your macro-synthesis, especially the cases that are consistent with your conclusion regarding the likely outcome for the client.

    Keep in mind that, when there are differences or conflicts between legal authorities of the same type, there are several rules of thumb for determining which legal authority is stronger:

    • If two statutes conflict, the more specific statute is stronger than the general statute
    • Supreme Court decisions are stronger than Court of Appeals decisions, regardless of the year of decision
    • If the decisions are from the same level of court (for example, two decisions from the Court of Appeals), the more recent decision is usually stronger

    Here's what an outline of the Rules for the “intentionally damaged” Question Presented might look like:

    Rules

    • Statute: Section 943.02(1)(a), Wis. Stat. (20xx): “Whoever … [b]y means of fire, intentionally damages any building of another without the other’s consent” is guilty of arson.
    • State v. Johnson, 349 Wis. 2d 894, 455 N.W.2d 338 (1988): explains how “intent” is proven. Facts are similar to Wonka’s facts
    • State v. Rodriguez, 548 Wis. 2d 293, 560 N.W.2d 81 (1993): clarifies what is needed to prove “intent.” Facts are mostly different from Wonka’s facts (do not use?)

    It can also be helpful to include the cases you determined were not similar to your client’s facts, or that had an outcome that is opposite to your conclusion about what the client’s income should be. Even if you don’t use that case in your IRAC, it’s a good idea to document your decision not to use it – this will come in handy later.

    You can also add some of the facts of the cases you include in your outline. Doing so will make it even easier to write the comparison of the caselaw facts and the client’s facts in your Application component.

     

    Step 5: Outline your Application component.

    This can be as simple as copying and pasting the legally significant facts you listed as part of your Question Presented. Even if it seems repetitive, it’s time well spent; it may even lead you to revise your Question Presented. Consider adding some of the contextual facts that you decided not to include in the Question Presented that are relevant to the legal standard.

     

    Here's what an outline of the Application for the “intentionally damaged” Question Presented might look like:

    Application/Client facts that support my conclusion

    • A fire occurred at the Chocolate Factory at 1 a.m. on January 30, [year], eight hours after the Factory had closed for the day,
    • No one was inside the Factory when the fire started,
    • Accelerants were used at several locations around the Factory,
    • Mary Worth, who lives across the street from the Factory, told police she saw a man dancing in front of her house, wearing camouflage clothing and shouting “Burn, baby, burn!” When she was shown a photo lineup by police, she identified Wonka identified as the man she saw.
    • The fire caused $1,000,000 in damage to the Factory.
    • Wonka is a co-owner of the Factory.
    • The Factory’s records are being audited for financial irregularities due to operating at a loss for three years. The audit noted that $1,000,000 is “missing from the books.”
    • Wonka owns a $1,000,000 Preferred Player’s Card from LaCasino.

    You can also include a separate list of facts that do not support your conclusion. Even though your IRAC analysis might not include those facts, they will come in handy later.

    Step 6: Repeat steps 1-5 for each Question Presented.

    Even if the Rules and Applications seem to overlap or be repetitive across Questions Presented, it’s important to outline each one separately. Remember, you’ll be writing a separate analysis of each Question Presented in the Discussion section of your legal research memo.

    Next, you’ll learn how to draft each IRAC component. Then, you’ll learn how to use the IRAC writing structure in the Discussion section of a legal research memorandum.


    13: Introduction to IRAC Writing Structure is shared under a CC BY 4.0 license and was authored, remixed, and/or curated by Beth R. Pless, J.D. (Northeast Wisconsin Technical College).