Performance Task 1 – Team Presentation and Defense

Overview

The AP Seminar Performance Task 1 (the Team Project and Presentation) is worth 20% of your AP Seminar score, and it has two graded pieces: an Individual Research Report (IRR) of 1,200 words and a Team Multimedia Presentation and defense (TMP) that runs 8-10 minutes. The IRR is scored by College Board and counts for 50% of PT1; the TMP is scored by your teacher and counts for the other 50%. You work in a team of three to five to investigate one complex problem through different lenses, then build a shared argument for a solution.

PT1 is one of two through-course performance tasks in AP Seminar. The other is Performance Task 2 (the Individual Research-Based Essay and Presentation, 35%), and the rest of your grade comes from the End-of-Course Exam (45%). Your IRR is due in the AP Digital Portfolio by April 30 at 11:59 p.m. ET, and your teacher must score the TMP and affirm authenticity by May 10 at 11:59 p.m. ET. If your teacher doesn't complete that affirmation, you get a zero on the IRR, so deadlines here are not optional.

How PT1 Is Scored

Performance Task 1 carries 20% of your AP Seminar grade, split evenly between two components scored in two different ways.

The IRR is your own score. The TMP is a group score, so your presentation grade rises or falls with your team. The oral defense isn't about quizzing you on facts; the questions are designed to make you reflect on how your team collaborated. Your teacher asks one question of each person, and you should be ready to talk about any part of the project, including a teammate's research.

There's also a required checkpoint baked into the process. During the research phase you submit a source log (an annotated bibliography, source chart, or annotated documents) and have a short conversation with your teacher about your process and sources. This is Checkpoint #1, and your teacher has to affirm you completed it. No affirmation means no score for the IRR. The AP Capstone policy also screens final papers through Turnitin and treats generative AI as an optional aid only, so the work has to be genuinely yours.

How to Approach PT1, Step by Step

Treat PT1 as a semester-long project that moves through four phases: pick a strong issue, research your lens, synthesize as a team, then build and defend the presentation. Your teacher should give you a calendar, but here's how to think about each phase.

Phase 1: Pick a Strong Issue and Build Your Team

Choose a problem with enough complexity that every teammate can contribute a genuinely different lens. A weak issue has an obvious answer. A strong issue has real trade-offs, credible disagreement, and enough evidence to support several perspectives.

Map out lenses early. Your lens is a specific way of viewing the issue, not just a topic area. If your team is studying social media's impact on democracy, "the economic lens" is too vague. "Advertising revenue models" or "market concentration effects" gives you something to dig into. Make lenses distinct but complementary, overlapping enough to talk to each other without duplicating work.

Phase 2: Research and Write the IRR

Go for depth over a giant source pile. Aim for roughly 8-12 strong sources rather than 20 shallow ones: foundational texts that set up key concepts, recent scholarly work that shows current debates, and credible real-world evidence. Read actively and keep notes on how each source connects to your teammates' lenses, because those links power the team synthesis later.

Your 1,200-word IRR should:

• identify your area of investigation and how it connects to the team's overall problem;
• summarize, explain, analyze, and evaluate the main ideas and reasoning in your sources;
• identify, compare, and interpret a range of perspectives on the issue; and
• cite all sources and include a works cited or bibliography.

Build understanding progressively. Open by explaining your lens and why it matters (don't assume the reader gets why an economic angle is relevant). When you analyze sources, go past summary: show where authors within your lens agree, disagree, and what assumptions they share. Avoid false binaries. Real perspectives live on spectrums and overlap in interesting ways, and showing that nuance is what separates a strong report from a basic one.

Phase 3: Synthesize as a Team

After everyone finishes their IRR, your job shifts from researcher to teacher. You have to help your teammates actually see through your lens, not just hand them your findings. Think teaching rounds, not data dumps. First pass: core concepts with analogies. Second pass: the complications and where the lens breaks down. Third pass: connection sessions where you spot how your argument links to a teammate's.

Strong synthesis is the whole game here. Weak synthesis sounds like "economics says X, sociology says Y, biology says Z." Strong synthesis explains how the lenses interact and what that interaction reveals that no single lens could. Make synthesis artifacts together: mind maps, tension charts, comparison tables that show where perspectives overlap, clash, or depend on one another.

Phase 4: Build, Practice, and Deliver the TMP

Your team's solution should emerge from the synthesis, not get forced onto it. Structure the argument to show the path: "The economic analysis revealed X, while the social perspective showed Y. Together, these point to Z." Support your claims with evidence that you attribute orally or visually, and address the limitations and implications of your proposed solution. Design the presentation for an educated, non-expert audience.

For design, use consistent slide templates so the deck feels like one team's work. Visual metaphors (Venn diagrams, flow charts, conceptual models) can show lens integration far better than bullet points. Hand off smoothly between speakers and reference each other's points out loud ("As Maya explained about economic impacts...") so the collaboration is visible. Equal participation doesn't mean identical roles; play to strengths, but make sure everyone's contribution is substantive and obvious. Then run full timed rehearsals until transitions feel natural.

The Oral Defense

The defense questions test your collaborative process. Each person answers one question, so come ready with specific examples of how teammates shaped your thinking and how your team made decisions. Practice answers like: "Originally I focused only on individual privacy, but Jordan's legal lens helped me understand systemic privacy infrastructure." Or, on decisions: "We considered three solutions. The environmental lens favored Option A, the technological lens favored Option B, and through discussion we realized Option C addressed both."

Be honest about challenges, too. "We struggled to connect the historical and scientific lenses until we built a timeline that showed how past patterns inform current possibilities" is a great answer because it's specific and reflective.

Sample Synthesis Progression

Here's an editorial example showing the difference between stapling findings together and real synthesis. Imagine a team studying urban food deserts.

Weak (compilation): "The economic lens shows low profit margins for grocers in poor neighborhoods. The public-health lens shows higher diabetes rates. The policy lens shows zoning restrictions."

Strong (synthesis): "Only by combining the economic and policy lenses could we see why public-health interventions alone keep failing. Grocers avoid these neighborhoods because thin margins collide with restrictive zoning, so any health-focused solution that ignores the financial and regulatory barriers can't actually change what's on the shelves."

The strong version says something no single lens could say on its own. That's the test: if your conclusion could have been written without team collaboration, you haven't synthesized yet.

Common Mistakes

• Fake synthesis. Teams staple individual findings together and call it synthesis. Fix it by pushing until your conclusion depends on combining lenses, with sentences like "only by combining X with Y could we see why Z fails."
• A solution that doesn't trace back. If you can't show how your synthesis led to your proposal, your teacher will notice. Track your logic step by step ("because the economic lens showed X and the social lens revealed Y, any solution must address...") so the path is clear.
• Lenses that are too broad or overlapping. "The economic lens" is a topic, not an angle. Narrow each lens to something specific and distinct early, and map how the lenses connect before anyone starts writing.
• One voice taking over. Letting a single teammate run everything can shut down better ideas. Build structures like rotating meeting leaders and timed speaking rounds so the quieter member's insight gets heard.
• Not documenting collaboration. Come defense day, teams scramble to remember how they worked together. Photograph whiteboards, save synthesis drafts, and note breakthrough moments so you can answer "how did you resolve disagreements?" with a real example.
• Missing the checkpoint or deadline. No source-log conversation means no IRR score, and a missed teacher affirmation gives you a zero. Submit the IRR by April 30 and confirm your teacher has everything they need before May 10.

Practice and Next Steps

The best practice for PT1 is reps on the skills it rewards: tight research, perspective-taking, and synthesis. Strengthen your source analysis and argument moves with the AP Seminar guided practice questions, and lock in the vocabulary that shows up across both performance tasks using the AP Seminar key terms glossary and the AP Seminar cheatsheets. Studying past AP Seminar exam questions helps you see how arguments and evidence are evaluated.

Once PT1 is solid, look ahead to Performance Task 2: the Individual Research-Based Essay and Presentation and the AP Seminar End-of-Course Exam, then check how all three pieces add up with the AP Seminar score calculator. You can also return to the full AP Seminar exam hub or the AP Seminar subject page anytime.