Route 01 · Documents ready
I already have an RFP, BOQ, drawings or specifications.
Upload the project documents and add the country, target timing and any important scope notes.
Upload project documentsRHELGAN · Project Brief
Start with the information you have. The brief can become more precise as the project develops.
Early-stage programmes rarely arrive with every engineering and procurement question resolved. Give us the known project conditions first; the next questions can then be structured around the actual programme rather than a generic product enquiry.
Route 02 · Early-stage project
I have the requirement, but the technical brief is still being developed.
Use the dedicated RHELGAN brief below. Unknown answers can stay unknown; the purpose is to identify the right next technical questions.
Open RHELGAN briefUseful starting information
Eight inputs make the first technical conversation much more useful.
Country + site
Country or territory, known site location, access constraints and whether the project is urban, remote, island or field-based.
Programme scale
Approximate homes, people, beds, classrooms, staff or other useful capacity information.
Buildings required
Housing mix, accessible housing, schools, clinics, community/worship buildings, administration, camps, WASH or other facilities.
Climate + hazards
Known wind/cyclone, seismic, coastal, flood, rainfall, heat, corrosion or other site conditions.
Water + wastewater
Known water source, municipal connection, bore/seawater options, wastewater connection, discharge or reuse expectations.
Power
Grid availability, critical loads and whether solar, battery or generator resilience is being considered.
Logistics + installation
Preferred port, road/site access, lifting capability, local labour and any programme phasing requirements.
Procurement + timing
RFP/tender status, target dates, donor or client requirements and known technical documentation needs.
Complete-community starting scales
Already know the approximate number of homes?
Use one of the RHELGAN planning scales as the starting point. These are programme frameworks, not fixed bills of materials.
Structured project intake
Turn the requirement into one controlled RHELGAN brief.
01
Project + contact
Enough information to identify the project and contact the right person.
02
Scale + systems
Planning scale is a starting point only; final facilities are sized from the actual brief.
03
Site + infrastructure
Unknown is acceptable. These fields stop critical utility and logistics questions being discovered too late.
04
What are you trying to deliver?
Describe the project outcome, known quantities, constraints and anything already decided.
Submitting a brief creates no purchase commitment. RHELGAN uses the information to structure the next technical and commercial questions.
Scope control
RHELGAN coordinates the supply brief. It does not hide the project responsibilities.
Local professional services, statutory approvals, humanitarian or donor requirements, geotechnical and civil works, final engineering, installation responsibilities, testing, commissioning and operations are identified as project interfaces unless explicitly included in a written Apollo scope.