A 2021 article on planning a small medical clinic may still explain patient flow clearly. Its advice on permit timing, though, could be out of date, and its floor-area figures may lack a stated basis. There is no need to discard the useful explanation. Keep it, check the claims that can change, and give clients enough context to judge what applies to their project.
Different articles call for different levels of review. A guide to building types might need only a clearer diagram; a post on approvals may require a line-by-line check. Treating both as copy edits risks leaving consequential errors in place. The goal is not to make every page look new, but to make the claims it retains dependable and the decisions it informs easier to understand.
Choose the scope before editing
Start with a short inventory: title, publication date, subject, intended audience, named projects, and the person qualified to check technical claims. Note in one sentence why the article is still useful. If that is hard to say, find out whether the page still has a distinct purpose before committing to a refresh.
Prioritize by the consequences of an error, not age or traffic alone. A widely read explanation of accessibility clearances or fire strategy needs earlier review than an equally old piece about presentation methods. Articles that inform budgeting, site selection, procurement, or consent decisions also carry more risk than accounts of completed design competitions.
| Article condition | Appropriate response |
|---|---|
| Core explanation is sound; minor details are stale | Check the details, add context, and retain the structure |
| Useful subject, but the scope is unclear | Revise the title, opening, headings, and examples for a defined audience |
| Project facts remain accurate but describe an earlier stage | Label the stage and add a dated progress note, if verified |
| Central premise is no longer defensible | Rebuild the argument or retire the page; cosmetic edits will not fix it |
Usage data can show which pages people still consult. Low traffic, however, does not make a technical explanation disposable: an article answering a rare but high-stakes client question may be worth maintaining.
Check what can actually change
Before rewriting, mark time-sensitive claims: approval routes, statutory thresholds, code references, construction costs, programme durations, energy-performance figures, product availability, and a project's consent or occupancy status. Keep these separate from durable principles, such as coordinating structure with services or testing a floor plan against everyday circulation.
For substantive changes, record the original claim, what was checked, the jurisdiction and date, who checked it, and the replacement wording. This matters especially when an article covers several regions. Advice about planning permission in one locality should not quietly become general guidance.
Distinguish a planning allowance from a promise
Older posts often give figures without explaining their basis: “Allow twelve weeks for approval” or “Budget a fixed amount per square metre.” Readers need to know what each figure covers. If a range still holds, say whether it includes consultant work, authority review, tendering, contingencies, tax, or site-specific conditions. If no reliable current figure is available, explain the variables and remove the number rather than substituting a newer-looking estimate.
Where requirements vary by jurisdiction, identify the location and project type, then direct readers to check current requirements with the relevant authority or a qualified professional. That is more useful than attaching a broad disclaimer to a claim written as though it applies everywhere.
Repair the parts readers use to make decisions
Read the page as a prospective client, owner, or project manager who needs to act on it. Does it show which decisions can be made at concept stage and which depend on surveys or specialist advice? Can a reader distinguish a legal requirement from a design recommendation? Are the assumptions visible?
Consider an older article on converting an office to a clinic. It may cover room layouts but miss the capacity of the existing ventilation system. A focused paragraph could explain why room function, occupancy, infection-control needs, and existing plant must be assessed together. That changes what the reader takes away without calling for a new article. A piece on compact housing might instead need an annotated plan showing storage, circulation, and furniture clearances, rather than more general prose.
- Clarify the decision: Name the project stage and the choice the information supports.
- Expose assumptions: Identify the location, building type, existing conditions, and anything not yet surveyed.
- Explain trade-offs: Show where a lower initial cost could raise maintenance demands or limit future adaptation.
- Add a usable example: Describe a plausible constraint and the checks needed before choosing a response.
Apply the same care to project descriptions. Label a rendering of an unbuilt courtyard as a proposal. If operating data are unavailable, do not present predicted performance as measured results. Readers should be able to tell design intent, approved scheme, constructed outcome, and observed operation apart.
Keep useful material and make changes traceable
Keep explanations, drawings, and examples that remain accurate. Do not replace a practical paragraph just to make it sound newer. Define an unclear term, update a caption, or place a short “as of” note beside a changing requirement. After extensive revisions, a brief dated editor’s note can tell returning readers what changed—approval guidance or a project's delivery status, for example—without suggesting that every sentence was rewritten.
Check supporting material in the same pass. A legible diagram may have room labels that no longer match the text. A cost table may lack a date or list of inclusions; a photograph may show an earlier design option. Captions and alt text should describe what is shown, not claim an outcome the image cannot establish.
Use feedback to locate missing context
Questions from clients, facilities teams, and building users can expose gaps in an older explanation. Repeated questions about delivery access, overheating, or maintenance may warrant a focused addition to an otherwise sound post. Treat feedback as a reason to investigate, not proof that one design conclusion applies everywhere. For a fuller method of gathering and evaluating those observations, using building user feedback in design and operations deals specifically with that evidence.
Publish with a clear record of what was reviewed
Before republishing, have someone with the appropriate expertise check consequential claims. Then proofread the page in its published layout: do headings fit their sections, tables work on a narrow screen, images match the text, and project facts refer to the right stage? If only one section was checked, do not label the entire article “fully updated.”
Set review schedules by risk. Revisit approval and technical guidance when relevant requirements change, project case studies at milestones, and durable design explainers when new evidence or recurring questions reveal a gap. Give each page an owner and a next-review trigger, not just a calendar date.
For the 2021 clinic-planning post, that might mean keeping the patient-flow diagram, marking the scheme as conceptual, removing an unverified approval timeframe, and adding a dated paragraph on the existing-building surveys needed to inform ventilation and accessibility decisions. Record who checked those changes. The next editor will know where to start.