Where Rentvine Keeps Your Inspection Dates (and Where It Doesn't)

Dana manages 312 doors across 220 properties in Austin. On a Tuesday in April she sits down to answer one question before she plans the month: which of these doors has not been inspected in over a year?

She knows the answer exists. Every inspection her team has completed came back into Rentvine and landed as a PDF on the property, so she opens the first property, clicks the Files tab, reads the date off the top of the report, and types it into a spreadsheet. Then the second, then the third. Somewhere around the fifth she does the arithmetic on the remaining 215 Files tabs and closes the browser.

Nothing is missing. Every date she wants is in Rentvine, in a shape she cannot sort.

The short answer

Rentvine stores completed inspection reports, as files, on each property. It does not store a last-inspection date you can drop into a report column and sort, which is why "what's overdue?" has no button to press. The fix is one custom field on the unit, updated as the last step of closing out every inspection. The setup is below, and it is worth doing whether or not you ever add another tool.

What Rentvine has

Rentvine does more here than it usually gets credit for. Out of the box you get:

• An Inspections section, plus inspection notifications.
• An internal-technician calendar with drag-and-drop scheduling.
• An "Open in Map" link on property and unit pages.
• Report exports in CSV, Excel, JSON and PDF, and scheduled reports that email themselves.
• Two-way integrations with zInspector and RentCheck, whose completed reports land back in Rentvine as files on the property.

If your question is "did this unit get inspected, and what did the report say," Rentvine answers it well. The report comes back, attaches to the right property, and is still there a year later when an owner asks.

What is missing

The gap is narrow. Three things are genuinely absent. The first is a last-inspection date as a queryable field: that date lives only in a user-defined custom field, if your org creates one. The second is a portfolio-level map, since "Open in Map" opens one property at a time and Dana has 220 of them. The third is a geographic route builder.

All three come from the same place. Rentvine hands your inspection history back as documents, and a PDF in a Files tab is ideal for reading and useless for sorting. The moment your question turns into "which ones are overdue" or "which of the overdue ones are near each other," every fact you need is sitting in a format that cannot answer a question about the whole portfolio at once.

Closing the gap with what you already pay for

This is fixable inside Rentvine plus free Google My Maps.

1. Add a "Last Inspection" custom field on units in Rentvine. Units rather than properties, because you want the date at the door level: a duplex can have one side inspected in January and the other still sitting from two years ago. The name you pick matters later, since this is the same field VestaGlass reads, and you tell VestaGlass which field it is by name in settings. So this step is not throwaway work if you ever connect anything to it.

2. Update the field after every inspection, in MM/DD/YYYY, as the last step of closing the inspection out. Make it the action that marks the inspection finished, the way the report upload already is, rather than a separate weekly cleanup task or something anyone does "when there's time." The field is only as good as the discipline behind it, and a half-maintained date column is worse than none because you will trust it.

3. Build a saved unit report that includes the field, and schedule it to email you weekly. The answer that used to live in 220 Files tabs now arrives in your inbox as one list. Report builders differ by org and by report, so if yours will not carry the unit custom field as a column, export the unit list and keep the dates in one sheet alongside it. That sheet is a fallback, and the field in Rentvine stays the system of record.

4. Sort that list by Last Inspection, oldest first. Everything past your interval is at the top. That is your overdue list, and getting it is a two-click sort instead of an afternoon.

5. Plot the overdue addresses in Google My Maps and pick 8 to 12 properties that genuinely sit near each other. That cluster is one day of inspections. Sequence them across the area in one pass rather than by ZIP code, and note that consumer Google Maps caps a single set of directions at 10 points including your start, so a full day often has to be split into two. The full method, including the export columns and how to sequence a cluster, is in how to plan an inspection day across a rental portfolio.

That is a complete overdue-and-routed workflow built on Rentvine's own export and a free map, with no new software.

The part that repeats

Steps 1 and 2 are permanent. Once the field exists and your team maintains it, Rentvine is better than it was, and it stays better.

Steps 3 through 5 are the ones you do again. Next month needs a new export, a new sort and a new My Maps layer, because the one you built in April describes April: doors got inspected, leases turned over, two properties came on. Inspection planning becomes a standing hour of exporting, sorting and plotting that has to happen before anyone drives anywhere.

Where VestaGlass fits

VestaGlass reads the same Last Inspection custom field you just created, by the name you give it in settings. It syncs your properties and units from Rentvine nightly and on demand, and puts every door on a portfolio map, current as of the last sync. Each door is colored by inspection status (overdue, due, due soon, scheduled, ok) and you can filter both the map and the list by status, so pulling the overdue set is one filter instead of a sort of an export. Occupied units come due 12 months after the last inspection; vacant units run on an interval your org sets.

You build the route by clicking doors on the map and ordering the stops yourself. VestaGlass shows the drive time for every leg of that order, with time-of-day traffic, and recomputes it each time you move a stop, so you can reorder until it's tight. A route can hold more than 10 stops, and each stop carries its own link into Google or Apple Maps for turn-by-turn, so Google's 10-point ceiling never enters into it.

Mark the stops done, and on completion VestaGlass can write the new date back into that same Rentvine custom field, if your org turns that setting on. That closes the loop at the far end: the field you created in step 1 gets maintained in both directions, by your team's manual updates and by the routes they finish.

Planning an inspection day that took about an hour of exporting, sorting and plotting takes a few minutes on the map. That is what we see on the product, not an industry statistic. Two limits are worth knowing before you decide: a property with no coordinates in Rentvine cannot be mapped, and the map is current as of the last sync rather than the last second.

Put the Last Inspection field on a map

See how VestaGlass turns your Rentvine property data into a usable inspection map.