[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Track ResMan make-ready units with AI

> See which vacant ResMan units are still Not Ready, which make-ready work order is open and how close each is to its available date.

Source: https://cotlet.dev/integrations/resman-api-mcp-server/track-make-ready-units

A resident moves out on the 30th, the next one moves in on the 5th, and in between a unit has to get from Not Ready to Ready. The manager needs to know every morning which units are on track.

Cotlet does it in your own ResMan account with list\_units, list\_work\_orders and get\_work\_order, called by your AI agent, an n8n workflow or a script.

[Sign up free](https://cotlet.dev/app/signup?app=resman) [All ResMan tools](https://cotlet.dev/integrations/resman-api-mcp-server.md)

Hosted · nothing to install or maintain

## Can ResMan do this on its own?

ResMan's Make Ready Board shows which units need to be made ready, and the Partner API documents the unit status, vacancy status and a make-ready flag on work orders (checked 23 Oct 2026). ResMan's pages do not describe a check that compares a unit's available date with the state of its open work, and the API is only for approved Integration Partners, so an agent working for a property manager cannot use it.

## How you do it in ResMan today

1. ResMan has a Digital Make-Ready Board where staff see which units need to be made ready, to turn units faster.
2. Each unit carries a status in ResMan, and the make-ready work for it is a work order that ResMan flags as make-ready.
3. To judge a unit, the manager opens its work order, checks its status and assignee, and compares it with the date the unit is available to rent.
4. A preleased unit has a move-in date attached, so it matters most, and the manager has to remember which units those are.
5. The check repeats every day for every vacant unit, and a unit with no open work order at all is easy to overlook.

## How to track ResMan make-ready units with AI

Prompt

```
List the units at Lemon Tree that are Not Ready and vacant. For each, check its make-ready work order and tell me which units are still open and when they are available to rent.
```

1. 01  
### List the units that are not ready  
list\_units runs with status Not Ready for the property. Each row carries the vacancy status and the date available, so the agent already knows which units are preleased and when the next resident is due.
2. 02  
### Keep only the vacant ones  
Units with vacancy status Occupied or Notice to Vacate are dropped, because those still have a resident. The agent keeps Vacant and Vacant Preleased, and lists Notice to Vacate Preleased units on a separate line, because nobody has moved out of them yet.
3. 03  
### Find the make-ready work order  
list\_work\_orders runs with the location set to the unit number, one call per unit, and the agent keeps the work orders that ResMan flags as make-ready. More than one open make-ready order on a unit is reported as one line each.
4. 04  
### Read the open ones  
get\_work\_order gives the status, the assignee, the scheduled and due dates and the notes of each open order. A unit with no make-ready order, or one that is On Hold or has no assignee, is listed first.
5. 05  
### Rank by the date available  
The agent sorts the report by dateAvailable, so a preleased unit due in three days is above one with no move-in. It changes nothing in ResMan: setting a unit to Ready stays your decision.

### What you get back

Example data

```
Not Ready and vacant at Lemon Tree: 2
On track 1: 1A (available Oct 28, In Progress, Robert Wilcox)
At risk 1:
- 2C is Vacant Preleased, available Nov 2, no assigned technician
```

### Other ways to ask

- Every Friday, list units that will be vacant next week and have no make-ready work order yet.
- Show only preleased units that are Not Ready and tell me the move-in date for each.
- List all make-ready work orders that are On Hold and say why, from their notes.

## What ResMan allows, and what to know first

- ResMan unit status takes the values Not Ready, Ready, Down, Admin and Model.
- ResMan vacancy status takes the values Occupied, Vacant, Notice to Vacate, Preleased, Vacant Preleased and Notice to Vacate Preleased.
- A work order carries a flag that tells whether it is a make-ready order assigned to turn a vacant unit.
- ResMan keeps for each unit the lease that occupies it now and the lease set to occupy it next, so a preleased unit has a known move-in.
- The date available is the first date a unit can be rented, and a property can choose which units it lists in its online availability.

Every tool here only reads, so it can run daily from n8n, Make, Zapier or cron without waiting for your OK.

Sources: [ResMan Maintenance](https://www.myresman.com/solutions/maintenance/) · [ResMan Partners API Documentation](https://partners-api-docs.myresman.com/)

## Call list\_units from a script

curl

```
curl "https://cotlet.dev/api/v1/resman/properties/f308c33b-5865-4f7e-97af-46d35f19eddf/units?status=Not+Ready" \
  -H "Authorization: Bearer $COTLET_API_KEY"
```

Example response

```
{
"units": [
{
"unit_id": "fad50f9c-c20e-4d61-a8d0-4f54420d2cd0",
"number": "1A",
"unit_type": "A1",
"status": "Not Ready",
"status_date": "2026-10-14",
"vacancy_status": "Vacant",
"date_available": "2026-10-28",
"market_rent": 1325
},
{
"unit_id": "03047f59-50bc-41d1-8e48-669df3d8287e",
"number": "2C",
"unit_type": "B2",
"status": "Not Ready",
"status_date": "2026-10-19",
"vacancy_status": "Vacant Preleased",
"date_available": "2026-11-02",
"market_rent": 1410
}
]
}
```

MCP: add https://cotlet.dev/mcp/v1 with the same key; the call is resman\_read → list\_units. Example data.

[Schedule it in n8n, Make, Zapier or cron](https://cotlet.dev/integrations/resman-api-mcp-server.md#automations)

## ResMan tools this automation uses

__Cotlet ResMan tools used to track ResMan make-ready units with AI__
| Tool | Parameters |
| ------------------ | ----------------------------------------------------------------------------------- |
| list\_units | property\_id, status, vacancy\_status |
| list\_work\_orders | property\_id, status, priority, location, assigned\_to\_person\_id, modified\_since |
| get\_work\_order | property\_id, number |

[All 13 ResMan tools with descriptions](https://cotlet.dev/integrations/resman-api-mcp-server.md#tools)

## Frequently asked questions

### Is it safe to connect ResMan to Cotlet?

Yes. You sign in to ResMan yourself, in your own Cloud Browser in the EU, and we never save your password. Your agents only get ResMan once you enable it, every background request is listed, and the browser profile is stored encrypted with AES-256-GCM, the cipher 1Password uses for its vaults. The AI model never sees a login, posts and messages wait for your OK, and Disable for agents cuts access in one click. Independent scanners grade cotlet.dev A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory; live results are on https://cotlet.dev/security.

## More ResMan automations

- [Triage new ResMan work orders with AI](https://cotlet.dev/integrations/resman-api-mcp-server/triage-new-work-orders.md)
- [Summarize ResMan aged receivables with AI](https://cotlet.dev/integrations/resman-api-mcp-server/aged-receivables-summary.md)
- [ResMan API and MCP server: every tool](https://cotlet.dev/integrations/resman-api-mcp-server.md)
- [All use cases](https://cotlet.dev/use-cases.md)

## Give your agent access to ResMan.

Free 7-day trial with 2,000 credits, no card needed. Cotlet is independent and not affiliated with ResMan.

[Sign up free](https://cotlet.dev/app/signup?app=resman)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.