Portfolio rent review Gantt chart template: owner approval to new rents

An editable Gantt chart for a yearly rent review across a rental portfolio: market data, owner approvals, notice periods as waits, tenant responses and ledger updates, with dependencies and milestones.

Use this template

What the portfolio rent review gantt chart template: owner approval to new rents process is

A yearly rent review looks like an admin task, but its length is set by other people. Owners need time to read a proposal and decide. A notice period has to run before a new rent can apply. Tenants then respond, and some of them dispute the increase. The work you do yourself, the data and the paperwork, is small next to those waits. A timeline helps because it shows where the waits sit in a sequence, so you know which start dates must be early and which dates you cannot move.

This template has five groups: Market data, Owner approvals, Notices, Tenant responses, and Ledger and records. It has 21 tasks and three milestones, and a total length of 52 working days in the illustrative numbers. **Pull the rent roll and lease terms** (2 working days) is the only starting task. It leads to **Mark the tenancies due a review** (1) and **Collect comparable rents** (4), which meet at **Compare each unit with the market** (3) and then **Draft the proposed rents** (2). **Prepare the owner review packs** (2), **Owners consider the packs** (7) and **Collect owner decisions** (2) lead to the milestone **Rent proposals approved**. Nothing in the notice path can start before that milestone.

The notice path is a chain with one long wait. **Prepare notices and letters** (2) leads to **Check the form and delivery method for each tenancy** (2), then **Issue the notices** (1) and **Notice period runs** (20). Tenant responses overlap with the wait: **Log tenant responses** (5) starts 3 working days after the notices go out, with a start-to-start link, because replies arrive during the notice period and not after it. **Negotiate disputed increases** (6) and **Refer unresolved cases to the owners** (2) follow. The milestone **Responses closed** needs both the notice period and the referral, so it is ready only when the slower of the two has finished.

The ledger tasks are the end of the cycle. **Update the rent ledger** (2) leads to **Send new payment schedules** (3) and **Update owner statements** (2), and the milestone **New rents take effect** closes the plan. In the illustrative numbers the notice wait, not the negotiation, is the longest path through the response phase, so a faster negotiation would not bring the date forward. Notice periods, the notice forms, any limits on increases and the rights of tenants to challenge them differ by country and by tenancy, so the plan holds your own durations and the numbers here are illustrative.

A timeline schedules the work. It does not decide what a rent may be raised to or whether a notice is valid. For related plans, see /templates/lease-renewal-and-rent-review-process for the steps of a single review and /templates/rent-arrears-collection-process for what follows a missed payment. For how a portfolio is planned across a year, see /guides/property-portfolio-calendar-gantt-chart.

What this flowchart covers

In this template

  • Five groups, Market data, Owner approvals, Notices, Tenant responses and Ledger and records, with 21 tasks and three milestones: "Rent proposals approved", "Responses closed" and "New rents take effect".
  • Owner approval as a gate: "Owners consider the packs" is a 7-day wait in the illustrative plan, and nothing in the Notices group starts before "Rent proposals approved".
  • A notice period as a plain wait task: "Notice period runs" has a duration and no work, so you can set it to match your own rules.
  • Tenant responses that overlap the wait: "Log tenant responses" starts 3 working days after "Issue the notices" with a start-to-start link.
  • A close that waits for two things: "Responses closed" needs both "Notice period runs" and "Refer unresolved cases to the owners".

When to use this template

  • You manage a portfolio and review rents every year, and you want one plan to reuse and resize.
  • You need to work out how early the review must start for new rents to apply on a given date.
  • Owners take a long time to decide and you want to show what that does to the date.
  • You want to check whether the notice period or the tenant negotiation is what limits the cycle.

The plan, task by task

Every task in the chart with its length in working days and what it waits for. A dependency is a step number; SS is start-to-start, FF is finish-to-finish, and +n is a lag in working days.

#TaskGroupWorking daysDepends on
1Pull the rent roll and lease termsMarket data2
2Mark the tenancies due a reviewMarket data11
3Collect comparable rentsMarket data41
4Compare each unit with the marketMarket data32, 3
5Draft the proposed rentsMarket data24
6Prepare the owner review packsOwner approvals25
7Owners consider the packsOwner approvals76
8Collect owner decisionsOwner approvals27
9Rent proposals approvedOwner approvalsMilestone8
10Prepare notices and lettersNotices29
11Check the form and delivery method for each tenancyNotices22, 10
12Issue the noticesNotices111
13Notice period runsNotices2012
14Log tenant responsesTenant responses512SS+3
15Negotiate disputed increasesTenant responses614
16Refer unresolved cases to the ownersTenant responses215
17Responses closedTenant responsesMilestone13, 16
18Update the rent ledgerLedger and records217
19Send new payment schedulesLedger and records318
20Update owner statementsLedger and records218
21New rents take effectLedger and recordsMilestone19, 20

How it works

  1. Fix the date that is real

    Give "Pull the rent roll and lease terms" a fixed Start on the day you begin and "New rents take effect" a fixed Start on the date you want the new rents to apply. The plan starts on the earliest fixed Start and is scheduled forward, so a conflict flag on the last milestone tells you the earliest date the plan allows. Compare it with the date you need and move the start earlier if it is too late.

  2. Replace the owner wait

    Set "Owners consider the packs" from how long your owners take. If one owner is slow, that owner's units can sit in a second copy of the chart.

  3. Replace the notice wait

    Set "Notice period runs" to the working days your rules and tenancies require. They differ by country and by tenancy, so use the longest one that applies in your portfolio, or split the plan by tenancy type.

  4. Resize the response phase

    Set "Log tenant responses" and "Negotiate disputed increases" from last year's experience, and adjust the 3-day start-to-start link to when replies usually begin.

  5. Add owners, share and export

    Put the person responsible for each task in People, share the chart as a link with the owners' representative and the team, and export a PDF or PNG for the file.

Frequently asked questions

Can the chart set a legal notice period for me?

No. Notice periods differ by country and tenancy, and the plan does not know them. It holds the duration you enter in "Notice period runs" and moves the later dates when you change it.

Can I review different tenancies on different dates?

Yes. Make a copy of the chart for each group of tenancies, change the fixed Start and the notice duration, and keep the same sequence. See /guides/property-portfolio-calendar-gantt-chart for a view across several plans.

What if an owner approves late?

Lengthen "Owners consider the packs" or "Collect owner decisions" and see which dates move. Every task from "Prepare notices and letters" onward moves with them, and the market data work does not.

Why does the milestone "Responses closed" have two inputs?

Because a review is not closed until the notice period is over and the unresolved cases have gone back to owners. It becomes ready when the later of the two has finished.

Does the plan check that a rent increase is allowed?

No. It schedules the work. Rules on what a rent may be raised to differ by country and tenancy, so keep them as notes or tasks next to the plan.

Part of

QueryChart features for this process

Use this template

More in Operations process templates

Browse all Operations process templates