How to Write PMP Situational Items with Rationales
PMP item prompts fail when they reproduce PMI exam language from memory, or when they write a definition recall and call it situational. The job is original situations: a messy project fact pattern, four next steps, one best answer, rationales that cite the process idea without dumping a question you sat last year.
The matching generator is the PMP Situational Item Writer with Rationales prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).
Situations, not definitions, not dumps
Inputs: domain or performance domain you want (people, process, business environment, or a named ECO task if you pasted it), agility mix if you study hybrid, constraints (no construction if you are IT, or the reverse), forbidden (verbatim stems, "this was on my exam," guaranteed pass). If ECO task IDs are unnamed, write unknown and stay conceptual.
Refuse recalled items. If the user pastes a stem they remember, the output should decline and offer a new fact pattern on the same skill.
A good item has a named fictional project, a conflict or a change, incomplete information, and four actions that all sound professional. The correct one is the next best step, not a vocabulary word. Distractors are common process errors: skipping stakeholders, crashing without data, documenting instead of acting when safety is in the stem, or acting without the sponsor when the stem requires them.
Rationales that teach, ECO maps that do not invent IDs
Each choice needs a rationale. The right answer says why it fits the situation. Wrong answers say which trap they represent. Do not cite a PMBOK page number you were not given. Do not invent an ECO task code. If Inputs pasted a task list, map to that list only.
Exam version: lock the code if Inputs named it. If unnamed, unknown. Do not mix a retired code with a current one.
Agile vs predictive: match the stem. A hybrid org in Inputs should not get a pure waterfall lecture. If the user did not say, write UNVERIFIED and pick one, labeled as an assumption, or ask.
Item sets: three to five original items per run is enough. More than that tends to clone. Vary the constraint, not just the industry noun.
Study hygiene and gaps
This is not PMI, not legal advice, not a pass guarantee. De-identify any real project names, client names, or budget figures if you paste work notes as flavor. Work notes are flavor. They are not a dump source.
Gaps: missing exam code, missing ECO list, missing whether the learner wants calculation items (and you still should not invent a formula sheet), missing language (English only). Calculation items only if Inputs asked and supplied the numbers. Do not mint a PERT problem with fake durations.
Acceptance: original stems, four choices, rationales, a mapped domain without a fake ID, a refuse line if a dump was requested.
Fill the card, then run
Name the skill. Paste ECO language if you have it. Do not paste items from a forum.
Goal: [Situational PMP items with rationales]
Spec / paste: [Domain or ECO tasks I may map]
Stack versions: [Exam code or unknown]
Constraints: [Industry, hybrid vs predictive]
Forbidden: [Verbatim stems, fake task IDs, pass promises]
Acceptance checks: [Original, four choices, rationales, mapped domain]
When a run declines a recalled stem and writes a new sponsor-conflict item with four adult distractors, share that filled card. The rationales are the study notes. The dump refusal is the ethics.
Re-run per domain, not per "give me 50." A stack of 50 is how wording starts to echo retired items you did not mean to echo. Keep a local file of stems you already used so the next card can say Forbidden: do not reuse these plots.