How to Brief a Polo or Golf Shirt Design Without Any Design Background

Ordering a custom polo or golf shirt design without a design background can feel like you already need to know the right terminology just to explain what you want clearly. You don’t. You just need to be specific about a handful of practical things, in totally plain language you already use every day without thinking twice about it.

What’s this actually for?

A team, a company, a golf club, a personal brand, an event? The context shapes tone considerably. A golf club crest and a startup’s branded polo call for genuinely different design approaches, even with pretty similar technical requirements underneath the surface of the actual work involved.

What colours are involved?

Your brand or team colours, and the garment colour, or colours, the design will actually be placed on during production. If you’re not locked into specific colours yet, say that too, since it’s a completely normal starting point. It just means colour becomes part of the first concept round instead of a fixed constraint decided before any real design work has even started.

Where does it go on the shirt?

Chest only, chest and back, a sleeve detail on one or both arms? Roughly how big, relative to the shirt, small and subtle, or a bold, large placement that commands attention from across a room?

What’s the vibe you’re going for?

You don’t need design vocabulary here at all, despite how intimidating that might sound at first. Plain description works completely fine for this purpose. Bold and eye-catching, clean and professional, a bit playful, premium and understated. A couple of reference designs you like, from anywhere, another brand, a photo, a Pinterest board you’ve been saving, communicate this even more clearly than words alone ever could manage on their own.

What do you already have?

An existing logo, brand colours, a mascot or symbol you want incorporated somehow into the final design. Send whatever exists, even if it’s rough around the edges or feels unfinished to you. If you’re starting from nothing at all, that’s a completely normal starting point too, just worth mentioning upfront so nobody’s confused about the actual scope of the work involved.

How will it actually be produced?

Embroidery, screen print, sublimation, if you already know which method you’re using for this particular order. If you don’t know yet, that’s fine, but mention it as soon as you find out, since it genuinely affects how the design should get built from the very first concept onward.

How many designs or concepts do you want to see?

Some orders want just one polished concept refined through revisions until it’s right. Others want a few different directions to choose between before committing to one path forward. Either approach is reasonable, just be clear about which one you’re expecting going into the process so a designer can plan their time accordingly.

A note on describing colour without technical terms

If you know an exact colour code, a Pantone number or a hex value, include it, but if you don’t, plain description works fine too. “Navy, like a dark police uniform blue” or “forest green, not too bright” communicates enough for a designer to start with, and exact colour matching can always get refined once a first concept is on the table for review, using swatches or references rather than guessing at codes upfront.

Putting it all together in one complete example

“This is for our golf club, navy and white colours. We want a small embroidered version on the chest and a bolder printed design on the back. We like clean, modern golf branding, similar feel to this reference. We have a logo already, attached. This will be embroidered on the chest, screen printed on the back.”

That’s a complete, plain-language brief, no design terminology required anywhere in it, and everything a designer needs for an accurate first concept right out of the gate without unnecessary back-and-forth.

Why plain language actually works better than you’d think

Designers who work regularly with clients outside the design industry are used to translating everyday descriptions into technical execution, and they generally prefer this over a client attempting to use jargon incorrectly, which can actually cause more confusion than plain language would in the first place. Trying to sound technical isn’t necessary and occasionally backfires if a term gets used slightly wrong, leading a designer down the wrong path based on a misunderstanding that could have been avoided entirely with simpler, clearer words.

What to do if you genuinely don’t know where to start

If even this structure feels like too much to organize on your own, a short conversation, a call or a chat message, before ordering formally often works better than trying to write everything down perfectly in advance. Talking through what you’re picturing out loud, with someone asking the right follow-up questions, frequently surfaces details you wouldn’t have thought to include in a written brief.

Why a slightly imperfect brief still beats no brief at all

Some people hesitate to reach out until they feel their idea is fully formed, worrying that a rough or incomplete brief will waste a designer’s time. In practice, an experienced designer would much rather work from an honest, imperfect starting point than receive nothing at all and have to guess entirely from scratch about what a client actually wants from the project.

A note on revisions once the first concept arrives

Whatever you send in your initial brief, expect the first concept to need at least some adjustment, and treat that as a completely normal part of the process rather than a sign the brief was somehow inadequate. Even the most detailed brief can’t fully capture every preference, and revisions exist specifically to close that gap between description and finished design.

Have a rough idea but don’t know how to describe it well? Message first and talk it through before ordering anything, that’s exactly what the process is built for.