How to Build an Eyeshadow Palette Brief

Define the everyday use case

Begin with the look your customer wants to create: a compact everyday edit, a coordinated evening story or a collection focused on expressive color. Describe the intended user and sales channel. Treat these as planning choices, rather than evidence that a particular formula or shade range is already available.

Give each shade a role

Sketch the function of each planned shade before choosing names. A concept might include a base, transition shade, deeper accent and highlight, but the right mix depends on the intended looks. Remove shades that repeat the same role unless the difference serves a clear customer need. This keeps the brief focused even before exact shades are selected.

Describe color and finish separately

Record color family, relative depth and undertone alongside a separate finish reference. Use physical references when possible, and label digital mood boards as directional. Do not assume that a reference photograph establishes a reproducible shade or that a desired finish is available in a selected formula. Ask for sample options tied to identifiable references.

Map a tentative palette layout

Create a simple numbered layout and use the same numbers in every shade discussion. Note which colors should sit together to communicate a look and which should be easier to distinguish. Pan count, shape and dimensions remain proposal fields until the component and product combination is confirmed.

Keep packaging questions visible

Include intended portability, opening style, decoration area and whether a mirror is requested. Record dimensions or material preferences only when known, marking the rest as questions. Connect this document to your packaging brief so component decisions do not drift away from the color plan.

Request evidence for the selected references

Ask the project team to identify each sample, formula version and proposed use. Any ingredient, testing, market or labeling documentation should correspond to the selected product. Leave claims such as long wear or waterproof performance out of public copy until the relevant support has been reviewed. Do not turn a visual mood board into a specification sheet.

Plan the review in stages

Review the shade story first, then the identified samples, followed by the proposed finished presentation. Keep written feedback for each stage. If a shade or component changes later, identify the affected approvals and review those again. Use one decision owner to consolidate comments and keep the numbered layout current.

Turn the concept into a useful inquiry

Share the target customer, intended looks, numbered shade roles, finish direction, packaging preferences, estimated quantity range and desired launch window. Ask which options can be reviewed and which information is still needed. Minimum quantities, prices and timing should be confirmed for the specific project rather than copied from a generic planning example.

Explore our color cosmetics categories, prepare a packaging brief, or discuss a private label project.