100-Floor Construction Playbook

1. Site fit: Can the land physically support the tower and its construction? 2. Market fit: Will enough people or businesses pay for the planned space? 3. Rule and service fit: Can the project meet height, zoning, access, utility, safety, and environmental requirements?

Start with site fit because the ground and surroundings set hard limits. Obtain a boundary survey, title documents, available zoning map, flood information, and utility plans. Request a preliminary geotechnical review, which studies soil and rock conditions. For a 100-floor building, ask specifically about bedrock depth, weak soil layers, groundwater, nearby foundations, and risks from excavation. A site beside a river may offer excellent views but require major waterproofing, pumping, and foundation work. A narrow plot may technically fit the tower but leave no room for cranes, delivery vehicles, worker access, fire access, or safe excavation.

Next, test market fit using evidence from the actual area. Define the intended mix before counting demand: apartments, offices, hotel rooms, retail, or a combination. Compare nearby buildings by asking what space they offer, how quickly they fill, what rents or prices they achieve, and which units remain empty. Speak with local brokers, employers, retailers, and property managers. Do not treat general city growth as proof that this tower will succeed. A market may need smaller apartments, while the proposed tower offers large luxury units; that mismatch can leave expensive floors unsold.

Finally, test rules and services. Confirm the permitted height, floor-area limit, setbacks, parking rules, road width, fire access, aviation restrictions, heritage controls, environmental review requirements, and connection capacity for water, power, drainage, and communications. A zoning map may show high-density development while another rule limits the building to a lower height. Ask the planning authority for written confirmation rather than relying on a broker’s statement.

Record each finding in a simple feasibility register:

| Check | Evidence required | Result | Action | |---|---|---|---| | Soil and groundwater | Preliminary geotechnical report | Acceptable / uncertain / poor | Order deeper testing or reject | | Height permission | Written planning response | Confirmed / conditional / blocked | Revise height or seek formal advice | | Power capacity | Utility provider letter | Available / upgrade needed | Price upgrade and schedule | | Market demand | Comparable rents, sales, vacancy | Strong / mixed / weak | Change mix or stop | | Construction access | Road and staging review | workable / restricted | Plan logistics or find another site |

Ask yourself: if one line says “uncertain,” can you price the risk, or are you guessing? A feasibility check works only when uncertainty becomes a task, cost, or decision.

Applying the Stack to a Candidate Tower Site

Consider a 1.8-acre urban site beside a rail station. The initial proposal calls for 100 floors: 60 residential floors, 25 office floors, 8 hotel floors, 4 retail levels, and 3 mechanical and service levels. The owner has not commissioned detailed design or submitted permits. The following sequence creates a go-or-stop decision.

1. Freeze the basic project brief. Write the proposed uses, approximate floor areas, target customers, parking approach, and expected opening date. Expected outcome: everyone tests the same project instead of comparing different assumptions.

2. Map the physical site. Obtain the boundary survey and mark roads, neighboring buildings, rail property, overhead lines, trees, drainage paths, and possible crane positions. The site has only 42 meters of road frontage, so the team identifies a likely need for off-site delivery coordination. Expected outcome: the team sees whether construction access can work before committing to a tower footprint.

3. Order an early ground review. A desktop geotechnical review finds deep fill near the old industrial edge and groundwater below the proposed basement. The team requests test locations on both the tower footprint and excavation perimeter. Expected outcome: the budget includes possible deep foundations, waterproofing, and groundwater control instead of treating them as surprises.

4. Check planning limits in writing. The planning office confirms high-density zoning but states that height depends on a special approval, airport review, shadow analysis, and a traffic assessment. Expected outcome: the project team lists those approvals, their likely sequence, and the design changes that could follow.

5. Test utility capacity. The water provider confirms a service connection but requires a pressure review. The electricity provider reports that the existing network cannot serve the full tower without a substation upgrade. Expected outcome: the team prices the upgrade and adds its lead time to the schedule.

6. Measure demand by use. Local records and broker interviews show strong demand for smaller apartments and flexible offices, while nearby large luxury units remain on the market. The team replaces part of the large-unit plan with smaller homes and checks whether the new mix still supports required lifts, lobbies, refuse rooms, and services. Expected outcome: the market test connects demand to the actual building plan.

7. Build a decision budget. Add land cost, demolition, surveys, geotechnical work, approvals, utility upgrades, access measures, likely foundation choices, financing time, and a risk allowance. Do not present one precise construction price when major ground and approval questions remain. Use low, expected, and high cases. Expected outcome: the owner sees how uncertainty affects the project rather than receiving a false sense of accuracy.

8. Set decision gates. Proceed only if the planning path remains open, utility upgrades have a credible price and schedule, market demand supports the revised mix, and ground risks fit the budget. Expected outcome: the project moves into concept design with documented reasons, or stops before detailed fees begin.

Quick checklist

• Obtain title, boundary, zoning, flood, and utility records. - Mark road access, neighboring buildings, rail lines, overhead services, and staging areas. - Request a preliminary geotechnical review covering soil, rock, groundwater, and nearby foundations. - Confirm height, floor-area limits, setbacks, parking, fire access, and special approvals in writing. - Compare nearby buildings by use, size, price, rent, occupancy, and time on the market. - Test demand for the exact proposed mix, not for the city in general. - Ask utility providers about capacity, upgrades, connection points, cost, and lead time. - Price three cases for major unknowns: low, expected, and high. - Record every unknown with an owner and a due date. - Approve concept design only after the decision gates pass.

The practical takeaway is simple: a site becomes a project candidate only when physical, commercial, and rule checks support the same version of the tower.

Mistakes That Distort the Feasibility Decision

Treating a large plot as proof of a suitable site

A large site may still fail because of weak soil, a narrow access road, flood exposure, or a neighboring structure that blocks excavation. A 100-floor tower also needs space for emergency access, construction deliveries, worker facilities, cranes, temporary utilities, and safe movement around the excavation.

Do this: Draw the tower footprint, basement boundary, fire route, crane zones, delivery route, and worker access on the survey before selecting a design direction. Not this: Measure only the space available for the above-ground floors.

Mistaking zoning for approval

A zoning label may allow tall development in principle without granting permission for the proposed height, use mix, traffic load, shadow, or environmental impact. Special approvals can change the height, floor area, parking plan, or construction hours.

Do this: Send the planning authority a short written project description and request a list of required approvals and studies. Save the response in the feasibility register. Not this: Treat a broker’s verbal statement as a permit pathway.

Using broad market demand to justify the wrong product

A growing business district does not automatically support a tower filled with premium offices. A popular residential area may favor compact units while the proposed plan contains oversized apartments. Demand must match floor area, price, timing, and customer type.

Do this: Compare at least three nearby projects with similar uses and record asking price, achieved price where available, rent, vacancy, unit size, and time on the market. Then test the proposed mix against those findings. Not this: Copy a successful tower from another district without checking customers, transport, competing supply, and price.

A further edge case appears when one major constraint remains unresolved. For example, the site may pass market and planning checks but lack confirmed power capacity. Do not hide that gap inside a general risk note. Assign the utility provider a written request, set a response date, obtain an upgrade estimate, and calculate the effect on cost and opening time. If the answer cannot arrive before the next spending gate, pause the design package.

The final test asks whether the evidence supports a controlled next step. If the site needs a different height, a different use mix, or a costly service upgrade, revise the brief before commissioning detailed design. A clear “not yet” protects more money than a fast “yes” built on assumptions. Once the three layers agree, the project has earned the right to move from feasibility into a measured concept - not because the tower looks impressive on paper, but because the site, customers, and constraints can carry it.

End of chapter one. 4 more chapters in the full book.