Ppda Uganda

Uganda PPDA Procurement Framework

Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.

Use When

• Use this skill when the solicitation follows Uganda PPDA procurement rules.
• Load it before drafting when you need form, scoring, threshold, or compliance guidance.

Do Not Use When

• The task only needs sector-domain framing without procurement mechanics.
• A different procurement framework clearly applies.

Required Inputs

Workflow

1. Confirm that PPDA procurement applies from explicit cues in the solicitation.
2. Read this skill and the local references to understand forms, scoring, procedures, and constraints.
3. Map those requirements into the numbered proposal section skills before drafting.
4. Draft to maximize technical quality without creating compliance risk.
5. Check the final output against thresholds, form placement, and submission rules.

Stop condition: Stop when proposer identity, controlling framework, mandatory form, sector fit, current rule, or load-bearing evidence remains unresolved.

Recovery: Record the gap and owner, seek clarification or current evidence, and return only the separable proposal content that remains supportable.

Quality Standards

• Treat PPDA instructions as hard constraints, not optional style guidance.
• Keep terminology, form names, and evaluation assumptions aligned to the actual solicitation.
• Optimize for evaluator behavior where the framework supports it.

Anti-Patterns

• Do not rely on generic public-procurement assumptions when the PPDA materials give exact instructions.
• Do not ignore eligibility checks, pass/fail gates, or form requirements.
• Do not mix PPDA assumptions with World Bank, AfDB, or UN rules.
• Treating a neighbouring sector or framework as interchangeable. Fix: identify the controlling rule and primary outcome.
• Adding terminology without changing a delivery choice. Fix: link each term to method, risk, output, or evaluation criterion.
• Presenting an unverified current rule or statistic as settled. Fix: cite and date the source or mark it not assessed.
• Ignoring a missing mandatory input. Fix: stop the affected claim and assign an evidence owner.
• Letting sector or identity framing contradict methodology, staffing, schedule, or price. Fix: reconcile all affected sections before release.

Outputs

Evidence Produced

Capability Contract

This skill may read supplied profiles, solicitations, ToRs, approved references, and proposal drafts and may prepare routing guidance or draft content within the authorised workspace. Review is read-only by default. It must not invent credentials, certify compliance, submit a bid, accept terms, publish, disclose confidential information, or change source records without explicit authority.

Degraded Mode

If the solicitation, profile, current procurement source, sector evidence, network, or reviewer is unavailable, provide the narrowest useful qualified routing or draft. Mark the missing check not assessed, omit unsupported credentials, thresholds, dates, or compliance claims, and identify the evidence owner. An unassessed requirement is never a pass.

Decision Rules

Worked Example

A solicitation requires ppda evaluation route, but one controlling input is missing. The proposal team applies this rule: Use the solicitation's method, mandatory documents, evaluation stages, forms, and approvals; flag any ambiguity for clarification. It records the gap and owner, withholds the affected assurance, and proceeds only with content that can be verified. This avoids administrative rejection or incorrect scoring response.

References

• Proposal skill router — orchestration, profile, reasoning, and release gates.

• Local references/ files for the PPDA Act, forms, procedures, and evaluation mechanics.
• ../SKILL.md to combine framework and sector context.

This skill provides the evaluation methodology, scoring rules, form structures, and procedural requirements that govern all public procurement in Uganda under the PPDA Act (Cap 205). Read this before writing any section of a Uganda government-funded proposal.

When to Read This Skill

• The procurement is managed by a Ugandan Procuring and Disposing Entity (PDE)
• The RFP/bidding document references the PPDA Act, 2003 or PPDA Regulations
• The assignment uses Technical Compliance, Quality and Cost Based, Quality Based, Least Cost, or Fixed Budget selection
• You need to understand how PPDA evaluators score to maximise points
• The proposal must comply with PPDA standard forms and procedures

Selection Methods for Consultancy Services

Evaluation Methods for Supplies, Works, and Non-Consultancy Services

The Two-Envelope Procedure

All QCBS, QBS, LCS, and FBS procurements use two sealed envelopes:

1. Envelope 1: Technical Proposal — opened first, evaluated and scored
2. Envelope 2: Financial Proposal — remains sealed in secure storage until technical evaluation is approved by Contracts Committee; only opened for bidders scoring above the minimum technical qualifying mark

Three-Stage Evaluation Process

Stage 1: Preliminary Examination (Pass/Fail)

Every bid/proposal is checked for:

• Eligibility Criteria — as per bidding document (C/NC per criterion)
• Administrative Compliance Criteria — as per bidding document (C/NC per criterion)

Any "NC" on any criterion eliminates the bid entirely. There is no recovery from a preliminary examination failure.

What to ensure:

• All eligibility documents present and valid
• Correct format, signed, sealed, submitted on time
• Bid securing declaration included
• Every administrative requirement in the bidding document addressed
• Beneficial ownership declaration form completed

Stage 2: Detailed Technical Evaluation (Merit Points or R/NR)

For Technical Compliance method (Form 14): Each bid assessed as Responsive (R) or Non-Responsive (NR) against the technical specification. Non-responsive bids eliminated.

For QCBS method (Forms 16, 24): Merit point system with:

• Up to 5 main criteria (A through E), each with sub-criteria
• Maximum total score: 100
• Minimum qualifying mark stated in invitation — proposals below this are eliminated regardless of price
• Multiple evaluators score independently; the average is used
• Strengths and weaknesses of each proposal are formally documented
• Large differences between evaluators' scores must be justified

Stage 3: Financial Comparison

For Technical Compliance (Form 14):

• Lowest price among eligible, compliant, substantially responsive bids wins
• Corrections for arithmetic errors, discounts, adjustments, currency conversion, margin of preference

For QCBS (Forms 15, 26):

• Lowest evaluated price receives a financial score of 100
• All others scored: (Lowest price / Your price) x 100 = Financial Score
• Combined: Total Score = (Tech Score x Tech Weight%) + (Financial Score x Financial Weight%)
• Highest total score ranked first

Financial Scoring Formula (QCBS)

Financial Score = (Lowest Evaluated Price / Your Evaluated Price) x 100

Total Score = (Technical Score x Technical Weight%) + (Financial Score x Financial Weight%)

Example at 80/20 split:

• Firm A: Tech 85, Price lowest → Financial 100 → Total = (85 x 0.8) + (100 x 0.2) = 88.0
• Firm B: Tech 90, Price 20% higher → Financial 83.3 → Total = (90 x 0.8) + (83.3 x 0.2) = 88.7
• Firm B wins despite higher price, because technical quality overcame the price difference

Post-Qualification (where required)

The best evaluated bidder may be assessed against qualification criteria stated in the bidding document to confirm capacity and resources to execute the procurement. Outcome: qualified or not qualified.

Standard Procurement Timeline (Quotation Method)

Contract Management (Form 49)

After award, a Contract Management Plan is prepared covering:

For Consultancy Services:

• Contract duration, start date, completion date
• Deliverables table with expected dates
• Payment schedule (percentage-based, lump sum, or time-based)
• Linked to specific deliverables

For Supplies:

• Deliverables, guarantees (performance + advance payment), inspection, installation, warranty
• Stage payment certificates tracked

For Works:

• Guarantees, interim payments, retentions, defects liability period, performance certificate
• Taking over certificate, extension of time, liquidated damages

Performance Security

Uganda PPDA uses a Performance Securing Declaration rather than traditional bank guarantees:

• Provider declares acceptance that failure to perform or default-triggered termination results in 3-year suspension from all Government procurement
• Valid until completion of all obligations and defects liability period
• Signed by authorised representative of the provider

Negotiations (Form 45)

When negotiations are required, the PDE prepares a Negotiations Plan with:

• Issues for negotiation
• Objectives (what the entity aims to achieve)
• Negotiation parameters (acceptable ranges, limits, walk-away points)

Negotiations team is named with positions and departments; Chairperson identified.

ESHS Requirements (Quotation Method)

All bidding documents must include Environmental, Social, Health and Safety requirements, evaluated on a pass/fail basis:

• Sustainable procurement criteria (energy saving, ISO 14001, marginalised groups support)
• H&S competence (policies, accident records, training, certifications)
• Code of Conduct (signed by each worker) covering GBV/SEA prevention, child protection, non-discrimination, community engagement

Reference Files

Load these references for detailed procedural requirements: