A Client-Approval Recipe for Preventing the Midnight Redesign

The proposal was approved three weeks ago.

Tonight, at 11:48 p.m., a message arrives asking whether the entire event can feel “less formal, more cinematic, and possibly blue.”

This may be a genuine change of heart. It may be anxiety arriving after business hours. It may be the first sign that everyone admired the proposal and nobody understood which decisions had actually become commitments.

The cure is not a more forceful “approved” stamp. It is an approval process that makes scope, evidence, authority, deadlines, and consequences visible before the midnight redesign discovers a group chat.

Define what is being approved

“Looks great” is praise. It is not necessarily procurement authorization.

Every approval request should identify the decision level:

• Concept: overall atmosphere, thesis, palette direction, and experience.
• Design development: layouts, materials, floral direction, lighting, furniture, and key interactions.
• Scope and quantity: how many pieces, where they appear, and what is excluded.
• Cost: approved price, allowances, taxes, delivery, labor, rentals, contingencies, and assumptions.
• Production: final specifications released for ordering, fabrication, printing, staffing, or installation.

A client may approve the mood and still have unresolved quantities. A color may be approved while a material sample remains open. Record those distinctions.

Name the decision owner

Identify who has final authority for each category and how input from other people reaches that person.

Some projects have one client. Others include partners, family, committees, sponsors, venues, brand teams, or cultural and religious decision-makers. Input can be broad. Approval cannot remain indefinitely plural.

Do not collect final direction from separate text threads, calls, comments, and someone’s mother after the person with budget authority has approved a different version.

When several approvals are genuinely required, list each one and the order in which they occur.

Input can be broad. Approval cannot remain indefinitely plural.

Present decisions with evidence

Show enough information for the approver to understand what the choice means.

Depending on the item, that may include:

• plan and elevation;
• dimensions and quantity;
• material, finish, texture, and color samples;
• day and night references;
• guest and service implications;
• venue restrictions and access conditions;
• price and what it includes;
• lead time and decision deadline;
• known substitutions or variability;
• what changes elsewhere if this option is selected.

A tiny image pasted into a moodboard cannot carry every one of those decisions. Use the format appropriate to the risk.

Offer bounded choices

When a decision remains open, present two or three developed routes with consequences.

“Anything is possible” is charming before procurement. It becomes expensive when every answer generates a new universe for comparison.

For each option, explain what changes in cost, labor, timeline, guest experience, venue fit, and visual result. Recommend one based on the governing concept and constraints.

The client remains free to choose. The process does not remain free to expand without limit.

Record open questions separately from approved work

After every substantive meeting or review, issue a concise decision record.

Include:

• approved items;
• rejected items;
• open questions;
• the owner of each answer;
• the deadline;
• budget or timeline effects;
• the current document or version.

Silence should not automatically become approval unless the agreement explicitly establishes that process and it is appropriate to the project. Ambiguity is not efficiency; it is a future disagreement acquiring stationery.

Use samples at the scale of consequence

A high-risk or expensive decision deserves more than a verbal description.

Mock up the centerpiece on the real table. Print the menu at final size. View the fabric under event lighting. Test the custom object in a guest’s hands. Mark the installation volume in the room. Confirm the arrangement’s unfinished side does not become visible after repurposing.

Not every detail needs a prototype. The pieces involving substantial cost, fabrication, interaction, fit, safety, or subjective interpretation often do.

Set design-lock dates by production reality

There may be several lock dates rather than one dramatic final deadline.

Printing, custom fabrication, rentals, flowers, menu counts, staffing, transportation, signage, floor plans, and guest data may close at different times.

Publish those dates early and explain what happens after them. A change may become impossible, require a substitute, trigger rush charges, affect other approved elements, or move to a later phase.

“Final” should mean the work has entered a different operational state—not that the project team has become emotionally tired of discussing it.

Price reversals honestly

A late change is not necessarily a moral failure. It is often a purchase order.

Document:

• work already completed or ordered;
• cancellation or restocking costs;
• new design and production labor;
• rush or overtime implications;
• changes to other vendors or materials;
• new risks and lead times;
• the revised approval deadline.

Do not absorb the consequences invisibly to preserve goodwill. Hidden costs tend to reappear later as resentment, reduced quality, or an invoice nobody recognizes.

Distinguish anxiety from a design problem

Late-stage doubt does not always require redesign.

Ask what prompted the concern. Has the client seen a new image, received outside criticism, misunderstood scale, become worried about guest comfort, or realized the event no longer feels personally recognizable?

A late change is not necessarily a moral failure. It is often a purchase order.

Return to the approved thesis and evidence. A fuller rendering, mockup, walkthrough, lighting test, or explanation may resolve uncertainty without changing the work.

When the concern reveals a real failure—access, service, safety, meaning, fit, or an emotional misread—correct it. Process should not be used to defend a bad decision merely because it is documented.

Create one current record

Maintain a central approved set containing the latest plan, scope, specifications, budget, decisions, and change log.

Retire obsolete files clearly. Vendors should not have to determine which attachment in a twelve-message thread became real.

Use file names, dates, version numbers, or whatever project tool suits the scale. The exact technology matters less than one rule: the current record must be identifiable without interpretation.

Brief every affected vendor after a change

A design reversal rarely belongs to one team.

Changing color can affect flowers, linen, lighting, print, rental inventory, food presentation, and photography. Moving a focal point can affect power, floor plan, service, sound, and access.

Issue the approved change to every affected party with the new specification, timing, cost authorization, and responsibility. Do not assume vendors will discover the revision through visual intuition on event day.

Protect the relationship and the work

A strong approval process does not silence clients or punish change. It allows people to make informed decisions while enough time remains to execute them well.

Midnight can return to being a time rather than a revision category.

Part of Start With What You Actually Have.