A congregation had been in design for two years and under construction for eight months when the pastor who carried the project from the very first conversation accepted a call in another state. The new pastor arrived in February to steel already standing, a capital campaign at sixty percent of goal, a building committee that had lost two of its seven members to job relocations, and a long list of decisions he had no part in making. His first question was the right one and the fairest one. Why is the fellowship hall sized the way it is? Nobody in the room could answer him. Leadership change during a building project is not a rare misfortune that happens to unlucky organizations, and the projects that survive it are not the lucky ones. They are the ones where somebody wrote down why.

Leadership change during a building project is closer to normal than rare

Consider the arithmetic. A church or nonprofit building project of any real size runs somewhere between two and four years from the first serious conversation to the day the doors open. Against that, Lifeway Research reported in 2025 that the median pastoral tenure at one church is eight years, and that among churches that existed and had a pastor ten years ago, only forty four percent still have the same pastor today. On the nonprofit side the numbers move faster still. In a Chronicle of Philanthropy survey of more than three hundred fifty nonprofit chief executives, a third said they were likely to leave their job within two years and twenty two percent said they were likely to leave the nonprofit world altogether. Those are not crisis statistics but ordinary professional mobility, and they mean that a three year project has a meaningful chance of outlasting the person who started it.

The same is true outside the faith world, though it shows up differently. Developers reassign project managers between assets, franchise operators lose the director of construction who ran the last twelve stores, and hotel ownership groups change hands mid renovation so that a new asset manager inherits a design she did not commission. Nobody has done anything wrong in any of those situations. People get promoted, called, recruited, and retired, and a building project simply takes long enough to collide with the ordinary movement of careers.

What actually leaves with the person who leaves

It is not the drawings. The drawings stay, and they are complete, and anybody can read them. What leaves is the reasoning. A set of construction documents records what the building is with enormous precision. It does not record that the fellowship hall was sized for two hundred forty seats rather than four hundred because the congregation decided, after three meetings and one genuinely difficult vote, that they would rather serve two seatings well than build a room they could not fill and could not heat. It does not record that the main entry faces the south lot because the traffic study showed a left turn stack that the city would not approve on the east side. It does not record that the sanctuary structure was designed to carry a future balcony, which is why the columns are where they are and why that line item survived value engineering when other things did not.

Every one of those decisions had a reason, and in most projects that reason lives in exactly two places. It lives in an email thread, and it lives in the head of the person who was in the room. When that person leaves, the thread is still on a server somewhere, but nobody knows which of four hundred messages holds the answer. What the new leader inherits, then, is a building full of choices that look arbitrary. Arbitrary choices invite reopening, and reopening a closed decision in month eight of construction is how a project loses a quarter and a good deal of goodwill.

That passage was written about dispute exposure between architects and contractors, and it applies just as directly to the owner side of the table. A decision that exists only as a verbal agreement is not a decision anyone can defend six months later, least of all a leader who was not present when it was made. The gap is rarely dramatic while it is forming. It becomes dramatic all at once, on the day somebody new asks a reasonable question and the answer has evaporated.

The record that keeps a project whole

We keep a written record on every project, not as an administrative courtesy but because it is the only thing that makes a long project transferable. The core of it is the building program, the document that states what spaces the organization needs, at what size, serving how many people, adjacent to what. Underneath that sits a basis of design that captures the assumptions behind the systems and the structure, including the ones that seem obvious at the time and never do later. Alongside both runs a decision log: what was decided, on what date, by whom, and what alternatives were considered and set aside. When a decision moves the budget or the schedule, that consequence is recorded alongside it.

The value engineering history deserves its own mention, because it is the record most often lost and most often needed. When bids come in high and a team works the number down, the list of what came out of the project is only half the story. The other half is what the team deliberately protected and why, and that half is what a new leader needs in order to understand the building she has inherited. Without it, the future balcony structure looks like an expensive column layout somebody should have caught, rather than the single decision that preserved the congregation’s ability to grow without building again in fifteen years.

Bringing a new leader up to speed without starting the project over

When a client’s leadership changes mid project, our first move is not to reassure anyone that everything is fine. It is to sit down with the new leader and walk the entire decision record from the beginning, in order, with the reasoning attached. That meeting usually takes two or three hours, and it is time well spent. A new pastor or executive director who understands why the building is what it is can defend it to a board, a campaign committee, and a congregation. A new leader who has only been told that the decisions were already made cannot defend anything, and will eventually start asking for changes simply to establish that the project is now theirs.

The second move is an honest map of what is still open and what is closed. Some things remain genuinely available: finishes, furniture, signage, landscape, and often lighting and casework are still in play well into construction. Other things are closed because the concrete is cured, the steel is fabricated, the permit was issued against a specific drawing set, or the long lead equipment is already in production. We do not pretend the closed list is shorter than it is, and we do not pretend it is longer either. When a new leader wants something changed that sits on the closed side, we price it and put the number in front of them rather than arguing about whether the request is reasonable. Most requests answer themselves once the cost sits next to the value. It is also the moment to be clear about the owner’s role during construction, because a leader who arrives mid project inherits a set of obligations nobody has briefed them on.

Build the project so it does not rest on one person

The deeper fix is structural, and it belongs at the front of the project rather than the middle. A building program that was defined in writing before any drawing was made belongs to the organization rather than to the leader who commissioned it, and an organization can hand that document to a new leader on day one. A building committee with staggered terms and more than four active members carries institutional memory that no single departure can erase. Minutes that record decisions rather than discussion give a successor something to read instead of something to reconstruct. None of this is exotic, and all of it is easy to skip when the project is moving and everyone in the room already knows the answers. The cost of skipping it does not appear until the room changes.

We would rather a client never need this, and many do not. But we have been doing this long enough, across enough church and commercial projects, to treat continuity as a design condition rather than a contingency. The organizations that came through a leadership change without losing ground were not the ones with the most stable leadership. They were the ones whose reasoning was written down, whose program was owned by a body rather than a person, and whose architect could sit with a stranger in February and explain, decision by decision, how the building on the site became the building on the site.

Continuity is one of the quieter things a firm brings to a project, and it is hard to see until the day you need it. Twenty five years and more than a thousand church projects have taught us that the reasoning behind a decision is worth as much as the decision itself, so we write it down, we keep it current, and we can walk any new leader through it from the first site visit forward. If your organization is planning a building and the leadership picture is less settled than you would like, or if you have already had a change and are trying to work out what you inherited, we would be glad to talk it through with you. There is no obligation in a first conversation, and you will leave it knowing more about your own project.