Project Development and Management
The Project Development and Management domain tests whether you can turn a research idea into a fundable project and then keep scope, schedule, budget, and roles aligned after award. Exam items often ask what should have happened during proposal planning, which post-award change needs approval, or why a project is off track.
Core rules and concepts
- The funding solicitation is the controlling document. Check eligibility, required components, page limits, review criteria, due dates, and sponsor-specific policies before drafting.
- Build a scope-to-budget map. Each aim or work package should show personnel and effort, supplies, travel, subawards, and other costs. Reviewers and post-award staff both look for consistency.
- Use a milestone timeline. Identify deliverables, dependencies, critical-path items, and decision points such as IRB approval, data-use agreements, hiring, and vendor lead time.
- Define roles with a responsibility matrix: PI, co-investigators, department administrator, central office, and subrecipients. Clarify who prepares, approves, submits, and monitors.
- Plan for risk: recruitment, data access, regulatory approvals, equipment lead time, and contingency. A feasible project is one the team can actually execute.
- Control changes. Post-award changes in scope, key personnel, or certain rebudgeting actions may require prior written approval under 2 CFR 200.407.
Worked example
A PI proposes a three-year study with 240 participants, 12 months of recruitment, and a survey at month 6. The year-one budget shows 0.5 FTE coordinator. Reasoning: 240 participants over 12 months is 20 per month; 0.5 FTE may be too little for consent, scheduling, and data entry. The month-6 survey also requires IRB approval by month 1 or 2, so the timeline must show IRB submission and approval before recruitment. If the budget does not fund coordinator effort or incentives, the scope is not feasible. The exam rewards linking scope, timeline, and budget, not just checking that totals add up.
Traps that cost marks
- Treating the budget as arithmetic only; the better answer shows scope-budget-timeline alignment.
- Missing sponsor requirements that override institutional defaults.
- Assuming all post-award changes can be handled internally without prior approval.