Applied The Nick E. Playbook

Morning Maintenance Triage Board

Last reviewed

Beginner

What you'll learn

~40 min
  • Ask an AI tool, in plan mode, for a small program that puts the open work orders, the maintenance requests your office has logged, in a suggested order for your day crew
  • Read its plan for what the board must do: every open request on it with a reason for its place and what was already done, ages counted from the right morning, nothing sent, your file left alone
  • Check the board against the work orders file: the count, what was done overnight, how long each request has been open, and what the file leaves blank
  • Find a request the board files as routine that needs a person at once, and see why a rule for its words would not catch the next one

The story, and what you will end up with

It is Friday 13 November 2026, 6:45 a.m., at The Concord. Since the office closed at 6 p.m. on Thursday, 14 new work orders have been logged. Five of them are about three emergencies, and those were dealt with when they came in, through the after-hours phone line and the overnight concierge. At 11:50 p.m. the east bank elevator stopped between floors with nobody in it; it was shut down and the elevator company called, and its technician is due at 9:00. At 2:40 a.m. the fire alarm panel by the garage door on L3, the garage’s third level, showed a trouble light; the alarm company was called, and its technician is due at 8:00. At 5:52 a.m. 1207 phoned about water coming through the bathroom ceiling; Luis, the tech on call, was there by 6:20, traced the leak to 1307 on the floor above and shut the water off there, and checked 1107 below. 1208 and 1206 reported the same leak through the resident portal, and Luis checked those too. You have read the after-hours log and talked to Luis before he goes home, and the work-order system records what was done and when.

The other nine came in through the portal: a dishwasher that smells (logged at 6:40 p.m. on Thursday), a backed-up kitchen sink and a garbage disposal in 0602, a bedroom window in 0905 that will not lock, two noise complaints, a squeaky closet door, a bathtub to re-caulk, and one from Ms. Chen in 1302: “no hot water!!! STILL!!! since wednesday”. Older requests and four units being readied for new residents are still open too. Your two day techs, Marco and Daniela, arrive at 7:30 for the standup, the short morning meeting where they hear the day’s order.

The night’s emergencies are already handled: an emergency is acted on when it comes in, under your company’s after-hours procedure, and residents are usually told to phone the after-hours line for one, not to use the portal. The board you build here sorts what remains for the day’s crew. Deciding what counts as an emergency stays yours, and the board gives you one more look for a request that reads as routine and is not.

Most mornings you scroll the list, sort it in your head and write the order on a whiteboard. By the end of this lesson you will have a small program on your own computer, the triage board, that reads an export of your work orders (a copy of the list, saved from your work-order software as a spreadsheet file) and makes a one-page sheet: the open requests in a suggested order, each with a one-line reason, ready to print for the standup. You build it by asking your AI tool in plain English, and you check it by reading what it makes.

🔍Words used in this lessonclick to expand
  • Work order: a maintenance request as your office logs it, with a number, the unit, what is wrong and its status (open, in progress, completed or cancelled).
  • PMS: property management system, the software your office logs work orders in, and where calls, visits and what residents were told are recorded.
  • After-hours line: the phone number residents call when the office is closed; whoever answers it sends the on-call tech or calls an outside company.
  • Make-ready: the work that gets an empty unit ready for its next resident (paint, clean, check appliances) before the move-in date.
  • Ticket age: how long a work order has been open, counted from when it was logged.

Before you start

First, if your AI tool is still open, leave it: type /exit and press Enter (if you use Antigravity, press Ctrl+D with nothing typed instead), and wait until you see the $ or % prompt. The next line goes there, in the terminal, not in the AI tool. It makes a new folder for this lesson inside property-ops, next to the earlier lessons’ folders, and goes into it:

Terminal window
mkdir -p ~/property-ops/02-maintenance-triage && cd ~/property-ops/02-maintenance-triage

Start your AI tool with the start line you kept from the setup lesson, the one with approval prompts off. Then ask it to set the folder up:

Set this folder up so we can undo any change you make, download https://learn.intellimetrics.net/starters/property-mgmt/02/work-orders.csv into a data folder, and save a checkpoint.

Look for it saying three things: the folder is set up with Git (the program that saves snapshots, from setup), the work orders are saved as data/work-orders.csv, and a first snapshot, your checkpoint, is saved. Later you can ask whether the file has changed since then. If it does not mention one of them, ask: “Did you save a checkpoint with the file in it?” If the download does not work, download work-orders.csv in your browser, check where it went (the browser’s list of downloads shows the folder), and tell your AI tool, for example: “work-orders.csv is in my Downloads folder. Copy that one file into a data folder here, and save a checkpoint.” In Windows PowerShell or a desktop app, “my Downloads folder” works as is; only say “my Windows Downloads folder” if you use Ubuntu (WSL) on Windows, which keeps its own Downloads folder apart from Windows.

The building, and every resident, unit and work order in the file, are made up for this course. No real resident’s details are in it, and none should go into this folder.

The box below says what is in the practice file; later steps refer to it.

ℹWhat is in work-orders.csvclick to expand

A spreadsheet file (it opens in Excel) with 25 work orders, one per row, numbered WO-4478 to WO-4512 with gaps. 22 are open or in progress; three are closed and belong on no board: WO-4480 and WO-4491 (completed) and WO-4495 (cancelled).

The open ones:

Work orderUnitLoggedWhat the request says
WO-4478050128 OctKitchen faucet leaking slowly (in progress; note: “Called again 11/9, not fixed”)
WO-448303092 NovReplace HVAC filter
WO-448605094 NovBathroom exhaust fan light out, needs a bulb
WO-448902045 NovPaint touch-up by the front door
WO-449304066 NovMake-ready (note: “Move-in 11/20”)
WO-44961305(blank)Make-ready, no move-in date
WO-4497070310 NovMake-ready (note: “Move-in 11/24”)
WO-4498110111 NovMake-ready (note: “Move-in 11/30”)
WO-4499040512 Nov, 6:40 p.m.Dishwasher smells bad
WO-4500060212 Nov, 7:30 p.m.Kitchen sink backed up, water won’t drain and it smells
WO-4501120713 Nov, 5:52 a.m.Water coming through the bathroom ceiling and dripping into the tub. Getting worse. (in progress; done: on-call tech Luis on site 6:20, leak traced to 1307 and water shut off there, 1107 below checked, ceiling repair still to do)
WO-4502060212 Nov, 7:35 p.m.Garbage disposal hums but doesn’t turn
WO-4503L3 garage13 Nov, 2:40 a.m.Fire alarm panel by the L3 garage door showing a trouble light and beeping (in progress; done: alarm company called 2:55, technician due 8:00 a.m.)
WO-4504120813 Nov, 6:05 a.m.Water on the bathroom floor along the wall we share with 1207 (in progress; done: Luis checked 6:30, same leak as WO-4501)
WO-4505090512 Nov, 8:10 p.m.Bedroom window lock is broken, window won’t lock
WO-4506080313 Nov, 12:40 a.m.Loud music from the unit above after midnight again (noise)
WO-4507130212 Nov, 9:15 p.m.no hot water!!! STILL!!! since wednesday (in progress; note: “Valve part on backorder; maybe Friday afternoon, not confirmed”)
WO-4508100512 Nov, 11:05 p.m.Dog barking in the unit next door for hours (noise)
WO-4509120613 Nov, 6:20 a.m.Ceiling over the bathroom sink is wet and the light above the mirror is flickering (in progress; done: Luis checked 6:35, same leak, light switched off at the breaker, electrician needed)
WO-4510070112 Nov, 9:40 p.m.Closet door squeaks
WO-4511130913 Nov, 6:30 a.m.Please re-caulk around the bathtub
WO-4512(blank)12 Nov, 11:50 p.m.East bank elevator stopped between floors 7 and 8 for a few minutes, doors opened after (in progress; done: elevator company called 11:55 p.m., car was empty, shut down until checked, technician due 9:00 a.m.; note: “Second time this week”)

The last 14 rows, from WO-4499 on, came in after the office closed. Each row also has the floor, the resident’s name, a category, priority_pms (the priority someone chose in the PMS when the request was logged), who it is assigned to if anyone, source (how it came in: the portal, the office, the after-hours line or the concierge) and action_taken, what was done before this morning and when; it is blank where nothing has been done yet. The older rows give a date with no time, written three ways (10/28/2026, 2026-11-02, 11/4/26), as exports from different screens sometimes do. Two cells that matter later are blank: WO-4496 has no logged date, and WO-4512 has no unit, because it is the elevator.

Each lesson’s practice files are their own made-up week and do not continue from one lesson to the next, so an apartment can be occupied in one lesson’s files and empty in another’s.

Switch to plan mode

Your AI tool is already open. Switch to plan mode now: Shift+Tab until it says plan, or /plan (the keys for each tool). In plan mode it usually reads your file, asks its questions and shows you a plan before it builds anything; the order can vary.

The conversation

Each message below is an example. Say it your own way.

Say what you want

Say what you do, which file to use, and what you want from it:

I manage an apartment building. Help me build a small tool that puts the open work orders in data/work-orders.csv in the order my maintenance techs should take them this morning, Friday 13 November. Ask me what you need first.

Your AI tool usually reads the file and comes back with questions. It may also point out things it noticed, such as the three 12th-floor requests being one leak, the two requests from 0602, or the missing date for 1305.

Answer its questions

Answer each in a sentence. These are questions the tools often ask, with one way to answer each. Yours may ask them in a different order or show a list of choices:

If it asksYou might say
Who is working this morning? One list, or one per tech?Marco and Daniela are on; Luis went home. One ordered list; I’ll split it at the standup.
Include in-progress orders, and leave out completed and cancelled ones?Yes.
What time should ages be counted from?6:45 a.m. Friday 13 November, for this file.
The alarm and elevator are with outside companies. On the techs’ list, or apart?They were called overnight. Show them apart, with when each technician is due.
Anything newer than what the file records?Nothing newer than the file.
Noise complaints: on the techs’ list, or apart?Apart, for the office.
Here is an order I suggest. Use it, or the PMS priority?Start from the PMS priority, and show where your order would differ and why.
Any building rules or response times to follow?None in this file. Show how long each has been open, from 6:45 a.m.
The 1206 light needs an electrician. Can your techs do it, or an outside company?An outside company.
Group the three 12th-floor requests, and the two from 0602?Group them, but keep each work order on the board.
When is 1305’s move-in? It has no dates.Unknown; show it as missing.
A page, a spreadsheet, or a sheet to print?A one-page sheet to print, with a one-line reason for each place.

This practice file has no response times. Your company, your leases and local law may set them, so the board shows how long each request has been open and promises nothing.

If it asks several questions at once, answer the ones about the work and the residents in a sentence, and for the rest say that its suggestions are fine. If it asks something not listed here, answer it the same way, in a sentence.

Read the plan

Next it usually shows you a plan: what it will build and how it will check it. Read it for five things:

  1. Every open request is on the board, 22 of them, counting any list set apart, and the three closed ones are not. A request with something missing, such as 1305’s logged date, stays on with a note; nothing is guessed.
  2. Each request has a reason for its place, in plain words, from rules that read what a request says, so the same board works on another morning’s export. What was already done for it shows beside it.
  3. Ages are counted from 6:45 a.m. Friday 13 November, the morning of this file, not from the day you run it.
  4. The board sends nothing. It assigns no one for you, contacts no resident or company, changes nothing in your PMS, and nothing goes online.
  5. Your work orders file is read and left as it is.

A first plan often leaves one of these out, most often what was done overnight or your file. Say so in a sentence, in your own words, for example:

Leave my work orders file as it is, and show what was already done overnight beside each one, so the techs don't repeat it.

When the plan has all five, approve it: if your AI tool offers a choice to go ahead, pick it; otherwise say “Yes, go ahead and build it.” In Codex, press Shift+Tab first to leave plan mode. In Copilot, saying it brings up a choice to go ahead; pick that. Let it build. It may run what it built and tell you how to run it yourself; either way, the next step asks it to. When it has finished, ask it: “Did you install anything, and where?” Nothing, or something inside this lesson’s folder, is fine for these lessons. If it names anywhere else on your computer, ask it what that is for, and to remove it if you do not want it there. It may say it made a temporary file elsewhere to check that the sheet fits on one page; ask it to remove that too.

Look at what it built

Ask it to run what it built:

Run it and show me the board, with how long each one has been open.

Your board will be worded and laid out in its own way. It changes nothing in your PMS: calls made, when someone was sent and what residents were told are logged there, the way last night’s were. Check the board for these:

  • 22 requests are on it in all, counting any list set apart. WO-4480, WO-4491 and WO-4495 are not among them; it may list them separately as left off.
  • What was done overnight shows beside those requests: the elevator (WO-4512) with its technician due at 9:00, the L3 fire alarm panel (WO-4503) with its technician due at 8:00, and Luis’s visits on the three 12th-floor requests, 1207, 1208 and 1206. The two noise complaints, 0803 and 1005, are apart for the office.
  • Every request has a short reason for its place.
  • WO-4478, the 0501 faucet, shows 16 days open: 28 October to Friday 13 November, counted in calendar days, because the file gives a date for it and no time. Its note, “Called again 11/9, not fixed”, is shown.
  • The make-readies show their move-in dates: 0406 20 November, 0703 24 November, 1101 30 November. For 1305 (WO-4496) the sheet says the logged date and the move-in date are missing, rather than showing a guessed date or a zero.
  • When you ask “Has my work orders file changed since the checkpoint?”, it compares the file with the checkpoint and says no.
  • Look yourself, in the notes on the board, for a unit that is named there and has no work order of its own. The board will not point it out. If your board doesn’t show those notes, ask: “Show what was done overnight beside each request.”

If something on the list is not true, tell your AI tool in a sentence what you see and what you expected, for example: “1305 shows 0 days open, but my file has no date for it. Show it as missing.”

Then read the order against what you know. Where the 0905 window that will not lock, the 0602 sink or the 0501 faucet whose resident has called again should sit is for your own priorities to settle; if you disagree with a place, tell your AI tool why in a sentence. A reason may also carry advice about what to do on site; check that with your maintenance lead before the techs act on it.

The two requests set apart for outside companies still give you calls to make this morning. Ask the alarm company whether the fire alarm system is impaired, and what they and the fire department require until it is repaired. For the east bank elevator, tell residents the car is out, starting with those who rely on it, and because the note says this is the second time this week, report the repeat failure to the elevator company and the building’s owner today.

Then ask what the board cannot show: a request nobody logged. The board lists only the rows in the file. Read the note on WO-4501 again: the leak was traced to 1307 and the water shut off there, and there is no work order for 1307. This morning you open one for 1307 in your PMS and get a plumber there today, because someone there has no water.

The 1302 request shows nine and a half hours open, because it was logged at 9:15 p.m. on Thursday. Yet it already carries “Valve part on backorder”, and Ms. Chen writes that her hot water has been out since Wednesday, so look in your PMS for an earlier ticket or other record of it. If you find one, tie the two together: ticket age is how long a work order has existed, not how long a resident has been without something, and the earlier record shows how long she has really waited. If there is none, write down the outage history she reported. A home without hot water may carry a deadline under the lease, your company’s rules or local law; check today which of them apply. Her fix date is still not confirmed, so whatever her place on the board, someone calls her today, without promising a time nobody has given you.

To print the sheet, ask: “Open the sheet in my browser so I can print it.” If it says the address is already in use, say: “Something else is using that address. Don’t stop it. Use a different address for my page.” If your AI tool does not take a message after opening the page, wait a minute. If it still does not, close the terminal window, open a new one, type the line at the top of this page that begins with mkdir again, start your tool, and say: “Start the page again so it keeps running while we talk.” The page and your saved work are files in the folder, so nothing is lost.

Notice what the order cannot tell you

The board has put this morning’s requests in order. Before the techs see it, try this:

Copy the work orders file in this folder. In the copy only, add a portal request from 0504: 'Kitchen smells like rotten eggs near the stove since last night. Not urgent, whenever.' Run the board on the copy, same rules.

If the board will not run on the copy, or says its rules know only this file’s requests, say: “Make the rules work from what each request says, so the board runs on any morning’s export, not just this file.” Then ask for the copy’s board again.

Look at where 0504 lands. Before you read on: would you leave this one for the techs’ list?

You would not. If this came in for real, the office reaches 0504 at once, the way your company’s gas procedure says. Kansas’s utility regulator, writing for people in Kansas, says that “Many people describe the smell of natural gas as similar to that of rotten eggs”, and: “If you smell gas, stop what you are doing and leave the area immediately.” “Don’t use any electrical device that would ignite the natural gas. That includes light switches, telephones/cell phones, or garage door openers.” “Once you are in a safe location, call your utility company or 911.” “Do not re-enter until a gas company employee says it is ok.” (Kansas Corporation Commission, Natural Gas Safety). So the resident is told to leave and to call from outside, and nobody is sent in to look first.

Now the board. Yours may well have put 0504 among the routine repairs, near the dishwasher that smells: its rules sort by the words on their lists, and the resident wrote “smells” and “Not urgent”, not “gas”. Your AI tool may say at once that this sounds like gas and offer to add a rule for it, or it may already have written one after seeing this request. A rule for “rotten eggs” would catch this request, not the next one written as “weird smell by the oven”. If it changed the rules without being asked, say: “Undo any change you made that I didn’t ask for.” A rule for a known danger word is a reasonable thing to add on purpose, as long as nobody takes it for a substitute for reading every request.

The board’s order is a suggestion, not a dispatched order: you read every request and decide what is an emergency.

When you have looked, remove the copy: “Delete that copy and its board; I’m done with them.”

One real run

Here is part of what one AI tool said after the experiment above, with Claude Code on 11 November 2026. Yours will word it differently; check your board against the list above, not against this.

The rules put the 0504 request last, at #19 of 19, which is wrong.
A rotten-egg smell near a stove is the classic sign of a gas leak.
It belongs at the very top, whatever the resident wrote about it
not being urgent.
The Safety tier looks for "gas", "smoke" and "burning smell", but
not the way residents actually describe gas. Nothing in "rotten eggs
near the stove" matched, so it dropped to "Small job" with the Low
priority I gave it.

The building, the residents and the requests in this answer are made up for this course.

“The very top” is about the board. A request like this one does not wait for the board at all: the office reaches the resident as soon as it is read, the way your company’s gas procedure says, and the resident leaves and calls from outside. The 19 is the techs’ list: the copy’s 23 open requests less the 4 set apart (the alarm panel, the elevator and the two noise complaints). “The Low priority I gave it” means the AI tool filled in a blank the message left. Here that only pushed the request lower; on a real list, a filled-in priority is one more thing to check.

How real properties differ

Some things only your company holds:

  • Your company’s emergency procedure, after-hours line, any response times and its list of outside companies are its own, and none of them are in this file. The board knows only what you tell it.
  • The gas safety words quoted above are the Kansas Corporation Commission’s, written for Kansas. Your own gas utility and your company likely have their own instructions for residents and staff; use theirs.
  • Your PMS export may name its columns differently or write dates another way, and it may have no column for what was done overnight. Tell your AI tool which column is which, in a sentence.

Keep going

Small changes do not need plan mode. Say each in a sentence, then run it again:

  1. “Keep our outside companies and their phone numbers in a small file I can edit, and show them beside each call.”
  2. “Keep a line for each morning with how many requests are open and the oldest, so I can see whether the list is growing.”
  3. “Show how many days each make-ready has until move-in.”
  4. “Save a checkpoint.” Your AI tool saves a snapshot you can return to.

When you want a board for your real work orders, use the finished triage board. It runs on your real export by itself, with your AI tool closed, so your AI tool never sees it. Do these steps in order; the first three happen now, while your AI tool is open and this folder still holds only practice data:

  1. Go through the data check, the questions in setup about what the data is, who decides how it is used, and which AI tool would see it. Residents’ names, units and requests are your management company’s to decide on. Go on only if it allows this use.

  2. Ask your AI tool for a folder of its own for your real exports, outside this course folder, and for the line to run the board there, for example: “Make an empty folder called real-exports in my home folder. Then write out the exact line, full path included, to run the board myself on work-orders.csv in it, with the sheet saved there too.” If it offers to copy your real export into this folder instead, say no.

  3. Copy the line it gives you into a note. It will look something like this one, though yours may differ:

    Terminal window
    python3 /home/dana/property-ops/02-maintenance-triage/triage.py /home/dana/real-exports/work-orders.csv --as-of "2026-11-13 06:45" --on-shift Marco,Daniela --out /home/dana/real-exports/board.html

    Read it left to right. python3 starts Python, which runs the program. Next comes the program you built, in this lesson’s folder, then your export in real-exports. --as-of is the date and time ages are counted from; the line may carry 6:45 a.m. on 13 November 2026 because that is the morning you gave it for the practice file, so change it to the morning you run it, or ask your AI tool to make the program use the current time when you leave that part out. --on-shift names who is working, and --out is where the sheet is saved. /home/dana is the home folder of someone whose computer name is dana; yours shows your own name. Your line may differ in any of these parts. If you are unsure about any part, ask your AI tool now, while it is still open.

  4. Leave your AI tool the way you did at the start of this lesson.

  5. Save your PMS export into the real-exports folder, named as the line names it. Paste the line from your note at the $ or % prompt and press Enter. The sheet appears beside your export, not in the course folder. Open it and read it before you print it. To come back to the lesson folder later, type the line at the top of this page that begins with mkdir.

Try another case

Before the quiz, write two or three sentences for yourself. At 6:10 a.m. a portal request comes in from 0306: “Smoke alarm went off twice overnight, no smoke. Probably the battery. Can someone check today?” Your board ranks it among the routine repairs. What would you do with it, and what would you tell your AI tool about the board?

A good answer sees three things. “Probably the battery” is the resident’s guess, and from the request alone you do not know what kind of alarm it is or why it sounded. How soon someone goes is set by your company’s procedure for smoke alarms, not by the board’s order. And a new rule for smoke alarms would catch this request’s words, not the next resident’s.

Key takeaways

  • Ask briefly, and let your AI tool ask back.
  • Read the plan for the work, not the code.
  • A blank stays a blank, never a guess or a zero.
  • The board sorts by the words written. You read every request and decide what is an emergency.
  • The board shows only what was logged: an unlogged unit or an earlier ticket is yours to find.
  • Real work orders wait for the data check, and go to the finished board with your AI tool closed.
KNOWLEDGE CHECK

Your triage board ranks a 5:30 a.m. request from 0906 as a routine repair: 'Hissing sound behind the stove, and I've had a headache since I got up. Probably nothing.' It is 6:50 a.m. and the standup is at 7:30. What do you do?

What’s next

In the next lesson you build the Renewal Risk and Outreach Planner, a call list of the residents whose leases end soon, worked in lease-end windows from your lease, payment and repair records, with a note inviting each to talk about renewing.

intellimetrics · Arlington, VA
© 2026 intellimetrics.net
Search lessons