Skip to main content
Apollo NZ Global

Apollo professional resources · reusable project tools

Procurement templates that keep the important project questions visible.

These templates are intentionally practical. Copy them into a project workspace, download them as CSV, or print the page for a working session. They are designed to make scope, technical information, logistics and local responsibilities easier to organise before quotation or procurement.

01International Project Procurement Checklist02Technical Submittal Register Template03International Project RFP Checklist

01 · Procurement checklist

International Project Procurement Checklist

Use this before comparing project quotations. It keeps scope, technical information, commercial terms, logistics and destination responsibilities visible so the whole project package can be reviewed consistently.

Review areaRequirement / questionStatusNotes / owner
Project briefDestination, site, intended use, dimensions, quantities and programme are recorded.Open
Project briefDrawings, BOQ, schedules or marked-up project information are attached where available.Open
Product scopeQuoted model, material, finish, configuration, accessories and exclusions are explicit.Open
Product scopeProject-dependent requirements are separated from current product information.Open
Technical documentsRequired datasheets, drawings, reports, certificates and calculations are listed.Open
Technical documentsDocuments are checked against the exact quoted configuration where relevant.Open
CommercialLead time, quote validity, payment terms, warranty and spare-parts pathway are recorded.Open
CommercialSamples, mock-ups, engineering, tooling or inspection charges are identified.Open
QualitySample / mock-up approval and any agreed inspection requirements are defined where needed.Open
LogisticsPackaging, crate / bundle dimensions and shipment method are confirmed.Open
LogisticsHandover point, importer, customs, onward freight, unloading and storage responsibilities are assigned.Open
Local project scopeFoundations, civil works, electrical work, local engineering, installation and approvals are assigned.Open
HandoverPacking records, manuals, warranty, spare-parts list and final project documents are included in handover.Open

This checklist is a project-control aid, not a substitute for the written contract, destination requirements or professional technical review.

02 · Technical submittal register

Technical Submittal Register Template

Use this to track what has been requested, received and reviewed for the exact project configuration. It is structured around applicability and revision rather than the size of the document set.

Document / submittalRequired?File / referenceRevision / dateStatusApplicability / review notes
Product datasheet / specificationYesRequested
Project / shop drawingsProject dependentRequested
Material / finish scheduleProject dependentRequested
Material certificatesProject dependentRequested
Independent test reportsProject dependentRequested
Certification / product listingProject dependentRequested
Structural calculationsProject dependentRequested
Wind / load evidenceProject dependentRequested
Fire-performance evidenceProject dependentRequested
Electrical / controls documentationProject dependentRequested
Installation manualYesRequested
Maintenance / care manualYesRequested
Warranty documentYesRequested
Sample / finish approvalProject dependentRequested
Mock-up approval recordProject dependentRequested
Inspection / quality recordProject dependentRequested
Packing list / crate registerYesRequested
Spare-parts scheduleProject dependentRequested
Final as-supplied document setYesRequested

Required documents vary by product, destination, contract and project stage. A document should only support claims that fall inside its actual model, configuration, material, test and revision scope.

03 · International RFP checklist

International Project RFP Checklist

Use this when sending Apollo a larger international project. It gives enough context to review products, scope and destination requirements from a clear project brief rather than a vague product list.

RFP sectionInformation to includeStatusNotes / attachment reference
Project identityProject name, organisation, country, city / island, site and main contact.Open
Project stageConcept, design development, tender, procurement, construction or replacement / upgrade.Open
Project typeResort, sports facility, school, church, public realm, commercial, industrial or other.Open
Drawings / BOQPlans, elevations, sections, schedules, BOQ or marked-up product requirements.Open
Product scopeRequired product families, quantities, dimensions and known configuration preferences.Open
Performance criteriaKnown wind, seismic, fire, electrical, accessibility, acoustic or other criteria supplied by project professionals.Open
Climate / exposureHeat, UV, coastal salt, rainfall, cyclone / hurricane, snow, dust or other material conditions.Open
Finish requirementsColours, coatings, materials, samples, mock-ups and architectural finish expectations.Open
Technical submittalsList the evidence, drawings, calculations, certificates or BIM / CAD required for review.Open
ProgrammeTender date, decision date, target order date, required delivery window and project opening / completion date.Open
Freight destinationNamed port, depot or final delivery point where known.Open
Receiving routeImporter / receiver, onward transport, road / island access, unloading, crane and storage constraints.Open
Local project teamArchitect, consultant, engineer, main contractor, installer or specialist roles where appointed.Open
Local worksFoundations, civil, services, electrical, installation and statutory responsibilities.Open
Commercial requirementsQuotation currency, validity, packaging, warranty, spare parts and any tender return format.Open
AttachmentsPhotographs, surveys, geotechnical information, existing-system data or other relevant project evidence.Open

You do not need every field resolved before sending an RFP. Unknown items should be marked unknown so they remain visible rather than being filled with assumptions.

How to use these resources

Templates organise the review. They do not replace project-specific technical information.

Use current information

Match technical information to the current product, configuration, document and revision where applicable.

Keep unknowns visible

Mark unresolved items as open, unknown or project-dependent rather than allowing assumptions to disappear into the quotation.

Assign responsibility

Name who owns the next action: Apollo, consultant, importer, contractor, installer or client-side project team.

Continue the professional workflow

Move from checklist to project-ready information.

International procurement guide International documentation guide Specification & Tender Guide Upload project documents Open Global Project Builder
Project