WelcomHeritage

1 · POSITION

WelcomHeritage was established in 1997 as a joint venture linking ITC and Jodhana Heritage Resorts. Its collection brings together palaces, forts, havelis and resorts. The common proposition is access to places with distinct local identities, rather than an expectation that every guestroom will belong to the same architectural model. [1]

2 · A COLLECTION WITH SEPARATE HISTORIES

A hotel’s earlier life remains essential to understanding its place in the collection. WelcomHeritage’s founding date identifies the brand’s beginning, not the construction or conversion of every member property. Its published aims include helping owners turn heritage properties into productive assets. This connects conservation with an operating business, although continued commercial use alone cannot demonstrate the quality of every restoration. [1]

3 · KASMANDA BEFORE WELCOMHERITAGE

Kasmanda Palace in Mussoorie supplies a concrete example. The house traces its beginnings to the Christ Church complex of 1836 and records subsequent uses as a sanatorium, school and family summer residence. Its main building became a hotel in 1992, five years before WelcomHeritage’s establishment. The affiliation thus gathers an existing hospitality history into a later collection. [1, 2]

4 · THE FAMILY IN THE ROOM

Kasmanda’s own account names Dinraj Pratap Singh and Yadu Nandini Singh in the conversion. It also describes family memorabilia in the Belvedere Lounge and the family’s continuing visits. Those details give the guest something more specific than generic palace imagery. The collection supplies a shared route to discovery and booking, while an individual house retains people and objects associated with its earlier use. [2, 3]

5 · ⚑ CANDOUR

The word heritage does not establish that every property was once a royal residence, nor that the collection owns every building. Its catalogue includes resorts as well as historic houses. Dates, family involvement, original fabric and subsequent additions should therefore be recorded separately for each property, rather than inferred from the shared name. [1–3]