Looking for a Typeface Design Brief Document
1. Who needs this typeface? And (more important) why? RP (Who is the client, or target customer? TP)
2. Tell me about the project. (Background and main need). RP
3. What is the intended function of the typeface? . NC
4. Who is going to be the main reader of this typeface? RP
5. Who is going to set text with this typeface? RP
6. What personality should it convey? NC
7. Is it replacing a current typeface? If so, what does the client like and dislike about the current typeface? What is motivating the change? TP
8. Mention 3 Like-to-look-like Typefaces for this project. RP
9. Mention 3 examples you consider Best Practices suitable for this project. RP
10. What is the typeface a vehicle for? What is to be communicated with it? In what way should it flavor the message? Is it intended for a particular project or product? TP
11. Is there a specific target usage, such as “advertising headlines” or “body text in all publications and online.” Even if not.... What sizes will it be used at? In what media? How will the type be reproduced (imaged, rasterized)? On screen? For web pages? In print? TP (In what sort of media will it be used? NC)
12. How many styles (individual fonts) are desired? TP
13. What kind of language coverage is required? TP 3. What language does it speak? NC
What is the tone of voice intended for this typeface? RP
How should it sound? is it friendly? serious? casual?
14. What kind of typographic extras are required, or might be desirable? TP
This connects with the main activity and language of the company or brand RP
15. Do you need exclusivity of the typeface or would you consider licensing it? For how long?
TP. Thomas Phinney: https://www.quora.com/What-does-a-typical-brief-for-a-new-typeface-look-like
NC. Nandine Chahine: https://www.smashingmagazine.com/2014/02/a-type-design-brief-arabic-typography-calligraphy/
RP. Rubén Pineda. (Myself)
A lot of the discussion I have with clients proceeds from typographic considerations around the kind of texts they work with, to determine what character coverage and typographic feature support is required. A primary goal of the brief development is to be able to define a reasonably accurate working glyph list, since this will provide a reliable basis for pricing the project.
I also tend to ask a lot of questions about output media, text workflow, and toolchains, in order to determine the appropriate font outline format and rendering model, as well as ensuring there won’t be any unanticipated issues with software support (especially important once one gets beyond a) typical office and desktop publishing workflows and b) European writing systems.
Document the technical design requirements, along with legal and contractual constraints but leave the visual design to free discussion, based on the circumstances of the project. In this way, the designer will be able to do his/her job more effectively.
And don't forget to define the contract process – initial ideas, proof of concept, sign-off / payment stages etc.
I feel that RP's draft brief pays unnecessary attention to the visual design while largely ignoring the technical design. In fact I don't think this kind of visual brief can usefully become standardised - I see a form that says Personality -> please select …
On the other hand a technical design template might be useful.
@JoyceKetterer: Great point about infringing other's ideas. I'll consider that, but I disagree on asking many of this questions directly to the client. I would do so assuming there is someone in their team that knows about the project and the main need. If they don't know how to answer I would help them to discover the real need.
@John Hudson : I agree with you. However, what I try to get from  is a couple of examples of what the client hope to get in terms of design, look, feel or performance. Would you ask a different question?
@Ray Larabie: After  about typographic extras (Thomas Phinney refers to) I am pointing out the fact that every company or brand have their own lingo or type language and may need specific glyphs, figures, ligatures, variables, etc. Makes sense?
@Nicholas Garner: This is so true! Honestly I am leaving the technical part aside. I have to consider that questions too (maybe in a separate Brief?).
Sorry to reply to everyone at the same time but can't find a way to reply to each comment separately.
I am working on the document considering every though.