How to Submit a Logo or Web Design Without Losing the Reply

Felix Rowan | Submission guide

If you want help, make the request easy to read, easy to trust, and easy to answer. The actual problem is rarely talent. It is usually a vague email with mystery files attached like a low-budget hostage note.

Most people who land on the Email Application Form are trying to solve three boring but important questions fast: what should I send, which files matter, and how do I avoid my message disappearing into the swamp. Those are good questions. The boring thing usually is the real thing.

Oz Designs keeps the application process simple on purpose. The service is free, submissions are reviewed manually, and the form exists to gather enough detail to tell a real project from a false lead. That means clear basics, sensible files, and contact details that do not self-sabotage.

Below is the checklist I would use before sending anything. It covers the subject line, the required project details, the least-annoying file formats, and the deliverability checks worth running before you blame the inbox gods.

First, mirror the point of the form

The form is there to request free help without creating a spam magnet. Keep your message aligned with that purpose:

• State the real request. Say whether you need a logo, a web graphic set, a page layout, or a combination.
• Use a working email address. If the destination address is wrong, the process dies before it starts. Symptoms do not lie.
• Do not pad the email with hype. Short context is useful. Performance art is not.
• Assume manual review. The easier you make verification, the easier it is to get a useful reply.

The checklist: what to include in the first message

If you send only one thing correctly, send a message that answers the reviewer’s first questions before they have to ask them.

Item	What to send	Why it matters
Subject line	Try: Logo Request – Brand Name – Needed by 30 May	A clear subject makes the request easier to recognize, search, and answer later.
Project type	Logo refresh, new logo, header graphic, landing page mockup, button set, or website visual cleanup.	Without the project type, the reviewer has to guess the scope. Guessing is how timelines get ugly.
Intended use	Tell them where the design will live: website header, favicon, social avatar, business card, email signature, or ad creative.	A logo for a website masthead is not the same job as a square icon for a profile image.
Dimensions or format	Include target size, orientation, and whether you need vector or raster output.	This rules out the classic false lead where everyone thinks "web-ready" means the same thing.
Brand text	Write the brand name, tagline, spelling, and any must-keep wording exactly as it should appear.	Names, capitalization, and taglines are the boring details that cause avoidable revisions.
Deadline	Give the actual date and say whether it is fixed or preferred.	"ASAP" is not a schedule. It is a confession.
Contact details	Add your preferred reply email and one backup contact method if the project is time-sensitive.	If the reply cannot reach you, nothing else matters.

File formats that do not waste everyone’s time

Use standard formats. Nobody wins awards for attaching a format the next person cannot open.

• PNG: good for transparent backgrounds, mockups, and quick logo previews.
• SVG: best when you already have vector artwork and want crisp scaling on the web.
• JPG: acceptable for photographs, sketches, and rough layout references.
• PDF: useful when you need to bundle a brief, brand notes, or approved reference pages into one readable file.

If you already have brand assets, name them plainly. brand-name-logo-black.svg is useful. final-new-2-really-final-v7.svg is evidence of a collapse in governance.

For anyone preparing graphics that need to stay sharp in headers, buttons, or icons, the existing guide on turning logo files into crisp web assets is worth reading before you send exports.

How to describe the goal so the reviewer can picture it

A design request needs direction, not a novel. Include these short answers inside the form or the email body:

1. What is the design for? Example: "A simple wordmark for a gardening service website and printed flyers."
2. What feeling should it create? Example: "Reliable, local, clean, not corporate."
3. What should it avoid? Example: "No metallic gradients, no cartoon mascots, no script fonts."
4. What already exists? Example: "Current site colors are dark green and cream; old logo attached for reference only."

If the request includes both design and technical work, say that plainly. For example: "I need a logo refresh and a matching website header," or "I need artwork only, no page build." Clear scope beats clever phrasing every time.

If you have source files, list them in the body before you attach anything: one SVG logo, two JPG references, one PDF brief. That gives the reviewer a quick inventory and rules out the false lead where the email sounds complete but the actual files say otherwise.

Deliverability checks: rule out the boring failures first

People love blaming invisible filters because it feels dramatic. Check the ordinary failure points first.

• Use a clear subject. Make it obvious that the message is a project request, not a mystery promotion.
• Include reply details in the body. Even if the sender field is correct, repeat your contact email and your name in plain text.
• Keep attachments reasonable. Large files are a common nuisance. If the assets are heavy, send a download link instead of stuffing the email.
• Do not split the brief across five messages. One complete submission is easier to recognize and track than a trail of fragments.
• Check your spam or junk folder if you expect a reply. Yes, this is obvious. Obvious things still fail every day.
• If no reply arrives, follow up once with the original details. Wait a sensible amount of time, then resend with the same clear subject and note that it is a follow-up.

If the main goal is a stable public contact address, the related article on keeping a public email address stable when your inbox changes explains why forwarding details matter and what to rule out before you switch anything.

A practical example of a good first message

Subject: Logo Request – Harbor Lane Books – Needed by 30 May

Hello, I would like help with a simple logo and website header for Harbor Lane Books.

The design will be used on a small online bookstore website, social profile images, and a printed bookmark. Brand text should read exactly: Harbor Lane Books. Preferred colors are navy, sand, and white. I want it to feel classic and calm, not ornate.

I have attached a JPG of the current storefront sign and a PDF with a rough mood reference. Final output needs to work in PNG and SVG. Preferred deadline is 30 May. Please reply to [email protected].

Notice what this message does not do. It does not ramble. It does not force the reviewer to guess the brand name. It does not attach a folder full of unlabeled debris. That alone puts it ahead of a depressing percentage of submissions.

Before you change anything else, run this first diagnostic step

Open your draft and check whether a stranger could answer these five questions in under a minute: what you need, where it will be used, what files are attached, when you need it, and how to reach you. If not, the draft is not ready. Fix the brief before you blame deliverability.

Then use the site paths that already exist for the job: start from the Home page if you want the broader service context, and send the actual request through the Email Application Form when your details are complete.