By Rev. Luan-Vu “Lui” Tran, Ph.D.
1. Name the Successor Church Clearly and Early
The resolution should state, without ambiguity, what the merged church will be called and when that identity takes effect. Avoid placeholder language or deferring the decision to a future committee. Uncertainty around identity often fuels congregational anxiety and later disputes.
Best practice:
“Upon approval, the merged congregation shall be known as ___ United Methodist Church, effective ___.”
2. Describe Governance During Transition
Even though the 2020/2024 Book of Discipline (“Discipline”) does not require granular governance detail, best practice is to explain how leadership will function during the transition period. Silence here often leads to power struggles or perceptions of unfairness.
Best practice:
Specify whether:
- one existing church council continues temporarily,
- a transitional council is formed with proportional representation, or
- elections will occur by a stated date.
3. Address Pastoral Leadership Transparently
While appointments remain episcopal, congregations need clarity about pastoral continuity or transition. Avoid implying guarantees, but do not leave the matter unaddressed.
Best practice:
Acknowledge the role of the bishop and cabinet while naming the anticipated pastoral arrangement (e.g., continuation during transition, timing of review).
4. Be Explicit About Property and Finances
Many merger conflicts arise not from theology, but from unspoken assumptions about buildings, funds, and debt. The resolution should state how property and financial assets will be held and administered after merger, consistent with the trust clause.
Best practice:
Clarify that:
- all property becomes property of the successor church,
- all assets and liabilities transfer to the successor church, and
- the trust clause under ¶ 2501 continues unchanged.
5. State the Missional Rationale, Not Just the Mechanics
Paragraph 2546 grounds merger in mission, not survival. A resolution that reads like a corporate transaction misses the theological point and weakens buy-in.
Best practice:
Include a brief narrative sentence explaining why this merger strengthens ministry, referencing worship, discipleship, outreach, or community presence.
6. Acknowledge Congregational History and Records
Members need assurance that their church’s story will not disappear. While ¶ 2546.5 addresses archives legally, best practice is to name this pastorally.
Best practice:
Affirm that membership, sacramental records, and historical materials will be preserved and honored by the successor church.
7. Avoid Conditional or Open-Ended Language
Resolutions that defer key decisions (“to be determined later”) or make merger contingent on future events invite confusion and legal vulnerability.
Best practice:
If a decision is essential to informed consent, it should be made before the vote, not after.
8. Coordinate Language Across All Churches
When multiple churches are merging, each resolution should be substantively consistent, even if tailored locally. Material differences between resolutions can call the merger into question.
Best practice:
Use a shared core resolution with limited, clearly identified local adaptations.
9. Document Everything
Votes, notices, approvals, and resolutions should be recorded, retained, and centrally filed. Memory is not evidence.
Best practice:
Keep a single merger file with:
- resolutions,
- minutes,
- superintendent approvals, and
- civil-law filings.
10. Treat the Resolution as a Covenant, Not a Formality
The resolution is more than a procedural checkbox. It is the covenantal moment when congregations consent to become something new together.
Best practice:
Draft the resolution in language that is clear, respectful, and dignified, suitable to be read aloud and remembered.
Bottom Line
The Discipline sets the minimum legal threshold. Best practices ensure the merger is also pastorally credible, congregationally trustworthy, and connectionally sound. A clear, complete resolution does not slow merger—it prevents regret.