A style guide can become a long list of preferences that nobody consults. It can also become a practical reference that prevents repeated factual mistakes and saves a small editorial team from deciding the same issue every week. The difference lies in what the guide is designed to do. For a cultural publication, consistency should support understanding, attribution and accountability before it supports a preferred surface tone.

Start with the problems your editors actually encounter. A contributor's name appears differently across pages. A date is ambiguous for international readers. A quotation has been shortened without preserving its qualification. A programme preview looks like a first-hand review. These are stronger reasons for a house convention than the desire to sound uniformly sophisticated. A useful guide gives writers enough structure to work confidently while leaving room for their own reporting and thought.

Collect editorial problems before writing rules

Review a manageable set of recently edited articles and note the decisions that required discussion. Separate factual or interpretive problems from matters of taste. A misspelled artist's name, an unclear event date and a missing attribution can change what readers understand. A preference about a particular adjective may matter less. This distinction helps a small team avoid spending its limited time on the easiest rather than the most consequential rules.

Ask occasional contributors what they find difficult to infer. They may not know whether the publication uses first-person visit notes, how to identify a supplied image or where to record a source. A permanent editor can forget that informal habits are invisible to someone joining a project. Include those practical gaps in the first version of the guide.

Do not attempt to solve every possible language issue. Use a reliable general reference for ordinary spelling and punctuation, then document the publication's important choices and departures. A local guide that restates an entire dictionary is harder to maintain and less useful than a short explanation of the decisions peculiar to the publication.

For each proposed rule, write the misunderstanding or production problem it prevents. If the only explanation is that one editor likes it, classify it as a preference rather than a major requirement. Preferences can still be recorded, but they should not receive the same weight as a convention protecting a person's identity or the meaning of a quotation.

Put names, dates and article status near the beginning

Specify how names are verified and where the verification is recorded. A contributor's preferred professional spelling, diacritics and role descriptions should be checked rather than guessed from a search snippet. The guide can explain how to handle a first mention and a later shortened reference while preserving the person's identity. It should not encourage an editor to remove unfamiliar characters merely for visual simplicity.

Choose an unambiguous date format for the audience. International readers can interpret short numeric dates differently. Give examples of the house format and explain how dates relate to a programme's local time and location. When an article contains a schedule, identify which official source confirms it. A style decision cannot replace verification of the actual arrangement.

Define the publication's article types. A listing communicates checked practical details. A preview examines a forthcoming programme without implying attendance. A review involves an identified evaluative basis. A practical guide offers methods and examples. A visit note describes the scope of a particular encounter. The labels help writers and readers understand what evidence the piece is expected to contain.

Explain publication and modification dates separately. A new title or a minor punctuation edit should not silently turn an older article into a newly reported feature. A substantive revision should have a record of what changed. This convention protects the usefulness of the archive and makes later factual questions easier to assess.

Write quotation and attribution rules as editing decisions

State that direct quotations must preserve meaning and be traceable to a recording, written response or reliable note. Explain what the team may do with repetition, incomplete speech and minor errors, then identify when a query is necessary. A short example is more useful than an abstract instruction to edit sensitively.

Keep paraphrase distinct from quotation. A writer can explain a contributor's position in their own words, but the result should not be placed inside quotation marks. A compressed quotation should not erase a meaningful condition. If a curator says an arrangement worked for one programme, the edit should not make them appear to recommend it universally.

Give attribution a consistent location when readers need to distinguish intention from established outcome. An organisation may say that a project aims to increase participation; the publication should not transform that aim into a demonstrated result without appropriate evidence. A house rule can remind writers to identify the source and status of such claims without forcing every sentence into the same formula.

Document later clarifications. If a contributor corrects a date or supplies a new explanation after an interview, retain that record alongside the original. The style guide does not need to expose the correspondence publicly, but it should explain how the published version remains connected to the material on which it relies.

Give each rule a reason and a worked example

A compact rule entry can contain the decision, the reason, one example and the route for exceptions. For instance, a date rule can show an ambiguous numeric version, the house version and the reader problem the change prevents. This makes the guide teachable and reduces the chance that a rule will be followed mechanically in a context where its purpose no longer applies.

Use examples from the publication's subject. A general writing rule becomes easier to apply when the example concerns an exhibition title, a maker's name or a programme description. Keep examples hypothetical unless they are drawn from material the team is entitled to reuse. Do not reproduce a contributor's mistake in a way that turns a useful training example into public embarrassment.

Show what a rule does not decide. A convention for title capitalisation does not establish an artwork's correct official title. A preferred spelling does not authorise changing the spelling inside a faithful quotation. A format for source notes does not prove that the underlying source supports the article. These boundaries prevent house style from becoming a substitute for judgement.

Keep the first version short enough to use during editing. A searchable page with clear sections can be more practical than a polished PDF that becomes outdated immediately. The delivery format matters less than whether writers can locate the relevant decision, understand its purpose and identify the current version.

Rule componentQuestion it answers
DecisionWhat should the writer or editor do?
ReasonWhich misunderstanding does it prevent?
ExampleWhat does correct application look like?
BoundaryWhat does this rule not establish?
Exception routeWho decides an unusual case?

Preserve voice and make exceptions visible

A style guide should not force every interview, essay and practical article into identical sentence rhythms. Shared factual conventions can coexist with different voices. Decide which elements must be consistent for readers and which can vary with the form. A reflective essay may use a different opening from a practical visitor guide without either becoming an editorial failure.

Create an exception log for decisions likely to recur. Record the case, the reason and the person who approved it. This is different from keeping a list of contributors allowed to ignore the rules. An exception should arise from the content or context, such as preserving an official title, rather than from a vague preference for a prominent person's wording.

Review recurring exceptions as evidence about the rule itself. If editors repeatedly work around the same instruction, it may be unclear, overbroad or unsuitable for the publication. Revise it openly instead of accumulating private habits that new contributors cannot discover. A useful guide evolves through editorial work rather than claiming permanent authority.

Distinguish an ethical boundary from a stylistic choice. Accuracy, honest attribution and respect for agreed private information are not simply matters of house taste. A team should not label a material misrepresentation an acceptable exception because it produces a stronger opening. The guide can make those priorities clear without pretending to replace the publication's wider editorial policy.

A hypothetical publication turns three recurring errors into conventions

Imagine a small culture website that repeatedly edits the same problems: abbreviated dates are unclear, programme previews sound like reviews and image records are scattered through email. Its first proposed style guide concentrates on preferred adjectives and punctuation. The team instead starts with the three errors that affect reader understanding and accountability.

The revised guide establishes a written date format with an example, defines preview and review by their information basis, and requires an internal image record before publication. Each convention names the person responsible for checking it. Contributors receive the relevant section with the commission rather than discovering the rules only after submitting a draft.

A later essay needs an unusual title treatment because the official exhibition title includes distinctive wording. The editor records the exception and preserves the official name. That does not change how ordinary article titles are handled. When several contributors ask the same question about the preview label, the team clarifies the definition instead of blaming writers for misunderstanding an informal habit.

This hypothetical example illustrates a guide built around actual work. It does not promise faster production or fewer errors as a measured result. It creates a clearer basis for decisions, which the publication can then evaluate through its own editing records.

Teach the guide through real editorial use

Introduce the guide when commissioning an article, with the small number of rules most relevant to that assignment. A new contributor should not have to absorb every archive convention before writing one interview. Explain how to ask questions and where to record sources. A short orientation can prevent the guide from appearing only as a list of corrections after submission.

Maintain a dated change log that describes meaningful revisions. Notify active contributors when a rule affecting their work changes. Do not require someone to follow a convention that was introduced privately after their deadline. Consistency includes the way the publication treats its collaborators, not only the appearance of the finished page.

Review the guide against recurring editing queries rather than its length. If the same factual problem keeps appearing, inspect whether the rule is understandable, findable and feasible. If a section is never used, consider removing or simplifying it. The goal is a working editorial memory: enough shared knowledge to prevent avoidable confusion while leaving room for careful thought in the next unfamiliar case.

Questions specific to this guide

How long should a small publication's style guide be?

Long enough to resolve its recurring consequential decisions, but short enough to consult during work. Use an established general reference for ordinary language questions and focus the house guide on the publication's own important conventions.

Should contributors all sound the same?

No. Consistent factual treatment, dates, attribution and navigation can coexist with distinct voices and article forms. Apply shared rules where they protect reader understanding, rather than treating uniform rhythm as the main goal.

Who should decide exceptions?

Give a named editorial role responsibility and record the reason. Repeated exceptions should trigger a review of the rule. An exception log should clarify judgement, not provide an unaccountable route around accuracy or honest representation.

Further reading

Authoritative background on related planning and access questions. These resources provide context; they do not endorse this guide or replace the current requirements for your specific setting.