Type direction comparison
Compare the same useful content instead of approving a typeface from one flattering word.
Voice
Observable type qualities connect to audience and purpose.
Response: Replace vague adjectives with visible criteria.
Hierarchy
Display, body, label, number, and status roles remain distinct.
Response: Test the complete role set with one content sample.
Coverage
Required languages, symbols, numerals, and punctuation are supported.
Response: Use the most difficult real strings early.
Delivery
Licence, loading, fallback, print, or embedding needs are known.
Response: Verify the actual agreement and production method.
Define the jobs type must perform
List the content roles before choosing a visual voice: display heading, section heading, body text, caption, navigation, label, number, price, data, quote, or packaging detail. Record the smallest size, longest line, likely device or material, and whether the work must support several languages.
Describe the desired voice with observable qualities. Open counters, narrow proportions, strong verticals, soft terminals, high stroke contrast, or compact rhythm are more useful than modern or premium alone. Connect each quality to the audience and task so the board can be evaluated without relying on taste.
Collect specimens rather than logos
Use references that show type in paragraphs, interfaces, signs, packaging, editorial spreads, and other relevant conditions. A logo or single display word cannot prove body readability, hierarchy, numerals, punctuation, or dense information. Label the quality you are studying in each specimen.
Do not assume the exact typeface in a reference is available or appropriate. The useful evidence may be its width, contrast, spacing, case, or relationship with imagery. Translate that principle into candidates you can license, deliver, and test with the project content.
Judge type where reading becomes difficult
The type direction earns approval by handling real information, not by looking distinctive in a specimen title.
Small text. Check body copy, captions, labels, and status messages at realistic sizes. A family selected for display character may need a different text strategy when reading is central. Compare line spacing, weight, contrast, and open shapes on the intended screen or material. Do not enlarge the test simply to make a weak candidate pass.
Dense content. Test tables, navigation, prices, dates, or product details when the project contains them. Width and numeral design can influence layout as much as personality does. Use the longest likely heading and a realistic paragraph rather than ideal specimen copy. Confirm that hierarchy survives without adding more colors or weights than the system can maintain.
Language. Use names, accents, punctuation, and scripts required by the audience. Do not approve a system that excludes real content and promise to solve coverage later. Check fallback fonts beside the primary choice and note where metrics or character shapes change. A multilingual project may need a coordinated family strategy rather than one visually identical typeface.
Delivery. Confirm files, licence, web performance, fallback, embedding, and print behavior. The most attractive direction is unusable when the project cannot lawfully or reliably deliver it. Record the foundry or provider, version, permitted uses, and people who need access. Test font loading and the fallback state before the visual direction becomes dependent on one file.
Compare candidates with the same content
Set the same representative headline, paragraph, link, number, date, and difficult label in each candidate. Keep size and line length comparable where possible. This reveals whether a direction depends on one flattering word or remains coherent across the actual information system.
Include awkward strings early: long names, uppercase abbreviations, currency, percentages, punctuation, accented characters, or scripts required by the audience. A beautiful specimen is not a complete font test. Missing characters or weak numerals can change the decision late and expensively.
Test hierarchy beyond the specimen with the accessible mood board method for contrast, order, and realistic viewing sizes.
Build a hierarchy, not a font collection
Assign size, weight, spacing, width, case, and color roles before adding another type family. Many systems can create a clear hierarchy with one family and a limited set of weights. Add a second family only when it performs a distinct job that the first cannot handle well.
Test hierarchy with realistic content density. A large editorial heading may work on a campaign page but crowd a dashboard or package. Check the smallest repeated label and the longest important paragraph, then compare how the same voice survives at both extremes.
For digital work, apply the type direction to real website interface states before approval.
Verify access, delivery, and licensing
Check contrast, zoom, line spacing, fallback behavior, font loading, and readability at the intended size. For the web, consider performance and what happens before the font loads. For print and physical work, inspect proofs at the real scale and production method.
Confirm the licence covers the intended use, users, applications, distribution, and embedding before approval. Keep the licence source and version in the project record. Licensing terms vary by foundry and plan, so verify the actual agreement rather than relying on a screenshot or font name.
The type direction approval check
- List content roles and reading conditions.
- Define type qualities in observable language.
- Compare candidates with identical content.
- Test difficult strings and required characters.
- Build hierarchy before adding another family.
- Verify licence and delivery.
Type choice, access, and licensing questions
Can a typography mood board use typefaces we do not own?
They can appear as clearly identified references, but do not treat them as approved production choices. Verify access and licensing before building the final direction around them.
How many type families should be compared?
Use a small set of genuinely different directions that meet the brief. More options can hide the criteria. Remove a candidate as soon as it fails a required role or character need.
Should body text appear on a mood board?
Yes when the project includes reading. A display word cannot reveal paragraph texture, line length, punctuation, or small-size clarity.
Can accessibility be judged from the board?
The board can identify intentions and risky combinations. Confirm readability, contrast, zoom, focus, loading, and fallback in the actual medium.
Build one honest comparison specimen
Set the same long headline, paragraph, navigation label, price, date, form error, and required characters in each candidate. Compare voice, width, hierarchy, readability, and technical fit rather than one display word. Remove any candidate that fails a required role, coverage need, licence condition, or delivery constraint.
Carry the type specimen through the complete board design path for hierarchy, color roles, layout, and access.