Build a Sustainable Publishing and Maintenance Process

19.1 Capture Expertise Efficiently Through Interviews, Project Debriefs, and Existing Materials

Begin with a specific question that a prospective client needs answered. Use the question backlog developed earlier in the playbook, together with recurring inquiries, misunderstandings, and gaps identified through monitoring. “What does a production diagnostic include?” gives a consultant a manageable assignment. “Write something about operational excellence” leaves the writer and expert to invent the purpose.

Prepare a short brief identifying the reader, decision, service, intended format, responsible expert, and boundaries. Check whether an existing page can answer the question with an update before commissioning another article. Record what the proposed piece would add.

Interview for decisions, evidence, and limits

A focused interview can produce the substance of a useful piece without asking the professional to write it. Send the questions in advance and book time that the expert can realistically protect. For a straightforward topic, a thirty-minute conversation might cover:

1. What is the prospective client trying to decide?
2. When is this service appropriate, and when is it unsuitable?
3. What does the work involve, and what does the client receive?
4. What do buyers commonly misunderstand?
5. Which assumptions, exceptions, or limitations change the answer?
6. What evidence or authorized example supports the explanation, and what still needs checking?

Record uncertainty as uncertainty. An expert’s recollection of a statistic is a lead to investigate. It becomes a publishable numerical claim only after the source, scope, and calculation have been checked. Experience-based judgment can be valuable when its basis and limits are clear.

Use the firm’s approved recording and transcription process. Check the resulting notes before treating them as evidence, especially names, numbers, quotations, and qualifications. A generated interview summary is a working aid.

Reuse existing work with a clear publication boundary

Review existing articles, public presentations, proposals, and project debriefs for useful explanations. Possessing a document does not establish permission to republish it. Distinguish material already cleared for public use from material requiring further permission or professional review.

For example, a consulting debrief might support an article explaining how a pricing diagnostic separates data problems from decision problems. The article can use a clearly labeled hypothetical illustration. A real client result needs both supporting evidence and appropriate permission; satisfying one requirement does not satisfy the other.

Removing a client’s name is not a complete publication review. A combination of industry, location, transaction timing, and project details may still reveal the relationship. Give the writer approved material to use rather than asking them to guess what is confidential.

Keep a compact evidence record

For each material claim, retain the proposed wording, supporting source or calculation, relevant date and scope, public-use status, and reviewer’s decision. Add a trigger for reconsideration when the claim could change. A short source list and a few annotated claims may be sufficient for a simple article.

Keep public citations separate from restricted working evidence. The published article may link to a public research report; client permissions and confidential debriefs belong in an appropriately restricted record. For complex pieces, resolve the factual outline before asking a writer to develop the full draft.

19.2 Coordinate Writers, Subject-Matter Experts, Professional Reviewers, Marketing, and Website Owners

Give each asset one named content owner. That person approves the brief, obtains decisions, resolves delays, and remains accountable for maintenance after publication. “Marketing” or “the agency” is not a sufficiently specific assignment.

The following are functions, not a requirement to hire five people. A boutique firm can assign several functions to one person where competence and the firm’s policies permit.

Make each review a defined decision

Send the draft with a short list of decisions required. Highlight new claims, changed service descriptions, unresolved evidence, client examples, and professional conclusions. The reviewer should be able to see where judgment is needed without reconstructing the entire assignment.

Separate approval of the substance, completion of required publication clearances, and authorization to release the final version. An editor may improve readability after expert review, but a change to meaning, a qualification, or a service promise returns to the appropriate reviewer.

Record the approved version and approver. A comment that an early outline “looks fine” is not approval of a later article containing new claims. When the page goes live, compare the implemented page with the approved version, including its title, summary, author information, links, and download.

Agree on a review date before drafting starts. If the reviewer is unavailable, the content owner can use a qualified backup, revise the publication date, or narrow the piece to material that can be properly checked. Silence is not approval. Refer conflicting professional judgments to the designated practice leader as a specific question.

Match drafting volume to review capacity

Set the work limit from the constrained resource. Suppose a practice can protect two substantive review slots each week. An initial rule could permit no more than two completed drafts to wait for that reviewer. Adjust the limit when actual review time and complexity become clear.

When the queue is full, the editor can resolve missing evidence, prepare future interviews, or complete approved maintenance. Starting more drafts can increase delay and rework. Leave room for corrections and consequential updates that should displace a new article.

Track the age of blocked items, missing decisions, substantive rework, and overdue maintenance. These measures help the content owner repair the process. Publication counts alone do not show whether the firm is creating information it can responsibly maintain.

19.3 Use AI Assistance With Source Verification and Clear Human Responsibility

Use AI for defined tasks within the editorial process: organizing approved notes, proposing an outline, identifying gaps, simplifying prose, drafting a summary, or comparing versions. Keep a human responsible for the published explanation and the evidence behind it.

A polished draft can still contain inaccurate claims. NIST’s Generative AI Profile recommends reviewing and verifying sources and citations in generated outputs. Google’s current guidance calls for manual factual review of AI-generated web content, including titles, descriptions, structured data, and image alternative text. 

Draft from an approved source packet

Give the tool the cleared interview notes, current firm facts, and selected primary sources relevant to the brief. Specify the intended reader, scope, and required qualifications. A useful instruction is:

“Use the supplied material to draft an explanation for the stated audience. Preserve qualifications. Identify missing evidence as a question. Do not invent client results, quotations, credentials, or sources.”

That instruction helps define the task; it does not validate the output. A writer should check that cited sources exist and support the specific claims made. The professional reviewer should check meaning, exceptions, dates, geography, and the description of the firm’s actual service. Recalculate material numerical examples independently.

If AI proposes an additional source, open and assess it before relying on it. Do not ask the same model whether its own unsupported assertion is correct and treat its confidence as verification. A source that discusses a broad topic may still fail to support the particular conclusion in the draft.

Approve the information and the attribution

Use tools approved for the information involved. Before using client material, follow the firm’s rules for confidentiality, access, retention, and external processing. Removing names does not necessarily make a document suitable for an unapproved service.

For law firms, the responsible lawyer should approve the workflow under the governing professional rules. ABA Formal Opinion 512 discusses verification, confidentiality, and supervision when lawyers use generative AI. It interprets the ABA Model Rules; the applicable jurisdiction, engagement, information, and circumstances determine the firm’s obligations. 

Describe authorship and review truthfully. An expert named as the reviewer should have reviewed the actual substantive version. An interview participant is not automatically the author of a later article. Google encourages accurate authorship information and identifies fabricated profiles and false credentials as deceptive. 

Explain material AI assistance when readers would reasonably need that context, using an accurate description of what the tool and the people did. Do not imply that professional judgment was automated if it was not, or that a human checked material that nobody reviewed.

In a hypothetical accounting article, an AI draft changes “effective next year” to “required now” and drops an exception. The accountant corrects both against the authoritative source. The editor then checks the title, FAQ, summary, and metadata for the same errors before releasing the approved version.

19.4 Make PDFs, Videos, Podcasts, and Webinars Accessible Through Appropriate Text and Attribution

Plan the supporting text when commissioning an asset. A report, recording, or slide presentation should have a clear public destination that explains what it covers and lets the intended audience use it. Producing that text is part of the publishing assignment.

For each significant asset, provide a descriptive page title, a substantive overview, contributor identities, relevant expertise, original publication or recording date, and links to the material and related practice information. If the full asset requires registration, describe the publicly available portion honestly. Keep client-only and confidential material behind the appropriate access controls.

PDFs: preserve actual text and reading structure

Google can index PDF content, so there is no basis for treating every PDF as invisible to search. Format support does not establish that a particular document has been indexed or selected for an answer. 

Start with the editable source document where possible. Export actual text with appropriate structure. For a scan, use optical character recognition and check the result. Adobe’s accessibility guidance addresses document tags and explicitly requires manual verification of logical reading order; searchable text alone does not establish accessibility. 

Check technical terms, tables, footnotes, figures, units, and names. A quick copy-and-paste check can reveal a broken text layer, but it is not a complete accessibility assessment. Give important findings and limitations a useful HTML explanation as well as a downloadable document.

Recordings: review captions and provide usable transcripts

W3C’s transcript guidance describes text covering speech and relevant audio information, with descriptive transcripts also covering necessary visual information. It discusses HTML presentation and speaker identification. These are useful production requirements for a professional interview, podcast, or webinar. 

Check automatic captions against the recording. W3C warns that errors can change the meaning, including when a single consequential word is omitted. Pay particular attention to professional terminology, amounts, dates, exceptions, and speaker changes. 

Explain relevant information that appeared only on slides, such as the conditions attached to a chart. Clearly distinguish editorial additions from the speaker’s words. A short promotional summary should be labeled as a summary.

Use “transcript edited for readability” only when that describes the treatment. A substantially reorganized explanation is better presented as an article based on the event, with appropriate attribution and approval. Preserve the recording date when later text is corrected or updated.

For example, a consulting webinar on integration planning might yield a corrected transcript and a separate article explaining a diagnostic method. The article identifies the event and contributors, preserves the method’s limits, and links to the recording. It does not turn a guest’s tentative observation into the firm’s established finding.

Treat these as improvements to the usability and clarity of the firm’s material. Assess any claimed GEO effect through the monitoring and experiment methods established earlier in the playbook.

19.5 Maintain Service Information, Credentials, Publications, and Time-Sensitive Technical or Regulatory Content

Assign maintenance when an asset is created. Record its URL or file location, content owner, relevant practice and jurisdiction, approved version, supporting evidence, last review, next review, and events that should trigger earlier attention. Link related formats and derivatives so a correction can reach all of them.

A date on a calendar is only one trigger. Changes to services, personnel, credentials, offices, methods, professional guidance, or the evidence underlying a claim can require action before the next scheduled review.

Review according to consequence and rate of change

Give priority to information that could materially mislead a prospective client or cause someone to rely on an outdated technical explanation. A changed service boundary deserves a different response from a broken link in a dated event announcement.

For technical or regulatory material, retain the relevant authority, jurisdiction, status, effective date, and period to which the explanation applies. Distinguish a proposal from an adopted requirement and an adopted requirement from one already effective. An alert opens a review task; an appropriate professional decides what the change means.

A law firm’s article might explain a rule as it stood when published. If a later amendment changes the practical answer, the reviewer can update the explanation or retain it as clearly identified historical material with a link to the current treatment. A generic footer does not resolve a misleading main passage.

For an engineering practice, the same method can track the edition of a technical standard discussed in an article. The responsible professional decides whether a new edition changes the explanation and which jurisdictions or projects it affects. The publication process should not automatically replace every edition number.

Choose the appropriate maintenance action

A review should end with a recorded decision: retain unchanged, update, correct, consolidate, archive, or remove. Retain a useful older explanation when it remains accurate. If two pages compete to describe the same current service, consider maintaining one clear destination and arranging suitable links or redirects through the website owner.

Preserve historical authorship when a professional leaves the firm. Update current biographies, affiliations, contact routes, and statements about who provides the service. Do not silently reassign the departed professional’s article to someone else.

For a material error, use the correction process established earlier in the book. Record what changed and why, check related pages and files, and add a reader-facing correction or status note where needed. If the material cannot safely remain public while being corrected, use the firm’s approved withdrawal process.

Keep dates honest and versions connected

Distinguish the original publication date, a substantive update, and a review that found no change necessary. Google cautions against changing dates to suggest freshness when content has not substantially changed. If a review date is displayed, label it as a review date and keep the record of the review. 

Keep equivalent visible dates and structured date values consistent. Google’s sitemap guidance says lastmod should reflect the last significant update; an annual copyright-date change is not such an update. Have the website owner implement these fields according to what actually happened. 

When a fact changes, inspect its related service page, biography, report, recording description, and other authorized copies. Updating the main article alone may leave contradictory material elsewhere. Keep the correction record and monitor important answers afterward; publication of a correction does not establish that external systems have already incorporated it.

19.6 Manage Agencies and Freelancers With Clear Methods, Approvals, Work Ownership, and Handover

Commission verifiable work. A provider can be accountable for research, drafts, implementation, records, and agreed checks. Evaluate claims about AI visibility through the program’s evidence, with the attribution limits explained in Chapters 17 and 18.

Give the provider the approved audience, question, service scope, expert contact, available material, deliverable, schedule, and acceptance criteria. Specify who can approve public claims and who can authorize publication.

Approve methods as well as deliverables

Ask how the provider will obtain and verify information, which AI tools and subcontractors it will use, and how it will protect firm information. Agree which routine changes it may make independently and which require further review.

State the ethical boundaries explicitly. Exclude invented expertise, fabricated citations, false reviews, misleading sponsorship, and hidden instructions intended to manipulate AI systems. Permission to work on GEO does not authorize every technique a supplier offers.

For an article or page, completion means that it answers the approved question, its material claims have support, required reviewers have approved the release version, and the published implementation matches it. Include editable source files, references, and maintenance information in the deliverable.

Arrange rights, access, and continuity

Document the firm’s rights to use, edit, and republish the commissioned work and its components. Distinguish those rights from the provider’s pre-existing tools or templates and separately licensed third-party material. Resolve these terms before production.

Keep core website and reporting accounts under firm-controlled administration. Give contributors appropriate individual access and retain the ability to obtain agreed data and source files. A routine correction should not depend on reaching a former freelancer or recovering a personal account.

Define the exit handover at the start. It should include the asset inventory, editable files, source and clearance references, unresolved questions, templates, publishing instructions, remaining work, reporting definitions, and account or integration inventory. Agree how access will transfer or end and how retained copies will be handled under the contract and applicable requirements.

Test the handover with a routine maintenance task. The incoming owner should be able to locate a page’s evidence, identify its approver, prepare a correction, and follow the release procedure. Resolve missing information while the outgoing provider is still available.

Practical Output: Editorial Workflow, Publication Checklist, Maintenance Schedule, and Supplier Brief

Use the following templates as a starting point. Assign named people, select review intervals appropriate to the practice, and keep the evidence record with the asset throughout its life.

1. Editorial workflow

Return substantive changes to the relevant reviewer. A blocked item retains an owner and next action; it does not advance merely because its planned publication date has arrived.

2. Publication checklist

• Purpose: The piece answers the approved reader question and accurately describes the relevant service.
• Evidence: Material factual claims, quotations, calculations, and references have been checked.
• Scope: Jurisdiction, periods, assumptions, exceptions, and limitations are clear where relevant.
• Permissions: Client examples and third-party material have the required clearance for this use.
• Attribution: Authors, contributors, reviewers, affiliations, and credentials are represented truthfully.
• Formats: The page, download, captions, transcript, and summary have received their applicable checks.
• Implementation: Titles, descriptions, links, dates, structured data, and access settings match the intended publication.
• Approval and upkeep: The release version is approved; the owner, evidence record, related assets, and review triggers are recorded.

3. Maintenance schedule

The intervals below are illustrative starting points, not platform requirements or professional review deadlines. An event or identified error can require earlier action.

4. Supplier brief

Complete these fields before the assignment begins:

• Purpose and scope: Reader, question, services covered, boundaries, and intended outputs.
• People and timing: Content owner, expert, reviewers, publisher, milestones, and review dates.
• Sources and methods: Approved material, verification method, permitted tools, subcontractors, and information handling.
• Acceptance: Required evidence, clearances, implementation checks, and editable deliverables.
• Rights and access: Agreed reuse rights, third-party licenses, account administration, and contributor access.
• Handover: Asset register, source and approval records, outstanding work, instructions, and transfer of maintenance responsibility.

Before expanding production, run one new asset and one maintenance task through the complete process. Check whether the people taking over at each stage can act from the record they receive. Repair missing evidence, ambiguous approvals, and unclear ownership before increasing volume.

A sustainable publishing process gives the firm a public body of work it can explain, support, and keep current. That is the foundation for helping prospective clients and AI services understand the firm accurately over time.