A commercial winter-service request can sound complete while leaving important decisions open. “Clear and salt the property” does not say which parking aisles, delivery approaches, internal roads, sidewalks or entrances are included. On a Surrey property with several buildings, the difference matters because the manager may be coordinating several users and access points.
Atlas Landscaping & Snow Removal lists commercial snow removal and salting for managed properties. Its Surrey service-area page asks managers to show the building layout and identify internal roads, delivery access, parking, sidewalks and entrances. This guide focuses on a scope register: a short table that connects each named area to the requested service, open questions and final decision. It complements the site's Surrey strata snow-removal quote checklist, which helps councils compare proposals.
What belongs in a scope register?
Start with a dated site plan or annotated aerial image. Give each building, road, parking section, loading approach and pedestrian route a short, stable label. For example, “B1 north entrance” is easier to discuss than “the side door.” Keep a copy of the labelled plan with the register. If the property has an unclear boundary or a surface maintained by someone else, flag that question before the scope is finalized.
The register should not be an equipment instruction. It is a record of what the property manager is asking about and what the proposed arrangement actually includes. Use one row for each area where the requested service, access or priority differs.
| Area ID | Property use | Snow clearing requested? | Salting requested? | Access or approval note | Final scope status |
|---|---|---|---|---|---|
| [B1 entrance] | [pedestrian] | [yes / no / discuss] | [yes / no / discuss] | [gate, hours or contact] | [included / excluded / unresolved] |
| [Parking A] | [vehicle] | [yes / no / discuss] | [yes / no / discuss] | [occupied spaces or access note] | [included / excluded / unresolved] |
| [Loading 2] | [delivery] | [yes / no / discuss] | [yes / no / discuss] | [access contact] | [included / excluded / unresolved] |
The sample labels are placeholders, not examples of an Atlas customer property. Replace them with the site's actual labels. Ask the bidder to check that the map and register match before any agreement is approved.
Keep snow clearing and salting as separate decisions
Atlas lists both services, but a manager should not assume that naming one automatically includes the other. For each row, ask whether snow clearing is proposed, whether salting is proposed, and how the two relate. A walkway might require a separate discussion from an internal road. The answer belongs in the written scope, not in an implied “all areas” statement.
For salting, ask which surfaces, material and application are included. Ask what conditions would prompt treatment and how repeat applications would be handled. For snow clearing, ask what conditions would prompt a visit, what area is to be cleared and how snow placement is addressed. If any action is optional or subject to another request, have the proposal say so.
Do not insert a response time or service trigger into a draft based on a general website description. Atlas's service page does not specify standard triggers or response timing. Request the terms offered for the property, then confirm them in the agreement.
Record access and decision contacts beside the affected area
A multi-building property may have different people responsible for gates, loading arrangements and common walkways. The register can show who can answer an access question and who can approve a change. That does not require sharing private codes in a public-facing document. Keep sensitive access details in the appropriate private handoff channel and put only the contact role or reference in the register.
If a parking area is occupied at certain times or a delivery entrance has a restricted approach, note the constraint beside that area. Ask the bidder how such a condition affects the proposed scope. A plan that shows a route but omits the access rule can lead two parties to interpret the same line differently.
Also establish how a site question will be reported. Which contact receives a notice about a gate problem, an excluded surface or a request for additional work? What written approval is needed before a change to the agreed scope? These are contract questions for the property manager and provider to settle; the Atlas website does not state a standard process.
Distinguish a requested priority from an agreed commitment
Rank the routes the property manager wants considered first, such as an entrance connection or delivery approach. The ranking communicates how the property is used. It does not by itself establish when service will occur or guarantee an outcome.
Ask the bidder whether the priorities can be reflected in the proposed service sequence. If the answer differs from the original request, record the agreed version in the scope register and final proposal. A clear difference is better than an unresolved assumption.
The same approach applies to snow placement. Mark locations where the manager does not want snow stored, then ask what is feasible and included. If relocation, hauling or a different approach may be needed, have the proposal identify whether it is included, optional or outside the scope. Avoid promising a placement method before the site is assessed.
Use a revision line when the site changes
Commercial sites change. An entrance may be reassigned, a gate rule may change, or a new area may be added to the manager's request. Keep a one-line revision history at the top of the register:
| Version and date | What changed | Requested by | Approved by | Agreement reference |
|---|---|---|---|---|
| [v2 / date] | [area label and change] | [role] | [role or pending] | [document or email reference] |
Do not treat an updated map as automatically changing an existing contract. Send the revised register to the provider, request clarification about scope and any terms, and keep the approved version with the agreement. This preserves a common reference for the property manager, council or owner and the contractor.
A short request to send with the register
We manage a commercial property in Surrey at [address]. The attached dated plan and area-by-area register identify the roads, delivery access, parking, sidewalks and entrances we want to discuss. Please confirm which labelled areas are proposed for snow clearing, which are proposed for salting, any access assumptions, the proposed service triggers and timing, the approach to snow placement, and all exclusions or optional work. Please identify the contact and approval process for a change to the agreed scope.
Questions Surrey managers may ask
Can one agreement cover several buildings?
You can ask for a proposal covering several labelled buildings and routes. The contractor must confirm the actual areas, access arrangements and terms it can offer for the property. Keep each different area in the register so inclusions are explicit.
Is salting automatically included with snow removal?
Do not assume it is. Mark salting areas separately and ask how material, application, conditions and repeat treatments are described in the proposed scope.
Does Atlas publish a standard response time?
The current Atlas commercial snow page does not specify one. Ask for the proposed trigger and timing for the Surrey property and confirm the final terms in writing.
What is the next step?
Send the Surrey address, labelled plan, draft scope register and property contact through the Atlas quote form. Atlas can then discuss availability and the site-specific scope without relying on a generic “entire property” description.