How to write an IRR in AP Seminar

What You Need to Know

What an IRR is (and what it is not)

• IRR = Individual Research Report: a concise, evidence-based research report that helps your team answer the team research question by examining it through a specific lens (your “slice” of the problem).
• Your job is to inform and explain what high-quality research suggests, including multiple perspectives, patterns, tensions, and limits in the evidence.
• Not an argument essay:
  • You can arrive at a reasoned takeaway (“the research suggests…”) but you are not writing a persuasive “pick-a-side” piece.
  • You should avoid advocacy language unless you’re reporting that a source advocates.

Why it matters

• Your IRR is the foundation for the team’s later writing/presentation: it supplies credible evidence, key concepts, and nuanced understanding (including tradeoffs and gaps).
• Rubric-wise, you’re essentially being evaluated on how well you:
  • Understand the problem and set a research direction
  • Use and evaluate credible sources
  • Synthesize (connect) evidence across sources
  • Write clearly in an academic, objective tone
  • Cite correctly and consistently

The core “rule” of an A-level IRR

You don’t earn credit for having sources—you earn credit for what you do with them: select, evaluate, connect, and explain evidence to answer your lens-specific research focus.

Key vocabulary you must use correctly

• Research question: the overarching question your team is investigating.
• Lens: your angle (e.g., economic, ethical, environmental, political, social/cultural, technological, historical).
• Claim (in a report): a defensible statement about what research indicates (not a “vote”).
• Evidence: data, findings, expert analysis, documented cases.
• Synthesis: showing relationships among sources (agreement, disagreement, causes, tradeoffs, gaps).
• Credibility: authority, methodology, bias, relevance, currency.

Step-by-Step Breakdown

1) Lock your lens + sub-question (so you don’t write a vague IRR)

1. Copy the team research question at the top of your planning doc.
2. Choose one lens you can actually support with research.
3. Convert that lens into a focused sub-question you will answer.

Example

• Team question: To what extent should cities restrict short-term rentals?
• Your lens: economic
• Your IRR sub-question: How do short-term rentals affect housing prices, rental supply, and local economic activity, and what does the evidence say about policy tradeoffs?

Decision point: If your sub-question can’t be answered in ~5–7 pages of notes, it’s still too broad.

2) Gather sources strategically (quality + variety)

1. Start with 2–3 background sources to learn key terms and debates.
2. Then prioritize evidence-rich sources:
   • Peer-reviewed studies (when possible)
   • Government/IGO reports and datasets
   • Reputable research organizations
   • Major investigative journalism (for cases, not as your only evidence)
3. Collect sources representing multiple perspectives.

Minimum mindset: You’re building a mini literature review for your lens.

3) Annotate like you’re building paragraphs (not like you’re “reading”)

For each source, record:

• Claim/finding (1 sentence)
• Evidence type (study? dataset? expert analysis? case study?)
• Method/context (sample, timeframe, location, limitations)
• Why it matters to your lens
• How it connects to at least one other source (agree/disagree/expand)

4) Plan your IRR structure (theme-based, not source-by-source)

A strong IRR usually looks like:

• Intro (problem + research question + your lens + roadmap)
• Body sections by themes (2–4 sections)
  • Each section answers a “mini question” under your lens
  • Each section uses multiple sources in conversation
• Conclusion (what research suggests + implications + gaps/limits)

Avoid the “Source 1 paragraph, Source 2 paragraph…” structure. That kills synthesis.

5) Draft using a repeatable paragraph pattern

Use this pattern to force analysis and synthesis:

1. Topic sentence/mini-claim (what the research indicates about this theme)
2. Evidence from Source A (data/finding)
3. Evidence from Source B (supports/complicates/challenges)
4. Your synthesis (why they differ? context? assumptions? definitions?)
5. So what? (implication for the team question; tradeoff; limitation)

6) Cite as you write (don’t “fix citations later”)

• Use in-text citations every time you quote, paraphrase, or summarize.
• Maintain a running Works Cited/References list.
• Keep citation style consistent (your class may require MLA or APA—follow your teacher’s direction).

7) Revise for rubric-aligned moves

Revision priorities:

• Clarity of lens + relevance (does every paragraph tie back?)
• Synthesis density (are sources connected, not stacked?)
• Credibility evaluation (do you comment on quality/limits when it matters?)
• Line-by-line concision (remove filler summary)

Key Formulas, Rules & Facts

What your IRR must consistently do (high-yield rules)

Best-practice source mix (aim for balance)

“Synthesis verbs” (use these to write like a researcher)

• corroborates, complicates, qualifies, extends, contradicts, contextualizes, attributes, suggests, indicates, raises concerns about, is limited by, generalizes poorly to

Sentence templates that earn points

• Connecting sources: “While [Source A] finds __ in __ context, [Source B] reports __, suggesting that __ may depend on __.”
• Evaluating credibility: “Because [Source] relies on __ sample/timeframe/method, its conclusions are most applicable to __, but less conclusive for __.”
• Defining terms: “Researchers operationalize ‘’ differently; in this report, ‘’ refers to __, which matters because __.”

Examples & Applications

Example 1: Turning a broad question into a lens-driven IRR

Team question: Should school districts adopt AI proctoring software?

Weak focus: “AI proctoring is good/bad.”

Stronger IRR lens options:

• Ethical lens: privacy, consent, surveillance, fairness
• Technological lens: accuracy, false positives, system limitations
• Social lens: student stress, accessibility, differential impacts

Ethical-lens sub-question (good):

• “What ethical concerns do researchers and policy groups identify in AI proctoring (privacy, bias, due process), and what safeguards have evidence or precedent?”

Example 2: A synthesis-heavy mini-paragraph (what “good” looks like)

Theme: algorithmic bias / false flags

• Mini-claim: Research indicates that AI proctoring can disproportionately flag certain student behaviors as suspicious, raising fairness and due process concerns.
• Evidence: One study/report finds higher flag rates associated with movement, lighting, or assistive behaviors, implying the system may confuse accessibility needs with cheating.
• Contrast: Another source argues accuracy improves with controlled testing environments and clear appeals processes, suggesting context and implementation determine harm.
• Synthesis: Together, these sources imply the main risk is not only detection error but also procedural fairness—how institutions handle flags, transparency, and appeals.
• So what: For policy decisions, evidence supports pairing any adoption with disclosure, accommodations, and a documented appeals pathway.

(Notice: no “I think,” no one-source dump, and you explain why findings differ.)

Example 3: Writing a strong introduction (fast template)

Include 4 moves:

1. Context: 2–3 sentences on the problem’s significance
2. Team research question (verbatim)
3. Your lens + sub-focus
4. Roadmap (themes you’ll cover)

Intro template:

• “As __ increases/changes, __ has become a contested issue because . This report addresses the research question: ‘?’ Using a __ lens, it examines __, focusing on __ and __. It synthesizes findings on __, __, and __ to clarify key tradeoffs and gaps in current research.”

Example 4: A conclusion that’s not just summary

A strong IRR conclusion does three things:

• What research suggests (most defensible takeaway)
• Implications/tradeoffs (what decision-makers must weigh)
• Gaps/limits (what evidence is missing; what varies by context)

Conclusion punchlines that work:

• “Overall, the evidence suggests __; however, outcomes vary when __.”
• “A key tension is __ versus __, which indicates that __ policy will likely require __.”
• “Future research is needed on __, particularly in __ contexts.”

Common Mistakes & Traps

1. Writing an argument instead of a report

   • What goes wrong: You sound like you’re campaigning (“should/shouldn’t,” loaded language) rather than analyzing.
   • Why it’s wrong: The IRR is designed to inform the team with research-based understanding.
   • Fix: Use “research indicates/suggests,” emphasize tradeoffs and conditions.

2. One-paragraph-per-source (no synthesis)

   • What goes wrong: Your paper reads like annotated bibliography entries.
   • Why it’s wrong: It shows summary, not analysis of relationships.
   • Fix: Organize by themes, and require 2+ sources in most paragraphs/sections.

3. Quoting too much (or dropping quotes without commentary)

   • What goes wrong: Long quotes replace your explanation.
   • Why it’s wrong: You’re assessed on your reasoning, not how much you can copy.
   • Fix: Quote only when wording is crucial; otherwise paraphrase and then explain significance.

4. Using questionable credibility sources without acknowledging limits

   • What goes wrong: You rely on biased/unclear-method sources as if they’re definitive.
   • Why it’s wrong: IRR expects credibility awareness.
   • Fix: If a source has potential bias, either replace it or explicitly contextualize it (funding, methodology, purpose).

5. Not defining key terms or scope

   • What goes wrong: Your sources use different meanings (e.g., “harm,” “success,” “equity”), and you treat them as identical.
   • Why it’s wrong: Causes fake contradictions or messy reasoning.
   • Fix: Define 2–4 core terms and note when studies operationalize them differently.

6. Cherry-picking (only one side of the debate)

   • What goes wrong: You only include evidence that supports your preconception.
   • Why it’s wrong: A research report should represent the conversation.
   • Fix: Intentionally include the strongest credible counter-perspective and explain the tension.

7. Weak linkage to the team question

   • What goes wrong: Interesting facts, but unclear relevance.
   • Why it’s wrong: Your IRR must function as a building block for the team.
   • Fix: End sections with a “So what for our question?” sentence.

8. Citation sloppiness

   • What goes wrong: Missing in-text citations, inconsistent format, or incomplete references.
   • Why it’s wrong: It undermines credibility and can become an academic integrity issue.
   • Fix: Cite during drafting; do a final pass just for citations.

Memory Aids & Quick Tricks

Quick Review Checklist

• [ ] Did you state the team research question and your lens clearly in the intro?
• [ ] Is your IRR organized by themes (not by sources)?
• [ ] Does each body section answer a clear mini-question under your lens?
• [ ] Do you use multiple perspectives and address key tensions/tradeoffs?
• [ ] Do most paragraphs include 2+ sources and an explicit synthesis sentence?
• [ ] Did you evaluate credibility/limitations where it matters (methods, bias, context)?
• [ ] Are your claims appropriately qualified (who/where/when does it apply)?
• [ ] Is your tone academic and objective (no “I think,” no loaded language)?
• [ ] Are all quotes/paraphrases cited in-text, with a complete Works Cited/References?
• [ ] Does your conclusion include what research suggests + implications + gaps?

You’ve got this—aim for clear lens focus, tight synthesis, and clean citations, and your IRR will feel “AP-level.”