AACE-PSP PDF Practice Test Questions Answers & preparation

AACE-PSP Planning & Scheduling Professional (PSP) Exam

The AACE Planning & Scheduling Professional (PSP) credential recognises practitioners who can design, build, analyse and maintain project schedules that support decision-making, contractual entitlement and project control. It sits in the project controls and cost‑engineering ecosystem: the PSP tests the candidate’s ability to apply scheduling theory and professional practice to real projects rather than simply operate one scheduling tool. Organisations use the PSP to demonstrate a scheduler’s technical rigour, ability to defend delay analyses, and to reduce risk in planning, baseline control and progress measurement.

AACE-PSP Exam Overview

Purpose and audience: the PSP targets planners, schedulers, project controls specialists and delay analysts who prepare or validate baseline schedules, track performance, and produce forensic schedule analysis in support of claims or litigation. It is also taken by project managers and contract administrators who need deep practical understanding of schedule logic and delay causation.

What the exam evaluates: competence in schedule development and maintenance, schedule quality assurance, delay and forensic analysis, the professional responsibilities of schedulers in contractual contexts, and the interpretation and presentation of schedule information. The focus is on applying methods and judgement in real project situations rather than memorising UI steps in a particular software package.

Why it matters in practice: a defensible schedule controls risk and money. Poorly constructed logic, inconsistent calendaring, uncontrolled baseline updates and weak change control create ambiguity that can cost millions in disputes or ineffective execution. The PSP signals that a practitioner can produce schedules suitable for both day‑to‑day control and for formal entitlement analysis.

Recommended experience: employers and assessors expect hands‑on experience in developing and managing multiple real project schedules, plus involvement in at least one delay or claims analysis. Formal education helps, but real-world exposure to baselines, updates and stakeholder review cycles is decisive.

Scheduling Techniques and Artefacts Every PSP Candidate Must Master

Schedule structure and coding: a professional schedule is more than dates. It must carry a coherent WBS (work breakdown structure), an aligned activity coding scheme for filters and roll-ups, an OBS (organisational breakdown structure) mapping of responsibility, and clear milestones that map to contract obligations. Candidates should be fluent in setting codes that enable traceability from an activity through to cost and risk registers.

Logic, relationships and calendars: the Critical Path Method (CPM) underpins professional scheduling. Understand relationship types (finish‑to‑start, start‑to-start, finish‑to-finish, start‑to-finish), correct uses and misuse of lags, and how calendar choices (work vs non‑work days, shift definitions) change float and criticality. A common practical error is mixing inappropriate calendars across linked activities, which silently shifts the critical path.

Float and critical path behaviour: distinguish total float, free float and project‑level float; recognise near‑critical paths and float sensitivity to duration changes. Practitioners must know how float allocation affects entitlement claims and how contractual clauses treat float ownership.

Baseline creation and maintenance: a baseline must be an auditable snapshot, with explicit version control and documented approvals. Progress updates should never overwrite the contractual baseline without formal change control. A robust practice retains original baselines, the approved revised baselines, and all update histories for forensic reconstruction.

Delay and Forensic Analysis: windows, time‑impact, and as‑built reconstruction

Basics of forensic approaches: real delay analysis uses multiple, complementary techniques. As‑built vs as‑planned reconstruction shows what actually occurred versus the plan; time‑impact analysis (TIA) models discrete delays inserted into a baseline to measure effect; and window analysis breaks the project into chronological windows to isolate causes. Candidates must understand strengths, limitations and appropriate application contexts for each method.

Evidence and traceability: credible analysis relies on contemporaneous records: daily reports, site diaries, change notices, approved drawings, meeting minutes and resource data. Successful practitioners know which documents to capture early and how to preserve them (date‑stamp, index, maintain chain of custody) so their analyses are verifiable months or years later.

Common forensics pitfalls: performing a TIA on a schedule already distorted by backdated changes, using pull‑up updates that erase original logic, or failing to reconcile progress percentages with resource consumption produces unreliable results. The PSP expects candidates to explain why these mistakes invalidate conclusions and how to avoid them.

Building Contractual Baselines and Controlling Change in Practice

Establishing a contractual baseline: in contracts the baseline typically becomes the reference for progress measurement and entitlement. A good baseline has mutually agreed milestones, realistic logic, documented constraints, and resource assumptions that reflect the contract scope. The baseline approval process should be formalised and recorded.

Change control discipline: every change that affects schedule must pass through a documented change control system: description of change, impact analysis (time and resources), approval trail, and baseline update. Practitioners should adopt a policy of “baseline preserved, change controlled” and be able to demonstrate audit trails that link approved contract variations to baseline revisions.

Reporting cadence and governance: schedule update frequency should align with project decision cycles—weekly for execution teams, monthly for management and contract milestones. Governance combines technical schedule checks with sign‑off gates; ideally the planner has no unilateral authority to accept scope changes without contractual sign‑off.

Tools, Data Formats and Interoperability Schedulers Encounter

Common professional tools and their practical differences: Oracle Primavera P6, Microsoft Project and specialist packages such as Asta Powerproject are widespread. The differences that matter in practice are not the GUI but how each tool handles relationship types, resource levelling algorithms, calendars, and export/import fidelity.

Data exchange and formats: for multi‑party environments you will commonly encounter Primavera XER exports, Microsoft Project MPP or XML, and generic interchange formats. Expect imperfect fidelity when moving schedules between tools—resource assignments, calendars and custom fields are typical loss points—so always reconcile imported schedules and keep a canonical source.

Automation and integrations: modern projects use integrations between scheduling tools and cost systems, ERP and field data capture (mobile progress apps). Understand the implications of automated progress feeds: they can speed reporting but will silently reinforce bad data unless quality controls are in place.

Schedule Quality Assurance and Risk Assessment Techniques

Schedule health checks: candidates should be able to perform structured quality assurance reviews that test logic completeness, negative lags, dangling or open‑ended relationships, equal‑duration links causing masking, long‑running summary tasks, and improper use of constraints. The US DoD/DCMA 14‑point assessment is one recognised practical checklist used widely; familiarity with structured assessments of similar rigor is expected.

Schedule risk and probabilistic analysis: deterministic schedules must be supplemented by risk analysis where appropriate. Monte Carlo simulations on activity durations or start windows produce probabilistic finish dates and confidence intervals. Experienced practitioners know when probabilistic outputs meaningfully inform contingency and when they add false precision.

Integration with earned value: schedule and cost integrate through work packages, resource profiles and earned value measurement techniques. A scheduler must understand how schedule changes affect earned value metrics such as Schedule Performance Index (SPI) and how misaligned measurement criteria produce misleading performance indicators.

Professional Responsibilities: impartiality, documentation and testimony

Independence and ethics: when involved in claims, the PSP practitioner’s primary responsibility is to present an objective, evidence‑based schedule analysis. That requires clear separation between advocacy and expert analysis, full disclosure of assumptions, and transparent methodology so others can reproduce results.

Record keeping and auditability: maintain contemporaneous evidence and an auditable update trail. Good record practice includes preserving original schedule files, update logs, baseline comparison reports and any scenario files used in analysis. Poor record keeping is the most common reason expert opinions are discounted in disputes.

Preparing for testimony or stakeholder review: translate technical findings into clear narratives and visualisations that non‑technical stakeholders can understand. Use milestone charts, critical‑path diagrams and concise impact statements. Practice concise, factual answers; in adversarial settings, avoid speculative language.

How to Prepare Practically for the PSP: study, practice and mentor feedback

Focus study on applied competence: read AACE International’s certification resources and recommended practices, then immediately put concepts into practice with real schedules. Passive reading is necessary but insufficient; the PSP is earned by demonstrating applied judgement.

Hands‑on exercises that matter: build a baseline from a scope narrative, create an update cycle with actual progress and resource consumption, prepare a delay analysis using both a TIA and a windows approach, and produce a written technical report summarising findings and assumptions. Ideally, review your work with an experienced planner who can critique logic, calendar use and documentation.

Simulate real deliverables: produce the artefacts you would in a professional engagement—baseline submittal, baseline acceptance minutes, update reports, change control transmittals, and a forensic analysis report. The discipline of producing these documents under realistic constraints separates competent candidates from merely knowledgeable ones.

Learning aids that accelerate progress: structured classroom workshops with real schedule files, mentorship on analysing contentious schedule logic, and participation in live projects where you can be the responsible scheduler for at least one baseline cycle.

Common Errors Candidates and Practitioners Make — and How to Avoid Them

Overreliance on software defaults: leaving tool defaults unchanged (calendars, relationship precedence, lag types) often embeds hidden assumptions. Always review and document defaults.

Treating percent complete as a sole progress measure: percent complete is subjective and can hide resource or cost trends. Reconcile percentage progress with resource burn and physical measurement.

Failing to lock down a contractual baseline: uncontrolled or undocumented baseline changes are fatal for entitlement. Implement and enforce version control from day one.

Poor logic discipline: using excessive constraints or unrealistic relationships to force dates will produce schedules that look stable but are not reliable for analysis. Use logic to represent how work will be performed, not to obtain desired dates.

Where PSP Fits with Other Professional Credentials and Career Paths

How PSP complements other credentials: the PSP sits squarely in project controls and complements cost, estimating and project management credentials. It strengthens a candidate’s ability to produce defensible schedules and to contribute to claims resolution, contract negotiation and risk management. Employers often look for PSPs in EPC, infrastructure and heavy construction sectors where schedule risk is high.

CCP, CEP, PMP, PMI‑SP

1. Who should take the PSP and what roles typically hold it?

The PSP is intended for planners, schedulers, project controls specialists, delay analysts and project managers who are responsible for developing, maintaining or defending project schedules; holders typically work in construction, oil & gas, infrastructure, utilities and large engineering projects.

2. What hands‑on experience is most valuable when preparing for the PSP?

Direct responsibility for creating and maintaining at least one full contractual baseline, performing regular updates, participating in change control and doing at least one delay or forensic analysis provides the practical evidence of capability that the PSP assesses.

3. Does the exam test a specific scheduling software package?

The credential is tool‑neutral and evaluates understanding of scheduling principles, quality practices and forensic techniques. Familiarity with common tools such as Oracle Primavera P6 and Microsoft Project is useful for practical work, but the judgement behind the schedule is the assessed skill.

4. What kinds of schedule quality checks should I practice?

Practice structured checks for logic completeness, dangling activities, negative lags, improper constraints, consistent calendaring, summary task misuse and realistic resource profiles; being able to explain why each issue matters is more important than simply listing checks.

5. How important is documentation and record keeping in PSP practice?

Extremely important. Contemporaneous records—daily reports, approved change notices, minutes and original schedule files—are the backbone of any robust update process or forensic analysis and are frequently decisive in disputes.

6. Which delay analysis techniques should I be competent with?

Be competent with as‑built vs as‑planned reconstruction, time‑impact analysis for discrete delays, and window or period analysis for cumulative effects. Know when each technique is appropriate and what evidence supports each method.

7. How should I integrate risk and probabilistic thinking into schedules?

Use risk registers to identify activities with duration uncertainty, apply probabilistic duration distributions where appropriate, and run sensitivity or Monte Carlo analyses to quantify finish‑date risk; document assumptions and avoid presenting probabilistic outputs as absolute certainty.

8. How does a PSP contribute to claims or expert testimony?

A PSP provides technically defensible schedule analysis, explains methodology and assumptions clearly, preserves evidence, and can present findings in a manner suitable for contractual review or legal processes while maintaining professional impartiality.

9. What are the most common mistakes in preparing a contractual baseline?

Common mistakes include unclear milestones, inconsistent calendars, hidden constraints or forced dates, lack of formal approval and inadequate documentation of assumptions; any of these undermines the baseline’s contractual value.

10. What study approach yields the best return in preparing for the PSP?

Combine study of AACE guidance and recommended practices with repeated, supervised hands‑on exercises: build baselines, run updates, perform forensics, produce reports, and get critique from experienced planners to sharpen judgement and communication.

External resources:

• AACE International certification information: AACE International Certification
• AACE International recommended practices (search within AACE site for planning, scheduling and forensic RP documents)