Build a Cost-of-Living Comparison That Actually Fits You

Use the same basket on both sides

Define housing, transport, food, utilities and other recurring costs once, then estimate each category for both locations. Do not compare rent-only data in one city with a broad household index in another. When a cost comes from an external source, record its geography and observation date.

Disposable income is the useful bridge

A salary-equivalence model is clearer when it preserves modelled disposable income. Estimate take-home or use an explicit effective-deduction rate, subtract recurring costs, then solve for the destination salary that leaves the same remainder. Keep currency conversion separate unless the model explicitly includes FX.

Household structure matters

A single person, couple and family can experience very different housing, transport and childcare costs. Build the household profile from the actual decision rather than assuming one city-level basket represents everyone.

Make local uncertainty visible

Use ranges where a location cost is volatile or household-specific. Housing and childcare can dominate the result while smaller categories barely move it, so test the categories with the largest cash impact first. If a figure comes from a city average, keep that distinction visible rather than presenting it as the household's exact future bill.

Check the comparison after currency and tax effects

When the two locations use different currencies or tax systems, keep those layers separate from the household basket. A reference FX rate is not the same as an executable transfer rate, and a generic effective-deduction assumption is not the same as a jurisdiction-specific payroll calculation. The final comparison should show which parts are measured and which are scenario assumptions.