How to avoid the copy crunch at the end of a website project

Here is how a lot of church website projects end. The design was approved months ago. The developers have built the templates. Everyone has agreed on a launch date. And the staff, who decided early on that they would write their own copy, are now trying to rewrite forty pages between Sunday services, with input from ministry leaders who haven't answered an email in two weeks.

We see this on most church and nonprofit projects, and it rarely comes down to anyone being lazy. Writing for the web is slow, it competes with everything else on a church calendar, and it's easy to put off while the design is still changing. Content is almost always the critical path, even when everyone assumes the code will be.

The good news is that the crunch is predictable, so you can plan around it. Most of what follows you can set up before you hire anyone.

Decide who writes, and when, before the project starts

Churches often want to rethink every page from the ground up, with two or three ministry leaders shaping each section. That's a good instinct. It also means dozens of writers, each with their own voice, and someone has to blend it all into one site at the end.

Before you sign a contract, settle a few things in writing:

• Who drafts copy, who approves it, and who has the final say on each section.
• Who owns photography.
• When drafts are due, tied to project milestones rather than a single date at the end.
• What happens if a ministry doesn't deliver (more on that below).

Assign one owner per page. Ministry leaders can contribute, but one person is responsible for getting each page to done. Pages with three owners tend to have none.

Be honest about how many sign-offs each page needs. On large church sites we've seen the most progress when the web team owns copy and layout, and ministry leaders get a narrow fact check ("that person no longer serves here") instead of an open invitation to weigh in. Open-ended review turns every page into a negotiation.

Settle structure before anyone writes final copy

The biggest source of wasted writing is drafting before you know what the page looks like. Staff write a full page, the design calls for a short intro and three cards, and now the copy has to be cut down.

So we work in two approvals. First, staff approve a page's structure: which sections it has, in what order, and roughly what each one says. That approval lets building start. Then they polish the wording on the real page, where length limits are obvious. You avoid perfecting a paragraph in a document only to find it doesn't fit the space it was written for.

Once the design system is settled, a block brief helps people write once. For each section of a page, list what's needed: a heading of so many characters, a body paragraph of so many words, a button label, a photo. Writers fill in the blanks instead of facing an empty document.

Put directional copy into the layouts

A blank page is the hardest thing to write. A rough draft sitting in the real design is much easier to fix. Craig Van Korlaar, our UX lead, explained it to one church this way: "When people see the layout and they see directional copy in place, it's a lot easier for them to jump in and redo it than to do it in kind of like a vacuum."

Directional copy can come from your current site, from a short interview with the ministry leader, or from whoever on the project writes well. It doesn't need to be final. It needs to be close enough that a staff member reads it and says "no, that's not quite us," and then rewrites it. That is far faster than starting from nothing.

There's a trade-off. Some teams worry old copy will anchor them to the old site. If you want a true fresh start, skip directional copy, but set due dates as soon as your navigation is settled so the writing doesn't all land in the final month.

Track copy, images and links separately

A single "page done?" column hides where the work actually is. We use a content tracker with separate columns for copy, images and links, each with its own status: in progress, ready for review, done.

You can approve a page's photos without rereading its copy, and everyone can see whether a page is waiting on a ministry's photos or on the developers.

One small lesson: explain the workflow. If reviewers don't know there's a "done" state, pages can sit in "ready for review" for weeks. Ask reviewers to flip items to done so nothing surprises anyone at launch.

Make placeholders obvious, and let nothing fake ship

When a bio or a ministry blurb isn't ready, editors should still be able to build the page. We have them drop in lorem ipsum on purpose. As Craig told one editor, "We do searches for Lorem Ipsum. So that'll be a nice way to make sure that that doesn't go unfixed." Gibberish is easy to find. A plausible-but-wrong sentence is not.

The harder problem is placeholder content that looks real. On one project, the staging site had sample testimonials so the design would look finished. Late in the build, the client asked whether those reviews were real. They weren't, and they were weeks from going live. The rule after that was simple: nothing fake ships. No stock testimonies, sample staff bios, made-up stats or filler sermon series. And run that final lorem ipsum search before launch: one stray paragraph on a page search engines can index is easy to miss and hard to explain.

The design pattern that makes this workable is hide when empty. Build templates so a section with no content simply disappears, rather than falling back to sample text. Then a missing testimonial means no testimonial section, which is fine.

Don't let late content hold up launch

On a big church site, some ministry will always owe copy. Don't hold the whole launch for it. Unpublish pages that have nothing on them, hide sections whose links point nowhere, and make sure no button leads to a dead end. One church kept two versions of a block, one with a button to the unfinished page and one without, and switched them when the page was ready.

The same goes for photos. Give every image slot a text-only fallback, and use decent placeholder photos now rather than waiting on sign-off for a site nobody has announced yet. And if a page matters too much to rush, like a careful explanation of the gospel, move it to after launch and say so out loud.

Start this week

You don't need a vendor to begin. Pick your top ten pages, assign an owner to each and set up a simple tracker. If you'd like a second set of eyes on your plan or your current site, get in touch.