Describe a renovation project the way you would explain it to a friend: name the area being worked on, say what should be different when the work is finished, describe the look and feel you are after, and list the constraints the job has to fit around. A contractor does not need design vocabulary. A contractor needs to know what changes, what stays, and what you have already decided.
What does a contractor need to know about your project?
A contractor needs four things before quoting: where the work happens, what should be different afterwards, what the result should look like, and what cannot change. Everything else follows from those four. A description that covers them lets a contractor picture the job, price the risk in it, and ask sharper questions instead of guessing.
- The area. Which room or rooms, roughly how big, and what floor of the house. Approximate measurements are fine; say they are approximate.
- What changes and what stays. "Replace the vanity and retile the shower, keep the bath and the window" tells a contractor far more than "update the bathroom".
- The outcome you want. The problem you are solving, described as a result: more storage, a second person able to work in the room, a space that is usable in winter.
- Look and feel. Two or three reference images, plus a sentence about what you like in each one. The sentence matters more than the image.
- Constraints. Whether you will be living in the house during the work, dates the space has to be usable, stairs and access, pets, HOA or strata rules, and anything already booked around the job.
- Decisions already made. Fixtures you have chosen, a tile you have bought, an appliance already sitting in the garage.
How do you describe what you want when you do not know the terms?
Describe the outcome, not the object. You do not need to know whether you want a full-height cabinet or a pantry pull-out; you need to say that there is nowhere to put a week of groceries. A contractor translates outcomes into products every day, and the translation is more accurate when the outcome is stated plainly.
Three habits make untrained descriptions land well. First, describe the moment that annoys you: "by four in the afternoon the room is too dark to read in" is precise, and "the lighting is bad" is not. Second, point at things that already exist — a finish in another room of your own house, a floor in a photo, a friend's countertop. Real references beat adjectives, because "warm" and "modern" mean different things to different people. Third, say what you do not want, which narrows the field faster than almost anything else.
If you keep repeating one sentence when you explain the project to people, that sentence usually belongs at the top of the description.
Which details matter more than design language?
The details that change the price are physical, not stylistic. The age of the house, what is behind the walls, how material gets in and out of the space, and what has already been altered by a previous owner all affect the work more than a color choice does.
Worth writing down before anyone visits: the approximate age of the building, any renovation you know about, where the electrical panel and the water shut-off are, whether the floor above is a bedroom, what the parking and stair access look like, and any problem the house has already shown you — damp patches, a fuse that trips, a door that has stopped closing.
Age deserves a line of its own. In homes built before 1978, work that disturbs paint falls under the EPA's Renovation, Repair and Painting rule, which sets requirements for how the work is carried out. Telling a contractor the house is older than that up front changes how the job is planned rather than surprising everyone on day one.
What goes wrong when a project is described badly?
A vague description does not produce a vague price. It produces a padded one, or a low one covering less work than you imagined, and you cannot tell which from the outside. Contractors who cannot see the edges of a job either add contingency to protect themselves or quote the narrowest reading of what you said.
The second cost arrives later. Work that starts from an unclear description generates change orders, and change orders priced mid-project are priced without competition. That pattern has a name — scope creep — and a written description is the main defense against it.
The third cost is that the quotes stop being comparable. If three contractors each interpreted your kitchen differently, the three numbers describe three different jobs, and comparing the bids becomes guesswork. One written description sent to everyone removes that problem entirely.
How do you get the description down on paper?
Write it once, in a single document, and send the same document to everyone. That document is a renovation brief: a page or two covering area, scope, materials, constraints, and open questions. It does not need drawings, and it does not need to be finished — naming the questions you want advice on is part of the job.
TrueBuild is built for the moment before that document exists. You describe the project in plain English, TrueBuild suggests style keywords you can accept or reject, drafts a written summary you can edit, and can generate a concept image to sit alongside it. You review everything before any of it is sent. See how TrueBuild works, or start a project — signup is not required to start.