Concept Design

A client may know what a space or product should achieve without knowing its form, and concept design explores possible ways to meet that brief before detailed technical development. In building projects, RIBA identifies Concept Design as Stage 2 in its plan of work, while other frameworks, such as AIA's schematic design phase, use different stage names, so do not assume every industry follows one sequence.

A fictional cafe owner who wants more seating and a better service flow might receive two sketched layouts with trade-offs explained, and these drawings are not yet construction instructions. Start with a clear brief that records goals, users, budget, site constraints and desired timeline, because unclear inputs can produce attractive ideas that cannot be built affordably.

A fictional office client asks for 80 desks in a limited area, and the designer checks circulation and access before promising capacity, so the concept tests the requirement. Concept deliverables may include plans, mood boards, massing images or a written design story, and the scope should state the number of options and level of detail, since a polished rendering alone may conceal unresolved issues.

In a fictional retail project that includes two options and one review meeting, the client requests six additional options, and the parties check whether this is outside the design fee. Compare options against the brief, not only visual taste, by discussing function, accessibility, structural implications, services and operating costs, and revise a concept that fails basic needs early.

A fictional restaurant plan looks elegant but blocks kitchen deliveries, so operations staff review it before the owner selects the direction, and the concept changes without expensive site work. An outline cost plan helps test feasibility, but at this stage quantities and specifications are incomplete, so estimates carry uncertainty and should show assumptions and exclusions.

In a fictional fit-out concept that requires a complex ceiling, the cost consultant flags it as a budget risk, and the team considers a simpler approach before detailed drawings. Site and regulatory checks can affect ideas, since planning, fire, accessibility and landlord requirements may need specialist input, and concept approval does not equal a permit or construction approval, as a fictional studio planning a new entrance finds when the designer notes that building approval is still needed and the owner stops advertising an opening date as guaranteed.

A design team may include architects, engineers, cost consultants and users, and responsibilities should be agreed at the concept stage because the right input reduces conflicting work later. A fictional architect proposes exposed services, and the mechanical engineer checks whether the idea can meet ventilation requirements, so the concept evolves with evidence.

Review rounds should be defined, with client feedback consolidated and tied to the agreed brief, because repeated changes to core requirements can expand scope and cost, as when a fictional owner first approves a minimalist office and then asks for a hospitality-style lobby, so the designer records the changed brief and a revised fee and timetable may be needed. A stage sign-off records the chosen direction and outstanding questions rather than final finishes or technical detail, so a fictional client who approves a floor plan subject to acoustic testing has given a conditional approval, which the team lists in its handover and no one treats as a finished specification.

Protect the project's documents and rights too, since the design-services agreement should say who may use drawings, when fees are due and what happens if the project stops, and paying a design fee does not answer every rights question when a client takes an unapproved concept to another contractor. Concept design saves money by exposing choices early, and it is successful when the client can select a feasible direction with clear assumptions, costs and next steps.