Abstract
A manuscript can appear nonconforming before an editor has made any explicit judgment about it. Reusable templates, styles, and defaults establish an ordinary case for heading structure, note treatment, spacing, citation appearance, page order, and other document relations. Their practical usefulness is real: they can make work more consistent, reduce repetitive decisions, and keep production handoffs legible. Yet a reusable rule can also make a textual relation look defective merely because the rule does not anticipate it. This paper introduces template authority—the practical power of a default to make a presentation or relation appear normal before a local decision is made—and offers the Template Authority Trace, a nine-field record that follows a default from rule to rendered consequence, presumed normal case, exception trigger, accountable review point, evidence, and non-conclusion. The instrument does not evaluate template software, prescribe style rules, or decide whether an editorial exception should be accepted. It is a way to make an inherited rule discussable before it silently becomes the decision.
Teaching proposition. A reusable default is not a verdict on the manuscript. It is a rule that has already made an ordinary case operational. Before treating a departure as a defect, an editor can trace the rule, its owner, its rendered consequence, the relation it presumes, and the place at which a reviewable exception could be considered.
The Manuscript That Looked Wrong
The warning appeared before anyone had disagreed with the essay.
Consider a constructed editorial case. A source-critical chapter arrives in a reused manuscript template. Its second section is only three paragraphs long. It begins with a heading, Documentary Breaks, followed immediately by a numbered note. The note identifies a gap between two surviving witnesses of the text and tells the reader why the break matters before the chapter’s explanatory prose begins. The author has not added the note for ornament, nor mistaken a comment for a citation. The note establishes the documentary condition under which the section must be read.
The template makes the page look careless. Its established heading hierarchy expects a heading to open directly onto prose. Its note treatment assumes that notes qualify claims made in a paragraph, rather than announce the evidentiary status of a section before the paragraph begins. The heading therefore appears stranded. The note marker looks like a leftover. A production review might state, in ordinary language, Please move this note into the first paragraph; the current layout is irregular.
The instruction is not obviously unreasonable. A manuscript template has to anticipate recurrent cases. It gives authors, copyeditors, typesetters, and proofreaders a shared field of expectation: which heading level belongs where; how notes attach to text; what kind of spacing signals a new movement; which elements a later production process is meant to recognize. Public documentation for reusable style systems makes a similar practical case in other settings. The U.S. Web Design System describes design tokens as a selected, limited palette of values for typography, spacing, color, and related elements; those values can then be made available through settings and components rather than redetermined in every instance.[1] The LibreOffice documentation likewise describes a style as a group of formatting attributes applied together and contrasts that method with manual attribute-by-attribute formatting, which it characterizes as more time-consuming and error-prone.[2]
But an ordinary case is not the only case. The question raised by the page is not, at first, whether the author deserves an exception. It is more elementary: Which rule has already decided that this page is irregular? Until that question is asked, a visible arrangement can be mistaken for a failure of authorial discipline rather than a mismatch between a textual relation and a template’s assumed normal use.
The distinction is practical. A default enters the document before an editor has articulated a local reason. It can make some relations easy to display and others cumbersome; it can make some departures conspicuous and others almost impossible to see. A source-critical note before a paragraph becomes a problem of placement. A heading that signals documentary status becomes a problem of hierarchy. The rule may be sensible, carefully maintained, and worth retaining. Still, it is carrying an unspoken proposition about what a normal manuscript is supposed to do.
This paper calls that condition template authority: the practical power of a reusable rule to make a presentation, hierarchy, workflow, or textual relation appear normal and thereby to shape editorial judgment before an explicit local decision is made. The phrase does not accuse templates of bad faith, and it does not make the author’s variation automatically virtuous. It names a mundane form of authority: the authority to establish a baseline that subsequent workers can inherit before they notice they have inherited it.
The teaching task is therefore neither to dethrone the template nor to defend it by reflex. It is to turn a complaint such as “this looks wrong” into a traceable inquiry. What default is in force? What relation does it affect? What normal case does it presume? Whose account of the rule is available? At what review point can a specific departure be considered with evidence, without quietly turning a local adjustment into a new house rule?
A Default Is a Rule with a Normal Case
The word default sometimes suggests the absence of a decision. In an editorial system, it is better understood as the result that follows if no one interrupts a prior decision. A heading style appears when a heading is assigned. A note is placed or rendered according to a standing instruction. A citation comes out in a familiar form because a style definition, class, template, or production routine has been given that work. The default may have originated in a deliberate conversation, a copied file, an inherited stylesheet, a vendor configuration, or a now-untraceable precedent. Its provenance can be clear or obscure. Its effect is still present.
Research on defaults must be used carefully here. In a different and much higher-stakes decision domain, Eric J. Johnson and Daniel G. Goldstein studied the no-action default for organ-donation agreement. Their article examines how the form of the question and the available opt-in, opt-out, or mandated-choice arrangement can influence observed responses.[3] A manuscript template does not ask an organ-donation question, and this paper does not claim that a template causes an effect of comparable kind or magnitude. The narrower lesson is conceptual: what happens without a fresh act of selection is part of the decision environment. Familiarity does not make a preselected path neutral.
For editorial work, the consequence to examine is usually not a reader’s preference. It is a relation among document elements. Does a heading announce a topic, a source division, an interruption, or a logical step? Does a note merely document a sentence, or does it qualify the status of a section? Does a local style make a distinction visible for downstream work, or does it erase the distinction before a human being has had reason to consider it? Such questions do not convert style into a matter of individual taste. They ask what a style is doing to the textual relation at hand.
A useful rule of inquiry follows: do not begin with the page’s deviation; begin with the rule’s presumed normal case. In the constructed chapter, the rule presumes that prose follows a heading and that notes qualify prose. That presumption is efficient for a great many chapters. The chapter in question asks the note to do a different job. The discrepancy is neither automatically an authorial error nor automatically an exemption. It is an exception trigger: an observable condition that calls for accountable attention.
The normal case matters because it gives a default its practical point. Without normal cases, a template could not reduce repeated labor or make a production process legible. But normal cases are not self-interpreting. They have boundaries. The moment a document relation lies at the boundary, a reusable rule becomes a governance question: Who can tell whether the rule applies? What evidence should be consulted? Who can distinguish an individual preference from a textual requirement? Where is the record of the decision kept?
Trace the Authority, Not the Person
When a page looks strange, the fastest response is often to correct it. That response can be right. It is not always sufficient. An editor who moves the note has solved a visible layout problem; the action may leave unanswered whether the note’s original location carried a source-critical function. An author who insists that the arrangement is intentional may be right; the assertion may leave unanswered whether the arrangement can survive editing, typesetting, proofing, and accessible presentation. The problem is not that one side is authorized and the other is not. The problem is that a document-level judgment is being asked to occur without a shared account of the rule and the relation.
The public template alone rarely contains that account. In a qualitative study of visualization style guides, Alvitta Ottley and Jonathan Schwabish argue that guidance must be understood as a socio-technical system rather than as a collection of visible rules. Their PRISM framework identifies Purpose, Rules & Mechanisms, Institutional Enforcers, and Situated Flexibility; the researchers emphasize that public guides expose only a portion of the surrounding system.[4] Their field is data visualization, not manuscript editing. Nevertheless, their distinction helps explain why a file with named styles can be legible while the justification, owner, and exception path remain invisible.
The implication is modest but useful. A template does not speak for itself. It can disclose a setting, a style name, a constraint, or a rendered result. It may not disclose why the setting exists, whose problem it was designed to solve, who may revise it, or whether a departure has ever been considered before. An editor should not invent hidden motives from a style definition. Instead, the absence of ownership or rationale should itself be recorded as an absence.
This is why the inquiry traces authority, not people. The purpose is not to identify a culprit for a line break, a heading level, or a note treatment. It is to identify the pathway by which a reusable rule becomes an apparent fact about a manuscript. The pathway begins with a default and ends with a visible consequence. Between those points are a normal case, a text relation, an exception trigger, a review point, and evidence. Once those links are visible, participants may decide that the default should stand. They may revise the local document. They may revise the template later. They may leave the matter unresolved pending more information. The trace does not select among those outcomes.
The Template Authority Trace
The Template Authority Trace is a working record for a managing editor, production coordinator, publishing-program teacher, design-system steward, or editorial-operations lead who encounters a document relation that appears irregular under a reusable template. It is not an audit score. It is not a platform comparison, a style guide, a conformance test, an organizational policy, or a universal decision protocol. Its function is narrower: to prevent a standing rule from posing as a complete explanation.
| Trace field | What the reader records | Why the field matters | What the field does not decide |
|---|---|---|---|
| Default rule | The actual reusable instruction, named style, setting, token, convention, or inherited action. | It identifies what is operating before a local decision is made. | That the rule is bad or obsolete. |
| Source / owner | The location of the rule and the person, role, or group able to clarify, revise, or retire it. “Unknown” is a valid entry. | It separates a visible result from accountable stewardship. | That the current user created or endorses the rule. |
| Rendered consequence | What becomes visible, absent, reordered, normalized, or hard to distinguish in the current output. | It connects a hidden rule to an inspectable artifact. | How all readers will respond. |
| Affected text relation | The relation at stake: heading to heading, note to claim, figure to paragraph, citation to bibliography, section to section, or another named relation. | It moves inquiry beyond appearance to textual function. | That every relation needs special treatment. |
| Presumed normal case | The document relation for which the default works without extra handling. | It makes an inherited assumption discussable. | That the normal case lacks value or legitimacy. |
| Exception trigger | The observable condition that puts the default’s adequacy in question. | It prevents personal preference alone from becoming an exception claim. | That the exception should be accepted. |
| Accountable review point | The named role, meeting, editorial stage, or documented handoff at which the departure can be considered. | It gives discretion a visible location and time. | That a single individual must rule. |
| Evidence source | The file, instruction, author’s note, production guidance, sample output, rationale, or proof consulted. | It makes the trace revisable and auditable. | That evidence will resolve every trade-off. |
| Non-conclusion | What remains undecided after the trace. | It prevents a procedure from being mistaken for a ruling. | A recommendation, policy, or final verdict. |
A trace is complete when a reader can understand why a default is appearing on the page and where a different treatment could be reviewed; it is not complete only when the issue has been settled. The final field is crucial. Editorial systems often mistake documentation for closure. A record that says, “The appropriate treatment remains undecided pending source review and production test,” can be more responsible than a record that converts an unexamined default into a quick correction.
The fields also keep distinct matters that are easily conflated. The source / owner field concerns accountability for the standing rule, not authorship of the manuscript. The exception trigger concerns a condition in the document, not the prestige or persistence of the person requesting a change. The evidence source field concerns what was consulted, not whether every item of evidence agrees. The non-conclusion field concerns the limits of the trace, not an evasion of editorial responsibility.
Worked Trace: Headings, Notes, and a False Irregularity
Return to Documentary Breaks. The following trace does not settle whether the note should remain after the heading. It shows the minimum record required before “irregular” is treated as a sufficient reason to move it.
| Trace field | Constructed entry | Editorial reading |
|---|---|---|
| Default rule | Level-2 headings are followed by prose before any note marker; notes are rendered as chapter endnotes in uniform text. | The page is not reacting to the note in the abstract. It is reacting to the template’s expectation of heading-to-prose sequence. |
| Source / owner | Reused house manuscript template; no current owner is documented in the file. | “Unknown” is an actionable finding. It signals that a visible rule lacks an identified custodian at this review stage. |
| Rendered consequence | The short headed section appears visually isolated, and the opening note looks like a formatting anomaly rather than a source relation. | The rendered result is visible; the reason for it has not yet been evaluated. |
| Affected text relation | Heading → critical note → explanatory paragraph. | Naming the relation prevents the matter from being reduced to an orphaned marker or an untidy gap. |
| Presumed normal case | A heading introduces prose; notes qualify claims embedded in prose rather than establish the documentary status of the section itself. | The template’s ordinary case is intelligible and may be useful across most chapters. |
| Exception trigger | The note identifies why the textual break is treated as evidence before explanatory prose begins. | The trigger is a functional claim about the note’s relation to the section, not a desire for visual novelty. |
| Accountable review point | Developmental-editor / production-editor handoff, with the author’s short rationale attached. | The proposal reaches people able to assess both textual function and downstream production. |
| Evidence source | Template styles pane; current press guidance; author’s source note; rendered proof. | The review tests the artifact and its supporting explanation rather than relying on a memory of house practice. |
| Non-conclusion | The trace does not determine whether the note should move, remain, be redesigned, or be rejected. | A choice still must be made, but it is now explicitly a choice rather than a reflex of the template. |
Several things change when the matter is written this way. First, the phrase the note is irregular becomes inadequate. It names an appearance but not the relation that gives the appearance its possible significance. Second, the author’s explanation becomes neither self-authenticating nor dispensable. It is one evidence source among others. Third, the template’s owner cannot remain a purely abstract concern. If no owner is known, the absence is visible at the moment the local issue requires interpretation.
Fourth, the exception becomes reviewable without becoming presumptively correct. The author may be asked to move the evidentiary explanation into prose. The production editor may find a way to retain the relation while changing the note device. The press may decide that its style cannot support the arrangement. Each of these outcomes remains available. The trace does not transform a hard editorial decision into a mechanical test. It prevents the easiest outcome from being mistaken for the only one.
The constructed case also reveals why a template should not be judged only by its ability to make common cases clean. A template is an agreement about what not to re-decide. That is one of its virtues. Its authority becomes invisible when the agreement has no documented point at which an uncommon case may be heard. The remedy is not a template with infinite options; that would merely transfer repetition and uncertainty back to every user. The remedy is a rule with a legible exception path.
Why the Default May Deserve to Stay
An account of template authority becomes misleading if it treats standardization as a failure by definition. The practical reason to use a template is that production contains repeated tasks and handoffs. A limited token system can restrict a large choice space to values that are already understood within a working system.[1] Linked styles can make global adjustments possible without a person changing every local instance, and the LibreOffice guide identifies consistency and reduced repetitive work as reasons to use them.[2] Ottley and Schwabish likewise report that organizations use guides, templates, defaults, and automation to address capacity, coordination, maintenance, training, and accountability pressures.[4]
Publishing records show a related value. Taylor & Francis directs authors to consult the instructions for a particular target journal and, when applicable, to apply the relevant template styles; the same record also notes that many journals permit a format-free submission route.[5] The point is not that templates are optional in every setting. It is that their applicability is conditional on a stated workflow. The template carries a promise only within a particular arrangement of requirements, handoffs, and later transformation.
The University of Chicago Press makes a different but equally relevant production distinction. Its manuscript-preparation guidance asks authors to keep formatting minimal and clear so that headings, extracts, notes, and other elements can be recognized during later processing and design. It instructs authors who depart from a citation convention to create a separate style sheet with examples that can help editorial staff understand the intention.[6] That procedure does not create a right to any requested treatment. It recognizes that downstream workers need a record when the ordinary convention does not fit.
The counterweight follows. A default can deserve to remain because it lets many people coordinate, reduces needless manual labor, and makes the next person’s task more predictable. An exception can deserve attention because the particular text relation would otherwise be misunderstood or erased. Both propositions can be true at once. The Template Authority Trace does not ask whether uniformity or variation is intrinsically better. It asks whether the relation at issue has been sufficiently identified for a responsible judgment to occur.
An exception also carries a burden. If it is not documented, later workers may encounter a singular treatment as an unexplained defect. If it is not bounded, a local solution may become an accidental precedent. If it cannot survive a production handoff, it may undermine the very relation it was meant to preserve. These are reasons to make exception review accountable, not reasons to assume that the default has already answered the question.
Make the Review Visible
The instrument is most useful at the moment of friction, when a reusable rule and a particular document seem to be disagreeing. It can be used in a short editorial exchange, in a style-maintenance meeting, during a template revision, or as a teaching exercise in a publishing course. The method is deliberately light: record the rule, read the rendered result, name the relation, identify the normal case, define the trigger, locate a review point, gather evidence, and write what remains undecided.
That sequence changes the quality of a familiar editorial conversation. Instead of asking, “Can the template handle this?” the participants can ask, “What is the template doing here, and for which ordinary case?” Instead of replying, “That is not how our documents look,” they can ask, “What relation does this arrangement ask a reader or production worker to recognize?” Instead of treating a special case as personal preference, they can identify an observable trigger and attach supporting evidence. Instead of asking a template to decide, they can assign a moment at which an accountable person or group will decide.
The method is also useful when the answer is to keep the default. A completed trace can show that the relation was examined, that the normal case remains adequate, and that no trigger justifies a departure. That is different from keeping the default because its authority went unnoticed. It gives the rule a reason that can be communicated to the author and carried into future work.
The method should stop before it becomes an excuse for delay. Not every paragraph break needs a governance inquiry. The trace is warranted when the difference concerns a meaningful textual relation, a recurrent production problem, an accessibility or semantic distinction that requires specialized review, a question of template ownership, or a departure likely to travel across multiple editions or collaborators. The instrument does not replace professional judgment, reader testing, accessibility evaluation, legal review, or a publisher’s actual instructions. It simply creates a disciplined moment before those activities are preempted by an inherited setting.
Boundaries of the Instrument
The Template Authority Trace has intentionally narrow claims. It does not recommend a document platform, template product, or workflow tool. It does not evaluate a real press, journal, editor, author, or organization. It does not make an accessibility conformance finding, determine whether a manuscript will be accepted, issue a universal style rule, or establish a legal duty. It does not prove that a template has caused a particular editorial outcome. It does not decide whether an exception should be granted.
The trace is also not a substitute for a style guide. A guide can state rules. The trace is used when a rule’s application has become uncertain in a particular textual relation. Nor is it a substitute for version control, copyediting, typesetting, or project management. Its distinctive task is smaller: to make the default, the assumed normal case, and the exception path visible enough for responsible people to deliberate.
Conclusion: The Rule, the Normal Case, the Review
The page that looked wrong may still need to change. The author’s note may move into prose. The heading may be revised. The template may remain exactly as it is. None of those possibilities is discredited by asking what the default has already presumed.
A reusable template is a compact form of prior judgment. Its force lies partly in its invisibility: it saves time because most users need not revisit what it has settled. That efficiency is a good reason to preserve stable conventions. It is not a reason to let a normal case decide an exceptional textual relation without review.
The closing test is therefore simple: Which default is deciding here, what normal case does it presume, and where can an accountable exception be reviewed? If a team can answer those questions, the template has not lost its authority. Its authority has become legible enough to be used well.
References
[1] U.S. Web Design System. Design Tokens.
[2] LibreOffice Documentation Team. Calc Guide 24.2, Chapter 5: Using Styles and Templates, 2024.
[3] Eric J. Johnson and Daniel G. Goldstein. “Defaults and Donation Decisions”. Transplantation 78, no. 12 (2004): 1713–1716.
[4] Alvitta Ottley and Jonathan Schwabish. “Data Visualization Style Guides in Practice: Why They Emerge, How They Work, and When They Bend”. arXiv:2607.29645, 2026.
[5] Taylor & Francis Author Services. “How to Format and Use a Journal Template for Your Research Paper”.
[6] University of Chicago Press. “Manuscript Preparation Guidelines”.