Set the business context
Document roles, headcount, shifts, customer activity, leadership travel, security, technical density, timeline and growth. These requirements determine the weights.
A GCC, regional headquarters, managed project team and showroom should not use the same generic location scorecard.
Score talent and commute
Use employee-origin and hiring data, timed route samples, public or company transport feasibility, parking and last-mile safety. Consider how access changes across shifts.
Avoid giving every residential catchment equal weight; focus on the roles and teams most important to the operation.
Score building and delivery
Assess floor efficiency, power, cooling, telecom, lifts, safety, accessibility, amenities, facility management, fit-out controls, approvals and handover certainty.
Separate commissioned capacity from future or marketing commitments and note the evidence date.
Score commercial value
Normalise area, rent, maintenance, parking, taxes, escalation, deposit and fit-out periods. Add build cost, technology, transport, utilities, overlap and internal programme costs.
Run downside scenarios for delay, slower headcount ramp and future expansion.
Use the result with judgement
The scorecard structures debate but does not replace site visits, references or professional diligence. Review sensitivities to see whether the winner changes when key weights move.
Million Minds Tech City should be evaluated using its exact off-SG-Highway address and unit evidence, not assumed corridor averages.
Sources
Source access and page review date: 12 September 2026.