Define the project outcome
Record client type, site role, primary users, activity mix, approximate area and intended operating model.
RIDEspan · SPECIFICATION & PLANNING CENTRE
RIDEspanActive Recreation SystemsA LUTHVAR sports brandMove from an idea to a controlled project brief.
This workflow is designed for architects, landscape architects, councils, schools, developers and procurement teams who need to define the project before exact RIDEspan models are released.
Select the RIDEspan pathway
Use PUMP, FLOW, STREET, SKILLS or PARK as the starting system — not a supplier model number.
Fix the planning envelope
Allow for riding space, entry/exit, waiting, circulation, supervision, spectators and future expansion.
Set the evidence schedule
List every technical document that must be received before procurement: construction, surfaces, anchoring, loads, standards, maintenance, warranty and spares.
Separate supply from local works
Define survey, civil works, base/slab, drainage, foundations, installation, electrical work, landscape and approvals.
Coordinate public realm
Add shade, seating, hydration, bike parking, lighting, paths and amenities without creating rider conflicts.
Freeze the equipment schedule
Only after exact product evidence and project interfaces are accepted should the final module schedule be released.
Prepare handover
Include drawings, manuals, inspection requirements, replacement parts, warranty, spares and responsibility matrix.
Minimum specification inputs
What a useful project file should eventually contain.
01Project / site description
02Selected RIDEspan pathway and purpose
03User groups and discipline assumptions
04Site plan and available envelope
05Activity / progression zoning
06Civil and base responsibility
07Exact product schedule
08Technical evidence register
09Installation scope
10Inspection and maintenance schedule
11Warranty and spares
12Freight / packing / delivery interface
Project handoff