Multi-property intake
Multi-Property Scope Requests for Property Managers
Explains how to organize a request covering several properties so that each site is described on its own record and service fit is confirmed for each one rather than assumed.
Editorial purpose: Help property owners and managers document a multi-property request so each site has its own record, priority labels stay separate from diagnosis, and service fit is confirmed for each property rather than inferred from a city page.
Prepared by: Seven Stones Construction Ltd.
Date reviewed: 2026-09-04
Scope limit: Educational planning only; this page does not diagnose any property condition, design or specify work, approve or accept a request, confirm that a service is available for a given property, or predict the outcome for any specific site.
A multi-property request should make each site reviewable on its own. A website city page does not prove that every service is available for every property. Fit depends on the service, location, access, timing, property rules, and current capacity.
Purpose and limits
A multi-property request should make each site reviewable on its own. A website city page does not prove that every service is available for every property. Fit depends on the service, location, access, timing, property rules, and current capacity.
Create one site record per property
For each property, record the general location, property type, decision-maker, service being considered, desired outcome, visible conditions, access rules, occupied-area impacts, timing constraints, and privacy-safe photos. Avoid combining unrelated sites into one description.
Separate priority from diagnosis
Use practical priority labels such as access blocked, active water observed, surface damage, seasonal planning, budget planning, or routine maintenance. A priority label is not a diagnosis, treatment recommendation, price, or response promise.
Identify authority and communication
Record who can authorize review, approve scope changes, arrange entry, notify residents or tenants, and receive follow-up. Note council, owner, manager, or procurement requirements without sharing unnecessary private records.
Confirm service-area fit
Seven Stones should confirm whether the requested service and location are within current capacity. Do not infer fit from a city page alone. When several properties are involved, identify which sites can be grouped for discussion and which require separate review.
Prepare a comparison record
Use consistent fields across sites: site ID, service, condition, access, timing, authority, evidence available, next decision, and status. This supports a clearer conversation without promising acceptance or schedule.
Next step
Review the relevant service page, then contact Seven Stones by phone or email with one privacy-safe record for each property.
Frequently asked questions
Does a city page confirm that every service is available there?
No. Service fit depends on the requested work, location, access, timing, property rules, and current capacity.
Should several properties be combined into one description?
Use one consistent record per property so the decision-maker, visible condition, access constraints, and open questions remain clear.
Is a priority label a diagnosis or response promise?
No. It is an intake label that helps organize review without determining cause, treatment, price, timing, or acceptance.