Detailed planning by public-sector facility type
Use the guide that best matches the actual facility. The same nominal capacity can lead to different access, engineering, procurement, acceptance and operating requirements.
Municipalities and local communities
Connect project need, facility data, funding, procurement, acceptance and operational responsibility in one planning workflow.
Open sector guide →EducationSchools
Capacity, safe access, accessibility, organised group movement and project scope for education facilities.
Open sector guide →Early educationKindergartens and preschools
Young children, adult supervision, group movement, sanitary needs and operational readiness.
Open sector guide →Higher educationUniversities and dormitories
Day and night occupancy, multiple campus buildings, student routes and dormitory scenarios.
Open sector guide →HealthcareHospitals and healthcare facilities
Patient categories, mobility, continuity of care and project-specific engineering requirements.
Open sector guide →Public buildingsAdministrative buildings
Employees, visitors, peak occupancy, wayfinding, procurement and operational responsibility.
Open sector guide →InfrastructureCritical infrastructure
A dedicated planning context for essential public infrastructure projects with project-specific review.
Open sector guide →A practical project sequence
- Confirm the facility, users and required capacity.
- Collect site or building source data and identify constraints.
- Determine the appropriate regulatory and technical solution through project-specific review.
- Structure the base budget and identify what is not yet priced.
- Separate unit metrics, logistics, risk reserve and lifecycle scenarios from the confirmed base budget.
- Define the funding model and any required co-financing.
- Build a realistic project timeline.
- Prepare a procurement specification that clearly separates supply, construction, installation and engineering scope.
- Compare like-for-like offers and review supplier evidence against the actual offered configuration.
- Define commissioning, documentation and acceptance criteria before award.
- At handover, close the delivered scope, defects and documents against the contract.
- After handover, separately verify operational readiness before treating the facility as routine operations and maintenance responsibility.
- During operation, keep factual checks and defects in a traceable lifecycle: follow-up plan → issue-linked work → explicit resolution review → retained history.
Keep public project costs traceable
Expected procurement value, base project budget, logistics, contingency, maintenance and total cost of ownership answer different questions. Keeping them separate makes it easier to explain what is already supported by source data and what remains a planning scenario.
Acceptance connects procurement to operation, but it does not prove ongoing readiness
A completed procurement does not by itself prove that every contracted deliverable has been handed over. Use the acceptance checklist to separate the contractual result, commissioning evidence, documents, defects and warranty responsibilities. Then use a separate operational-readiness check for access, engineering systems, documentation and assigned responsibility after handover. Once operations begin, use the factual operations log to retain open issues, follow-up plans, linked work and explicit resolution history rather than treating a repair entry as automatic closure.
For donors and international programmes
A shared project passport helps separate confirmed project facts from assumptions that still need technical, legal or financial validation. This makes early screening and communication with Ukrainian beneficiaries more efficient and keeps funding discussions tied to a traceable project baseline.