Start Project BriefDevelopment & Humanitarian Infrastructure · Free programme-delivery handbook
This handbook brings the main planning decisions into one sequence. It is designed for teams managing more than one building or one shipment and focuses on the interfaces that commonly fall between procurement, technical design, logistics and local delivery.
Record the population or users, infrastructure types, target capacity, permanence, project phases, funding / procurement pathway, destination and operating model. Build the programme around service outcomes rather than the supplier's catalogue.
Issue the same room schedules, dwelling mix, performance criteria, service requirements, documentation expectations, climate and logistics information to competing suppliers. Mark unknown criteria instead of allowing different assumptions.
Confirm legal identity, factory role, engineering capability, quality control, normal production range, capacity, project references, packing, installation support, warranty and spare-parts process.
Normalise structure, finishes, MEP, foundations, local works, freight, unloading, installation, technical documents, supervision, spares and warranty before comparing headline price.
Validate the design, factory quality, packing, shipping, local assembly, utility connections, user feedback and maintenance process before releasing large repeat batches where programme risk justifies it.
After pilot or design approval, establish the approved drawings, specifications, bill of materials, finish schedule, inspection plan, packing standard and process for approving any later change.
Manufacturing batches should follow foundation readiness, utility progress, freight capacity, storage and installation sequencing. Factory output alone does not determine the achievable programme rate.
Close the programme with as-supplied drawings, manuals, warranties, spare-parts lists, inspection or commissioning records, operator information and a named long-term maintenance owner.
Comparison reference
| Planning criterion | Main output | Key risk to close |
|---|---|---|
| Needs + programme brief | Defined uses, quantities, users and phases | Buying products before defining the service need |
| RFP + supplier qualification | Comparable bids from qualified suppliers | Different assumptions hidden inside prices |
| Pilot / design validation | Approved repeatable configuration | Scaling unresolved pilot issues |
| Production + QA | Controlled batches and records | Unmanaged changes or quality drift |
| Freight + site delivery | Sequenced receiving and assembly | Site not ready for incoming cargo |
| Handover + operations | Records, spares and maintenance ownership | Infrastructure delivered without long-term support |
Not every project requires the same number of stages. The programme team should scale controls to project value, technical complexity, safety risk and procurement requirements.
Reference this resource
Link to the live page rather than a saved copy so readers reach the current Apollo planning resource and its latest product and planning links.
apollonzglobal.com/knowledge-centre/development-humanitarian-infrastructure/development-programme-delivery-handbookapollonzglobal.com/knowledge-centre/development-humanitarian-infrastructure/development-programme-delivery-handbook#comparison-matrixMove from knowledge to project