Draft
Lockbox codes and tenant windows across 20 properties
Access notes scattered across old texts and one manager's head cause lockout trips. Here is a per-property sheet that lets any tech get in cold.
It is 8:10 and your tech is standing on a porch two towns over, on the phone with you, because the lockbox code you texted him three weeks ago is wrong. The property manager changed it after the last turnover and told you in a message that is now buried under forty others. Your tech cannot get in. The tenant is at work. You are on a ladder at your own job, scrolling your thread with one hand, trying to remember which of your twenty accounts this even is.
Every handyman who services rental properties has lived some version of that morning. The access information exists. Somebody knew the code, the alarm sequence, the fact that unit 3 has a dog that bolts. It just lives in scattered texts and one person’s head, and the one person is never the one standing at the door. When you ran five properties, that head was enough. At twenty, it is the quiet reason a third of your lockout trips happen, and every one of them costs you a roll you cannot bill.
Where the access notes actually live right now
Walk your own memory for a second. Where is the gate code for the townhomes on Fifth? The alarm panel sequence for the vacant on Oak? The fact that the tenant in 12B only lets you in after 2pm because she works nights?
For most owners the answer is: some of it is in your phone, some of it is in a text from the PM, some of it is written on the back of a work order in your truck, and a good chunk of it is nowhere but your own head. That is not a filing problem you can fix by trying harder. It is the same wall the group text hits on a growing crew: a single stream of messages cannot hold twenty properties’ worth of standing facts without losing them, and standing facts are exactly what access notes are.
The cost shows up as three specific failures, and they repeat:
The stale code. The PM rotated the lockbox after a move-out and the new code is in a text you skimmed. Your tech uses the old one, cannot get in, and calls you. Now two people are stopped instead of none.
The missing warning. Nobody told the new tech that 3 has a dog, or that the alarm at Oak trips in sixty seconds if you do not disarm it. He finds out the hard way, and you get a call from the tenant or the monitoring company.
The wrong window. Your tech rolls up at 9am to a unit where the tenant said mornings do not work. No-access trip, rescheduled, and the tenant now thinks your company does not listen.
The number on one lockout trip
Put a plain dollar figure on the stale-code morning, because it is not small.
One tech, drive out and drive back, plus the time on the phone with you and the PM sorting out the real code: call it a wasted hour and a half, easy, once you count the windshield time. On a loaded labor rate that is real money before you have turned a screw. Then the job slips to the afternoon or the next day, which pushes everything behind it, and if the PM is paying you by the ticket you have now spent an hour and a half you cannot invoice. Do that twice a week across twenty properties and you are eating most of a day every week on doors you could not open.
The part that stings is the same part that stings with a missed schedule text: the information existed. Someone knew the code. It just had no home where the tech at the door could reach it without a phone call.
The per-property access sheet worth stealing
Here is the fix, and it is boring on purpose. Every property you service gets one short sheet, kept in the same place, that any tech can read cold and get in without calling the office. Steal this layout outright:
- Address and unit. The full address plus which unit or building, spelled the way the PM spells it, so there is no wrong-address guess.
- Lockbox location and code. Not just the code. Where the box physically is (right of the front door, on the gas meter, hanging on the side gate), because a tech who cannot find the box is just as stuck as one with a bad code.
- Alarm sequence. Panel location, disarm code, and how many seconds he has. If there is no alarm, say so, so nobody hunts for one.
- Pet and hazard warnings. Dog that bolts, cat that must stay in, aggressive dog next door, the step on the back porch that is rotted. The things that turn into a claim or a bite.
- Tenant availability window. Occupied or vacant, and if occupied, the hours the tenant actually allows access. “After 2pm weekdays” saves a whole trip.
- Parking and entry notes. Where to park so you do not get towed, which door actually opens, gate code for the complex versus the unit box.
- Who to call when the code fails. The one name and number, PM or owner, who can give the current code or buzz you in. Not the general office line, the person who actually answers.
That last line is the release valve. A tech who hits a stale code and has the right person to call fixes it in two minutes instead of losing the morning.
Why the sheet has to live on the job, not in a binder
Plenty of shops build a version of this sheet and then lose to it anyway, because they park it in a shared spreadsheet or a binder in the office. The tech at the door does not have the binder. He has his phone, and on his phone the access notes are back in the same scattered texts you started with.
The sheet only works if it lives where the work lives: attached to that property, on the phone, visible to whoever is assigned that day. When the PM changes a code, you update it in one place and every tech who opens that property sees the new one. No re-texting twenty people. No stale copy in someone’s saved messages. This is the same reason gate codes and property notes belong where the crew sees them rather than in your head: standing facts have to travel with the job or they do not travel at all.
It also protects you when a tech leaves. If the routes and the codes were in his phone, they walk out the door with him, and you are rebuilding twenty properties’ worth of access from scratch. When the notes belong to the company and sit on the property, a departing tech takes nothing with him but his tools.
Where Crewmigo fits
This is the part Crewmigo was built for. Each property is a thread that remembers, so the access sheet lives right at the top of it: lockbox location and code, alarm sequence, warnings, tenant window, and the one person to call when the code fails. Whoever you assign that day opens the thread and has everything the door needs, without a call to you. When the PM rotates a code, you change it once and the thread carries the new one to the next tech. The record belongs to your company, not to whichever phone happened to hold it, so a tech leaving does not take your twenty front doors with him. We are new, so put one hard property on it, the one that generates the most “what is the code again” texts, and see if the calls stop.
Crewmigo runs every job in a thread your crew already knows how to use, with the photo that proves it and a sign-off that closes it. One plan, one price a head. Subs ride free.
Start a job