From a request a business posted
Renewals and rate increases caught early
Account managers scan renewal spreadsheets line by line, hunting for rate increases before the insured opens the renewal notice.
Property management
A property manager keeps track of every inspection cycle a building owes the city, from facade and gas piping to boilers and elevators. The dates sit across DOB, HPD and Local Law filings, so one building can mean three lookups before anyone knows what is due.
Who does what
What you get
Draft for review
The rules it follows
These are your company's own rules, written down and confirmed with your team during the build. It works on its own only within limits you set.
What it learns when your team adjusts its work
The busywork it takes off the property coordinator. It takes over the lookups, the re-entering of dates and the follow-up with vendors that the property coordinator does building by building today. That time goes back to the work only they can do.
What it starts out knowing
It works from these sources, shows which one an answer came from, and asks when the answer is not there.
Who reviews its work, and when review can stop
At first the property coordinator reviews every work order and follow-up before it goes out. Review stops for a routine inspection type only once the agent's record on that type is good and the business agrees.
Violations, extensions, costs above an owner's limit and anything unclear in a city record keep going to the property coordinator.
It no longer needs review once its record on them is good and you agree, one type of task at a time. New, unusual and high-stakes work stays with a person.
When your team adjusts its work
When the property coordinator changes the facade work order for one building to open 180 days ahead instead of 90, because engineers in that area book up early, the change is saved as a rule for that building. Next cycle the agent opens that building's facade work order at 180 days, and the team decides which changes it keeps.
It learns how your company does this job. It does not watch, rate or profile your employees. Your team decides what it learns. You can read everything it has learned and remove anything. Whoever runs it, your team or our engineers, makes sure on a regular cycle that what it learned stays inside the bounds you agreed.
From a request a business posted
The owner came close to letting a Local Law inspection cycle pass without noticing. Working out what the building owed meant looking through DOB, HPD and Local Law records, and each source showed only part of it. The owner asked how other managers keep these deadlines, since most seem to rely on spreadsheets, calendar reminders, vendor alerts or waiting for a notice.
Paraphrased from a public post, not quoted, and not a client engagement.
From first principles
Before we build anything, we take the work down to what has to be true. What is left over is habit. Habit gets deleted, not automated.
What has to be true
What is only habit
Re-entering dates from city websites into a spreadsheet and a calendar is only habit. So is waiting for a vendor alert or a notice in the mail to start the job.
What we delete before building anything
We delete the separate spreadsheet and the personal calendar reminders, so the inspection dates live in one place tied to each building. We also drop the routine lookups that repeat records the city already publishes.
What is left
The agent. The agent reads the city records for each building, keeps its compliance calendar current and opens the work order with the preferred vendor at the lead time the company sets. It then follows up on scheduling, filing and proof of completion.
A person. The property coordinator reviews each new work order, confirms the cycle date and decides anything involving a violation, an extension or a cost the owner must approve.
The kind of work: Follow-ups and deadlines. This is the work of noticing that a date is coming or something has changed, then getting the right person to act before it is too late. EZLynx, AppFolio and the city's DOB and HPD records already hold the dates, but people still read them line by line, re-enter them into spreadsheets and decide by hand who needs a follow-up.
What the engagement needs
The engagement needs the building list with addresses and block and lot numbers, read access to the public DOB and HPD records, and access to create work orders in AppFolio, Buildium or the system the company uses. It also needs the company's vendor list, owner approval limits and the lead times it wants for each inspection.
We check the time this job takes, access to your systems and how you would review the result. If a ready-made tool is enough, we say so.
Senior engineers agree the rules with the property coordinator, test on past cases and set approval limits and a way to switch it off.
Work with the agent in Slack, Teams or text messages. We fix problems and adjust it as unusual cases come up.
You own the agent and keep its source, tests and guide either way. Your team runs it, or our engineers run it with a monthly report. Learning continues on your own servers, in your own cloud account or in our data center.
When we'd point you elsewhere
The fit test checks this first. If one of these covers your case, we tell you, and you keep the map of the work.
Honest limits
City records can lag behind filings or change after a notice, so the property coordinator checks each due date the agent uses before work starts.
This situation is drawn from a public request a building owner posted, paraphrased, not a client engagement.
More use cases
From a request a business posted
Account managers scan renewal spreadsheets line by line, hunting for rate increases before the insured opens the renewal notice.
From a request a business posted
Someone opens every cleaner checklist and photo set after each checkout, then sets the unit ready by hand.