OpenEDG PCAD exam-day guide
OpenEDG PCAD · Prepare for the day ahead.
Your checklist
Government-issued photo ID
Bring the exact ID type the test provider requires, with a name matching your registration. Confirm with the provider which forms are accepted and whether a secondary ID is needed.
Appointment confirmation and candidate number
Keep the confirmation email or candidate ID accessible so check-in goes quickly. Confirm with the provider whether printed copies are required.
Know your test format and delivery method
PCAD is a practical, performance-based certification: you are given a Python programming task and must build a working solution rather than answer multiple-choice questions. Re-read the official exam description so you know the task style, time limit, and passing approach before test day.
Set up your coding environment in advance
Practice in the same editor or IDE the test environment offers, or in a plain editor if you are unsure. Know how to create files, run a script, and read error output without relying on autocomplete or extensions.
Practice with the standard library only
The exam tests core Python: data types, control flow, functions, classes, exceptions, file handling, and common standard-library modules. Confirm with the provider whether third-party packages are available; if not, prepare to solve everything with the standard library.
Rehearse timed practice tasks
Complete at least two full practice tasks under the real time limit, from blank file to working, tested solution. This trains pacing more than reading notes does.
Prepare a testing routine
Write down the steps you will run after coding: run the script, test edge cases (empty input, wrong types, boundary values), and confirm output format. Practice applying it to every exercise.
Quiet, distraction-free test space (remote testing)
If testing remotely, confirm the provider's requirements for camera, microphone, desk clearance, and room privacy. Rules vary, so confirm with the provider rather than assuming.
Know the break and timing rules
Check whether breaks are allowed and how the clock is handled. Confirm with the provider, since practical exams often run as a single timed block.
Plan arrival or login early
Arrive or log in ahead of your appointment to absorb check-in, ID verification, and any environment setup. Confirm with the provider how early you should be present.
Read the scoring and retake policy
Understand how your solution is evaluated (for example, automated tests against the task requirements) and what happens if you do not pass. Confirm with the provider for exact scoring and retake terms.
Sleep, food, and water plan
A practical coding exam rewards clear thinking. Plan a normal night's sleep and a light meal before the session rather than last-minute cramming.
Plan the day
Shift from reading to doing. Complete two or three timed practice tasks end to end, then review your own code for the mistakes you repeat: off-by-one errors, unhandled exceptions, wrong output formatting, and missing edge cases. Re-read the official exam description and task requirements so nothing about the format surprises you. Confirm logistics now: appointment time, ID, delivery method, and any environment requirements. Stop learning new libraries; consolidate what you already use well.
Do one light practice task to stay sharp, then stop heavy study. Prepare your materials: ID, confirmation, and anything the provider requires. If testing remotely, test your camera, microphone, internet connection, and room setup. If testing at a center, plan the route and arrive time. Write a one-page personal checklist of the coding steps you will follow: read the task fully, plan, code, test edge cases, verify output. Get a full night's sleep.
Eat a normal meal and avoid cramming new material. Re-read your one-page checklist. Log in or arrive early per the provider's guidance, complete ID verification, and set up your environment. Keep water nearby if permitted. Close unrelated applications and silence notifications. Take a few calm breaths and remind yourself the task is to build a correct, working solution, not to be clever.
Read the entire task before typing, and identify the required inputs, outputs, and edge cases. Sketch a short plan, then code in small increments, running the script often. Test with normal, boundary, and invalid inputs. If you get stuck, move to a simpler working version first, then improve it. Watch the clock and reserve time at the end to re-read the requirements and confirm your solution actually meets them. Do not leave required files unsaved.
Rules to check
Bring the exact ID the provider requires and ensure your name matches your registration; confirm accepted ID types with the provider before test day.
Follow all environment rules for remote testing, including camera, microphone, room privacy, and desk clearance; confirm the specifics with the provider.
Work only from the materials and tools the provider allows. Do not use unauthorized references, communication tools, or assistance.
Know whether breaks are permitted and how the timer behaves; confirm with the provider, as practical exams are often one continuous timed block.
Read the task requirements carefully: solutions are typically judged on whether they meet the stated behavior, so a working, correct program beats an ambitious incomplete one.
Confirm the scoring method and pass criteria with the provider; do not rely on assumptions about partial credit.
If something goes wrong, such as a technical failure or a rule you do not understand, stop and contact the test administrator immediately rather than improvising.
Confirm the retake policy with the provider before you sit the exam so you know your options if you do not pass.