Broncos Logo Redesign: Evaluate the Proposed Changes

Before you start

Treat the redesign as a visual artifact to inspect, not a claim to accept. Work from the supplied PNG, SVG, or mockup files. If you only have a screenshot or a presentation slide, ask the designer for the actual working files. For a local file, evaluation can run entirely on your device in a browser tool. For a shared review link, you are viewing that service's rendered version and cannot assume the underlying file is identical until you download it.

Identify the comparison baseline first. Keep the current Broncos mark open beside the proposed version. Note the intended context: primary badge, helmet decal, small profile icon, scoreboard graphic, or social avatar. The same logo can be acceptable in one context and fail in another.

Step-by-step instructions

• 1. Open both versions at equal display width. Do not judge from thumbnails.
• 2. Check silhouette first. Blur your eyes or view the mark at 24 to 32 pixels high. A redesign works only if the horse head and mane still read as a single strong shape.
• 3. Compare orange and navy contrast. The orange should separate clearly from the dark blue on a light background, and the dark blue should separate from the orange on a dark background.
• 4. Inspect white or light outlines around the head and mane. Note whether they are part of the shape or simply gaps between filled areas.
• 5. Read any lettering or wordmark at 60 pixels wide. Check that counters, letter spacing, and descenders stay legible.
• 6. View the redesign on flat white, flat navy, and a busy photo background. Mark any context where part of the shape disappears.
• 7. Check version differences by toggling the old and new marks repeatedly. Look for accidental shifts in eye position, jaw angle, ear shape, and mane rhythm.
• 8. If you have an SVG, open a copy and confirm that there are no embedded raster images, scripts, or external resource references. Keep SVG previews sandboxed when the source is unknown.
• 9. Place the proposed mark in the actual small placement: helmet decal, social avatar, or score bug. At small sizes, count how many detail lines become noise.

Check the output

At displayed sizes from 32 to 128 pixels, the mark should still read as a horse head inside a contained shape. At helmet size, the eye should remain a visible focal point without turning into a dark smudge. At avatar size, the orange and navy should remain distinguishable on both a white and a dark background. If the redesign is supplied as an SVG, verify in a text editor that it is vector-based and free of linked assets. If it is a PNG, note the largest available pixel dimensions and check for edge artifacts around the mane at that size.

For color, obtain the exact hex or RGB values and check the light and dark pairs. A useful first gate is whether each pair holds in the intended place. Do not rely on a screen impression alone, because display brightness and viewing angle change perceived contrast.

Common problems and next steps

• If the shape breaks at avatar size, ask for a simplified secondary mark rather than scaling the primary badge down.
• If the orange appears brown or the navy appears black, check whether the file has an embedded profile or the export shifted the intended palette.
• If the SVG preview looks correct but a text editor shows embedded raster data, request a true vector version instead of treating the preview as proof.
• If the mark gains a white halo on dark backgrounds, confirm whether that outline is intentional and export a clean dark-background variant.
• If the horse's eye vanishes in dark navy areas, test a lighter eye shape or reduce surrounding detail before accepting the redesign.
• If edges look jagged in the PNG, inspect the anti-aliasing and the original export size. Upscaling a small raster will not recover detail.
• If the redesign only works at exhibition sizes, it is not ready for game and interface use.

Record your findings with a simple pass or fail note per context: large badge, helmet, scoreboard, and small profile icon. Keep the original file unchanged and create a separate marked-up comparison export. Ask for corrections in terms of observable output, such as "the eye disappears at 32 pixels" or "the orange value differs from the approved palette by this amount."