Beñat Juaristi EliasLETTERING & TYPOGRAPHIC DESIGN

Project guide

A clearer brief.
A more useful
conversation.

You do not need to decide every visual detail in advance. Start with the content, the reading context and the result you need to use. This guide helps turn those into questions for a lettering or typographic project.

1. Bring the real words.

For lettering, specify the exact name, title or phrase, including capitals, punctuation and accents. An alternate language or a different word can change the letter relationships; it is not always a simple text replacement.

For typographic design, provide a realistic sample of every content level: title, subtitle, body, captions, numbers and any longer or shorter variants. Indicate what is final and what may still change. Content volume affects the design, so a short placeholder can give a misleading impression of the available space.

Useful to include

  • The approved spelling and the person responsible for approving it.
  • Required languages, accented characters and symbols.
  • A content outline that distinguishes primary information from supporting detail.

2. Name the reading conditions.

“A logo” or “a layout” leaves many questions open. Explain where the design will appear, the smallest and largest intended size, whether it is seen at a distance or read closely, and what the reader should understand first.

List formats separately. A poster, a printed card and a narrow screen are different contexts, even when they share the same words. References are most useful when you explain the relevant quality: calmness, density, contrast, clarity or a particular relationship between letters. They are a basis for discussion, not permission to copy another design.

3. Agree the files for the next step.

Vector artwork describes shapes and can be useful for a fixed lettering mark at several scales. Raster files have a defined pixel size and may be useful for particular placements. PDF is often used for reviewing or delivering a composition, but the required settings depend on its purpose.

Ask the printer, fabricator or implementer for their requirements before final delivery: dimensions, bleed, colour handling, minimum detail and accepted formats. Editable source files are a separate handoff question. A flattened preview, a production file and an editable template serve different needs.

If the work will become a website or an app, say who implements it and what information they need. A visual composition does not itself provide code, hosting or a complete accessible implementation.

4. Separate artwork rights from font rights.

A licence for a typeface can cover some uses and exclude others. Desktop design, web embedding, app distribution and sharing font files can have different conditions. Identify any existing type family and who holds the licence. Do not send a font file unless you have permission to share it.

For commissioned work, discuss permitted applications, exclusivity, territory or duration where relevant, and which rights apply to the approved design. Preliminary directions and third-party resources may have different terms. A piece of lettering is not automatically a complete font, and viewing a concept study does not grant permission to adopt its design.

Trademark availability and legal clearance require their own consideration. Make clear who is responsible for those decisions.

5. Check more than appearance.

Legibility depends on size, contrast, spacing, material and viewing conditions. Review the smallest real use and a realistic amount of text. A dramatic heading can work while a caption still fails to read comfortably.

In a digital implementation, text that must be read should remain available as text where appropriate, with a meaningful structure and keyboard access to interactive controls. Outlined lettering and images need suitable text alternatives in their context. Do not rely on colour alone to communicate an essential distinction.

The type lab is a quick way to compare measures and spacing; it is not a certification of accessibility or a substitute for testing the finished output with its actual content.

Try a paragraph in the type lab →

6. Define who reviews what.

A useful project agreement distinguishes exploration, selection, refinement and final approval. Name the person who consolidates feedback. Separate a correction to approved content from a new direction or additional application, because those may affect the work required.

Before starting, discuss deliverables, formats, schedule, fees, review stages, usage rights and any production checking. Before handoff, review spelling, accents, dimensions, versions and the intended output conditions. Website examples do not establish a fixed package or revision allowance.

Prepare your project enquiry ↗