# Maintenance work orders

> A repair from an owner's first report through triage, an insured vendor, the work itself, and the invoice — with a record at every stage.

Source: https://managestrata.ca/docs/property/maintenance

Maintenance is where a strata corporation is judged. Owners forgive a slow decision far more readily than a repair nobody ever answered for.

**Maintenance**.

## The stages

A work order moves through six stages, and the current one is visible to everyone who can see it — including the owner who reported it.

| Stage | Means |
| --- | --- |
| **Requested** | Reported, not yet looked at |
| **Triaged** | Assessed, priority set, deciding who does it |
| **Assigned** | A vendor or a strata volunteer has it |
| **In progress** | Work under way |
| **Completed** | The contractor is finished; council hasn't signed it off |
| **Closed** | Reviewed, invoiced, done |

**Cancelled** is a seventh state, but it isn't a stage on that path — it's an exit from it, and the job records which stage it stopped at. Cancelling asks you to confirm, because it's the one move that takes a job off the open list.

The council's page says where a job has got to in words — *"Stage 4 of 6"* — above the one button that moves it on. The owner's view of their own request draws the full trail instead: a marker per stage with the date under each one actually reached. It doesn't say who has the job — only that someone has been given it.

> **Completed and Closed are not the same thing**
>
> **Completed** is the contractor's word: they've left, the work is done as far as
> they're concerned. **Closed** is the council's: somebody looked, the invoice was
> recorded, and the corporation is content. Keeping them apart is what stops a job
> being signed off by the only person who was never going to inspect it.

### The work order list

**Maintenance** is one table of every work order — open and finished — with a filter strip above it, the same shape as Vendors and Meetings.

| Column | Shows |
| --- | --- |
| **Work order** | The title (which opens the job), an *Urgent* or *High* tag where it applies, and the first line of the description |
| **Stage** | Where it has got to |
| **Unit** | The lot it concerns, if any — *Not tied to a lot* when it's common property |
| **Vendor** | Who's doing it — a vendor from your directory, or a name marked *(volunteer)* |
| **Filed** | How long ago it came in |
| **Next step** | The one button that moves it on — or **Choose a vendor**, which opens the job, when it's ready to assign and nobody has it |

Narrow it with the filters:

- **Search** covers the title, the description, the lot (*lot 4*), the vendor and the stage.
- **Stage** — *Any stage*, *Open*, one of the open queues (**New requests**, **Ready to assign**, **Waiting to start**, **Work under way**, **Awaiting sign-off**), or *Closed or cancelled*.
- **Priority** — any one priority, or *Urgent or high*.
- **Filed** — *Last 30 days*, *Last 12 months*, *Last 3 years*, or a calendar year.

**Sort** sits beside the count. The default, **By stage**, keeps the order a council works in: open jobs by stage — new requests first — with urgent and high ones leading inside each stage, then finished jobs at the bottom. **Newest first**, **Oldest first** and **Title A–Z** are there too.

The filters are kept in the page address, so a narrowed list survives opening a job and pressing back. On a phone, the Unit, Vendor and Filed columns fold under the title.

With no work orders at all, the page says so and offers **Create your first work order**, which opens the same drawer as **Create work order** in the header.

> **The status is the communication**
>
> Most maintenance complaints are really complaints about silence. An owner who can
> see their request move from *requested* to *triaged* to *assigned* stops emailing
> the council, because the question they were asking has been answered.

## The job page reads as a sequence

A work order used to be five panels stacked down a page, and briefly three tabs. It is now the four things you do to a repair, in the order you do them, each one collapsible:

  1. **What was reported**

   The description, the photographs, the lot it concerns. The trade you call
   out and the priority you set are both chosen from this, so it is worth it
   being right.
  1. **Get prices**

   Ask vendors for a price, then accept one. Accepting gives them the job.
  1. **Do the work**

   Move the job along as it happens, and keep the conversation here rather than
   in somebody's inbox.
  1. **Tell the owners**

   Optional, and usually done once the work is arranged.

The step the job is actually at is open; the rest are collapsed behind a line that still says where they stand — *"3 quotes · none accepted"* — so nothing is hidden and nothing has to be hunted for. Which step is open is worked out from the job itself, not from where you last clicked, because a work order isn't filled in once by one person: it's picked up on Tuesday by whoever is free.

**Edit details** in the header corrects what the job *is* — title, description, priority, the component it belongs to, and **Who's doing it**. Moving it between stages stays on the progress card. A priority typed wrong when the request came in used to be permanent.

## The thread on each job

Every work order has a conversation attached, shared by the people in it: the council, the manager, the owner whose lot it concerns, and whoever reported it. "Which tap?" — "the ensuite one" — "the plumber comes Thursday" now lives on the job instead of in one council member's texts.

Each message says which seat its author spoke from — council, manager, owner — because most council members also own a lot, and "the council said" and "an owner said" are different sentences in a dispute.

> **Who can read a thread is narrower than who can read the job**
>
> The repair register itself is the building's business: any member can see that a
> lobby door is being fixed. The *thread* is scoped to the council, the manager,
> the lot's owner and the requester. A neighbour sees nothing of it — "the smell is
> coming from 103 again" is exactly what an owner shouldn't be able to read about
> somebody else's home.

> **Messages can't be edited or deleted — by anyone**
>
> This is correspondence the corporation is required to keep (BC Strata Property
> Regulation s.4.1), and a thread that can be rewritten afterwards isn't a record
> of what was said. "The council never told me about the deductible" is the
> argument it exists to settle. Write it as you'd want it read.

## What's new to you

The sidebar badges **Maintenance** with the number of jobs filed since **you** last looked — not since the corporation last looked. An owner files a leak at 2am; by morning one council member has read it and the other two haven't, and the badge tells each of the three the truth about their own reading.

Opening the page clears your own count and nobody else's.

## Who gets emailed

The badge tells you what's new once you're already looking at the dashboard, which is the one thing a volunteer council doesn't do daily. Three things now leave the building as email:

| When | Who hears about it |
| --- | --- |
| A request is filed | The council and manager — except whoever filed it |
| The stage changes | The owner side: the lot's owner and whoever reported it |
| A message is posted in the thread | Everyone else on that job's thread |

Nobody is emailed about their own click, which is what makes the council-filed case work: a job logged by one councillor is news to the other four.

The recipients are exactly the people who can already open the job's thread — council, manager, the holder of the lot, and whoever filed it — and no wider. A page can be re-secured; an email cannot be un-sent.

A status change is written in words, not in the product's vocabulary: an owner is told a contractor is lined up, not that the row is `in_progress`.

> **Owners can opt out; council members can't**
>
> An owner's email preference is honoured here as it is everywhere else — they're
> a private person receiving mail about their home. A council member is an
> office-holder being written to about the corporation's operations, so council
> mail goes out regardless. A councillor who also owns a lot and has opted out of
> owner mail still gets the council mail.

## How a work order starts

**An owner reports it.** From [their portal](https://managestrata.ca/docs/basics/owner-portal) — or straight from their overview, which now has a way in — describe the issue, answer **How urgent is it?**, **attach photographs**, and press **Send request**. It arrives as *requested*. The page tells them first that for a leak, a fire or anything unsafe they should phone the property manager or council, or 911, rather than file a form. They can open the job afterwards to read the stages — each one dated as it's reached — and answer questions in its thread. An owner whose account isn't linked to their lot yet is told to ask the council to link it.

Up to **six photographs** per request, as PNG, JPEG or WebP, 8 MB each. Each one uploads as soon as it's picked; if the owner presses **Send request** while a photo is still on its way up, it waits — with a note saying so — until the upload finishes, so a quick press can't file the request without the picture. A maintenance request was one line of text for a long time, and "leak under the kitchen sink" leaves the council guessing between a dripping trap and a ceiling coming down in the lot below — a guess that sets the priority, the trade called out, and how fast anybody moves. The picture that settles it is already on the owner's phone.

> **Photographs are narrower than the register**
>
> Any member can see that a lobby door is being fixed. The *pictures* follow the
> same rule as the [thread](#the-thread-on-each-job) — council, manager, the lot's
> owner and whoever filed it — because a photograph of the inside of somebody's
> home is not the building's business.

**Council raises it.** **Maintenance → Create work order** for anything found on inspection or arising from an [action item](https://managestrata.ca/docs/meetings/minutes-and-directives#action-items).

**From the component registry.** For planned reserve work, use the **wrench** on the component's row in **Assets & reserve study**. It files the job on your Maintenance page with the component already attached — which is what lets the job show whether the work is in your depreciation report (below). See [assets and reserve study](https://managestrata.ca/docs/property/assets-and-reserve-study#correcting-a-component).

> **Emergencies don't go in a form**
>
> Flood, fire, gas, no heat in winter — the emergency contact your corporation
> publishes, immediately. Raise the work order afterwards so there's a record of
> what happened and what it cost.

## Triage

The judgement step, and worth doing properly.

  1. **Is it the corporation's responsibility?**

   Common property is the corporation's; inside a lot is usually the owner's —
   but your bylaws govern, and the boundary is exactly where disputes live. When
   it's genuinely unclear, decide it at council and minute it.
  1. **How urgent?**

   Safety and active water damage come first, whatever else is queued.
  1. **Which fund?**

   Routine repair is operating. A major planned replacement is the
   [reserve](https://managestrata.ca/docs/compliance/reserve-fund). Decide before the invoice arrives, not
   after.
  1. **Who does it?**

   A vendor from your [directory](https://managestrata.ca/docs/property/vendors) — or, for a small job, an
   owner or council member doing it themselves ([below](#a-strata-volunteer)).
   The job's **Who could do it** list ranks the vendors in your directory by
   trade and current insurance, and **Find the best fit** has AI re-rank them
   against the job's description.

## Getting prices

[Video walkthrough: Quotes in ManageStrata: ask for a price, get it on the job, find it again](https://www.youtube.com/watch?v=RPmbRsFYrZ8)

For anything substantial, get more than one quote. Owners ask, and *"we got three quotes"* carries far more weight when you can produce them.

Quotes hang off **the work order**, not off the vendor and not in the document library, because the question they answer is which bid to take *for this job*. A quote records the vendor, the amount, the scope, the reference the vendor put on it, and the date the price holds until. Accepting one **also gives that vendor the job** — one press, both effects, which is the whole reason bids live here rather than in a folder.

### The list is not sorted cheapest-first

Deliberately. The list stays in the order the bids arrived; above it, the count and the spread are stated as a fact, and the lowest is marked. The low bid is routinely low for a reason — the flashing is excluded, or the insurance lapsed in March — and a council that takes the middle bid has to be able to say why it did.

Each bid also shows how much life the price has left, on the same scale as a vendor certificate: current, expiring within 30 days, expired, or no expiry stated.

> **What the spend would need to be approved**
>
> From the first bid onwards, the section states what a spend of that size would
> require: the s.98(2) ceiling, a 3/4 vote, or the majority a current depreciation
> report buys you. Better to learn that while you're reading prices than after
> you've committed. See [what approval does a spend
> need?](https://managestrata.ca/docs/finances/budgets#what-approval-does-a-spend-need)

### How it's paid

**How it's paid** on the job records which fund the work comes from, and two things only the council can say: whether it's **immediately necessary** to ensure safety or prevent significant loss or damage (no vote, s.98(3)), and whether it's **recommended in the most current depreciation report** (a majority rather than a 3/4 vote for reserve spending, s.96(b)). None of it is inferred.

For reserve work, the job shows what your records say about that second box:

| The job | What it says |
| --- | --- |
| Linked to a component from your **current** depreciation report, box ticked | Confirms the component is in that report — the basis the majority vote rests on |
| Linked to such a component, box not ticked | Points out the component is in the report, and that *if this job is the work the report recommends*, saying so lowers the vote |
| Box ticked, nothing linked behind it | Warns that nothing on file backs the claim: link the job to a component from the current report, or untick it |

A component from a superseded study doesn't count — the test is the *most current* report.

> **A listed component isn't the same as recommended work**
>
> The Act asks whether the report recommends *this work*. A leak repair on a roof
> the study lists is not the roof replacement the study recommends. That's why the
> box stays the council's to tick — the evidence is shown so you can decide, and
> so a majority vote isn't recorded on a basis the corporation can't show.

Every quote across every job is also listed in one place, on the Vendors page's **Quotes** tab — [see it →](https://managestrata.ca/docs/property/vendors#the-quotes-tab). Accepting still happens here, on the job.

### Let the vendor file their own bid

The step that doesn't happen at nine at night after a meeting is somebody keying a roofer's PDF into a form — and a bid nobody keys in is a bid the comparison doesn't have.

So you can generate a **quote link**, one per vendor per job, under **Ask a vendor to quote**, and send it to them. They open it, enter their figure, attach their PDF, and it lands as a quote on the right work order. No account, no password.

> **A quote link is a bearer token — treat it like one**
>
> Anyone holding the URL can use it, including anyone the email was forwarded to.
> What makes that acceptable is how little it can do: **add a bid to one job**. It
> cannot read the other quotes, the thread, the photographs, the ledger or any
> other job, and it cannot accept itself. The worst a leaked link achieves is an
> unwanted quote from a stranger, which you delete in a click.
>
> The URL is shown **once**, when you create it — it's stored only as a hash, so
> nobody can go back and look it up. It expires after **21 days**, accepts at most
> **five** submissions (a revised bid is ordinary — *"same job, we missed the
> flashing"*), and can be revoked at any time.
>
> A corporation can issue **5** quote links in any 24 hours on Free or a trial, and **30** on a paid plan. Past that, the link is refused with the number, and you can try again the next day — or write to support if you're tendering more jobs than that.

Quotes are **council and manager only**. The job's photographs and thread deliberately admit the lot's owner and whoever filed it; competing prices are procurement, and that's a different question.

## Assigning a vendor

> **Check the coverage first**
>
> Never assign a vendor whose insurance (COI) or WorkSafeBC coverage has
> lapsed. If they're injured or cause damage on your property while uncovered, the
> corporation is exposed. ManageStrata tracks both expiry dates on the
> [vendor record](https://managestrata.ca/docs/property/vendors) and warns you before they lapse — which is the
> main reason to keep the directory current.

Accepting a quote assigns its vendor. Where you're not taking bids, there are two ways in.

**Who could do it** is a **ranked list of vendors** from your [directory](https://managestrata.ca/docs/property/vendors) — a row each, showing the trade, the certificate status and anything the research found. It's sorted by trade, current insurance and what the research turned up; press **Find the best fit** and AI ranks them against this job's description instead, best fit first, with the date it was *Checked* underneath. **Check again** re-runs it after the description changes or a vendor is added. Each row has an outlined **Give them the job**, which assigns that vendor without a quote. It's outlined rather than filled on purpose: the list sits above the quotes, and giving a job unquoted is allowed but is the exception, not the next step. With no vendors in the directory, the list says *No vendors yet* and links to add one.

**Who's doing it**, on the progress card, is one dropdown with an **Assign** button. It lists your **Vendors**, your **Strata volunteers**, and **Someone not in this list** — for a vendor you booked outside the directory. That last one moves the job to *assigned* with nobody named, which is worth knowing before you press it; the dropdown then stays beside **Start work**, so you can name them later. If the directory is empty, the job says so and points you to add vendors.

Whichever way it's assigned, the job moves to *assigned* and the date goes on its trail. Like any stage change, it's emailed to the owner side — [who gets emailed](#who-gets-emailed).

### A strata volunteer

Plenty of small jobs — re-hanging a gate, swapping a light fitting — are done by an owner or a council member for nothing. Pick them under **Strata volunteers**, on the progress card or in **Edit details**. The list holds every current owner and council member, labelled *Council* or by their lot. Property managers aren't in it: managing the building is their paid job.

- The job page and the list show them as *Name (volunteer)*.
- **Get prices** reads *A strata volunteer is doing it — no quote needed*.
- A volunteer isn't a vendor, so they never appear in the directory, its insurance and WorkSafeBC checks, **Find the best fit**, quote links or vendor spend.
- A job has a vendor or a volunteer, never both. Assigning one — by **Assign**, **Give them the job**, accepting a quote, or **Edit details** — takes the other off.
- Owners following the request still aren't told who has it.

> **Accepting a stale or uninsured bid is a warning, not a block**
>
> Accept a quote from a vendor whose certificate isn't current, or a price that
> expired last month, and you're told so plainly and asked to confirm — not
> stopped. The warning names the certificate that's missing. No current
> **insurance** means the corporation is on the hook for what happens on site. No
> current **WorkSafeBC clearance** means the corporation can be held liable for the
> contractor's unpaid WorkSafeBC premiums — ask them for a clearance letter before
> the work starts. A contractor will very often still honour an expired price, and a
> council that has phoned to check shouldn't be blocked by a date field. What is
> refused outright is a *second* accepted quote on one job: the books can't be
> reconciled against two.

## While the work happens

Keep the record on the work order rather than in an inbox: quotes, scheduling, photographs before and after, complications, the decision to vary the scope. Say it in the job's thread and the owner sees it without anyone forwarding anything. The work order is what a future council will read when the same component fails again.

For anything that disrupts the building — water shut off, scaffolding, parkade closed — post an [announcement](https://managestrata.ca/docs/people/announcements). A work order can be announced to owners directly.

## Closing it out

  1. **Confirm the work is actually done**

   Ideally someone looks.
  1. **Record the expense**

   Against the right fund, linked to the work order.
   [Payments and expenses →](https://managestrata.ca/docs/finances/payments-and-expenses)
  1. **Link it to the component**

   If it was a reserve item — a roof, a boiler, a membrane — make sure the job
   is linked to its [component](https://managestrata.ca/docs/property/assets-and-reserve-study) (**Edit
   details**), and correct the component's remaining life in the registry.
   That's what keeps the next reserve projection honest.
  1. **File the warranty**

   In the [document library](https://managestrata.ca/docs/documents/library). A warranty nobody can find is
   a warranty nobody claims on.
  1. **Close it**

   The owner who reported it sees it close.

## Maintenance Triage

> **Council plan:** The Maintenance Triage agent is included on the Council plan and above.

It reviews incoming requests, proposes a priority, and suggests an insured vendor from your directory. Every suggestion is added, or turned down with **Not needed**, by a person, and anything added becomes a tracked action item in the [audit trail](https://managestrata.ca/docs/account/privacy-and-data). See [Suggestions](https://managestrata.ca/docs/ai/agents).

## Recurring work

Annual inspections and servicing are better handled as [tracked duties](https://managestrata.ca/docs/compliance/tracked-duties) on Compliance, which reminds you *before* they're due. Raise the work order when the duty comes round, so you keep both the reminder and the record of who did it and what it cost.

## Patterns worth noticing

Three separate leaks on the same stack is one problem, not three work orders. The history is there to be read: before approving a fourth repair to the same component, look at what the first three cost. That's usually the moment a repair becomes a [reserve project](https://managestrata.ca/docs/compliance/reserve-fund).
