A partner changes the consultation fee. The website still shows the old amount, and a scheduled social post repeats it. The draft was accurate when it was written, but no one checked it before publication. In a small law practice, an editorial workflow gives each change an owner, a review, and an identifiable final version.
You do not need a new software platform to do this. A shared task list, a restricted draft folder, and a brief publishing record may be enough. Everyone does need to know which version is current and who can approve it.
Give every page a job before anyone starts drafting
A website request often starts with “We should say more about our family law work.” Before assigning a writer, ask what decision the page should help a prospective client make. Does the practice handle their type of matter? What happens at the first appointment? How are fees discussed? One page need not answer everything.
Keep a brief for each proposed item. Five fields are enough to start:
- Page purpose: the client question or business need it addresses.
- Intended reader: for example, a prospective client comparing local counsel, rather than lawyers seeking a technical update.
- Owner: the person responsible for getting the item published or closed.
- Required checks: legal accuracy, fee details, confidentiality, accessibility, or approval by a particular lawyer.
- Next review date: when someone should check whether the information still holds.
The brief can also keep a new practice from publishing every idea at once. A lawyer building a small employment practice might put a clear description of accepted matters ahead of a broad commentary post. If the firm does not yet serve a particular type of client, its website should not imply that it does. A manageable schedule based on real client questions is easier to keep than a promise to post every week; a separate content calendar for a small law practice can hold longer-term ideas without making each one an immediate assignment.
Assign roles, even if one person holds several
In a two-person practice, the same lawyer may propose, draft, and publish a page. Treat those as separate checkpoints anyway. “I finished writing” does not mean “this is approved for the website.”
| Role | Responsibility | Typical owner in a small team |
|---|---|---|
| Request owner | Defines the purpose and confirms that the page is needed | Practice owner or responsible lawyer |
| Drafter | Prepares text using the agreed brief | Lawyer, staff member, or external writer |
| Substantive reviewer | Checks legal statements, scope of services, and client-facing claims | Lawyer familiar with the practice area |
| Publisher | Enters the approved version and checks it on the live site | Office manager or designated lawyer |
One person can fill all four roles, but it helps to perform the checks at different times. A solo lawyer might draft on Tuesday, review the facts and professional-responsibility issues on Thursday, then publish on Friday from the approved file. That pause can expose a sentence that assumes every client matter follows the same process.
If an external writer or web contractor helps, set boundaries. They can improve readability or upload approved text; they should not decide whether a legal claim is sound, a testimonial can be used, or a fee is correct. Limit their access to the files and website functions they need.
Use a short sequence with visible handoffs
Give each stage a clear exit condition. A shared board or spreadsheet could use Proposed → Drafting → Legal review → Ready to publish → Live → Review due. Add “Waiting for information” when a fee, service detail, or approval is missing, so a stalled draft does not look finished.
1. Gather source information
Before writing, the request owner provides the facts: services the firm currently offers, who handles inquiries, what can be said about fees, and which statements need qualification. For an office-location page, confirm where clients can actually meet the lawyer. A shared office may offer bookable meeting rooms without a staffed reception desk every day; the website should describe what clients will encounter.
Ask staff who answer calls what clients tend to misunderstand. Their notes may show that a page needs a clearer explanation of consultation booking or billing. Remove identifying client details before those notes become part of a drafting brief.
2. Draft in one controlled place
Choose one working document and name it clearly, such as “Consultations page — draft — 2026-03.” Keep comments there or in the associated task, not across scattered email threads. If a contractor edits the website while a lawyer revises a separate file, it becomes hard to tell which version is final.
Mark unresolved points in the draft. “Confirm whether evening appointments are offered” is a useful working note, but it must be resolved before publication. Keep drafts out of public website folders and broadly accessible shared drives if they contain sensitive business or client information.
3. Review substance before polishing
The substantive reviewer should focus on statements a reader might rely on. Are the practice areas current? Does “free consultation” apply to every initial conversation or only certain inquiries? Does the cost description need a qualification? Can the firm support words such as “specialist,” “best,” or “guaranteed result” under the rules where it practices?
Then read the page as a client would. Is the main point clear? Is the next step apparent? Do the phone number, hours, office arrangements, and fee language agree with other pages? The pages need not sound identical, but they should not give conflicting instructions.
4. Approve a specific version
Record approval against a dated file or document version, rather than a message saying “looks good.” Send meaningful wording changes back to the substantive reviewer. A small typo correction may not need another legal review; a changed price, service description, eligibility statement, or outcome claim does.
5. Publish, then inspect the live page
The publisher should transfer only the approved version. Once it is live, open the page on a phone and a desktop screen, test the contact route, and check the headings, lists, and images. Look for an old fee or office address lingering in a callout, menu, or other page element. Add the live URL, publication date, approver, and next review date to the task record.
Build safeguards around sensitive material
Law firm content has risks that a general small-business blog may not. A case example can identify a client even without a name if the circumstances are distinctive. A desk photograph can expose paperwork. A casual claim about expected results can give the wrong impression about an individual matter.
Require specific approval for client stories, testimonials, screenshots, and case details under applicable confidentiality and professional-conduct rules. If a hypothetical example explains the point just as well, label it as hypothetical. Do not let a deadline push uncertain material onto the site.
Legal and tax information on a practice website cannot replace advice from a qualified professional about a reader’s circumstances. Check current legislation and applicable professional rules before publishing or revising it. Rules on lawyer advertising, fee descriptions, privacy, and testimonials vary by jurisdiction and can change.
Give small updates a lighter route
Not every edit needs the full path from brief to publication. Updating an office closure date or fixing a broken sentence should be quicker than launching a new practice-area page. Set up two routes:
- Routine correction: a designated person makes a verified factual or formatting change, checks the live page, and records what changed.
- Substantive change: new legal information, fees, services, promises, testimonials, or contact procedures go through lawyer review and approval.
Judge the change by its meaning, not its word count. Replacing “may” with “will” is a tiny edit that can change a claim materially. Swapping a meeting-room photograph may be routine, but check its caption if it suggests clients can visit without an appointment.
For an urgent correction, such as a wrong phone number or outdated consultation price, remove or correct the inaccurate statement promptly, then complete the record afterward. The log should help the team track fixes, not hold them up.
Connect website work to the channels that repeat it
A new page often supplies wording for a social post, directory profile, email reply, or printed handout. Each is a separate publishing surface: approval for the website does not automatically approve every reuse. A social post may drop an important qualification, while a staff email template may keep quoting an old consultation fee.
When a page changes a core fact, add an “other places to check” note to its task. A move from a home office to shared meeting space might affect the contact page, appointment confirmation, public profiles, and receptionist instructions. A fee change might affect the consultation page, intake script, and scheduled social posts. Assign each check to someone.
Keep the system proportionate to the team
If maintaining the workflow takes longer than making the update, simplify it. Start with one task record per piece of content, one location for approved versions, and a short checklist. Restrict publishing access, and update account permissions when staff or contractors leave. An inexpensive shared document may suffice if it has version history and restricted access; a more elaborate tool helps only if the team will keep using it.
Set realistic review dates. Check a page showing current fees or office arrangements whenever those details change, as well as on its scheduled review date. A general explanation of how to request an appointment may stay accurate longer, but it still needs an owner. If one lawyer owns every page, a brief monthly pass through items marked “Review due” is more manageable than rereading the whole site.
For the next website change, open a task named after the page. Before drafting, add the working document link, named approver, factual checks, and proposed review date. When it goes live, record the URL and the date the approved version was published. The next person handling that page will know where to start.
