| name | giz-eu-local-procurement-response |
| description | Use when responding to GIZ local procurement, EU/BMZ/GIZ tender packs, AVB/local application requirements, two-zip submissions, GIZ technical grids, self-declarations, price schedules, or GIZ clarification protocols. |
| metadata | {"portable":true,"compatible_with":["claude-code","codex"]} |
GIZ EU Local Procurement Response
Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178.
Overview
Use this skill to make GIZ local procurement failures structurally hard to miss. It turns a GIZ tender pack into a compliance matrix, eligibility verdict, two-envelope submission architecture, page-budgeted concept plan, and rejection-risk register before proposal drafting starts.
This skill is built from the GIZ 7000012724 EU-EAC DEEP tender evidence, but it is reusable for GIZ local tenders with similar application requirements. For 7000012724, remember the decisive constraints: technical 30 percent, personnel 70 percent, 500 technical-point floor, two separate zip folders, no price in the technical bid, two-page concept excluding CVs, CVs of four pages or less, and mandatory eligibility evidence.
Use When
- The buyer is GIZ, a GIZ-implemented EU/BMZ programme, or the tender pack includes GIZ AVB/local application requirements.
- The pack has a GIZ technical grid, self-declaration, price schedule, two-envelope or two-zip submission rule, or technical threshold.
- You need a bid/no-bid, compliance, submission, or final readiness review for a GIZ tender.
Do Not Use When
- The tender is World Bank, UNDP, AfDB, PPDA, open commercial, or another donor with its own procurement rules.
- You only need marketing copy, credentials text, or generic methodology prose.
- The tender pack has not been read. Do not infer GIZ rules from memory.
