Outputs vs. activities: what your role actually delivers
Most MCA staff can describe what they do every day. Far fewer can describe what they produce. That distinction — between doing things and delivering things — sits at the heart of how compact delivery works, and how it fails.
This unit explains the difference between activities and outputs, shows what that means across MCA roles, and explains why it matters that you understand it clearly.
This isn’t a test of effort or commitment. It’s about precision. The compact is funded to produce results — verifiable, measurable outputs. Your job is to be clear about which of those results you are responsible for.
Activities are what you do. Outputs are what you deliver.
An activity is something you do: a meeting, a review, a site visit, a report, a training session. Activities consume time, people, and money. They are necessary — but they are not what the compact is funding.
An output is something you produce: a signed contract, a certified payment, an approved environmental plan, a section of road handed over to government, a system operating as designed. Outputs are verifiable, measurable, and defined in the project logic.
- Attending a procurement review meeting
- Reviewing a contractor’s monthly report
- Conducting a site inspection
- Preparing a payment certificate
- Running a stakeholder consultation
- A signed, compliant contract awarded
- A certified and disbursed payment
- Works section accepted and handed over
- An approved resettlement action plan
- A verified M&E baseline dataset
Activities can happen without outputs. A team can attend every meeting and travel to every site — and still fail to deliver. When the compact ends, MCC doesn’t ask how many meetings you attended. It asks: was the output delivered, on time, to spec?
What this looks like in different roles
The outputs you are responsible for depend on which division you work in and which role you hold. Here are examples across the MCA — pairing a common activity with the output it is meant to produce.
- PProcurement: Preparing and issuing a Request for Proposals → a signed, compliant contract awarded to a qualified firm
- PMProject Management Team: Attending weekly site meetings → works delivered on schedule, to specification, and accepted
- FFinance: Reviewing and processing a payment certificate → a compliant disbursement made within the required period
- EESP: Conducting an environmental compliance site inspection → a verified ESMP being implemented; issues logged and resolved
- MM&E: Collecting beneficiary data in the field → a validated indicator dataset, on time and to MCC data quality standards
The pattern is the same in every case: the activity is the work; the output is the result that activity is meant to reliably produce.
Construction outputs and non-construction outputs
Not all compact projects work the same way. The MCA manages two distinct types of implementation contracts, each producing different kinds of outputs.
- CConstruction contracts produce physical infrastructure: roads, irrigation systems, water networks, buildings. The output is a completed, verified, and handed-over asset that meets a defined specification.
- PPolicy and Institutional Reform (PIR) contracts cover all non-infrastructure projects — service delivery, technical assistance, and institutional strengthening. Outputs are less physical but equally defined: a functioning registry system, a trained inspectorate, a reform implemented and operational.
Whether you work on a construction or PIR contract, your role is still measured by outputs — not effort. The output types look different, but the accountability question is the same: was the defined deliverable produced, to the required standard, within the required time?
What is your output?
Before you move on, take a moment to think about your own role. Not what you do day to day — but what you are ultimately responsible for producing.
“My role exists to deliver ___________.”
If you can complete that sentence with something specific and measurable, you are thinking about your role correctly. If the answer is vague — “I support the team” or “I handle the procurement process” — it’s worth pressing further.
In Unit 3 you’ll find role profiles that answer this question for the main positions across the MCA. Starting to think about it now will make those profiles land more clearly.
The compact doesn’t pay for processes. It pays for results. Every role in the MCA connects to a specific set of outputs that, together, add up to the project objective. Knowing yours is the starting point.
What you’ve covered in this unit
- ✓Activities are what you do. Outputs are what you produce — verifiable, measurable results the compact is funded to deliver
- ✓Activities can happen without outputs. What gets measured at compact end is whether outputs were delivered on time and to standard
- ✓Every MCA role connects to specific outputs — whether in procurement, finance, the Project Management Team, ESP, or M&E
- ✓Both construction and PIR contracts produce defined outputs — the accountability standard is the same for both
Upstream and downstream — how your outputs depend on inputs from others, and how your work in turn enables other teams to do theirs. Understanding your place in the chain is part of doing your job.