Church facilities management for UK churches

Quick answer

If your church needs software at all, these directory options suit different routes:

• iKnow Church: start here if recurring governance tasks need to sit alongside existing parish administration.
• HCOMS Diocese Management System: start here if you are a diocesan team considering a broader operations and property-data model. The supplier describes property and quinquennial-inspection workflows and faculty and DAC process tracking; pricing is by scoped proposal. HCOMS Diocese Management System.
• Hallmaster: start here if the immediate problem is public hall hire. It publishes prices from £195 a year including VAT. Keep maintenance records separate unless the supplier can show the combined workflow. Hallmaster pricing.

This representative shortlist was researched on 13 September 2026. It is not a ranking or a record of hands-on testing. Supplier details added to this list were checked on 25 July 2026.

Church Software UK has an affiliate relationship with Hallmaster. It does not affect which products are included or the order they appear in; see the affiliate disclosure.

Choose facilities-management software only when a church cannot reliably see its buildings, assets, recurring checks, repairs, owners and evidence in its existing process. A room-booking calendar alone is not facilities management: it may show who is using a room, but it does not necessarily record a fault, assign a repair, track a safety check or preserve a decision trail.

For a single building with a small, stable team, a shared task list, asset register and documented review rhythm may be safer than buying another system. For a multi-building parish, benefice, diocese or organisation with repeated inspections, contractors and compliance cycles, a structured platform may reduce lost hand-offs. It cannot decide what work is permitted, safe or legally required.

Who this guide is for and how it was researched

This guide is for UK churchwardens, trustees, operations leads, parish administrators and diocesan property teams deciding how to organise facilities work. It covers the operational record around planned maintenance, faults, inspections, asset information, building use and ownership. It does not provide legal, conservation, health-and-safety or faculty advice, and it does not treat software as proof that a church has met its obligations.

The options below are representative operating models, not a market ranking. Product facts are drawn from current supplier pages; Church of England material provides context for Church of England readers. Other denominations, nations and building types can have different governance and permissions. No hands-on testing, supplier contact or user research was undertaken. The Hallmaster affiliate relationship disclosed above is the only commercial relationship relevant to this guide.

When software may not be the answer

Start with the operating problem. If a church cannot say who owns a fire-alarm test, where the last inspection is recorded, which contractor was appointed or what was agreed at a PCC meeting, a new platform will merely move an unclear process online.

The Church of England describes maintenance as preferable to major repair and publishes a calendar-of-care resource for regular maintenance. Church of England maintenance and repair guidance. Its building guidance also says that permissions can apply to works and that a Diocesan Advisory Committee is the first place to seek advice about proposals. How the Church of England manages buildings.

Those are process and governance questions, not software features. Use an existing system when the church can maintain one trusted register with: a named owner for every recurring task; a realistic review date; links to evidence; a fault-and-repair log; a clear route for urgent escalation; and a record of who can approve expenditure. A spreadsheet can be enough when it is owned, backed up, reviewed and not exposed to people who do not need access.

What to compare

Compare a complete facilities workflow, not a feature list. Ask the same questions of every option.

For a Church of England building, keep software outputs separate from permissions. The Church of England notes that routine maintenance and repairs may have different permission requirements, and that churches can also remain subject to planning, building-regulation and other secular controls. Seek the appropriate professional and diocesan advice for the proposed work rather than relying on a task status. Church building permissions guidance.

How the options differ

Existing administration system with a governance workflow

An existing church-administration system may be the lightest option where the need is recurring tasks, named owners and ordinary meeting governance rather than property-portfolio management. iKnow Church publishes a Governance module for recurring tasks, responsibilities and reminders, including examples such as fire-alarm tests, PAT testing, insurance renewals and policy reviews. iKnow Church Governance.

This can fit a parish that already uses iKnow Church and needs a single place for routine administrative ownership. It does not establish that the product is a complete facilities, contractor, condition-survey or regulatory-compliance platform. First practical check: create three recurring tasks, attach the evidence a PCC would need, reassign one when a churchwarden changes and export the overdue-task list.

Dedicated property or diocesan operations platform

For a diocese or substantial multi-site organisation, a specialist operations platform can make sense when property information must connect with wider portfolios, compliance cycles, finance and parish records. HCOMS describes its Diocese Management System as covering property, compliance, finance and people across diocesan operational areas; its separate Property Management System describes tenancies, repairs, inspections and compliance cycles. HCOMS Diocese Management System and HCOMS property-management information.

This is materially different from a parish buying a calendar. The trade-off is procurement and implementation: map what data a diocese owns, what a parish can see, how contractor access is governed, and how existing records will be migrated. First practical check: model one inspection, repair approval, contractor update and parish hand-off using the real property hierarchy and permissions.

Booking software plus a separate maintenance process

Churches with public halls often need booking software, but that should not be stretched into a facilities system without evidence. A booking product may handle availability, enquiry, invoices or access arrangements well; it may not maintain an asset register, planned-maintenance cycle or contractor record. Use this model when the main operational problem is public hire rather than building condition.

First practical check: put a room out of service for maintenance, notify the people affected by existing bookings, record the approval for the closure and confirm where the repair evidence will live. If this requires several unconnected workarounds, a combined operating design may be needed.

Software listings to explore

These listings are relevant starting points, not rankings or endorsements. The guide remains usable without clicking them.

• iKnow Church is relevant where recurring governance tasks need to sit alongside existing parish administration. Confirm the precise permissions, current pricing and evidence record your church needs.
• HCOMS Diocese Management System is relevant to diocesan teams considering a broader operations and property-data model. Confirm the parish-data boundary, implementation scope and current processing terms.
• Hallmaster is relevant where the immediate problem is public hall hire. Keep booking, invoices and maintenance evidence distinct unless the supplier can demonstrate the full combined workflow.

A practical decision tool: one-month facilities trial

Run this test with fictional or minimised data before moving live building, contractor or incident information.

1. List one building, three rooms and five assets or recurring checks.
2. Give a churchwarden, administrator and treasurer their intended permissions.
3. Schedule one planned check, log one urgent fault and attach the evidence or decision note each would require.
4. Assign a contractor action and record who may approve the cost.
5. Mark a room unavailable, then check how a booked user and the responsible volunteer would be told.
6. Produce an overdue-work report and a list of tasks without an owner.
7. Export the trial data and confirm that an ordinary office user can open it without supplier assistance.

Record the result in a short decision record: the operational problem; candidate and price terms; what passed; what needed a workaround; unresolved permissions or compliance questions; first-year cost; migration owner; review date; and exit/export result. Do not mark missing evidence as a failed feature: turn it into a supplier or adviser question.

Implementation, ownership and exit

Name one operational owner, but do not make that person the only person able to retrieve the record. Agree a simple data boundary: which documents belong in the platform, which must remain in an approved record system, which information is too sensitive for contractor access, and how completed work is retained. Review access whenever volunteers, wardens or contractors change.

Before committing, test the actual building calendar, recurring maintenance, urgent-fault escalation, expenditure approval and evidence export. For Church of England readers, involve the DAC and suitable professional advisers before relying on a software workflow for proposed works. The Church of England also recommends an asset-management plan and realistic annual maintenance provision after a building project. Church building project completion guidance.

Your next step

At the next PCC, trustees’ or operations meeting, choose one recurring building task and one recent repair. Map their current owner, evidence, approval, hand-off and archive location on one page. Only shortlist software if that exercise exposes a repeatable coordination gap that the church cannot safely solve in its existing tools.

Sources and research limits

Research completed 13 September 2026. This is a representative guide, not a complete facilities-software market survey. It does not provide legal, conservation, safety or faculty advice. Product claims are supplier-published and should be confirmed in a live demonstration and contract; no hands-on testing occurred.

• Church of England: Building maintenance and repair (accessed 13 September 2026).
• Church of England: How we manage our buildings (accessed 13 September 2026).
• iKnow Church: Governance (accessed 13 September 2026).
• HCOMS: Diocese Management System (accessed 13 September 2026).
• HCOMS: Property Management System information (accessed 13 September 2026).