TREADSTONE LAW · ONTARIO · DIGITAL LEGAL SERVICES · EST. MMXXI ·TSL
Home/Case Studies/Litigation
№ 152 Case Study — Litigation

A Shared Markham Driveway Buckled Under Someone Else's Guests

A logistics truck could not reach its loading dock because the asphalt underneath it had given way. Mehrdad, watching from overseas, had to work out why and who would pay for it.

Litigation8 min readMarkham, OntarioShort-term rentals next door
All Litigation case studies
ClientMehrdad, a supplier whose Markham property he manages from overseas
The issueA shared commercial driveway broke down under traffic from a neighbouring short-term rental business, blocking a loading dock
ServiceReviewed the shared-access agreement remotely, coordinated an engineering assessment, and negotiated a cost-sharing and use-restriction settlement
ResolutionPartial win, a negotiated repair split and new usage limits, with both sides giving up ground to avoid a drawn-out remote lawsuit

The situation

The call came in at four in the morning Mehrdad's time. A section of the shared driveway apron between his Markham property and the building next door had collapsed under the weight of a moving truck, and the collapse had taken out the approach to the loading dock his tenant's logistics company used every day. Kaveh, who owned that logistics business and leased the space from Mehrdad, was standing in front of a hole in the asphalt with three trucks idling and nowhere to unload, trying to reach anyone who could tell him what to do next.

Mehrdad owned the Markham property as one piece of a supply business that fed a chain of clinics he ran, and he had not set foot on the site in over a year. He managed it the way he managed most of his holdings, through a local property manager and occasional video calls, trusting that the day-to-day would sort itself out on its own. It usually did, until the driveway gave out under a truck it was never built to carry.

The property next door had been a straightforward office building for years, sharing a single wide driveway and turning apron with Mehrdad's site under an old access agreement neither owner had looked at closely in a decade. That changed about eighteen months earlier, when the neighbouring owner converted the building into short-term furnished suites, listed nightly on a rental platform aimed at business travellers. Guests came and went constantly, and so did the vehicles that served them: moving trucks bringing furniture in and out for turnover stays, delivery vans restocking supplies between guests, rideshare pickups idling at odd hours, all funnelled across the same stretch of pavement that had been engineered decades earlier for occasional office traffic and not much else.

By the time the apron collapsed, the surface had been cracking for months, something the property manager had flagged in a routine site visit and nobody had acted on with any urgency. Mehrdad, coordinating everything from a time zone eight hours removed, needed to work out who was responsible for the damage, who was responsible for the repair, and how to stop it from happening again, all without being able to walk the site himself, look at the cracks, or shake hands with the neighbour across the fence.

Where it went wrong

The original shared-access agreement, drafted decades earlier when both buildings held stable office tenants, described the driveway as intended for normal business and delivery traffic and split maintenance costs evenly between the two owners. It said nothing about short-term rental use, because that use did not exist when the agreement was written. The document was silent on the question that now mattered most: whether traffic generated by a nightly-turnover rental business, structurally different in volume and vehicle type from office traffic, still counted as the normal use the agreement contemplated.

The neighbouring owner, Marco, argued it did. Guests still drove cars, delivery vans still delivered, and nothing in the decades-old agreement barred him from renting his building the way he chose. From his position, the driveway's condition was ordinary wear from ordinary traffic, and the even cost split the agreement already set out should apply regardless of who generated the load.

Kaveh, whose business bore the daily cost of the blocked loading dock, had his own view too. He had been raising concerns about the driveway's condition with the property manager for months before the collapse, concerns that had been logged but never escalated into anything more formal, which left him frustrated that a problem he had flagged early was only being taken seriously once it became impossible to ignore.

An engineering assessment we arranged told a different story. The apron had been built to a specification suited to periodic heavy vehicles and steady light traffic, not the volume of moving trucks and turnover-related deliveries a short-term rental operation generates when a portion of its guests are effectively moving furniture in and out every few days. The assessment estimated that a majority of the surface stress causing the collapse traced to vehicle types and frequency tied specifically to the rental conversion, not to the traffic pattern either building had generated when the agreement was signed.

That distinction mattered because a shared-access agreement generally assumes both parties are using the easement consistently with what was contemplated when it was made. A material change in use, one that measurably increases wear and was never priced into the original arrangement, can shift responsibility even where the agreement's cost-sharing language looks even on its face. Where it went wrong was not the agreement itself. It was one side changing what the driveway was used for without ever revisiting what that change should cost.

What we did

  1. Set up a structured remote workflow with Mehrdad from the outset, since every instruction, signature, and review had to happen across time zones, using scheduled calls and a shared document folder so decisions did not stall waiting on a single overnight window to close, and so nothing depended on a single missed message. A driveway that blocks a working loading dock cannot wait a week for signatures to travel back and forth, and the structure kept the file moving on our own business hours while still giving Mehrdad a clear daily window to review and approve.
  2. Pulled and reviewed the original shared-access agreement, identifying that it described normal business traffic without anticipating short-term rental use, which became the central gap the rest of the dispute turned on, and confirming neither owner had ever formally amended it since it was signed. That review told us the fight was not really about the wording of the agreement at all, but about a change in use the document had never contemplated, which reframed the entire dispute before a single letter went out.
  3. Commissioned an independent engineering assessment of the driveway, arranged and attended locally on Mehrdad's behalf since he could not be there himself, to establish objectively how much of the damage traced to rental-related vehicle traffic rather than ordinary wear, giving the dispute a factual anchor instead of two owners trading competing impressions. The resulting report became the single most persuasive document in the file, because it let us argue from a specific, defensible number rather than a guess about how much heavier the new traffic really was.
  4. Sent a formal notice to Marco setting out the assessment's findings and proposing that repair costs be apportioned to reflect actual use rather than split evenly under the old agreement, while keeping the tone focused on a workable resolution rather than an opening threat, since an ongoing neighbour relationship still had to survive the dispute. The notice opened a direct channel to Marco's own representative within days, rather than leaving the dispute to drift through informal calls between property managers who had no authority to settle anything.
  5. Coordinated with Kaveh's logistics business on interim access, arranging a temporary route around the collapsed section so his trucks could keep operating during negotiations, which reduced the pressure on Mehrdad to settle quickly on unfavourable terms just to restore day-to-day access to the dock. Solving the immediate operational problem separately from the legal one meant the negotiation over cost-sharing and future use could proceed on its own timeline, without Kaveh's idle trucks forcing a rushed concession.
  6. Negotiated directly with Marco's representative over several weeks, working through cost apportionment and, separately, limits on future use, since the repair cost and the risk of repeat damage were really two different problems needing two different terms rather than one bundled compromise. Splitting the two issues let each side make concessions on the one that mattered less to them, which moved the talks forward faster than a single all-or-nothing proposal would have.
  7. Documented a new written agreement covering the repair cost split, a maintenance reserve funded going forward by both owners, and specific limits on heavy-vehicle traffic tied to turnover volume, replacing the ambiguity in the original decades-old document with clear terms both owners could point to later without needing to renegotiate from scratch. Putting the traffic limits and the funding mechanism in writing was what actually protected Mehrdad's investment, since a one-time repair payment alone would have left the same collapse likely to happen again.
  8. Walked Mehrdad through every draft before signing, translating the engineering and legal detail into plain terms over video calls, so decisions made an ocean away were still decisions he fully understood rather than ones he simply trusted us to make correctly. That step gave him genuine confidence to sign off remotely, knowing exactly what the repair split, the reserve, and the new traffic limits would mean for the property going forward.

The outcome

Marco agreed to fund the larger share of the driveway repair, reflecting the engineering assessment's finding that rental-related traffic caused most of the damage, while Mehrdad accepted a smaller share rather than pressing for full recovery, which would likely have meant a lawsuit fought almost entirely by video call and courier over repair, drainage, and lost-access costs that, once the loading dock disruption and the underlying structural work were added together, ran well into seven figures. Both sides also agreed to a going-forward maintenance reserve funded jointly, so future wear from ordinary use would not turn into another surprise bill for either of them.

On future use, Marco accepted specific caps on heavy-vehicle and turnover-related traffic across the shared apron, addressing Mehrdad's real underlying concern, that the damage would simply recur once the repair was finished and the same volume of moving trucks resumed. In exchange, Mehrdad gave up any claim to restrict the short-term rental use itself, which he had initially hoped to challenge outright as an improper change from what the old agreement contemplated. Neither side got everything it wanted out of the negotiation, but neither side was left facing an uncertain, costly fight over an old agreement that had never anticipated this kind of use in the first place, and both kept a working relationship with a neighbour they would still be sharing a driveway with for years.

The repair was completed within a few months of the settlement, and Kaveh's logistics business regained full access to its loading dock well before that, thanks to the interim route negotiated early in the process rather than left until the dispute resolved. Mehrdad, still managing the property from overseas, now has a written agreement that actually describes the traffic the driveway carries and sets out who pays for what when it wears down, something the original decades-old document never did and never could have anticipated when it was signed.

What you can learn from this

  • A shared-access agreement written for one kind of use does not automatically stretch to cover a very different one. Revisit it when a neighbouring property's use materially changes.
  • An independent engineering or factual assessment can turn a dispute over impressions into one over evidence, which usually shortens negotiations rather than lengthening them.
  • Managing a property from a distance does not have to mean managing it passively. A structured remote process can move a dispute forward as effectively as being on site.
  • Arranging interim access or a workaround early removes the pressure to accept a bad settlement just to restore day-to-day operations while a dispute is ongoing.
  • A partial settlement that trades a smaller repair share for firm future-use limits can resolve the real risk, ongoing damage, more durably than chasing full recovery on the past damage alone.
This case study is entirely fictional. It does not describe any real client, file, or matter handled by Treadstone Law, and it is not a real file with details changed. All names, people, properties, businesses, dollar amounts, dates, and events are invented, and any resemblance to a real person, business, or situation is coincidental. Fictional scenarios like this one illustrate the kinds of legal issues people in Ontario commonly face and how a lawyer can help. They are general information, not legal advice — no two matters unfold the same way, and nothing here predicts the outcome of any real case. Reading a case study does not create a lawyer-client relationship. If you are facing something similar, speak with a lawyer about your specific circumstances.

This is a litigation problem we handle

Start a file online — flat, published fees, reviewed by a licensed lawyer before a dollar is owed.

ContactStart a File →