Serving on a church building committee is rarely something people signed up for as a specialty. Committee members are usually there because they care about the church, not because they have architectural or construction experience — and that gap between what a committee knows and what a project actually requires is where a lot of unnecessary stress creeps in.
I understand that gap from both sides. I’ve sat on a building committee myself, working through a church building project as a volunteer alongside my own church community — not as the architect, but as one of the people trying to make sense of drawings, budgets and timelines in my spare time. And I’ve spent years on the other side of the table, as the architect other churches have engaged to guide them through exactly that process. That combination shapes how I work, and it’s why I think a guide like this is worth writing plainly, without jargon, for people who are giving up evenings and weekends for a project they care about but didn’t train for.
Early Conversations: Testing the Idea, Not Selling a Design
In the first meetings, a good architect isn’t trying to show you a finished vision — they’re trying to understand your church properly. Expect to be asked about how the building is actually used across a week, not just on Sundays; about your congregation’s growth, constraints and priorities; about budget realities, even rough ones; and about who else needs to be part of the conversation, from ministers to diocesan or denominational bodies. When I was on a committee myself, the meetings that felt most useful were the ones where the architect asked more questions than they answered. If an architect skips straight to concept sketches before that, it’s worth noticing.
A Brief That Reflects Your Church, Not a Template
Once your committee’s priorities are reasonably clear, a good architect will help develop those into a proper brief — a working document that captures what the building needs to do, not just what it should look like. Expect this to take longer than feels comfortable at first. I remember, as a committee member, wanting to move faster than the brief stage allowed — it can feel like stalling when you’re keen to see a design. But a brief that’s rushed tends to produce a design that solves the wrong problem well, rather than the right problem adequately. A good architect will push back gently on assumptions and help the committee articulate things it hadn’t fully put into words yet.
Concept Design: Options, Trade-Offs, and Honest Cost Signals
At concept stage, expect to see real options rather than a single “take it or leave it” design — along with a clear explanation of the trade-offs each one carries, and an honest, early read on likely cost, even before detailed costing is possible. This is the stage where the biggest decisions get made, and it’s worth taking the time your committee genuinely needs. I know how much easier it is to sit with a decision when you understand why the options in front of you look the way they do, rather than being asked to simply choose.
Documentation and Approvals: Where the Architect Does the Heavy Lifting
Once a concept is settled, the bulk of technical work — drawings, specifications, coordination with engineers and other consultants, and navigating council or heritage approvals — sits largely with the architect. Committees shouldn’t need deep technical fluency here, but you should expect regular, plain-language updates, and clear explanations any time something changes from what was agreed at concept stage. As a committee member, the updates I valued most were the honest ones — including when something had slowed down or changed — rather than being told everything was on track when it wasn’t.
Construction: An Advocate on Site, Not a Distant Consultant
During construction, expect your architect to stay genuinely involved — reviewing progress against drawings, answering site queries from the builder, and flagging issues before they become expensive problems. Construction rarely goes exactly to plan, and a good architect keeps the committee informed honestly, including about the things that haven’t gone smoothly.
Completion and Beyond: The Relationship Doesn’t End at Handover
A building’s real test begins once the congregation starts using it properly. A good architect stays engaged through this period, helping the committee understand how the building is performing and refining anything that needs it, rather than considering the job finished the moment keys are handed over.
What Good Collaboration Looks Like From Your Side
Committees get the most out of an architect when they engage honestly and consistently, and when the process respects that large groups take time to reach consensus. I know that pace from personal experience — the meetings that get pushed back, the decisions that need another week to land properly with everyone. A good architect should expect that rhythm and work with it, not against it.
If there’s one thing I’d want a building committee to take from this guide, it’s that the uncertainty you’re feeling is completely normal, not a sign you’re doing anything wrong. I’ve felt it myself, from the other side of the table. A good architect’s job is to make that process feel manageable — with clear information, realistic pacing, and honesty at every stage, including the parts that aren’t easy to hear.