Performance Management Plan (PMP)

A Performance Management Plan (PMP) connects intended results to a usable measurement and learning system. Names and scope differ across organizations: a strategy-level performance plan and an activity-level MEL plan need not be the same document. Check the applicable funding agreement and proposal instructions for the required plan, format, deadlines, and review process.

What a Performance Plan Can Contain

• Results framework linking measures to intended outputs and outcomes, assumptions, and risks
• Indicator tracking table with definitions, reporting periods, actuals, targets, and baselines where needed
• Indicator reference sheets or equivalent protocols explaining units, eligible populations, calculation, sources, disaggregation, limitations, and responsibilities
• Data collection and analysis plan with timing, methods, quality controls, resources, and secure handling
• Data quality review schedule based on risk, data use, and any explicit agreement obligations
• Evaluation plan connecting questions and methods to decisions, feasibility, ethics, and resources
• Learning and adaptation arrangements identifying who reviews evidence, makes decisions, and records changes

PMP and MEL Plan

Both can connect results, measurement, evaluation, and learning, but they are not automatically interchangeable submissions. Define whether the document covers an organizational strategy, portfolio, project, or activity. Use the required terminology and explain any crosswalk between documents. A reference sheet is useful discipline; its absence does not prove a team cannot measure an indicator if an equivalent operational protocol exists.

Baselines, Targets, and Quality Checks

Identify which measures need an initial-condition reference. Do not invent a zero baseline or assume every output count requires a survey. Set provisional targets transparently when evidence is incomplete, and agree how revisions will be approved. Describe data quality checks, their scope and responsible people, and how issues will be resolved. There is no universal three-year DQA obligation established by this guide.

Proposal Context

Read the actual solicitation and applicable agreement before asserting a required PMP, MEL plan, reference sheet, or submission date. Provide the requested detail and label future plans as proposed. Cost the work that will actually be done: staff time, collection, training, verification, analysis, evaluation, learning, and reporting. A polished plan or a high score does not establish compliance or readiness.

Common Mistakes

Treating the plan as a filing requirement. Use it in regular evidence reviews and update it when approved definitions, responsibilities, or timelines change.

Leaving measurement vague. Replace placeholders such as “monitoring system” with the actual source, population, collection procedure, calculation, owner, and limitations.

Inferring current obligations from an old policy. An archived policy may explain historical terminology but does not establish the rules for a current award. Confirm its version, scope, and incorporation in the agreement before describing an obligation.