How detailed do project descriptions need to be on the application?
Hey everyone, I am finalizing my application right now and I am second-guessing how I wrote my project descriptions. I worked on a massive two-year hybrid software project, and I am struggling to break down my hours by domain without it looking like I am just copying the ECO. Do I need to be super granular here, or is a high-level summary enough? Just trying to avoid triggering an audit if I can help it. Thanks!!
1 Answer
Hey there! First off, take a deep breath—it is completely normal to overthink this part of the application.
To answer your question directly: you actually want to use the ECO terminology, but you need to wrap it in the context of your specific project. PMI reviewers are looking for those keywords to prove you understand formal project management, but they want to see how you applied them.
Here is the best formula to keep it clear and avoid looking like a copy-paste job:
Objective: Briefly state the project goal (1-2 sentences).
Role: Clearly state you were the Project Manager (or equivalent title leading the work).
Responsibilities: Break this down by the traditional domains (IN, PL, EX, MC, CL). Write 1-2 sentences per domain using PMI terminology mixed with your project details. (e.g., "PL: Developed the project management plan and defined scope using agile story mapping.")
Outcome: State the final result.
As for audits—don't let the fear of an audit dictate how you write! The vast majority of audits are completely randomized by the system the second you hit submit. Keep it between 200-500 words, focus on your leadership role rather than the technical coding work, and you will do great. Let us know if you want us to review a draft!
Want to answer, follow this discussion, or submit for Official Review?
Log in to join the discussion