The MCC–MCA relationship: oversight without micromanagement
The relationship between MCC and the MCA is one of the most frequently misunderstood aspects of compact implementation. Staff either over-rely on MCC — treating every decision as requiring MCC input — or under-engage it, proceeding with decisions that require MCC no-objection. Both mistakes cost time and create risk.
This unit clarifies exactly what MCC controls, what the MCA decides, and how the no-objection process works in practice. It takes about 12 minutes.
Distinguish between decisions that require MCC no-objection and those that belong to the MCA, describe how the no-objection process works, and identify the most common points of friction in the MCC–MCA relationship.
What MCC controls vs. what the MCA owns
MCC is an oversight body, not a co-implementer. The compact gives MCC specific approval rights over defined categories of decisions. Everything outside those categories belongs to the MCA to decide and act upon independently.
- ✓Procurement plans and significant modifications
- ✓Bidding documents at each stage
- ✓Bid evaluation reports and contract award recommendations
- ✓Significant program modifications (scope, budget, design)
- ✓Environmental and Social Management Plans
- ✓Senior MCA staff appointments
- ✓Disbursement requests
- ✓Day-to-day contract administration (Procurement) and contract management (Project Teams) within approved scope
- ✓Contractor instructions within approved scope
- ✓Internal management and staffing decisions
- ✓Operational scheduling and sequencing
- ✓PIR deliverable review and acceptance
- ✓Stakeholder engagement and communications
- ✓Routine financial management within approved budgets
When in doubt about whether a decision requires MCC no-objection, the answer is to ask Legal — not to proceed and hope, and not to send everything to MCC unnecessarily.
How the no-objection process works
MCC’s oversight mechanism for procurement and major decisions is the no-objection process. A no-objection is MCC’s written confirmation that it has reviewed a submission and has no objection to the MCA proceeding. It is not an approval in the traditional sense — MCC is not taking ownership of the decision. The MCA remains responsible for the outcome.
- 1MCA prepares the submission. The relevant division compiles the required documents — bidding documents, evaluation report, ESMP, or other instrument — in the format MCC requires. Incomplete or poorly prepared submissions are the most common cause of no-objection delays.
- 2CEO or designated authority submits to MCC. The submission goes to MCC’s Country Director or designated counterpart. The MCA should include a clear cover note summarizing what is being submitted and what decision or action it enables.
- 3MCC reviews within its standard timeframe. MCC has defined review periods for different submission types — typically 5 to 21 business days depending on complexity. The MCA should know these timeframes and build them into procurement and implementation schedules.
- 4MCC issues no-objection or raises questions. If MCC has questions or concerns, the MCA must respond before the no-objection can be issued. Each round of questions resets the review clock — this is where most delays accumulate.
- 5MCA proceeds once no-objection is received. The MCA must not proceed with a no-objection-required action before the no-objection is in writing. Proceeding without no-objection is a compliance violation regardless of how confident the MCA is about the outcome.
Where the MCC–MCA relationship most commonly breaks down
Most friction in the MCC–MCA relationship is predictable and avoidable. It tends to cluster around the same four patterns across compacts.
- !Poor quality submissions that generate multiple rounds of questions. A submission that arrives incomplete, inconsistent with MCC guidelines, or lacking required documentation forces MCC to ask questions — each of which resets the clock. The MCA controls submission quality entirely. Investing in quality upfront saves weeks downstream.
- !MCA proceeds before no-objection is received. Usually driven by schedule pressure. Always a compliance violation. When discovered — and it usually is discovered — it creates a retroactive compliance problem that consumes far more time to resolve than waiting for the no-objection would have.
- !Disagreements about program direction escalated too late. MCC and the MCA sometimes have different views on program design, scope, or approach. These disagreements are legitimate and manageable — if raised early. Raised late, when significant resources have already been committed, they become crises.
- !MCA treats MCC as the decision-maker for MCA decisions. Asking MCC to decide things the MCA is empowered to decide creates unnecessary delay and signals institutional weakness. MCC will often push the decision back — which was the right answer — but time has been lost and the relationship is strained.
What a productive MCC–MCA relationship looks like
The MCA teams that maintain the most productive relationships with MCC share a consistent set of practices. None of them are complicated — they require discipline, not genius.
Submit complete, well-prepared documents the first time. Build MCC review periods into every procurement and implementation schedule. Flag emerging problems to MCC early — never surprise MCC with bad news. Distinguish clearly between what requires MCC input and what the MCA can and should decide independently. Maintain consistent, professional communication at the working level between MCA divisions and their MCC counterparts.
Surprising MCC with problems that were visible weeks earlier. Submitting incomplete documents and expecting MCC to fill the gaps. Proceeding without no-objection. Treating MCC oversight as an obstacle rather than as part of the accountability structure the compact was built on. Once trust is damaged, MCC scrutiny increases — which slows everything down further.
What you’ve covered in this unit
- ✓MCC is an oversight body, not a co-implementer. It has defined approval rights over specific categories of decisions; everything else belongs to the MCA
- ✓The no-objection process is MCC’s confirmation that it has reviewed a submission — not that MCC is taking ownership of the outcome. The MCA remains responsible
- ✓The MCA must never proceed with a no-objection-required action before the no-objection is received in writing
- ✓Most MCC–MCA friction is caused by poor submission quality, premature action, late escalation of disagreements, and confusion about decision authority
- ✓The strongest MCA–MCC relationships are built on complete submissions, early flagging of problems, and clear separation between MCC oversight and MCA operational decisions
Fiduciary obligations — what they are, why they apply to every staff member regardless of role, and what the consequences of fiduciary failure look like in a compact context.