Grading Design Brief: What to Confirm Before Drawings Begin

Key Takeaways

• Describe the proposed change before choosing a drawing package.
• Separate confirmed records from assumptions and information still needed.
• Identify who supplies each design input and who can approve a change.
• Keep one current brief and drawing list as the project develops.

You do not need a complete technical package to make the first enquiry. However, a short, honest description of what is known helps the team ask better questions. The aim is to make the next decision clear, rather than to solve the grading yourself.

What belongs in a grading design brief?

A grading design brief is a working summary of the property, intended changes, available records and decisions that may affect levels or drainage. It supports the engineering assignment. It does not replace a survey, a grading plan, a professional opinion or a municipal application.

Think of the brief as the cover note for your project information. A folder of drawings can show many details without explaining which version is current. Likewise, an email saying “we need grading” may leave the engineer unsure whether you need initial advice, new design, revisions or later field review.

A useful brief connects those pieces. It names the current layout, explains what you want to change and identifies questions that remain open. It also records who supplied the information, so the design team can confirm important details with the right person.

Confirm the purpose of your design brief

Start by stating the decision you need help with. For example, you may want an engineering scope for a planned addition before the architect fixes the floor levels. Alternatively, you may have municipal comments and need to understand which civil drawings require revision.

These are different starting points. Therefore, include the actual request or review letter when one exists. Avoid selecting a service solely because another project used the same name.

What a site grading plan covers, from design through review

1. Define the project in your grading brief

Begin your grading design brief with the property address, municipality and a plain-language project description. Explain what will remain, what may be removed and what you want to add. Include the building and the outside areas that could change with it.

For instance, a rear addition may also affect a patio, basement entrance, downspouts and access beside the house. A commercial alteration may leave the building footprint unchanged but revise parking or loading areas. These connections help the engineer understand the project before reviewing individual dimensions.

Distinguish a concept from a decision

Clearly label an idea that is still being explored. A sketch for discussion should not look like an instruction to use a fixed floor elevation. Similarly, a preferred driveway layout may remain subject to planning, access or engineering review.

Write down the current stage: early concept, design coordination, application preparation, response to comments or proposed change after approval. Then identify any drawings already submitted. This avoids designing against an option the rest of the team has stopped using.

Set priorities in the grading brief

Explain why a feature matters. Perhaps you want step-free access to a door, continued access to a garage or room for a future pool. The team can then assess the priority alongside site conditions and applicable requirements.

However, avoid treating the preferred outcome as technically proven. A brief can say “please assess whether this entrance arrangement works.” It should not imply that a particular grade, drain or retaining wall is already acceptable.

2. Record the sources behind your design brief

The most helpful grading information pack uses a small record register. For each document, note its title, author or source, date, revision and purpose. Also say whether it represents existing conditions, proposed work or an earlier approval.

A property survey, old grading drawing and current architectural plan may all be useful. Yet they answer different questions. The engineer needs to know what each file represents before using it as a design input.

Keep originals and identify current versions

Send readable original PDFs when available. If a drawing was emailed to you, retain its filename and revision information. Cropped screenshots can remove notes, scales or title blocks that explain important limits.

Where editable files are available, ask which format the design team needs and confirm that you may share them. Do not assume that receiving a drawing gives you permission to alter another professional’s work. Keep the issued document alongside any working file.

Flag differences instead of silently choosing one

Suppose an older drawing shows a deck that no longer exists, while a recent sketch omits a retaining wall. Flag both differences in the project brief. Let the appropriate professional decide what needs to be checked or measured.

Use straightforward status labels such as “current,” “superseded,” “background only” or “needs confirmation.” You do not need a complex document system. A clear distinction is more useful than a folder full of files all called “final.”

Give each grading brief input a clear status

A grading project brief becomes easier to use when every important input has a status. Three simple labels can separate reliable starting information from decisions that still need attention. Use them consistently in your cover note and record register.

“Confirmed” needs a defined purpose

A layout can be confirmed for preliminary coordination while still requiring technical review. Therefore, state what the confirmation means. Avoid using “approved” unless you can identify the actual approval and the work it covers.

Likewise, a client decision and an engineering conclusion are different records. The owner may confirm the preferred building option. The engineer still needs to assess the relevant grading implications using suitable information.

Prioritize gaps that affect the next decision

Ask which missing inputs prevent meaningful progress and which can follow later. A small administrative detail may not stop an initial scope discussion. In contrast, an unresolved building location may change the design work being requested.

This does not mean guessing missing information to keep moving. Instead, ask the responsible professional whether any preliminary work is appropriate and how its assumptions should be recorded. Keep those assumptions visible until they are resolved.

Close the loop when an answer arrives

When someone supplies an updated record, change its status in the brief and notify the people using it. Include the new revision rather than simply saying “the issue is sorted.” A brief note about the decision helps the team understand what changed.

Finally, ask whether that answer affects any earlier work. An updated survey or changed building level may require another review. Closing a question in the register is useful only when the relevant design team receives the answer.

3. Confirm survey inputs for your grading brief

Survey information is a major input to grading design, but not every survey contains the same information. Ask the engineer to review what you have before commissioning additional work. The required scope depends on the site, proposed changes and review pathway.

The Association of Ontario Land Surveyors’ Topographic Surveys Guide emphasizes understanding a survey’s purpose, required features, accuracy and deliverables. This supports an important practical step: coordinate the survey scope with its intended design use.

Survey questions for the design brief

For your grading design brief, record the survey date and any stated limitations. Ask whether the available information covers the areas affected by the proposed work. The team may need to consider relevant features beyond the immediate building footprint.

Also ask whether the survey and other drawings use compatible elevation references. A number on one drawing cannot safely be compared with another without understanding how each level was established. Leave that technical reconciliation to the responsible professionals.

Tell the team what has changed since the survey

Identify visible changes such as new paving, altered entrances, removed structures or a changed fence line. Describe what you know and when you noticed it. Do not move surveyed boundaries or adjust elevations yourself.

Photos can help explain the change, but they do not establish precise levels or legal boundaries. As a result, the team may recommend updated information before detailed design can proceed.

4. Add observations to your grading brief

Owners often know useful things that do not appear in a drawing. Water may collect at a doorway after heavy rain, or a low area may remain wet long after nearby surfaces dry. Include those observations in the brief without claiming a technical cause.

State where the condition occurs, when you observed it and what else was happening. For example, “water remained beside the rear steps the morning after rainfall” is more useful than “the entire drainage system has failed.”

Photos in a grading information pack

Take clear views from locations you may lawfully access. Show both the detail and its surroundings, and identify the viewing direction. If useful, mark photo positions on a simple copy of the site layout.

Avoid entering neighbouring property, lifting covers, approaching unstable excavations or exposing yourself to traffic for a photograph. Existing photos and a written description are enough for an initial discussion. The professional team can identify any further field information it needs.

Record uncertainty openly

If you do not know where a drain connects, say so. A visible inlet does not establish a lawful outlet, pipe condition or available capacity. Likewise, an apparent slope does not prove how water behaves during different conditions.

Keep observations separate from proposed remedies. This gives the engineer room to investigate the actual problem rather than design around an unverified assumption.

5. Connect design decisions in your grading brief

Grading design can depend on decisions made by several people. Your brief should identify those connections before the drawings develop independently. The important question is not only “who draws this?” but also “whose information does that drawing rely on?”

For Toronto Site Plan Control applications, the City’s Site Grading Plan terms of reference connect grading with the site plan, topographic survey, servicing plan and supporting reports. That is a Toronto application-specific example, not a single submission rule for every Ontario property.

Building levels and outdoor access

Ask who is responsible for confirming proposed floor levels, doors, garage thresholds and basement entrances. Identify the current architectural drawing and the person coordinating it. Changes to these features can affect surrounding ground levels and drainage routes.

Similarly, note any access objectives for walkways or outdoor spaces. Record the desired use so the relevant designers can coordinate it. Do not insert a generic slope from another municipality into the brief as a fixed design instruction.

Servicing, stormwater and landscape features

Identify known work on water, sanitary or storm services. Also flag proposed walls, pools, planting areas and large changes in hard surfaces. These features may need input from different disciplines or separate review.

The brief should ask which connections matter for this project. It should not assume that grading design includes every related report, permit or specialist assignment.

How site servicing plans connect utilities with the site layout

6. Give your design brief the review context

Attach relevant municipal correspondence, application checklists and previous approval documents to your grading information pack. Identify the application or file number, where available. Include the full request so the team can read qualifications and context.

A comment copied into an email may omit the drawing reference or condition that explains it. Therefore, send the complete comment letter together with the drawing set it addressed. Tell the engineer if another consultant has already responded.

Confirm the pathway for the actual property

Municipal requirements vary with project type and location. For example, Toronto publishes separate grading guidance for qualifying infill housing. Its stated scope excludes projects subject to subdivision or site plan approval.

Use that distinction as a reminder to confirm the correct pathway. Do not combine requirements from different application types simply because both mention grading. The project team should check the current requirements with the governing authority.

Separate design dates from decisions by others

Share the dates that matter to you, including intended construction, financing or application milestones. Then identify which dates are preferences and which arise from an actual notice or commitment.

Design preparation, consultant coordination and authority review are separate stages. A requested drawing date is not a guaranteed approval date. A clear brief makes these dependencies visible before the schedule is treated as settled.

7. Assign responsibilities in the grading design brief

A short responsibility list can prevent repeated requests and conflicting instructions. Name the person who coordinates the owner’s decisions, the current building designer and the source of survey information. Add other consultants where they are already involved.

Next, identify who will gather missing records, confirm design choices and circulate new drawings. One agreed contact can consolidate the owner’s comments. However, that does not transfer professional responsibility away from the person preparing each discipline’s work.

Define what the engineering proposal includes

Ask the proposal to identify the drawings, reports and review services included in the assignment. Discuss assumptions, client-supplied information and items that may need a separate scope. This makes it easier to compare proposals on their actual content.

Also ask how revisions will be handled. Responding to comments on an agreed design is different from redesigning after the owner changes the building footprint. The proposal should explain how the project team will assess additional work.

Plan the later stages early

Field review and final grading documentation may be separate parts of the assignment. Discuss them before construction planning depends on their availability. The appropriate scope and responsible professional depend on the project and its review requirements.

For instance, Toronto’s qualifying infill-housing guidance describes design, field review and final certification duties. Do not assume that obtaining an initial drawing automatically arranges every later service.

A grading information pack checklist you can use

Use the following checklist to assemble an initial package. Include what you have, clearly mark missing items and ask which gaps matter first. You can start a conversation before every box is complete.

• Property address, municipality, project description and current design stage.
• A brief explanation of goals, features to retain and options still being considered.
• Available surveys, architectural plans and earlier civil drawings with dates and revisions.
• Relevant approval documents, application checklists and complete review comments.
• Site observations and labelled photos, with unknown conditions clearly identified.
• Project contacts, desired timing and questions about the engineering scope.

Write the grading brief’s cover note

Your cover note might say: “We are planning a rear addition and reviewing the entrance arrangement. The attached layout is for discussion. The survey predates recent patio work, and the floor levels remain unconfirmed. Please identify the information and engineering scope needed before detailed design.”

This is an illustrative example, not a completed project record. Notice that it describes the objective, identifies a data gap and asks for a next step. It does not prescribe unverified elevations or claim an approval.

Ask for the next decision, not every answer at once

End the brief with two or three practical questions. Which record needs updating? Which design decision should be resolved first? What services should the proposal include? Focused questions keep the initial review useful and manageable.

Keep the grading brief current as design changes

Your grading design brief should develop with the project. Add a date whenever you issue a new version, and identify the current supporting drawings. Keep earlier versions for context rather than overwriting the only record of a decision.

When a design change occurs, explain what changed and why. A revised entrance, driveway or building footprint may affect more than one drawing. Ask the coordinator which disciplines need to review the change before issuing an updated package.

Add a change note to the design brief

A useful change note records the requested change, its source, affected drawings and decisions still needed. It also records who will confirm the response. Avoid marking an item “resolved” merely because an email was sent.

For example, an owner may choose a different patio layout after an earlier grading review. Circulate the revised layout and ask whether levels, drainage or walls need reassessment. The design team can then identify the effect on its work and scope.

Do not mix a new option with an earlier approval

Keep the approved set clearly separate from later proposals. If a change may affect an issued permit or approval, ask the appropriate professional and authority how to proceed. A revised drawing in a shared folder does not, by itself, amend an approval.

Likewise, do not send competing versions to different team members without explaining their status. A short drawing register makes a practical difference here: everyone can see which information the next design step should use.

When stormwater management becomes a separate engineering workstream

Common gaps in a grading information pack

The most common problem is not a missing technical calculation. It is uncertainty about what the project actually includes. A clear grading design brief should resolve simple communication gaps before the team spends time interpreting them.

“Use the latest plan” without a revision

Name the plan and revision rather than relying on a file’s upload date. Someone may have uploaded an older drawing recently. If you are uncertain which version is current, ask the document’s author to confirm it.

“Everything is included” without a scope

Specify the services being discussed. Surveying, architectural design, structural design, civil reports, municipal submission and construction review are distinct activities. They may be coordinated, but their inclusion should be clear in the proposal.

“The neighbour did it” without project evidence

A nearby project can prompt useful questions, but it does not establish your requirements or approvals. Differences in levels, drainage, proposed use and review history can matter. Use the actual property information to define the assignment.

“We will confirm that later” without an owner

A missing input needs a responsible person and a next step. Otherwise, it can disappear from the conversation until it blocks design. Record who will obtain the information and whether work can proceed without it.

Turn your grading design brief into a clear next step

A useful first conversation should leave you knowing which information is sufficient, which items need confirmation and what the proposed assignment covers. Ask for that clarity before treating a preliminary discussion as a completed design decision.

Keep the brief proportionate. A small residential change may need a short cover note and a few records. A larger development may need a more detailed information register. In both cases, clear sources and responsibilities are more useful than an impressive-looking document with uncertain facts.

Finally, share the current package through the agreed project channel. Explain what changed since the last issue and identify the questions that need an answer. This gives the engineering team a practical basis for a proposal and the next stage of coordination.

Coordinating building permit drawings with the proposed site changes