Apollo project brief checklist · reference standard
Build a project brief Apollo can actually review.
You do not need every answer before contacting Apollo. Start with the information you have. A stronger brief reduces avoidable back-and-forth, helps separate product supply from local project work and gives Apollo a better basis for technical review and manual quotation.
Project basics
Project name / reference
Site address and destination country
Organisation and main contact
Residential, school, council, club, hospitality, commercial or other
Target timing / required delivery window
Dimensions + site
Overall available area or opening dimensions
Existing base, slab, deck, structure or surface
Site access for unloading / handling
Photos from several angles
Exposure: coastal, high wind, cyclone/hurricane, snow or other relevant climate conditions
Use + outcome
What the product needs to achieve
Primary users / sports / activities
Expected frequency and intensity of use
Permanent, seasonal, relocatable or future-expandable requirement
Any automation, lighting, camera or smart-control requirement
Supply + destination
Required quantity and product configuration
Freight destination: site, depot or port
Unloading / lifting constraints if relevant
Known local technical or compliance requirements
Any required product documentation for the purchaser's project team
Apollo Project Brief Standard
Start simple. Add detail only when it changes the decision.
The project can enter Apollo's review pathway before every technical answer exists. This table separates the minimum useful brief from information that strengthens selection and information that usually belongs later in specification, tender or procurement.
| Brief area | Minimum useful brief | Stronger first review | Project-specific / later stage |
|---|---|---|---|
| Project identity | Project name or working reference, organisation, main contact and broad project type. | Project stage, procurement route and the outcome the project team is trying to achieve. | Tender reference, consultant team, approval pathway or other formal project controls where they already exist. |
| Site + dimensions | Country / destination and the best available overall dimensions, opening size or usable area. | Drawings, marked-up photos, existing base or structure, access and relevant climate / exposure information. | Survey information, structural details, service layouts or site-specific engineering inputs when the selected system requires them. |
| Use + performance | What the product must do, who will use it and whether the environment is residential, commercial, public, sport, hospitality or another application. | Operating frequency, intensity, maintenance expectations, weather exposure and the priorities that matter most. | Known project standards, loads, acoustic, fire, accessibility, wind, electrical or other verified criteria supplied by the appointed project professionals. |
| Product + supply scope | Product family or requirement, approximate quantity and any obvious options or accessories. | Preferred configuration, finish, controls, complementary systems and what needs to be included in Apollo's product package. | Approved alternates, exact interfaces, specification clauses and controlled schedules once the project reaches tender or procurement. |
| Freight + receiving | Destination country and city / region, plus whether the likely handover is site, depot or port if known. | Receiving party, site access, unloading or lifting needs, storage constraints and any known importer / customs arrangement. | Final handover point and freight responsibilities as defined in the written quotation and receiving plan. |
| Programme + documents | When the project is being planned and any required delivery window. | Tender date, decision date, planned order date and the documents the project team expects to review. | Controlled revision schedule, final approval documents and shipment / handover records for the confirmed project package. |
This is a briefing standard, not a requirement to complete every field before contacting Apollo. The exact information needed depends on the product, project stage, destination and technical risk.
Upload project filesSpecification & Tender GuideSpecification ToolkitTechnical Document GuideGlobal Project ReadinessProject toolsProduct Finder
Send a structured project brief