Galle Fort: A Boutique Hotel Inside a World Heritage Property
A client has bought a two-storey house dating from around 1850 inside the Galle Fort, a UNESCO World Heritage property. The walls are lime-and-coral masonry 450 mm thick, the roof is timber with clay tiles, and the rear service block is in poor condition. The client wants an eight-room boutique hotel: demolish and rebuild the rear block in reinforced concrete, insert a new first-floor slab across the main hall, chase the walls for air-conditioning conduits, and repaint the street facade a bright terracotta. The budget is LKR 120 million and the opening is set for the December season, ten months away. The client says a "heritage permit" is a formality because the building is privately owned, and that a friend at the local authority has said the council will approve the drawings.
1. What approvals does this scheme actually need, and why does private ownership not remove them?
Read the worked answer
Private ownership gives the client the right to use the building; it does not give the right to alter fabric that the state has declared worth protecting. Several separate consents are engaged, and they are not substitutes for one another:
- Director-General of Archaeology. Galle Fort is protected under the antiquities legislation, and alteration or demolition within the protected area requires the Department of Archaeology's approval. This is the consent that governs the works to the historic fabric, including the rear block and the facade.
- The Galle Heritage Foundation and the Fort's conservation framework, which review proposals against conservation principles and can require a conservation architect's input.
- Galle Municipal Council building approval for the structural and planning aspects - use, fire, sanitation, parking.
- UDA/planning consent for the change of use from residence to tourist accommodation, plus the tourism authority's registration for the hotel operation.
- Fire clearance, which for a timber-roofed historic building with eight guest rooms is a substantive design constraint, not a stamp.
The client's friend at the council can approve a building; he cannot approve an intervention in a protected monument. Relying on that assurance would produce a project that is built and then stopped.
2. Which parts of the client's brief should the architect resist, and what should be proposed instead? Give the technical reason for each.
Read the worked answer
Resist on engineering and conservation grounds, not on taste, and offer an alternative for every refusal so the conversation stays on the programme:
- Demolish and rebuild the rear block in RC. Demolition destroys the evidence and the patina that justify the property's status, and an RC frame tied into 450 mm lime-coral walls introduces a stiff element against a flexible one, with differential movement and cracking at the junction. Alternative: repair the rear block, underpin where needed, and use a lightweight steel or timber frame inside the existing envelope.
- A new RC slab across the main hall. The existing walls were never designed for the added load, and chasing or pocketing them for slab bearings removes section from the very material carrying the building. Alternative: a self-supporting frame founded independently, or a lightweight timber floor on independent supports.
- Chasing walls for AC conduits. Cutting horizontal chases into lime-coral masonry is one of the fastest ways to crack it and to create a path for rain. Alternative: surface-run services in designed ducts and bulkheads, or vertical drops in secondary partitions.
- Bright terracotta on the facade. Lime renders need to breathe; modern acrylic or cement-rich paint traps moisture and leads to spalling and salt damage. Alternative: limewash in an approved colour, with a sample panel for the heritage authority.
The general principle worth stating to the client is minimum intervention and reversibility: every new element should be capable of removal without damage to the historic fabric.
3. The ten-month opening date is fixed and the approvals will take at least four months. How should the architect handle programme and the client's expectation?
Read the worked answer
The architect should not absorb the risk silently. The correct move is to convert the programme problem into a documented sequence with named decision points.
First, separate the works into two packages: the main house, where consents and conservation input are complex, and the rear block, which may be capable of a simpler consent route if the scheme is repair-led. That gives the client a phasing option - open six rooms in the main house first, add the rear rooms later.
Second, put the approval chain on a bar chart with the architect's submission dates, the authority's statutory or typical response times, and the client's decision dates. Show what each week of late approval costs in lost December revenue, so the client chooses between programme and scheme rather than blaming the architect later.
Third, be explicit in writing that the opening date is not achievable on the current brief unless the scope is reduced, and that the architect does not guarantee authority timelines. If the client proceeds to instruct a contractor before consents are in place, record the instruction and its consequences.
The commercial reality is that a December opening in a heritage building is usually won by reducing scope, not by compressing the consent process. An architect who says so early keeps the client; one who promises the date and misses it loses the client and the fee.