Maintaining Mosques, Churches and Heritage Buildings

I have spent most of my career configuring maintenance and asset systems for commercial estates, where the model is well understood: register the plant, schedule the preventive maintenance, raise work orders, track spares. When people ask me to point that same model at a mosque, a parish church, or a heritage hall, I have to slow them down. These buildings follow different rules. The fabric is not a set of replaceable components, the work needs approved methods and specialist trades, and the busiest days are religious or ceremonial rather than commercial. This piece explains why the standard approach misfires, and how to shape a system that actually fits.

Why the standard CMMS model breaks

A conventional CMMS is built around plant assets. You create an asset record for a pump, an air handler, a chiller, and you attach a preventive maintenance schedule to it. When it wears out, you replace it with an equivalent unit and the record carries on. That logic is sound for mechanical and electrical equipment, and I would not change it. But it does not describe a stone parapet, a lime-plastered wall, a lead roof, or a run of medieval oak.

Three assumptions quietly fail:

• Fabric elements are not replaceable components. You do not swap out a section of carved stonework the way you swap a bearing. You repair it in place, matching original material and technique, and you accept that the element is meant to last centuries with care rather than be retired on a lifecycle curve.
• Work requires approved methods and specialist trades. A general contractor cannot re-point a rubble wall with modern cement without doing long-term harm. The right answer is a lime specialist, a leadworker, a joiner who understands historic timber, a stained-glass conservator. The method matters as much as the outcome.
• Usage peaks are religious or ceremonial, not commercial. An office fills nine to five on weekdays. A mosque fills for Friday prayers and swells at festival times; a church fills on Sundays and for weddings and funerals booked months ahead. The calendar that governs access is a worship and community calendar, not a shift roster.

Put those together and the plant-asset register starts to feel like the wrong shape. You end up forcing building fabric into equipment records, and the preventive-maintenance engine has nothing sensible to schedule against. The fix is not a better CMMS. It is a different unit of record.

A fabric-oriented register, not a plant list

For a heritage or religious building I build the register around elements of fabric rather than items of plant. An element is a meaningful part of the building envelope or interior: the roof covering, the tower stonework, the structural timber, the glazing, the rainwater goods, the internal finishes. Each element carries a condition grade rather than a run-hours counter, a last inspection date rather than a last-service date, and a plain-language consequence-of-failure note that tells a non-technical trustee why it matters.

The condition grade is the spine of the whole thing. I use a simple four-point scale that inspectors and trustees can both read: Good (sound, routine care only), Fair (minor defects, monitor), Poor (defects that will worsen without action within a cycle), and Urgent (active failure or imminent risk to fabric or people). That grade drives the priority of any work the element generates, in the same way asset criticality drives priority on a commercial estate. If you want the underlying reasoning on how a grading or criticality scale should be structured, I set it out in my note on asset criticality and classification.

The register also wants a shallow hierarchy so an element belongs to a zone of the building. That is the same discipline I apply to any estate, and it pays off the moment you filter a report by "nave" or "minaret" or "west range". If hierarchy design is new to you, my guide on asset hierarchy design covers the principles that carry straight across to fabric.

A worked fabric register (extract):

Notice what this table does that a plant list cannot. Rainwater goods graded Urgent sit next to a roof graded Poor, and any competent estates manager can read the story in one line: water is getting in, deal with the gutters this season and plan the roof next. The consequence note is deliberately written for a trustee, not an engineer, because the register has to serve the people who approve the money.

From cyclical inspection to a costed programme

Heritage and religious buildings are typically looked after on a cyclical inspection model. Many are surveyed on a five-year cycle, often called a quinquennial inspection, carried out by an accredited architect or surveyor who walks the whole building and reports on the condition of every element. Between those major surveys there are lighter annual or seasonal checks, especially of roofs and rainwater goods where small faults do the most damage.

The recurring failure I see is that this excellent report becomes a PDF in a drawer. Someone commissions it, files it, and refers to it only when a leak forces the issue. The whole value of the survey leaks away because it never becomes a plan. What I do instead is treat the inspection report as structured input to the system:

1. Update the condition grade of every element from the surveyor's findings, and reset the last inspection date. The register now reflects reality, not last cycle's guess.
2. Turn each recommendation into a costed line of work with a priority band: urgent, within one year, within the cycle, desirable. This is the difference between a narrative report and a programme you can act on.
3. Sequence the work by dependency and cost, not just by severity. Water always comes first, so rainwater goods and roof coverings lead; then structure; then the finishes that were only ever symptoms.
4. Keep it live. As jobs are completed, grades improve and the programme reshapes itself, so the next survey starts from an accurate baseline rather than a cold read.

The payoff is a rolling, prioritised, costed work programme that a facilities manager and a treasurer can both open and understand. It is the same discipline I would apply to any planned maintenance backlog, but expressed in fabric and condition rather than plant and run-hours.

The access calendar the planner must respect

On a commercial estate you plan work around production or occupancy, and a weekend shutdown is a gift. Religious and heritage buildings invert this. Their most important days are exactly the days you cannot work: Friday congregational prayers, the festivals that draw the largest gatherings, Sunday services, and the weddings and funerals that families book around a specific building and a specific date. These events are not interruptions to the maintenance calendar; they are the reason the building exists, and they take precedence.

So the planner needs an access calendar as a first-class constraint, sitting alongside the work programme. High-occupancy and ceremonial dates are blocked out, and scheduling logic simply refuses to place intrusive work into those windows. Scaffolding cannot go up across a doorway the week of a festival. Noisy or dusty work cannot land the morning of a funeral. In practice I map each building's rhythm once, mark the fixed and movable dates, and let the calendar shape when work is offered rather than discovering the clash on site.

This is where a facilities-management mindset earns its keep, because it treats space and occupancy as real, not as an afterthought bolted onto a maintenance tool. If you are weighing which class of system suits an estate like this, my explainer on CAFM vs CMMS vs EAM vs IWMS walks through where the occupancy layer lives and why it matters here.

Funding reality: donations, grants and endowments

The last thing the standard model gets wrong is money. A commercial estate has an operating budget and a capital plan. A mosque, church, or heritage trust usually runs on some blend of congregational donations, restricted grants, and endowment income, and each of those has its own rules. Donations are goodwill and can vanish in a hard year. Grants are competitive, restricted to specific work, and demand evidence. Endowment income is steady but modest and rarely stretches to a major repair.

This funding reality is exactly why the fabric register and the costed programme are worth building. They are not administrative overhead; they are the evidence base that unlocks money:

• For a grant application: a funder wants to see the condition grade, the professional inspection behind it, the consequence of inaction, and a costed scope for the specific element being funded. The register produces that in a page instead of a scramble.
• For a trustee decision: trustees are stewards spending other people's gifts, and they need to prioritise honestly. A programme that ranks an Urgent gutter above a desirable redecoration lets them defend where the money went.
• For the donor and the congregation: showing that a gift moved an element from Poor to Good, with dates and cost, turns maintenance from an invisible drain into a visible act of care people want to support again.

Good practice and published guidance in this field are widely available. Bodies such as ICOMOS set out international conservation principles, and national heritage authorities such as Historic England publish detailed guidance on the care of historic and religious buildings. Treat those as the authority on method and consent; treat your system as the place that holds the record and turns it into a plan.

Conclusion

Heritage and religious buildings break the plant-asset model for honest reasons: their fabric is repaired rather than replaced, their work needs approved methods and specialist hands, and their calendars belong to worship and ceremony. Build the register from elements and condition grades, convert the cyclical inspection into a live costed programme, respect an access calendar that puts the community first, and let all of that feed the grant and trustee reporting the funding depends on. Do that and the system stops fighting the building and starts serving it.

Independence note: I am an independent practitioner and hold no affiliation with the organisations named here. External bodies are referenced for guidance only. Conservation consent and approved methods are the province of accredited conservation professionals, and nothing here replaces that advice for your specific building.