Logo Feedback Examples: Write Actionable Redesign Review Comments

What this review is for

Actionable logo redesign comments are written notes a reviewer leaves on vector artwork so a designer can change paths, type, spacing, and construction without guessing. The subject here is the review language itself: how to name the mark, name the layer or element, describe the visual or structural problem, and state the change. It is not a critique of a named brand, a specific file, or a particular drawing tool.

A useful comment has three parts. First, point to the exact element: wordmark, symbol, lockup, tagline, or a named path group. Second, say what is wrong in the artwork: contrast, alignment, optical size, stroke weight, enclosed counters, or how the mark behaves at small sizes. Third, state the intended result: simplify a form, unify weights, convert a construction, or separate the lockup. Preference alone is not enough; the designer still needs a construction task.

Review vector construction, not only the preview

Logo reviews often start from a raster preview: a PNG, JPEG, or on-screen snapshot. That preview is useful for judging silhouette, contrast, and scale. It does not prove the file is editable vector. Paths, live type, and embedded bitmaps can look similar in a flat image. Treat the preview as evidence of appearance. Treat the working file as evidence of structure. Do not infer editable paths from a filename or extension alone.

When the working file is available, comment on construction. Note whether letterforms are live type or outlined paths, whether strokes are live or expanded, whether shapes overlap or are united, and whether a photographic or illustrated bitmap sits inside a vector frame. A comment that says “make it a vector” is incomplete if the file already contains paths with an embedded raster. Name the raster object and ask for a redraw as paths, or ask that the raster be removed from the master.

• Point to the element by name: primary mark, stacked lockup, icon, or a specific letter or path group.
• Describe the problem in the artwork: weight, spacing, alignment, contrast, or how a form closes at small size.
• State the change: unite, outline, redraw, reweight, optically space, or separate versions.
• Separate appearance comments (how it looks) from file comments (how it is built).
• Leave permission and trademark questions out of drawing notes; treat them as a separate clearance item.

Comment patterns that a designer can execute

The examples below are review language, not measured findings from a named test. They show how to turn a vague reaction into a construction request. Swap the element names for the mark in front of you.

Weak comment	Actionable rewrite
The logo feels off.	The wordmark and symbol compete at small size. Reduce the symbol to a single weight that matches the type stem, then test the lockup at favicon scale.
Make the type nicer.	The custom letterspacing collapses the counters in a, e, and s. Open tracking until those counters stay clear at the smallest intended print size, then kern the pairs around the crossbar of t and the arm of r.
It should be more modern.	The mark uses three stroke weights and a gradient fill. Rebuild it as two weights, flat fills, and no gradient so it holds in one-color and embroidery.
Fix the icon.	The icon’s enclosed triangle reads as a hole at small sizes. Close the gap or thicken the outer stroke so the silhouette stays a single recognizable shape.
This file is not a real logo.	The artboard shows paths, but the leaf is an embedded bitmap. Redraw the leaf as closed paths and remove the raster from the master.
I don’t like the color.	The current fill fails on a dark background. Supply a one-color positive, a one-color reverse, and a limited palette with a documented fallback when the secondary color is unavailable.

Vector-specific notes worth writing every time

Scalability is a construction issue. Ask whether hairline strokes, thin serifs, or tight counters survive reduction. If a stroke is set to a paper-unit width, say whether it should remain a live stroke or be expanded, and at which master size. Optical alignment is also construction: round letters and pointed vertices often need to overshoot the cap line. Write that as “optically align the O and A to the cap height of the H,” not as “center it.”

Lockups need version comments. Horizontal, stacked, icon-only, and type-only arrangements are separate drawings, not one file cropped in a layout. If the review is of a single lockup, say whether a stacked or icon-only version is required, and whether the symbol may be used without the wordmark. If type is live, name the font and say whether outlines are required for delivery. If type is already outlined, do not ask the designer to “edit the font”; ask for a redraw or a new live-type master.

Overlap and boolean work belong in the comments when the mark will be cut, embroidered, or used as a single color. Overlapping strokes that look fine on screen can trap, gap, or double-up in production. Ask for united shapes, consistent outer contours, and a version with no hidden paths underneath. If a designer used blends, meshes, or transparency, say whether those must be flattened to solid fills for the master.

Tone that keeps the review usable

Write in the present tense about the artwork, not about the designer. “The stem of the n is heavier than the h” is usable. “You didn’t match the weights” is not. Keep one issue per comment when the file will be revised in rounds. Bundle related construction items that must change together, such as stroke weight and counter size, so the designer does not fix one and break the other.

Separate taste from requirement. “The geometric o feels cold next to the humanist n” is a direction. “The client needs a single-color mark for forms and signage” is a constraint. Label them. A designer can argue with taste and still must meet the constraint. When you do not know the intended sizes, substrates, or color limits, say that those inputs are missing instead of inventing a production spec.

Name the element, describe the construction problem, and state the change. Preference without a drawing task leaves the file unrevised.

Permission is not a drawing comment

Being able to download a logo file is not permission to modify it, to reuse its letterforms, or to apply the trademark. Review comments that ask for redraws, font substitutions, or derivative lockups assume the reviewer and designer already have the right to alter that artwork. If rights are unclear, flag clearance as a blocker and keep the visual notes limited to observation. Fonts inside a logo may be licensed for the original designer and still be restricted for a new edit. Trademarks can remain protected even when the vector paths are technically editable.

What this article cannot settle

No specific logo, file, or tool was supplied, so these examples are comment patterns, not a review of a named mark. There is no measured contrast ratio, reduction test, or production sample behind the table. If you are reviewing a real file, attach the working artwork, list the required sizes and color modes, and say whether the type is live or outlined. Those facts belong in the brief; the comments above only show how to write the notes once those facts exist.