Site plan review inside Tramview Heights with GenAnywhere
An illustrative walkthrough of a hillside district review, from slope and massing to a clear action list.
Tramview Heights is a composite hillside district used here to show how a review sequence works. The questions it raises are ordinary ones: how buildings meet the slope, how frontages meet the street, and how people walk between them. A map-based 3D site scene gives a review team one shared object to inspect, which is often the difference between a useful meeting and a long argument. This site plan review follows a sequence that a real team could repeat on another hillside parcel.

1 Begin with slope and street grid
A hillside site punishes assumptions. Grades change quickly, and a street that looks continuous on a plan may step or bend in reality. Starting the review with terrain and the grid prevents later proposals from floating above the ground.
1.1 Trace grades along the main street
Follow the main street from the lower edge to the upper edge and note where the slope steepens. Those points affect access, drainage, and the height of buildings that front the street. In the scene, rotate the view to see the grade rather than relying on contours alone. Mark the steep stretches so the design team knows where retaining structures may be needed. If the model and the survey disagree, the survey wins, and the scene should be corrected before the next review.
1.2 Note where blocks step down the hill
Blocks on a slope rarely share a single level. Note the places where one block sits higher than the next and how the transition is handled. A retaining wall, a stepped building, or a planted bank each produces a different street experience. The review should agree on which approach the plan assumes, because the answer affects both cost and character. The transition also affects how water moves across the block, which drainage engineers will need to check.
2 Check building mass against the public realm
Massing is easier to judge in context than in a spreadsheet. A tower that looks reasonable on its own can overwhelm a narrow street or leave a plaza without sunlight. The scene lets reviewers compare the proposal with the existing fabric block by block.
2.1 Compare setback gaps between towers
Look at the gaps between buildings rather than at the buildings themselves. A narrow gap can feel like a slot, while a wider one can become a usable courtyard. Compare the proposed gaps with the existing ones along the same street. Consistency is not always the goal, but a sudden change should be intentional. A gap that works at ground level may feel different higher up, so check both views.
2.2 Read frontage heights along the sidewalk
Walk the camera along the sidewalk and note how the frontage heights change. A continuous low edge with one tall element creates a different street than a row of similar towers. Reviewers can point at the specific segment that feels wrong instead of making a general complaint. That specificity makes the feedback usable. The same walk also shows where a blank wall or a service door interrupts the street. Note the segments where the height changes.
3 Review access for people arriving on foot
A site plan can look orderly and still be unpleasant to walk through. The review should follow the pedestrian route from the block edge to the front door. Small gaps in the network matter more than the overall diagram suggests.
3.1 Trace sidewalk continuity across driveways
Follow the sidewalk and note every driveway that interrupts it. A series of curb cuts turns a walk into a series of small hazards. If the plan adds more driveways, the review should ask how pedestrians will be protected. The answer may be a shared access point or a redesigned crossing. Count the driveways along the route and compare them with the pedestrian crossings. A short detour is acceptable; a blind crossing is not.
3.2 Place bus stops within a short walk
Mark the bus stops and measure the walk to the main entrances. A stop that sits just beyond a comfortable distance will be ignored, even if it appears close on the map. Check the route for crossings and shelter. Access is a practical question, and the scene makes the practical answer visible. A stop that looks close on the map may still fail that test.

4 Use the scene as a shared review surface
A review works when everyone looks at the same thing. Screenshots and separate drawings fragment the conversation. An editable scene keeps the group on one object and lets changes happen in the room.
4.1 Replace one building to test an alternative
When a reviewer questions a building, replace it in the scene and look at the result. GenAnywhere lets the team swap a building, move or rotate it, and adjust its height and type while the layers stay separate. The change is approximate and clearly labeled as a test. Even so, it answers the question faster than a new drawing, and it keeps the discussion tied to the site rather than to preference. The test does not need facade detail; a simple mass with the right height is enough. Keep the original building as a hidden group so the comparison can be repeated.
The platform builds the district from map data and keeps buildings, terrain, and vegetation in separate layers. A reviewer can hide the trees to read the street edge, or hide a block to check the route behind it. GenAnywhere also lets the team test a height change without rebuilding the block. A saved scene gives the next reviewer a clean starting point, and it can be rebuilt from map data for another block.

4.2 Keep notes verbal rather than drawn on the scene
Resist the urge to draw conclusions on the model. Notes drawn on a shared scene are easy to misread as design decisions. Keep the discussion verbal, capture the points in a list, and leave the geometry clean. The scene stays a reference for everyone, and the action list carries the decisions. A clean scene is easier to hand to a colleague who was not in the meeting.
5 Separate review findings from approvals
A review group can identify issues. It cannot approve a scheme. Zoning, building code, and engineering checks sit with other people, and confusing the roles creates false confidence. The review should end with questions and actions, not with a verdict.
5.1 Zoning interpretation rests with the local authority
Setbacks, heights, and permitted uses are interpreted by the local planning authority. The review can note where a proposal appears to conflict with the published rules. It should not declare the scheme compliant or non-compliant. Send the question to the authority or to a planning consultant with the relevant drawings and the scene view. Publish the rule reference beside the finding so the next reviewer can check it.
5.2 Engineering checks need licensed professionals
Structural, geotechnical, and drainage questions need licensed professionals. A site scene can show where a retaining wall might be needed or where water might collect, but it cannot design either. Bodies such as the Urban Land Institute publish guidance on development review practice, and local codes set the actual requirements. Keep the engineering questions on their own list. A short, specific list is more useful than a general warning, and the design team can respond to it in one pass.
6 Close the review with a clear action list
A review that ends without actions tends to repeat itself. The closing step is short and unglamorous: write down what changed, what is still open, and who owns each item. That list is the real output of the meeting.
6.1 List the changes the team accepted
Record the changes that the group agreed to test, such as a lower frontage, a wider gap, or a new pedestrian route. Mark each one as a test rather than a decision. The design team can then respond with a proposal instead of guessing what the meeting meant. Add the date and the person who raised each change, so the trail stays clear.
6.2 Assign follow-up data requests
List the data the review needs, including survey levels, boundary information, and traffic counts. Assign an owner and a date to each request. Data gaps are a common reason reviews stall, and naming them early keeps the schedule honest. A request without an owner tends to sit until the next meeting. A date is useful even when it is provisional.
6.3 Schedule the next design checkpoint
Set the next review date before the meeting ends. A checkpoint gives the team a reason to resolve the actions and a chance to see the scene again. Teams can start a district scene in GenAnywhere and use the workflow overview to plan the export. The meeting record closes when the next date is in the calendar. Put the checkpoint in the project calendar before people leave the room.
7 FAQ
FAQ-1 Is Tramview Heights a real project?
No. It is a composite example used to describe a review method, and the details are illustrative rather than drawn from a specific client or site. The questions in the walkthrough are the same ones a real hillside district would raise. Apply the sequence to your own site and replace the example with local data. The method matters more than the fictional name.
FAQ-2 Can the scene replace a site visit?
No. A site visit shows drainage, noise, and street life in ways a model cannot. The scene helps you prepare for the visit and review it afterward with the team. Use both: walk the site, then mark the findings in the model so the discussion has a common reference. Neither step replaces the other.
FAQ-3 How detailed should the buildings be?
Detailed enough to judge mass, frontage, and access, and no more. A simple block with a roof line is often sufficient for a planning review. Adding facade detail can distract from the questions the group needs to answer. Save the detail for the design stage, where it can be tested properly.
FAQ-4 Can residents use the scene in a consultation?
Yes, a shared view can help residents understand what is proposed and where it sits. It should be presented as an illustration, not as a final design, and the conversation should include the limits of the model. A facilitator can rotate the view and answer questions. Keep the session focused on issues rather than on rendering quality.
Content and technical notes
This article was prepared by the GenAnywhere team with AI-assisted drafting and human review.
Product features, formats, and availability change as the platform evolves; refer to the official GenAnywhere website for current details.
For technical questions or corrections, contact support@genanywhere.com.
Last reviewed: 2026-11-16.