Describe the morning, not just the room
A renovation brief begins with the people who will use the space. Saying that a kitchen should be timeless offers little direction. Saying that two people prepare breakfast while a third packs a bag at the counter explains something a plan can address. Describe a few ordinary sequences in the room, including the moments that currently cause friction. The objective is not to produce an exhaustive diary. It is to give the project a practical center so attractive materials are chosen in support of daily life rather than used to distract from unresolved problems.
Include occasional uses, but distinguish them from everyday ones. Hosting twelve people once a year should not automatically dictate a dining arrangement that is inconvenient for two people every evening. Explain how often each activity happens and whether it can be accommodated flexibly. A home office may need to become a guest room several weekends a year; a family bathroom may also be the room used by visitors. Those overlaps are important. They reveal where storage, privacy, lighting, and furniture need to work harder than a simple room label suggests.
Document what works before listing faults
Walk through the existing space and identify the features worth keeping. Perhaps the sink has a pleasant view, the morning light reaches a favorite chair, or a cabinet already stores awkward equipment well. Renovation can accidentally remove these advantages when attention focuses entirely on what is wrong. Record them explicitly, with photographs and a short explanation. A brief that includes only complaints can encourage a sweeping redesign that solves minor irritations while losing the room's strongest qualities. Keeping something useful is a positive project decision, not evidence that the project lacks ambition.
Then separate symptoms from assumptions about solutions. The room feels dark is an observation. We need a larger window is one possible response, with technical and financial consequences that need assessment. A cluttered counter may indicate inadequate storage, but it might also reflect poorly placed storage or items that no longer belong in the room. Write the problem first and discuss potential solutions with the relevant professionals. This leaves room for simpler alternatives and prevents the brief from becoming a shopping list based on a diagnosis that has not been tested.
Set priorities that can survive a compromise
Divide the requirements into essential outcomes, strong preferences, and optional improvements. Keep the essential list short enough to guide a real tradeoff. If everything is indispensable, the list cannot help when cost, space, or timing creates a conflict. An essential outcome might be a clear route through the room or storage for equipment that is used daily. A preference might be a particular cabinet finish. The distinction does not make appearance unimportant. It establishes which aspect of the project should be protected if an unforeseen condition forces a decision.
Explain why each high priority matters. More storage is vague; a place for a folding vacuum, two large trays, and recycling containers can be designed. Better lighting is vague; a comfortable place to read after dark without glare on a nearby screen is more precise. List actual objects and activities rather than relying on general adjectives. Include dimensions when they are relevant and have them checked by the project team. The more concretely a need is described, the easier it becomes to compare options without arguing about what practical or generous means.
Record constraints without guessing at technical answers
List the constraints already known: a lease restriction, shared building rules, an appliance being retained, a limited access route, or a period when the room must remain usable. Identify uncertain conditions separately. A wall's structural role, the condition of concealed services, and ventilation requirements are matters for qualified assessment. Do not turn a visual guess into a fixed project assumption. A useful brief makes uncertainty visible early so it can be investigated before commitments are made. It is better to ask a clear technical question than to hide a hopeful answer in the layout.
Access is easy to overlook. Note stairs, narrow doors, delivery restrictions, parking arrangements, and shared entrances where relevant. Large materials and furniture need a route into the property, while removed materials need a route out. Ask the contractor what additional information is required rather than planning these operations yourself. Also record household constraints: pets, remote working, care responsibilities, and any accessibility requirements the project should accommodate. Share only information relevant to the work, but give the team enough context to propose a realistic sequence and an appropriate temporary arrangement.
Use reference images as explanations
A reference image becomes useful when it has a caption explaining what you like. It might be the low contrast between wall and cabinetry, the generous walking route, or the way a curtain softens a hard edge. Without that explanation, someone else may focus on the wrong feature and reproduce a color you dislike. Limit the collection to images that communicate a clear point. A folder containing dozens of unrelated rooms can conceal the priorities rather than clarify them. Include examples of what you do not want only when they explain a specific concern respectfully and precisely.
Look for recurring qualities across the references. You may discover that the apparent style preference is really a preference for closed storage, natural light, and a few substantial pieces of furniture. Those qualities can be achieved in several visual languages and at different budgets. Avoid asking a project team to copy a photographed room without understanding its dimensions, construction, or context. Use images to establish direction, then let the actual building and household requirements shape the proposal. A successful result should belong to your space rather than feel like a compressed version of someone else's.
State the money and timing clearly
Give an honest working budget and explain what it must include. Construction alone is different from an all in allowance covering design fees, approvals, fixtures, delivery, temporary accommodation, and tax where applicable. Ask the team to identify exclusions and uncertainties in writing. A brief should not imply that the final cost is guaranteed before the scope and existing conditions are understood. It should establish the financial boundaries within which options are developed. Keep a contingency separate from money already assigned to desirable extras, so it remains available for genuine uncertainty.
For timing, distinguish a preference from a fixed constraint. Wanting the room ready before a holiday is different from a lease deadline or an agreed period when access is available. Ask the team what decisions and deliveries control the programme. Some items need approval long before they appear on site. If the household cannot tolerate a long interruption, make that a planning requirement and discuss what it may mean for scope. Do not assume working faster is a cost free adjustment; sequence, availability, inspection, and curing or drying requirements may limit what is realistic.
Decide who approves what
A project can stall when several people believe they are the final decision maker. Name the person who coordinates questions and explain which decisions need joint approval. Agree how proposals, substitutions, and changes will be documented. A conversation on site can be useful, but any change affecting cost, scope, or timing should be confirmed through the agreed process before it becomes work. This protects the household as well as the contractor by reducing misunderstandings. The brief does not replace a proper contract; it gives the later documentation a clearer foundation.
Ask for a decision schedule if the project is complex enough to need one. A list of materials is not the same as a sequence of approvals. The team may need a fixture choice before finalizing a cabinet dimension, or a floor specification before coordinating a threshold. Understanding these dependencies helps avoid rushed purchases. It also makes it easier to see which decisions can wait until more information is available. The aim is to make important choices at the right time, with enough evidence, rather than to settle every decorative detail on the first day.
Keep the brief short enough to remain useful
A clear brief can be a small document with supporting photographs, measurements, and reference images. Use headings that someone can scan during a discussion. Put essential outcomes near the beginning and keep technical questions distinct from confirmed facts. Review the document with the project team and invite them to point out contradictions. A request for extensive storage, a larger open area, and no change to the footprint may require a conversation about priorities. Discovering that tension early is useful; it is exactly the kind of work a brief is meant to do.
Update the brief when the agreed direction changes, keeping a record of the revision. It should remain a description of the current project rather than an archive of every idea considered. At the end of the planning stage, read it beside the proposed drawings and quotation. Can you see how the most important requirements are addressed, and are any unresolved matters clearly identified? That final comparison gives the project a coherent starting point. Buying a beautiful fitting can wait until you know the room around it has a reason to be designed that way.
Keep a copy of the agreed brief with the drawings and contract information. It can provide a useful reference when a later choice feels uncertain. Rather than asking whether a new idea is attractive in isolation, ask whether it advances the outcomes the household agreed were important. That question helps preserve the project's purpose through the many small decisions that follow.
Take it home
- Describe routines and objects rather than relying on style words.
- Mark uncertain technical conditions for professional assessment.
- Agree how changes and approvals will be recorded.



