Style Guide
.png)
A style guide is a firm-level document that governs the visual and editorial standards applied to all proposal and marketing content: typefaces, color values, logo usage rules, header hierarchies, boilerplate voice, and punctuation conventions.
Style Guides Are More Fragile Than Firms Realize
Most AEC style guides were written during a rebrand and haven't been updated since. By the time a proposal manager inherits one, it may conflict with the current logo suite, reference a deprecated InDesign template, or omit entire content categories like project case study formatting or resumes. The gap between the written guide and actual practice tends to widen with every new hire who never read it. Firms with multiple offices compound the problem: regional teams develop local conventions that quietly diverge from the master document over years.
What a Working Style Guide Actually Contains
A functional proposal style guide goes well beyond hex codes and margin widths. It should specify how project descriptions are structured (scope sentence, client name, delivery method, relevant metric), how staff bios differ between SF-330 Section E and a shortlist presentation, and what the firm's editorial voice sounds like at the sentence level. It should also document exceptions: federal pursuits under FAR Part 36 often require plain-language descriptions that conflict with a firm's marketing voice, and the guide should acknowledge that tension explicitly. Without that level of specificity, the guide becomes a brand reference sheet rather than a production tool.
Style Guides as Pursuit Infrastructure
On a two-week proposal timeline, no one has time to audit whether a subconsultant's submitted resume matches the firm's format. A style guide that is actively embedded in templates, content libraries, and reviewer checklists prevents that audit from being necessary. The real value isn't aesthetic consistency; it's decision speed. When a coordinator knows the answer to "how do we handle this?" before the question comes up, that's time recovered across every pursuit. Kantiv surfaces approved content alongside the style conventions that govern it, so teams applying boilerplate or pulling project narratives aren't working from institutional memory alone. Firms that treat the style guide as living infrastructure rather than a static PDF see fewer last-minute formatting corrections and fewer rounds of principal review tied to presentation rather than substance.
Related terms