How to read and review a floor plan

Read the walls, the rooms and the openings

A plan is made of a few entity types, and reading it means knowing which one you are in front of. Walls are lines with a thickness and a kind: Exterior, Interior or Partition. Rooms are rectangles with a name, a type and an area. Openings are doors and windows on a room edge. Dimension lines and notes sit on top.

Start with the walls, because they decide the shape of everything else. Follow the outside line and check that it closes: a gap is either a missing segment or a door you have not noticed. Then look at the interior partitions and ask what each one does, because one splitting a zone in two is usually a leftover.

Then read the rooms. Every rectangle needs a name and a type, and the area label tells you whether the size is plausible. A bathroom larger than the kitchen is worth a question, and a rectangle with no name means the plan was unfinished.

• Walls carry a thickness and a kind: Exterior, Interior or Partition
• Rooms carry a name, a type, a fill color and an area
• Openings are attached to a room edge and drawn with a swing or a sill
• Dimension lines and notes are annotations, not geometry

Check the numbers against the room schedule

The fastest way to check a plan is to read it as a list. Export the room schedule as CSV and open it in a spreadsheet. Every room appears with its name, type, width, depth, area, an optional floor finish and an optional note, and the file ends with a total row for the plan.

Three things jump out of a list that are invisible on a drawing. A room whose area does not match the shape in front of you. A room whose name does not match its type, such as Study typed as Meeting room. And a total that does not match the floor area, which usually means a corridor was never drawn.

Read the list against the drawing too. The schedule gives numbers and the drawing gives positions, and a plan works only when the two agree. If a room is called Kitchen in the list and looks like a closet, ask which is right before anybody acts on it. The export guide explains how to produce the schedule in the first place.

• The CSV gives name, type, width, depth, area, finish and notes
• Compare each area with the shape you see on the drawing
• Check that each room name agrees with its type
• The total row should match the floor area of the building

Note: The schedule describes the rooms in the plan and nothing else. It does not include walls, openings, dimension lines or the space between the rooms.

Trace the routes through the plan

Now read the plan as movement rather than geometry. Pick the people in it and trace their day. In a home, the route from the front door to the kitchen, bathroom and bedrooms. In an office, from the entrance to the furthest desk and the meeting room. In a shop, from the entrance through the sales floor to the counter.

Watch the swing arcs while you walk. A door that opens across the only route is a real problem, and it is visible only in the drawing. Watch the widths too: a route that narrows to a point, or a hallway two people cannot pass along, is worth a note even when no rule says so.

Then trace the routes that do not exist yet. Where does the recycling go? Where does a delivery trolley end up? Where does a visitor wait when they arrive early? These are the questions a plan invites, and two or three beat a long list of style opinions.

• Trace the real daily route of the people who use the space
• Note every door swing that crosses the path
• Look for pinch points where the route narrows
• Ask where the deliveries, the recycling and the waiting happen

Note: A plan is a flat drawing, so it cannot show a level change, a slope or a stair detail. Ask about those separately.

Ask what the plan leaves out

Every plan is a set of decisions about what to show. A plan with walls, rooms and openings does not show plumbing, electrical runs, ventilation, structure or drainage. Those may have been decided, or never considered, and the plan cannot tell you which of them applies.

The version you are reading also has limits worth stating out loud. There is no 3D view, no section or elevation, and no DXF import, so a survey drawing cannot be brought in. There is no cost estimation, no code checking and no occupancy calculation, and nobody can edit beside you.

So decide which omissions matter for the decision in front of you. If the question is whether the layout works, the plan answers it. If the question is whether the building will pass inspection, it cannot, and an honest review says so plainly. The boundary guide sets out that line in full.

• Services, structure and electrical runs are not shown
• No 3D view, no sections and no DXF import
• No cost estimation, no code checking, no occupancy rule
• Decide which omissions matter for this particular decision

Separate problems from preferences

A review that mixes faults with tastes is a review nobody can act on. Sort your comments into two piles as you go. A problem breaks a stated requirement: the bathroom has no door, the route to the kitchen crosses the hallway, twelve desks are planned and eight will arrive. A preference is another way of doing something that works.

The test for a problem is that it has a right answer: somebody can say whether the plan satisfies it. The test for a preference is that two competent people can disagree for ever, so it belongs in a conversation, not in a list of defects.

Write the two piles separately, even if you send them together. The problem list is a set of instructions that can be ticked off, and the preference list is a discussion the author can accept or decline. Reviewing a wireframe has the same split, and the wireframe review guide explains why style is graded differently.

• A problem breaks a requirement somebody actually stated
• A preference is a different way of doing something that works
• Problems can be ticked off; preferences need a conversation
• Keep the two lists separate even if you send them together

Write the feedback so it can be acted on

Good review feedback is small and specific. "The hallway feels cramped" cannot be acted on. "The hallway is 1100 mm wide, and I would want 1200 mm for two people to pass with a box" can, because it names the number, the reason and the change.

Point at the thing rather than at the person. Reference the room by name, the opening by the edge it sits on, and the number by the field it comes from. A reviewer who says "the Width (mm) field on the Living room is 3200 and the note says 3600" has saved the author a hunt.

Close with the decision you want. A review should end with a request for a revised entrance area, a question about a window width, or a request to compare two versions. The complete Canvasola guide covers keeping versions side by side so a change request is easy to answer.

• Name the room, the edge and the field you are talking about
• Give the number you read and the number you expected
• Ask for a specific change, a comparison or an answer
• Keep comments small enough to act on this week

Note: Feedback that says what should change, and why, gets acted on. Feedback that says what you would have done gets argued about.

A checklist you can reuse

• The exterior wall line was read and confirmed
• Every room has a name, a type and a plausible area
• The room schedule was exported and compared with the plan
• The total area was checked against the floor area of the space
• One real route was traced through the plan
• Door swings across the path were noted
• Problems and preferences were written in two lists

Common mistakes to avoid

• Reviewing the drawing without the numbers. A picture hides size errors and mismatched names. Export the room schedule and read the plan as a list first.
• Confusing taste with a fault. Comments that mix a broken requirement with a personal preference get argued as one item. Keep two lists so the actionable half is not held hostage.
• Writing feedback that cannot be executed. It feels cramped leaves the author guessing. Give the number you read, the number you expected and the change you want.
• Ignoring what the plan never claims. A plan drawn here is a planning aid with typical dimensions. It carries no services, no structure and no code compliance, and treating it as a construction document is the costliest misreading.
• Ending the review without a decision. A list of observations leaves everyone unsure what happens next. Close with one question that can be answered.

Frequently asked questions

What do the different wall types mean on a plan?

Exterior, Interior and Partition are the three wall kinds in the builder, and they set the thickness and the drawn weight of a wall. They are planning categories rather than structural specifications, so they show intent, and no wall in the plan is load-bearing by definition.

Can two people review a floor plan together?

Not inside the app. There is no real-time collaboration and no share link, so a review happens by exporting files and comparing them, usually in a spreadsheet. The room schedule CSV is the easiest artifact to circulate, and the PNG is the easiest one to look at.

How do I check whether a plan is code compliant?

You cannot with this tool, and no plan drawn here claims to be. The builder has no code checking and no per-country building code data, so compliance has to be confirmed by a qualified professional against your local rules and the specifics of the project.

What is the difference between a room area and the room schedule total?

The total row is the sum of the areas of the rooms you drew. It excludes walls and any corridor not drawn as a room, so it is normally smaller than the gross floor area of the building by a fair margin.

This guide is part of the floor plan guides collection. For the wider product tour, read the complete Canvasola guide, and keep the keyboard shortcut cheat sheet open while you work.