Applied The Nick E. Playbook

Vendor & Make-Ready Orchestrator

Last reviewed

Intermediate

What you'll learn

~40 min
  • Ask an AI tool, in plan mode, for a small program that schedules the make-ready work (the work that readies an empty unit for its next resident) from what each unit's inspection found, your own steps and your vendor list
  • Read its plan for what the schedule must respect, and say in a sentence what it left out
  • Check the schedule against dates you can work out yourself, including a unit that waits for the painter and one that only a decision of your own can put back on time
  • Try a change to a vendor's limit and a change to one of your own answers, and tell which of the two still needs someone else's yes

The story, and what you will end up with

It is Saturday 5 December 2026 at The Concord. Seven residents handed back their keys this morning, and by early afternoon your maintenance team had inspected each unit and written down what it needs. Six of the seven have a new resident with a signed lease and a move-in date in the next two weeks; the seventh, 1104, is not leased yet. When the notices to vacate came in, someone from the office walked each unit with the resident’s things still in place, and you pencilled your vendors in for the week of Monday 7 December from that first look. Today’s inspection of the empty units is where the real lists come from, and this afternoon you lay the week out again from them.

The inspections did not find the same work in every unit. One needs only touch-up paint and a clean before its lock change and final walk; others need a full repaint, new carpet or repairs. Your make-ready board is a whiteboard and a spreadsheet, and the vendors are booked by phone and text. What you cannot see from the board is where the week breaks: which unit needs the painter on a day the painter already has as many units as they take, and which unit cannot be ready unless you change how you schedule it.

By the end of this lesson you will have a small program on your own computer, the scheduling program, that reads your units, your make-ready steps and your vendor list, and lays out a day-by-day schedule for every unit, with the days each one has to spare before its move-in and a flag on each one that cannot be ready in time. It sends nothing to anyone, and it does not read what you pencilled: it gives you the schedule the inspection lists now call for. You put that beside your pencilled bookings and call the vendors about the differences. You build it by asking your AI tool in plain English, and you check it against dates you can work out yourself.

🔍Words used in this lessonclick to expand
  • Needs: the steps a unit’s move-out inspection found it needs, as your team wrote them down.
  • Steps: your make-ready work in your order, with the days you plan for each. In a unit, each step starts once the one before it is finished.
  • Limit: the most units a vendor takes on in one day, as the vendor has told you.
  • Days to spare: the days between a unit’s last step and its move-in day, counting neither. A unit whose last step falls on or after its move-in day is late.

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/04-make-ready && cd ~/property-ops/04-make-ready

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/04/make-ready.zip and unpack it 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), three files are in the data folder (units.csv, steps.csv and vendors.csv; a .csv file is a plain spreadsheet that Excel opens), and a first snapshot, your checkpoint, is saved. Later you can ask whether the files have changed since then. If it does not mention one of them, ask: “Did you save a checkpoint with the files in it?” If it says it kept the zip file somewhere outside this folder, ask it to delete that copy. If the download does not work, download make-ready.zip in your browser, check where it went (the browser’s list of downloads shows the folder), and tell your AI tool, for example: “make-ready.zip is in my Downloads folder. Unpack 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.

Every unit, vendor, person, phone number and rent in the files is made up for this course. No real resident’s or vendor’s details are in them, and none should go into this folder.

The box below says what is in the practice files; later steps refer to them.

ℹWhat is in make-ready.zipclick to expand

units.csv: the seven units, one per row. All seven residents handed back their keys on Saturday 5 December 2026, and each unit was inspected that day. Every move-in date is in a signed lease. Dates are in December 2026.

UnitBedroomsMonthly rentNew resident moves inNeeds, as the inspection found them
03021$2,150Sun 13repairs, carpet replacement, cleaning, lock change, final walk
04102$2,875Sun 13full paint, cleaning, lock change, final walk
05071$2,200Sat 12full paint, cleaning, lock change, final walk
06082$2,950Sun 13full paint, carpet replacement, cleaning, lock change, final walk
12031$2,400Thu 10repairs, cleaning, lock change, final walk
0706studio$1,890Sat 19touch-up paint, cleaning, lock change, final walk
11042$3,100(not leased yet)repairs, carpet replacement, cleaning, lock change, final walk

Each row also has the inspection’s notes, such as “Leaking sink trap and a broken closet door” for 1203. Three of the move-ins fall on Sunday 13: the trades are off on Sunday, and someone from the office still hands over the keys.

steps.csv: your make-ready steps, in your order, with the days you plan for each: repairs (1 day), full paint (2 days), touch-up paint (1 day), carpet replacement (1 day), cleaning (1 day), lock change (1 day) and final walk (1 day). A unit gets only the steps on its own list, one at a time in this order. These are your planning numbers for practice; yours come from your own building.

vendors.csv: who does each kind of work, with a contact, a phone number, a limit and days off.

WhoDoesLimit (units in one day)Days off
Example Painting Co.full paint, touch-up paint2Sunday
Example Carpet Co.carpet replacement2Saturday, Sunday
Example Cleaning Co.cleaning4Sunday
In-house maintenance teamrepairs, lock change, final walk6Sunday

Two things matter later. 1203 moves in on Thursday 10, five days after its keys came back. And on Monday 7 three units need the painter first thing (0410, 0507 and 0608), and the painter takes two units in one day.

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 files, 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 files to use, and what you want from them:

I manage an apartment building. Help me build a small tool that schedules the make-ready work for the units turning over in my data folder, using my steps and vendors files. Ask me what you need first.

Your AI tool usually reads the files and comes back with questions. It may also point out something it noticed, such as 1203’s short time before its move-in, or three units needing the painter on Monday 7.

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
Can work start on move-out day, or the next working day?The next working day. The inspection was done on move-out day.
Must each step finish before the next starts, or can short tasks share a day?No sharing. One step at a time in a unit, in my steps file’s order.
Does a bigger unit take longer, or are the days in the steps file fixed?Each unit gets the steps its inspection lists, for the days in my steps file.
Does a two-day paint use one of the painter’s slots on both days?Yes, on both days. It can pause over a day off.
Must a unit be finished by the day before move-in?Yes, finished by the end of the day before move-in.
Who goes first when a vendor is full?The earliest move-in first, then the unit with the fewest days to spare.
1104 is not leased. Schedule it, or leave it out?Schedule it last, and don’t make up a move-in date.
When a unit cannot be ready, should it only flag it or also suggest fixes?Flag it with the reason, and show every unit’s days to spare. I’ll call the incoming resident myself.

If it asks several questions at once, answer any about how something is counted or who decides from your owner’s agreement or your own judgment, and accept its suggestions only about how the page looks. If it asks something not listed here, answer it the same way, in a sentence.

These are one manager’s answers for one week, and yours change the schedule: a team that starts on the Saturday the keys come back starts a working day sooner. Two of them say who waits when a vendor is full, and that is your call each week. Earliest move-in first protects the signed move-in dates, and this lesson’s dates further down follow it. Putting 1104 last protects them too, but every day it waits may be a day it is not ready to show to anyone looking for a home, and at $3,100 a month that is $100 a day of potential rent in December. You may move it ahead of a unit with days to spare.

Read the plan

Next it usually shows you a plan: what it will build and how it will check it. It may also show the dates it expects. Read it for five things:

  1. Every unit gets a schedule, all seven, and no date is made up: 1104 has no move-in date, and the schedule leaves it blank.
  2. Each unit gets only the steps its inspection lists, one at a time, in the order of your steps file, for the days that file gives.
  3. No vendor gets more units on one day than its limit, and nobody is booked on a day off.
  4. Each unit shows its days to spare, and every unit that cannot be ready before its move-in day is flagged, with the reason. No step is dropped or shortened to make a unit fit.
  5. Every vendor date is marked as proposed, nothing is sent to anyone, and your data files are read and left as they are.

A first plan often leaves one of these out, most often item 5. Say so in a sentence, in your own words, for example:

Mark every vendor date as proposed until I've confirmed it with the vendor. Don't send anything to anyone, and leave my data files as they are.

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.

Look at what it built

Ask it to run what it built:

Run it and show me the schedule and anything it flags.

Your schedule will be laid out in its own way, and your AI tool usually shows a summary of it in its answer as well as saving the spreadsheet. Check it for these (all dates December 2026):

  • All seven units have a schedule: 0302, 0410, 0507, 0608, 1203, 0706 and 1104. Work starts on Monday 7, and nobody is booked on a Sunday or the carpet company on a Saturday.
  • Each unit has only the steps on its own list, one at a time. For 0302: repairs Monday 7, carpet Tuesday 8, cleaning Wednesday 9, lock change Thursday 10, final walk Friday 11. 0706 has touch-up paint on Wednesday 9 and no full paint or carpet.
  • The painter never has more than two units on one day. On Monday 7, 0507 goes first because it moves in first (Saturday 12). 0608 and 0410 both move in on Sunday 13; with the painter free, 0608 would have no day to spare and 0410 one, so 0608 goes next. 0410’s paint waits until Wednesday 9 and Thursday 10, its lock change is Saturday 12 and its final walk Monday 14, the day after its move-in. 0410 is flagged late.
  • 1203 is flagged late. Its list is four steps of one day each, four days of work, and only three working days come between its keys on Saturday 5 and its Thursday 10 move-in: Monday 7, Tuesday 8 and Wednesday 9. Its final walk falls on Thursday 10, its move-in day. That comes from two of your answers: work starts the next working day, and one step at a time in a unit. No vendor’s yes fixes 1203; a decision of yours does, and a later section tries one.
  • Two units have no days to spare: 0507 finishes on Friday 11 for its Saturday 12 move-in, and 0608 on Saturday 12 for its Sunday 13 move-in. 0302 has one (Saturday 12) and 0706, finishing Saturday 12 for a Saturday 19 move-in, has six.
  • 1104 finishes on Friday 11, and no move-in date is made up for it.
  • Every vendor date is marked as proposed, and nothing has been sent.
  • When you ask “Has my data changed since the checkpoint?”, it compares the files with the checkpoint and says no.

If something on the list is not true, tell your AI tool in a sentence what you see and what you expected, for example: “0410 is booked with the painter on Monday 7, but the painter already has two units that day. Keep to the limit.” If you answered “who goes first” another way, 0608 may be the unit that waits for the painter instead; one of 0410 and 0608 still misses its move-in.

When a unit will not be ready

1203 and 0410 are flagged. Both incoming residents hold signed leases with a move-in date, so the question for them is not which date to give them but whether the unit will be ready on the date they already have, and the schedule says it will not. Your first call is the one that could still fix it: for 0410 the painter, since one more painter slot on Monday 7 and Tuesday 8 puts it back on time (the next section shows this), and for 1203 a decision of your own (tried further down). If a unit still cannot be ready by the end of that day, its incoming resident hears it from you that day, before anything else on the list. What you can offer them is often worked out with the property’s owner, so the call says what you know and when you will call back. The scheduling program only flags; it calls nobody and promises nothing.

Notice what the schedule cannot know

0410 is late because the painter takes two units in one day. That number came from your vendors file. Try this:

Make a copy of the vendors file in this folder. In the copy only, change the painter's limit from 2 units to 3. Then run the schedule with the copy and tell me what changed.

Look at what happens to 0410. Before you read on: did anyone ask the painter?

0410 is now on time: paint on Monday 7 and Tuesday 8, cleaning Wednesday 9, lock change Thursday 10, final walk Friday 11, with Saturday 12 to spare. Nothing else moves; 1203 is still late, because no vendor’s limit changes it. The schedule now looks better for the week, and nothing about the painter has changed. The only thing that changed is a number you typed. Your scheduling program takes the number in the file as true, because it has nothing else to go on. It cannot know whether the painter can send a second crew on Monday, or is already promised to another property.

Your AI tool may point this out itself and suggest asking the painter whether they can take a third unit those days; it may also report the better schedule without a word of doubt. Either way, the schedule that came out of the copy rests on a number nobody confirmed. If you told 0410’s incoming resident that all is well because the schedule says so, their move-in would depend on a phone call nobody has made.

Scheduled is not available: a date on the schedule is a proposal until whoever does the work confirms it.

So the step after the schedule is yours: call or text each vendor with the days it proposes, and note each yes wherever your office keeps vendor bookings, such as your make-ready board or your property management software. When you have looked at the copy’s schedule, remove the copy: “Delete the copy and anything made from it; I’m done with it.”

Change one of your own answers

1203 needs a leaking sink trap and a broken closet door fixed, then a clean, a lock change and a final walk, and your own team does three of those four. You answered one step at a time in a unit; for this unit you might let the lock change and the final walk share a day. Say so:

In 1203 only, let the lock change and the final walk happen on the same day. Run the schedule again and tell me what changed.

1203’s lock change and final walk now both fall on Wednesday 9, so it is ready before its Thursday 10 move-in, with no days to spare. Nothing else moves, and 0410 is still late. No vendor had to agree to this; the change was yours, and your own team does both steps that day. Starting 1203’s repairs on Saturday 5, the day its keys came back, would also have it ready on Wednesday 9 without the shared day. Either way it has no day to spare, so any slip makes it late again.

One real run

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

With the painter's limit raised to 3, unit 0410 is on time, ready Fri,
Dec 11 with 1 day to spare. Unit 1203 is still late and nothing else
moved.
With a third slot, 0410 paints alongside 0507 and 0608 on Dec 7-8
instead of waiting two days.

The building, the apartments and the dates in this answer are made up for this course.

It reports the better schedule without asking whether the painter can take a third unit. That question is yours, and if your AI tool has not raised it, say so: “The painter hasn’t agreed to three units, so treat this schedule as a what-if.”

How real properties differ

  • Your steps, their order and the days you plan for each are yours to set from your own past turns, and each unit’s list comes from its own inspection. One unit may need a step to take longer than your steps file says. The steps file is used for every unit, so do not change it for one unit; ask your AI tool to let that unit’s own row carry its different days.
  • A vendor’s limit and days off change from week to week. Ask for them when you book, and update the vendors file before you run the schedule, not after.
  • Whatever a vendor has agreed with your company in writing is not in these files, so the schedule knows none of it.
  • Your own make-ready checklist holds things this short practice list leaves out. Testing the smoke and carbon monoxide alarms at the final walk is one nobody skips; others are checking the appliances and, before you offer a vendor a date, their current insurance certificate on file and how they get in (keys, lockbox).
  • Your property management software may already have a make-ready board. The schedule can help you plan the week; the board, or whatever your company keeps, stays the record.

Keep going

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

  1. “Let me mark a vendor’s day as confirmed, and keep confirmed days fixed when you run the schedule again.” The schedule then shows which dates are still only proposals.
  2. “Make a calendar file for each vendor with their proposed days, so I can attach it when I ask them.”
  3. “Show what each empty day costs for each unit, using its monthly rent divided by the days in that month.” For 0410, $2,875 over December’s 31 days is $92.74 a day. Some offices divide by 30 instead ($95.83); use whichever your company reports.
  4. “Save a checkpoint.” Your AI tool saves a snapshot you can return to.
  5. “Let me give you a list of the dates I already booked with each vendor, and show it beside the schedule.” Your list of pencilled bookings then sits next to what the inspections call for.

When you want to schedule your real units, use the finished scheduling program. It runs on your real files by itself, with your AI tool closed, so your AI tool never sees them. Do these steps in order; the first two happen now, while this folder still holds only practice files:

  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. Units, rents and vendor contacts are your management company’s to decide on. Go on only if it allows this use.

  2. Choose a folder of its own, outside this course folder, for your real units, steps and vendors files. While this folder still holds only the practice files, ask your AI tool for the exact line, naming that folder with its full path, for example: “Give me the exact one line to run this myself on the three files in /home/dana/make-ready-real, saving the schedule there too.” Use your own folder’s full path. If it offers to copy your real files 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/04-make-ready/make_ready.py --data /home/dana/make-ready-real

    Read it left to right: python3 starts Python, which runs the program; /home/dana/property-ops/04-make-ready/make_ready.py is the program itself, in this lesson’s folder; --data says that the folder after it, /home/dana/make-ready-real, holds your three files, and this program saves the schedule in an output folder inside that folder. /home/dana is the home folder of someone whose computer name is dana; yours shows your own name. If your line has a part you cannot explain, ask your AI tool about it, or for a simpler line, before you leave.

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

  5. Paste the line from your note at the $ or % prompt and press Enter. The schedule appears in your real folder, beside your real files, not in the course folder. 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. On Monday morning the carpet company phones: they will do 0608’s carpet on Wednesday 9, as your schedule proposes, and they say yes on the call. On Tuesday you run the schedule again. What does it show for 0608’s carpet, what do you do about that, and can you now tell 0608’s incoming resident the unit will be ready on Sunday 13?

A good answer sees three things. The schedule still shows Wednesday 9 as proposed, because the yes was said on the phone and nothing in your files records it. You note the yes where your office keeps vendor bookings (and mark it confirmed, if you added the first “Keep going” change). And one yes is not enough for 0608: the painter, the cleaner and your own team have their days on it too, and 0608 has no days to spare, so you hold off until each of them has said yes.

Key takeaways

  • Ask briefly; its questions fill in the rest.
  • Work a few dates out by hand and hold the schedule to them.
  • A late unit is fixed by a vendor’s yes or by a decision of yours. Make the call that could fix it first.
  • A number in a file is not a phone call. The schedule believes your files.
  • Real units go to the finished program, with your AI tool closed, after the data check.
KNOWLEDGE CHECK

Your schedule shows 0302 with repairs Monday 7, carpet Tuesday 8, cleaning Wednesday 9, lock change Thursday 10 and the final walk Friday 11, with Saturday 12 to spare before its Sunday 13 move-in. The carpet company calls: they can come Wednesday 9 instead of Tuesday 8, and they confirm Wednesday. What happens to 0302?

What’s next

In the next lesson you build the Occupancy & Revenue Pulse Reporter: it reads two weekly rent rolls and makes the one-page report for the owner: occupancy, leased apartments, what changed and what is owed, each figure with what it counts.

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