10 Tips to Ace the AP CSP Create Performance Task

The Create Performance Task is worth 30% of your AP Computer Science Principles score, and unlike the multiple-choice exam, you have weeks to prepare it. That means you have an incredible opportunity to earn a significant portion of your score if you approach it strategically. Here are ten tips to help you choose, build, and submit a Create Performance Task that earns maximum points.

1. Start Early

The single biggest mistake students make with the Create Performance Task is waiting too long to start. You are expected to spend at least 12 hours of class time on this project, and many students need even more. Start brainstorming ideas at least six weeks before the submission deadline. This gives you time to develop your program, write thorough responses, record your video, and handle any unexpected technical issues.

Starting early also reduces stress. When you rush through the project at the last minute, your code is more likely to have bugs, your written responses will be less polished, and your video may not demonstrate all the required features. Give yourself the gift of time.

2. Choose a Manageable Project

Your project does not need to be groundbreaking or complex. In fact, a simpler program that clearly demonstrates all the required elements is much better than an ambitious project that is riddled with bugs. Good project ideas include quiz games, flashcard apps, budget trackers, grade calculators, and simple text-based adventures. These projects naturally include input, output, lists, loops, conditionals, and procedures.

Avoid projects that require external libraries, APIs, or network connections. The College Board wants to see code that you wrote yourself, and using external resources complicates your submission and introduces potential points of failure.

3. Understand the Rubric

The Create Performance Task is scored on six one-point rubric rows. You need to earn all six points for a perfect score on this component. The six rows are: program purpose and function, data abstraction, managing complexity, procedural abstraction, algorithm implementation, and testing. Before you start coding, read the rubric carefully and make a checklist of every element you need to include.

Many students lose points not because their code is bad, but because they miss a specific requirement. For example, your program must include a list that is used meaningfully, a procedure with at least one parameter, and an algorithm that includes sequencing, selection, and iteration. If any of these elements are missing, you lose the corresponding point regardless of how well the rest of your program works.

4. Use a List Meaningfully

One of the six rubric rows specifically requires you to use a list (array) in your program. This list must be used to manage complexity — you need to explain why a list is better than individual variables for your use case. A common mistake is creating a list that is never actually used in any meaningful way. Your list should store, retrieve, add, or remove data during program execution.

For example, if you are building a quiz game, your questions and answers should be stored in a list. If you are building a flashcard app, the terms and definitions should be in lists. The list should be central to how your program works, not an afterthought.

5. Write a Procedure with a Parameter

Your program must include at least one student-developed procedure that takes a parameter. A procedure is a block of code that performs a specific task and can be called from different parts of your program. The parameter is an input that the procedure uses to do its work.

For example, if you have a procedure called displayQuestion that takes a question number as a parameter, it can be called with different arguments to show different questions. Make sure your procedure does something meaningful and that you can explain what it does in your written responses.

6. Document Your Code

While the rubric does not specifically require comments, documenting your code makes it much easier to write your written responses and helps the graders understand your program. Add comments at the top of your program explaining its purpose, before each major section of code explaining what it does, and inside complex procedures explaining the logic.

Good documentation also helps you during the development process. When you return to code you wrote days ago, comments help you remember what each section does and why you made certain design decisions.

7. Write Clear Written Responses

The written responses are scored separately from your code, and they are just as important. For each response, be specific and thorough. Do not just describe what your program does — explain why you made certain design choices and how your code works internally.

When describing your program's purpose, explain who would use it and why. When explaining how a list manages complexity, compare it to the alternative of using individual variables. When describing your procedure, explain what the parameter does and how changing it affects the output. The more detail you provide, the more points you are likely to earn.

8. Record a Clear Video

Your video must be one minute or shorter and must demonstrate your program running with input and output. Plan your video before you record it. Decide what inputs you will use and what outputs you expect. Make sure the video is well-lit, the screen is clearly visible, and the audio is clear if you are narrating.

Test your video before submitting it. Make sure it plays correctly on different devices and that the file format is accepted by the AP Digital Portfolio. A common mistake is recording a video that is too long, includes too much detail, or fails to show the required input and output.

9. Test Thoroughly

Before submitting your project, test it with a variety of inputs. Try normal inputs, edge cases, and invalid inputs. Make sure your program handles errors gracefully and does not crash. The testing rubric row requires you to describe two calls to your procedure with different arguments, so make sure you have tested these scenarios and can explain the results.

Ask a friend or family member to test your program. Fresh eyes often catch bugs that you miss because you are too familiar with the code. Have them use the program without any instructions and see if they can figure out how it works. If they struggle, your user interface may need improvement.

10. Submit Early

Do not wait until the last minute to submit your project through the AP Digital Portfolio. Technical issues, internet problems, and server slowdowns are common near the deadline. Submit your project at least two days before the deadline to give yourself a buffer. Once you submit, you cannot make changes, so make sure everything is complete before clicking the submit button.

After submitting, verify that your submission appears correctly in the AP Digital Portfolio. Check that your code file is uploaded, your video plays, and your written responses are saved. If anything looks wrong, contact your teacher immediately.

Conclusion

The Create Performance Task is your chance to demonstrate everything you have learned about programming in a real-world context. By starting early, choosing a manageable project, understanding the rubric, and submitting a polished product, you can earn maximum points on this important component of the AP CSP exam. Remember, the goal is not to create a perfect program — it is to demonstrate your understanding of computer science concepts through a program you created yourself.