This lesson introduces the AP CSP Create Performance Task (Create PT)
with one goal: clarity. Students should leave understanding what the
task is, what must exist in their code, and why simple + explainable
beats impressive + confusing.
Create Performance Task
Lesson 1: What AP Actually Wants
Today's goal: remove confusion, reduce anxiety, and make the task
feel doable.
Today's Plan
What the Create PT is (plain English)
What you submit
The Big Three required code elements
What doesn't matter as much as you think
A minimum-viable mental model
Exit check
What is the Create PT?
You will build a small program of your choice and explain parts of
it to prove you understand core computer science ideas.
This is an evidence task — not an “impress the grader” contest.
What You Submit
Program Code (your proof)
Video (shows input → output)
Written Responses (explain how your code meets requirements)
The grader typically does not run your program. They score based
on what you clearly show and explain.
What the Grader Actually Sees
Your video
Your written responses
Your code
So your job is to make your evidence easy to find.
The Big Three Your Code Must Include
A List (stores related data in a way that matters)
A Student-Developed Procedure with a parameter
An Algorithm inside that procedure with:
Sequencing
Selection (if)
Iteration (a loop)
One strong procedure can satisfy multiple requirements.
Lists That “Count”
Counts when…
It stores multiple values over time
You use it meaningfully (read + update)
The program would be worse without it
Often doesn't count when…
You use it once and forget it
It only holds one value
It could be replaced with 2-3 simple variables
Procedures That “Count”
It must be student-developed (not built-in)
It must have at least one parameter
It should do real work (not just “print one thing”)
It must be called in your program
Parameters help prove your procedure can handle different inputs.
What AP Means by “Algorithm”
AP's algorithm requirement is about proving you can write logic —
not about advanced math.
Sequencing: steps in order
Selection: decisions using if
Iteration: repetition with a loop
The algorithm should live inside your procedure.
What Doesn't Matter as Much as You Think
Students over-focus on…
Fancy UI / graphics
Huge codebases
Complicated games
Extra features “just because”
What actually helps…
Easy-to-find evidence
Clear input → processing → output
One meaningful list
One strong procedure + algorithm
Simple and explainable beats impressive and confusing.
Minimum-Viable Mental Model
Example concept: Quiz / Survey Analyzer
Ask questions (input)
Store answers in a list
Call a procedure(parameter) to analyze
Inside the procedure: loop + if (algorithm)
Display a result (output)
Micro-Activity (3-5 min): Evidence Spotting
With a partner, answer:
What could the list store in the quiz example?
What could the procedure parameter be?
Where would the loop and if naturally happen?
You are not writing code yet — just locating evidence.
Concept Demo: A Minimal Example
This is not “the Create PT” — it's a tiny example showing the
structure.
demo.js
1
// Create PT "Minimum Viable" Example (concept demo)
2
3
// LIST: stores user answers over time
4
let answers =[];
5
6
// PROCEDURE (student-developed) with a PARAMETER
7
functionanalyzeAnswers(answerList)
8
{
9
letscore=0;
10
11
// ITERATION
12
for(leti=0;i<answerList.length;i++)
13
{
14
// SELECTION
15
if(answerList[i]==="yes")
16
{
17
score++;
18
}
19
}
20
21
// OUTPUT (return value)
22
returnscore;
23
}
24
25
// INPUT (simulated here for demo)
26
answers.push("yes");
27
answers.push("no");
28
answers.push("yes");
29
30
// CALL THE PROCEDURE
31
let result =analyzeAnswers(answers);
32
33
// OUTPUT
34
console.log("Yes count:", result);
Where's the Evidence?
In the demo, we can point to each requirement:
Checklist
1
✅ LIST: answers
2
✅ PROCEDURE with PARAMETER: analyzeAnswers(answerList)
3
✅ ALGORITHM in the procedure:
4
- Sequencing (top-to-bottom steps)
5
- Selection (if)
6
- Iteration (for loop)
7
✅ INPUT → PROCESSING → OUTPUT shown
Common Traps (Preview)
Procedure has no parameter
List is used once and forgotten
Algorithm exists, but not inside the procedure
Video doesn't clearly show input and output
Next lesson: “counts” vs “looks like it counts.”
Exit Ticket
Answer one prompt in 2-3 sentences.
Exit Ticket
1
Pick ONE to answer:
2
3
1) In your own words: what is the purpose of the list in a Create PT program?
4
2) Why does AP require a procedure with a parameter?
5
3) Name one thing students often overdo on the Create PT that doesn't help their score.
'F' → Fullscreen
Objectives
Describe the Create Performance Task in plain English
Identify the Big Three required code elements (List, Procedure, Algorithm)
Explain why “simple + explainable” is a winning strategy
Recognize common Create PT traps before they happen
Activity Tasks
During the micro-activity slide, write down your team's answers for:
list idea, procedure parameter, and where the if + loop would go.
Complete the exit ticket (Slide 16) and submit it in your LMS / on paper.
(Optional) Write 2-3 program ideas that fit the “minimum-viable” model:
input → list → procedure(parameter) with if + loop → output.
Reflection Questions
Why might a “simple but clear” program score better than a “big but messy” program?
Which of the Big Three (List, Procedure, Algorithm) do you feel most confident about right now?
Which feels the most confusing?
In your own words, what does it mean to “make the evidence easy to find” for a grader?
Submission
Submit your exit ticket response (and optional homework ideas if assigned) to the appropriate dropbox.