Sending lease renewals to a hundred tenants without losing track of any of them

This page may contain affiliate links from which Blur Studio earns commissions.

Sending a hundred lease renewals one at a time is not just slow, it's where mistakes hide. A property manager handling each renewal individually, often while also handling everything else that day, is exactly the setup where a rent figure gets copied from the wrong unit or a renewal gets sent to last year's email address. A batch process, done properly, is both faster and more accurate, because the repetitive, error-prone part gets handled by a template and a data source instead of memory.

Spreadsheet to signed leases

Start with a clean spreadsheet, one row per tenant, with columns for exactly what differs between renewals: tenant name, unit number, current rent, new rent, lease start and end dates, and email address. Pull this from your property management software's export if it has one, rather than rebuilding it by hand, since manual rebuilding is where the first errors usually creep in.

1. Build one renewal template. The lease terms that stay the same across every tenant, standard clauses, your renewal policy language, written once. The fields that change per tenant, rent, dates, unit, left as clearly marked merge fields rather than retyped for each person. Saved templates also work for addenda, as in reusing a lease addendum for every new tenant.
2. Merge the spreadsheet into the template. Most e-signature tools, including QuickSigner, an electronic signature platform for uploading a document and collecting a legally binding signature from any device, support sending a template to a list of signers with their individual data filled in automatically, often called a bulk send or mass distribution feature. Confirm the specific mechanics and any per-document limits on your current plan before relying on it for a hundred at once, since free or lower tiers often cap document volume. If you are still choosing a tool, see the best e-signature for property managers.
3. Review before sending, not after. Spot-check a meaningful sample, not just the first one or two, before the batch goes out. A merge error caught before sending is a five-minute fix. The same error caught after a tenant has already signed the wrong rent figure is a genuine legal mess.
4. Send in a batch, not all at the exact same moment if your tool caps simultaneous sends. Some platforms throttle large sends; confirm this with your specific tool rather than assuming a hundred documents all generate and deliver instantly.
5. Track responses against the original spreadsheet. Mark each row signed, pending, or declined as responses come in, so you always know your actual renewal rate without having to open a hundred individual documents to check.

Reminders that actually get responses

At this scale, a meaningful share of tenants will not sign on the first send, not out of refusal, just ordinary inattention to an email among dozens of others. Build a reminder cadence into the process rather than treating the first send as the only send: a reminder at the halfway point of your renewal window, and a more direct, personal follow-up, a call or text rather than another automated email, for anyone still unsigned a week before the deadline. The automated reminder most e-signature tools send on an unsigned document covers the inattentive majority; it's the stragglers close to the deadline who need a human touch rather than another email that will likely get the same non-response as the first one. Keep a visible count of outstanding signatures as the deadline approaches, so the follow-up calls are prioritized by whoever is genuinely running out of time, not handled in whatever order they happen to come to mind. Common reasons are in why tenants stall on online lease signing.

Notice period rules: check before you send, not after

Many states and cities require landlords to give tenants a minimum amount of advance notice before a lease renews at a higher rent or before a tenancy ends, and in some rent-controlled jurisdictions, how much rent can increase at all is itself capped by local law. These rules vary significantly by state and city, and some change from year to year, so confirm the specific notice period and any rent-increase limit that applies to your jurisdiction before building your renewal timeline, rather than assuming a generic 30 or 60 day window covers you everywhere you operate. If your tenant base spans multiple cities or states, this is one place where a single undifferentiated batch genuinely cannot work, since the legally required lead time for a renewal notice in one jurisdiction may be meaningfully different from another, and sending a batch built around the wrong state's rule risks a renewal that is not actually enforceable as written. When you are not certain which rule applies to a given unit, confirm with a local attorney or your state's tenant-landlord statute directly rather than guessing. Rent changes follow a similar bulk process, as in getting every tenant to sign a rent increase notice.

A worked example

A property manager overseeing 100 units across two states exports a spreadsheet of every lease expiring in the next 90 days: 62 units in one state, 38 in another, each state carrying a different required notice period. Rather than one batch, this becomes two: each built on its own template reflecting that state's specific notice and rent-increase rules, merged against its own filtered list of tenants. Both batches go out on the same day, each tenant receiving a renewal with their correct unit, correct new rent, and the legally required notice window for their specific state already built into the send date rather than calculated after the fact. A reminder goes out automatically at the halfway point of each window. Two weeks before each deadline, anyone still unsigned gets a phone call rather than a third email. By the deadline, roughly 90 signed renewals come back without a single individual email having been typed by hand, and the remaining ten get handled as deliberate one-off conversations, not because the batch process failed, but because that is exactly the number of cases that genuinely need a person rather than a template.

Errors to avoid

• Merging the wrong row to the wrong tenant. The single most damaging possible mistake at this scale, sending tenant A a renewal with tenant B's rent or unit number. Always spot-check a sample against the source spreadsheet before sending, and double-check any row that was recently edited.
• Sending to an outdated email address. Confirm the tenant contact list against your most recent correspondence, not an old master list that may not reflect a tenant who changed their email a year ago.
• Treating every tenant identically when policies actually differ. A rent increase cap, a different renewal term length, or a unit-specific condition may mean not every tenant should get the exact same template terms. Segment the spreadsheet by whatever actually differs rather than forcing every renewal through one undifferentiated batch.
• No record of who declined or went silent. A tenant who does not sign by the deadline needs a defined next step, a move-out notice process, a short extension, a follow-up call, decided in advance rather than improvised tenant by tenant once the deadline has already passed.

How I'd approach this

The real leverage in a batch this size is not the e-signature tool itself, it's whether your underlying tenant data, rent figures, dates, contact information, is clean and current before you merge it into anything. A perfect signing workflow built on top of a messy or outdated spreadsheet just sends mistakes faster and to more people at once than doing it by hand would have, which is the opposite of what the automation was supposed to achieve. If your property management software and your renewal process are not currently talking to each other cleanly, meaning someone is manually re-typing data between the two every renewal season, that's exactly the kind of connection worth building once rather than repeating by hand every year. Get in touch if that's genuinely where the friction is for you.