What a useful first architecture meeting looks like
A first meeting does not need a finished design. It needs a clear picture of why the project matters, what is already known and which constraints will shape the next stage of work.
Bring the problem before the solution
Describe the moments that do not work: a room that stays unused, a difficult circulation route or a lack of privacy. Bring photographs and any reliable existing drawings, but mark assumptions as assumptions. A list of everyday frustrations gives the architect something more useful than a fixed layout that has not yet been tested.
Discuss the practical boundaries
Talk openly about the intended scope, budget range, timing and decision-makers. Identify permissions or ownership questions that need specialist attention. Ask how the design stages are organised and what information is required before fees or delivery commitments can be confirmed. Early clarity makes later choices easier to assess.
Agree the next piece of work
Finish with a written account of the proposed next step: perhaps a survey, feasibility review or brief-development exercise. Define what that step will produce and what it will not resolve. Ask who will carry out the work, what information you need to provide and when the findings will be discussed. A clear first stage gives both sides a useful basis for deciding how to proceed.
