The Personalized Project Reference (PPR) is a set of carefully selected code screenshots from a student's own Create Task program. It is used later on the AP CSP exam during the written response section.
What the PPR Is
The PPR is not an essay, not a reflection, and not the student's entire program. It is a code reference sheet made from screen captures of specific parts of the student's own code. These code segments are uploaded into the AP Digital Portfolio and later printed for the student to use during the exam.
The main purpose of the PPR is to help the student answer the written-response questions on the AP exam by giving them access to important parts of their own code.
Why the PPR Is Important
The written-response questions on the AP CSP exam are based on the student's own Create Task program. During the exam, the student will use the PPR as a reference while answering those questions.
What Must Be Included in the PPR
The PPR must include code screenshots from two required areas:
1. Procedure Section
- One code segment showing the student-developed procedure
- One code segment showing a call to that procedure
2. List Section
- One code segment showing how data is stored in a list
- One code segment showing how that same list is used in the program
Procedure Section in Detail
The first procedure screenshot must show a student-developed procedure. This means the student must have created it. It cannot simply be a built-in event handler or a method automatically provided by the programming environment.
The procedure should include:
- The procedure name
- A parameter or parameters
- A return type if the language uses one
- An algorithm that includes:
- Sequencing - steps happening in order
- Selection - a decision such as
iforif-else - Iteration - repetition such as a
fororwhileloop
The second procedure screenshot must show where that same procedure is called in the program. This proves that the procedure is actually being used.
List Section in Detail
The list part of the PPR must show both how data is placed into the list and how the list is used later in the program.
- Storage screenshot: shows the list being created, filled, or updated with data
- Use screenshot: shows the list being used in a meaningful way related to the purpose of the program
The list should help manage complexity. In other words, it should make the program easier to build, easier to update, or more powerful than writing the same code over and over again.
What “Screen Captures” Means
Students do not type paragraphs into the PPR. Instead, they upload images of code. If a code segment is too long to fit into one screenshot, it may be split into multiple screenshots as long as the images stay in order and remain readable.
Readability Rules
The screenshots must be easy to read on exam day. Students should make sure the code is clear, not blurry, and not too small.
- Use a readable font size
- Take screenshots at normal zoom
- Do not let the code become blurry
- Do not cut off important lines
- Crop tightly enough to focus on the required code
What Is Not Allowed in the PPR
Examples of things that should not appear in the PPR:
- Comments in the code
- Notes such as “This is my algorithm”
- Labels such as “This shows iteration”
- Vocabulary reminders or teacher notes
- Rubric-style explanations
The PPR must contain only the code screenshots themselves. The code should be clean and free from extra explanation.
Who Completes the PPR
The PPR must be completed by the student individually. Even if students worked together on the program code, each student must prepare and submit their own PPR for their own exam use.
How the PPR Is Used on Exam Day
Before the exam, the AP coordinator prints each student's final PPR from the AP Digital Portfolio. Students do not bring their own copy. The printed PPR is given to the student for the written-response portion of the AP CSP exam.
What Makes a Strong PPR
- A procedure with a clear parameter and real logic
- A procedure that clearly shows sequencing, selection, and iteration
- A clear call to that procedure
- A list that is actually useful in the program
- Clean, readable screenshots
- No comments or extra notes
Common Mistakes Students Make
- Choosing a procedure that does not include selection and iteration
- Showing a list that is declared but not really used
- Forgetting to remove comments before taking screenshots
- Using blurry or tiny screenshots
- Including too much unrelated code in one image
- Submitting the PPR but not marking it as final
Simple Student Explanation
Your PPR is your code reference sheet for the AP exam. You must include screenshots of:
- Your student-developed procedure
- A call to that procedure
- Code that stores data in a list
- Code that uses that list
Your procedure must have a parameter and include sequencing, selection, and iteration. Your screenshots must be clear and cannot have comments or class notes.
Best Student Workflow
- Finish your program first
- Pick the best procedure that shows the required algorithm
- Pick the best list example that shows storage and use
- Remove comments from the code sections you will screenshot
- Take clear screenshots at normal zoom
- Check that every requirement is visible
- Upload and mark the PPR as final before the deadline
Final Thought
A strong PPR can make the written-response section much easier. If students choose the right code segments and keep the screenshots clear, the PPR becomes a helpful tool instead of a last-minute problem.