How to plan a yearly property portfolio calendar on a Gantt chart

Plan a yearly rent review across a property portfolio on a Gantt chart: market data, owner approvals, notice waits, tenant responses and ledger updates, with the notice wait shown as the task that sets the date.

A yearly review across many tenancies is mostly waiting: for owners to decide, for notices to run and for tenants to reply. This guide shows how to put those waits on a Gantt chart, find the one that sets the effective date and start the review early enough.

The short version

  • Fix the first task's Start on the day the review begins and, if new rents must apply from a given date, fix the last milestone's Start on it.
  • Show owner decisions and notice periods as plain wait tasks with durations you replace.
  • Start the tenant response work inside the notice wait with a start-to-start link, so the two run together.
  • Turn on Critical path to see which wait sets the effective date.
  • Copy the chart each year and move the first Start, instead of rebuilding the plan.

Plan the waits in the year, not only the work

The work in a portfolio calendar is small and repeated: pull a list, compare figures, write letters, update a ledger. The calendar is long because of the waits between those tasks. Owners take time to consider a pack, a notice has to run before a change takes effect, and tenants are given time to answer. None of these is your own work, so they are easy to leave off a plan and easy to underestimate.

A Gantt chart in QueryChart schedules forward. With no dates set, the plan starts on the day the chart is created and each task starts when what it depends on allows. For a yearly calendar, give the first task a fixed Start on the day the review begins. If a date is set from outside, such as a date from which new rents should apply, give the final milestone a fixed Start on it. The chain produces a finish date, and the chart flags the fixed date if the chain cannot meet it. Run the review again next year by copying the chart and moving the first Start.

The example below has five groups and 21 tasks. **Owners consider the packs** (7 working days) is a wait for a decision. **Notice period runs** (20) is a plain wait that starts alongside the first tenant replies, because **Issue the notices** links to **Log tenant responses** with a start-to-start link and a 3 day lag. The responses are handled inside the notice period, so the tenant stream is not the longer one, and the notice wait sets the effective date.

After the example, a flowchart shows the decision a single tenancy goes through, which a Gantt chart does not draw. Durations are illustrative working days; replace each with your own, and replace the notice wait with the period that applies to each tenancy, because notice rules and limits on rent changes differ by country and by type of tenancy. A timeline schedules the work. It does not make a rent change valid, so keep your local requirements as a checklist beside it. For more on waits, see /guides/gantt-chart-delays and /guides/gantt-chart-buffer-time. The full chart is at /templates/portfolio-rent-review-gantt-chart.

A yearly portfolio rent review, built in stages

Twenty-one tasks in five groups. Durations are illustrative working days. Open the spreadsheet panel to see the rows behind each stage.

  1. Market data

    "Pull the rent roll and lease terms" (2 working days) is the first task. "Mark the tenancies due a review" (1) and "Collect comparable rents" (4) both start from it. "Compare each unit with the market" (3) needs both, and "Draft the proposed rents" (2) follows. Fix the Start of the first task on the day the review begins.

  2. Owner approvals

    "Prepare the owner review packs" (2) leads to "Owners consider the packs" (7), a plain wait. "Collect owner decisions" (2) follows, and "Rent proposals approved" is the milestone that closes the stage. The wait is longer than the work around it.

  3. Notices and the wait that sets the date

    "Prepare notices and letters" (2) and "Check the form and delivery method for each tenancy" (2) come before "Issue the notices" (1). "Notice period runs" (20) is a plain wait that follows it. Replace the 20 with the period that applies to each tenancy, or split the wait by tenancy type if the periods differ.

  4. Tenant responses inside the notice

    "Log tenant responses" (5) starts three days after "Issue the notices" with a start-to-start link, so it runs inside the notice wait. "Negotiate disputed increases" (6) and "Refer unresolved cases to the owners" (2) follow. "Responses closed" is a milestone that also waits for the notice to run out.

  5. Ledger and records

    "Update the rent ledger" (2) leads to "Send new payment schedules" (3) and "Update owner statements" (2). "New rents take effect" closes the plan. In this example the notice wait is the longest path, so the effective date follows it. If new rents must apply from a given date, fix the Start of that milestone and read the conflict flag.

The decision behind one tenancy

A lease renewal and rent review flowchart. The Gantt chart schedules this decision for every tenancy in the portfolio at once.

  1. Gather the evidence for one tenancy

    "Pull the payment record and arrears balance" and "Review inspections, repairs and complaints" come before "Check local market rents for similar homes". The result is "Renewal recommendation with proposed rent". On the Gantt chart this is the market data group, run for all units together.

  2. The landlord decides

    "Landlord wants to renew?" leads either to "Proposed rent change within the permitted limits?" or to ending the tenancy. A No at the limits question sends the recommendation back for a revision. The owner approvals group on the Gantt chart has to allow for that return.

  3. The offer and the tenant's reply

    "Renewal offer with rent, term and effective date" leads to "Review the offer and reply" and then "Tenant response?". The answers are Accepts, Negotiates or Declines. Negotiation is the loop that the tenant responses group on the Gantt chart has a duration for.

  4. Sign, record or end the tenancy

    An accepted offer goes through "Prepare the renewal agreement or addendum" and "Sign the renewal" to "Update the rent schedule, deposit and records". A declined offer goes to "Agree the move-out date and serve notice". A Gantt chart holds only the time the common route takes, so use this flowchart for the exceptions.

Lease renewal and rent review process flowchart

How it works

  1. Open the portfolio rent review chart

    Open the template and replace each duration with what your owners, your team and your local rules tell you. Put the responsible person for each task in People.

  2. Fix the first Start and any required date

    Give "Pull the rent roll and lease terms" a fixed Start on the day the review begins. If new rents must apply from a given date, give "New rents take effect" a fixed Start on it. The plan is scheduled forward from the earliest fixed Start.

  3. Set the waits to real values

    Change "Owners consider the packs" to the time your owners usually take and "Notice period runs" to the period that applies to your tenancies. If the periods differ by tenancy type, split the wait into one task per type.

  4. Find the wait that sets the date

    Turn on Critical path in the View menu. The lit chain shows whether the owners, the notice or the tenant responses decide the effective date. Hover over each wait to see its dates.

  5. Start earlier or overlap more

    If the plan does not fit, move the first Start earlier, send owner packs in batches or begin tenant replies sooner with a start-to-start link. Read the finish date after each change.

  6. Copy the chart for next year

    Duplicate the chart, move the first Start to next year's date and adjust any durations that turned out wrong. Share the chart as a link so owners and colleagues can see their waits.

Mistakes to avoid

  • Leaving the owners' time off the plan

    A review pack that sits with an owner for a week moves everything after it. Keep the decision as its own task with the time the owner usually takes.

  • Using one notice period for every tenancy

    Notice rules differ by country and by type of tenancy. The 20 working days in the example is a placeholder. If tenancies differ, give each type its own wait task.

  • Waiting for all replies before updating the ledger

    Responses arrive inside the notice period. Start the response work with a start-to-start link instead of after the notice, or the plan shows a longer year than the real one.

  • Assuming the chart checks the rent change

    The chart schedules the tasks. It does not check that a proposed rent is allowed or that a notice is valid. Keep those rules as a separate checklist.

Open the portfolio rent review Gantt chart

Open the rent review chart, fix the first Start and see which wait sets the date new rents take effect.

Open the portfolio rent review Gantt chart

Related guides

Frequently asked questions

Can QueryChart plan back from the date new rents must apply?

No. Scheduling is forward only. Fix the Start of the first task and of the final milestone, then compare the finish date with the date you need. A fixed Start that conflicts with a dependency is flagged.

Does the chart repeat itself every year?

No. A chart is one run of the review. Duplicate it each year and move the first Start to the new date.

What if owners take longer than planned?

Increase the duration of "Owners consider the packs" and read the finish date. Every task after it moves, and the conflict flag shows whether a fixed effective date still holds.

How do I show different notice periods?

Add one wait task per tenancy type, each linked from "Issue the notices" and leading to "Responses closed". The longest wait then sets the date.

Does the timeline make the rent change valid?

No. It schedules the work. It does not make a rent change allowed or a notice valid. Use your local rules for that.

The template behind this guide

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.