A civil engineer needs a controlled site plan, building elevations, development statistics and confirmed service interfaces from the architect. These inputs allow grading, servicing and stormwater design to use the same geometry and assumptions as the rest of the application.
Site and building geometry
The architectural base should identify building footprints, entrances, loading areas, parking, fire routes, curbs, walls and other fixed elements. Proposed finished-floor elevations, threshold elevations and basement limits are essential for grading and gravity service checks.
Development statistics such as use, floor area, unit count, occupancy and building height support water and sanitary demand estimates. Roof areas and drainage zones support stormwater calculations.
Service interfaces
The civil and mechanical teams need agreed water, fire, sanitary and storm exit locations, sizes and elevations. Roof-drain strategy, sump or foundation drainage and unusual process discharges should also be identified. These decisions should be tracked when the building changes.
Park architecture may include washrooms, change rooms, fountains, splash-pad equipment, irrigation controls and maintenance spaces. The civil engineer needs demand and discharge information for each facility, plus the accessible route and entrance elevations that the grading must meet.
Bous Engineering coordinates these inputs through development application engineering packages. Read why civil engineering should start before the site plan is final and how landscape and civil conflicts arise.
Key takeaway
Exchange dated, controlled design files and a short interface schedule—not screenshots or verbal assumptions. Reconfirm elevations, statistics and building exits whenever the architectural plan changes.
Bous Engineering supports servicing, stormwater, grading and municipal approval assignments across Eastern Ontario.