Weekly Leasing Report Template for BTR Property Teams

Weekly Leasing Report Template for BTR Property Teams

Blog

Blog

Weekly Leasing Report Template for BTR Property Teams

Weekly Leasing Report Template for BTR Property Teams

Imagine a leasing meeting that starts with three signed leases. Marketing points to fourteen new enquiries. Someone divides one by the other and calls it conversion, but two of those leases came from earlier enquiries.

A useful weekly leasing report template keeps those questions separate: what happened this week, how a particular group of enquiries is progressing and what your team needs to do next. For BTR teams, that means a short asset summary, a clearly dated enquiry cohort and an action log with owners.

Make a copy of the weekly leasing report template. The fictional two-asset example below shows why a healthy weekly signature count can tell a different story from new enquiry conversion.

Start with this weekly leasing report template

Use one summary row per asset, backed by the enquiry and event records behind each count. Keep lead source, contact channel and record identifiers in those supporting rows. That lets you investigate a result without adding every detail to the meeting report.

State the dates once

Put these fields at the top of the report:

  • Weekly event window: [start inclusive] to [end exclusive], [time zone].

  • Extract refreshed: [date and time for each source].

  • Enquiry cohort: [first valid enquiry window].

  • Cohort observed through: [date and time].

  • Scope and owner: [assets, exclusions, report owner, definitions version].

The event window decides which activity belongs in the week. The refresh tells you how recently the extract saw source records. The observation cutoff tells you how far the cohort has progressed. They can have different values, so keep all three explicit.

Count this week's activity


Asset

Valid enquiries received

Viewings attended

Applications submitted

Leases signed

Missing dates or links

[Asset]

[Count]

[Count]

[Count]

[Count]

[Count]

These columns count events in the weekly window. The prospects behind each column may differ. Missing dates or links is a data-quality flag that can overlap the activity counts, not an exclusive outcome. Record the affected IDs and what is missing so somebody can fix the source record. If you build this in Google Sheets, COUNTIFS can count rows matching the asset, event type and reporting dates. Use date and time values in the reporting time zone, and check duplicates separately.

Follow the selected enquiry cohort

A cohort is a group defined by a shared entry period, such as enquiries first received during the reporting week. Follow that same group as its outcomes develop.


Asset

Valid cohort enquiries

Reached signed lease

Still open

Closed without lease

Unknown outcome

[Asset]

[Count]

[Count]

[Count]

[Count]

[Count]

The four outcome columns must add up to valid cohort enquiries. This is the selected cohort's progress, not a snapshot of every open case in the portfolio. Keep pending case IDs, age, unit issues and next owner in the supporting detail. Use dropdown validation in Google Sheets to keep these outcome labels consistent. Set one outcome per enquiry and check that it matches the case record.

Agree what each count means

You do not need a long reporting manual to start. You do need the teams supplying the figures to mean the same thing when they say enquiry, application and signed lease.

Use these working rules and record any changes:

  • A valid enquiry is a distinct enquiry meeting your stated inclusion rules. Keep duplicates, invalid contacts and uncertain cases identifiable. Reporting validity is not an affordability decision.

  • An attended viewing is explicitly recorded as attended. A scheduled appointment or a group session taking place is not enough to count every prospect as present. Our guide to rental viewing no-shows explains how to record cancellations, reschedules and missed appointments.

  • An application counts when it reaches your agreed submission event. Keep unfinished drafts separate.

  • A signed lease counts at the defined completion event, with its date recorded. Sending a signature request is a different event.

Agree whether one enquiry means one household or another defined unit. Several contacts from the same household should not become extra enquiries merely because they used different channels.

The residential property data guide covers the broader KPI picture. Here, the definitions need to support one repeatable weekly comparison.

Read a completed two-asset report

All figures, assets and case details in this example are fictional. They demonstrate the template, not a performance benchmark or customer result.

The weekly event window starts at 00:00 on 12 October 2026 and ends at 00:00 on 19 October, UK time, excluding that endpoint. The extracts refreshed at 09:00 on 19 October. The cohort includes enquiries first received within the weekly window, with outcomes observed through 09:00 on 19 October.

An event after the weekly window would belong in the next activity report even if the refreshed extract already contained it.

Activity during the week


Asset

Valid enquiries received

Viewings attended

Applications submitted

Leases signed

A

8

5

3

2

B

6

4

2

1

Total

14

9

5

3

The activity columns contain 31 events in total: fourteen enquiries, nine attended viewings, five submitted applications and three signatures. Some enquiries appear at several stages, so those events do not represent 31 different prospects.

Asset A's signatures are AL01, linked to enquiry A01, and AL02, linked to A00. Asset B's signature BL01 links to B00. A00 and B00 first enquired on 5 October, before this week's cohort began.

That explains why three leases signed this week does not mean three of the fourteen new enquiries have signed.

Progress among this week's new enquiries


Asset

Valid cohort enquiries

Reached signed lease

Still open

Closed without lease

Unknown outcome

A

8

1

5

2

0

B

6

0

4

2

0

Total

14

1

9

4

0

At the observation cutoff, A01 has signed. A02–A06 remain open; A07–A08 have closed without a lease. At Asset B, B01–B04 remain open and B05–B06 have closed without a lease. Those outcomes reconcile: 1 + 9 + 4 + 0 = 14.

For this cohort, enquiry to signed lease conversion is:

1 signed enquiry ÷ 14 valid cohort enquiries × 100 = approximately 7.1%.

Dividing all three weekly signatures by fourteen gives approximately 21.4%. That is an activity ratio, not this cohort's conversion, because two signatures belong to older enquiries.

The 7.1% is also an early observation. Nine enquiries remain open. Keep following them with the same entry definition rather than treating this result as their final outcome or comparing it uncritically with a much older cohort.

Turn the open cases into decisions

The nine open enquiries give the meeting something useful to investigate. Which applications need information? Which cases are waiting on the property rather than the applicant? Which missing records prevent a sound decision?

Continuing the fictional example:


Issue

Decision and next action

Owner

Due date

A02 lacks a required document

Confirm missing item and contact applicant

Leasing lead

20 October 2026

B03 linked to a unit not ready

Obtain readiness date before promising move in

Operations lead

21 October 2026

A06 has unknown lead source

Check original record; retain unknown if unresolved

Marketing lead

20 October 2026

These are illustrative role labels. Assign named people in your live action log, and record status, outcome and next review alongside the due date.

Keep ageing applications and units needing attention in the supporting rows. Define the age you are measuring, such as time since submission or time waiting at a stage. A case awaiting a document and one awaiting unit readiness require different action even if both appear in an overdue list.

Carry unresolved actions into the next meeting with their original due dates. Moving the date forward without recording what happened makes a report look current while the work stays where it was.

Compare assets and sources without losing the context

Use consistent dates, stages and counting units across compared assets. Then check what could explain a difference: available units, readiness constraints, enquiry mix or incomplete records. A portfolio total shows where to look; it does not independently tell you which team or channel caused the result.

Keep acquisition source separate from contact channel. Someone can find the property on a portal, ask a question by email and continue on WhatsApp. Those contacts do not create three sources or three signed leases.

State your attribution rule and retain an unknown category when the evidence is missing. Check the underlying counts before acting on a percentage from a small sample. A source comparison with unresolved attribution is a reason to investigate, not a reason to guess where the enquiries came from.

Check the extract before calling it a trend

Reconcile the summary to source rows before the meeting. Look for duplicate enquiries, missing stage dates, broken links and records that arrived late. A current refresh timestamp cannot prove that every upstream system is current. The Government Data Quality Framework offers a useful reference for checking completeness, uniqueness, consistency, timeliness, validity and accuracy.

Choose how corrections will appear. You can restate a previous report or show a disclosed adjustment, but preserve the earlier version and explain the change. Do not let a corrected signature date look like a sudden improvement in the current week's activity.

For connected systems, identify any approval, export or manual update still needed. That helps the team separate an actual slowdown from a record that has not caught up with the work.

Where AI and Lette can help

Once the definitions work, assess the repetitive reporting tasks: gathering available records, preparing a summary and flagging missing information. Those are tasks to evaluate against your connected setup. A person still needs to interpret the result, choose the next action and verify important exceptions.

In a demo of Lette’s property management reporting, check which connected systems can supply leasing activity and which weekly figures you still need to verify manually.

Your PMS remains the system of record; Lette is the system of action across connected work. Trace one enquiry from its original record to the summary, including any staff steps. That will reveal whether the available data supports the decision your meeting needs to make.

FAQs about weekly leasing reports

How should you count enquiries across several assets?

Keep a portfolio enquiry ID alongside asset interest records. One household asking about two buildings can represent one portfolio enquiry and two asset interests. State which unit the report counts. Do not add asset interest totals and label them unique portfolio enquiries.

Should several people on a joint application count separately?

Follow the reporting unit you agreed. If the enquiry represents a household, link each applicant to it without multiplying the enquiry count. Keep the application and lease links traceable so a joint household does not produce a different conversion denominator merely because more people supplied details.

Can you compare a new cohort with an older one?

Only with elapsed time clearly shown. A cohort received last week has had less opportunity to sign than one received months ago. Compare progress at equivalent ages where practical, and retain pending outcomes. Otherwise, the apparent gap can simply reflect how long each group has been observed.

What happens if an old enquiry becomes active again?

Keep its original identifier and history. Document whether it remains part of the original journey or qualifies as a genuinely new enquiry under your rules. Do not restart the date simply because someone replied again. Disclose any rule change before comparing the resulting conversion figures.

Should renewals appear beside new lettings?

Show them separately if both belong in the meeting. A renewal starts from an existing tenancy rather than a new enquiry, so it needs its own denominator and dates. Combining the outcomes can disguise whether a change came from new leasing activity or retention among existing residents.

Use the report to decide what happens next

A useful weekly leasing report gives your BTR team a shared view of activity completed during the week and the enquiries still needing attention. In the worked example, three leases were signed during the week, while nine of that week's new enquiries remained open. The team needs both views to understand what happened and decide where to act next.

Use the meeting to choose those actions. Missing documents need a follow-up with the applicant, while a unit that is not ready needs an answer from Operations before anyone promises a move-in date. Give each action a named owner and a due date, then review unresolved work at the next meeting without erasing the earlier commitment.

Once the report supports those decisions reliably, look at the effort involved in producing it. AI may help gather available records and prepare summaries where your setup supports that work. If colleagues still spend too much time assembling and checking the same information each week, talk to Lette about your leasing reporting needs.

Imagine a leasing meeting that starts with three signed leases. Marketing points to fourteen new enquiries. Someone divides one by the other and calls it conversion, but two of those leases came from earlier enquiries.

A useful weekly leasing report template keeps those questions separate: what happened this week, how a particular group of enquiries is progressing and what your team needs to do next. For BTR teams, that means a short asset summary, a clearly dated enquiry cohort and an action log with owners.

Make a copy of the weekly leasing report template. The fictional two-asset example below shows why a healthy weekly signature count can tell a different story from new enquiry conversion.

Start with this weekly leasing report template

Use one summary row per asset, backed by the enquiry and event records behind each count. Keep lead source, contact channel and record identifiers in those supporting rows. That lets you investigate a result without adding every detail to the meeting report.

State the dates once

Put these fields at the top of the report:

  • Weekly event window: [start inclusive] to [end exclusive], [time zone].

  • Extract refreshed: [date and time for each source].

  • Enquiry cohort: [first valid enquiry window].

  • Cohort observed through: [date and time].

  • Scope and owner: [assets, exclusions, report owner, definitions version].

The event window decides which activity belongs in the week. The refresh tells you how recently the extract saw source records. The observation cutoff tells you how far the cohort has progressed. They can have different values, so keep all three explicit.

Count this week's activity


Asset

Valid enquiries received

Viewings attended

Applications submitted

Leases signed

Missing dates or links

[Asset]

[Count]

[Count]

[Count]

[Count]

[Count]

These columns count events in the weekly window. The prospects behind each column may differ. Missing dates or links is a data-quality flag that can overlap the activity counts, not an exclusive outcome. Record the affected IDs and what is missing so somebody can fix the source record. If you build this in Google Sheets, COUNTIFS can count rows matching the asset, event type and reporting dates. Use date and time values in the reporting time zone, and check duplicates separately.

Follow the selected enquiry cohort

A cohort is a group defined by a shared entry period, such as enquiries first received during the reporting week. Follow that same group as its outcomes develop.


Asset

Valid cohort enquiries

Reached signed lease

Still open

Closed without lease

Unknown outcome

[Asset]

[Count]

[Count]

[Count]

[Count]

[Count]

The four outcome columns must add up to valid cohort enquiries. This is the selected cohort's progress, not a snapshot of every open case in the portfolio. Keep pending case IDs, age, unit issues and next owner in the supporting detail. Use dropdown validation in Google Sheets to keep these outcome labels consistent. Set one outcome per enquiry and check that it matches the case record.

Agree what each count means

You do not need a long reporting manual to start. You do need the teams supplying the figures to mean the same thing when they say enquiry, application and signed lease.

Use these working rules and record any changes:

  • A valid enquiry is a distinct enquiry meeting your stated inclusion rules. Keep duplicates, invalid contacts and uncertain cases identifiable. Reporting validity is not an affordability decision.

  • An attended viewing is explicitly recorded as attended. A scheduled appointment or a group session taking place is not enough to count every prospect as present. Our guide to rental viewing no-shows explains how to record cancellations, reschedules and missed appointments.

  • An application counts when it reaches your agreed submission event. Keep unfinished drafts separate.

  • A signed lease counts at the defined completion event, with its date recorded. Sending a signature request is a different event.

Agree whether one enquiry means one household or another defined unit. Several contacts from the same household should not become extra enquiries merely because they used different channels.

The residential property data guide covers the broader KPI picture. Here, the definitions need to support one repeatable weekly comparison.

Read a completed two-asset report

All figures, assets and case details in this example are fictional. They demonstrate the template, not a performance benchmark or customer result.

The weekly event window starts at 00:00 on 12 October 2026 and ends at 00:00 on 19 October, UK time, excluding that endpoint. The extracts refreshed at 09:00 on 19 October. The cohort includes enquiries first received within the weekly window, with outcomes observed through 09:00 on 19 October.

An event after the weekly window would belong in the next activity report even if the refreshed extract already contained it.

Activity during the week


Asset

Valid enquiries received

Viewings attended

Applications submitted

Leases signed

A

8

5

3

2

B

6

4

2

1

Total

14

9

5

3

The activity columns contain 31 events in total: fourteen enquiries, nine attended viewings, five submitted applications and three signatures. Some enquiries appear at several stages, so those events do not represent 31 different prospects.

Asset A's signatures are AL01, linked to enquiry A01, and AL02, linked to A00. Asset B's signature BL01 links to B00. A00 and B00 first enquired on 5 October, before this week's cohort began.

That explains why three leases signed this week does not mean three of the fourteen new enquiries have signed.

Progress among this week's new enquiries


Asset

Valid cohort enquiries

Reached signed lease

Still open

Closed without lease

Unknown outcome

A

8

1

5

2

0

B

6

0

4

2

0

Total

14

1

9

4

0

At the observation cutoff, A01 has signed. A02–A06 remain open; A07–A08 have closed without a lease. At Asset B, B01–B04 remain open and B05–B06 have closed without a lease. Those outcomes reconcile: 1 + 9 + 4 + 0 = 14.

For this cohort, enquiry to signed lease conversion is:

1 signed enquiry ÷ 14 valid cohort enquiries × 100 = approximately 7.1%.

Dividing all three weekly signatures by fourteen gives approximately 21.4%. That is an activity ratio, not this cohort's conversion, because two signatures belong to older enquiries.

The 7.1% is also an early observation. Nine enquiries remain open. Keep following them with the same entry definition rather than treating this result as their final outcome or comparing it uncritically with a much older cohort.

Turn the open cases into decisions

The nine open enquiries give the meeting something useful to investigate. Which applications need information? Which cases are waiting on the property rather than the applicant? Which missing records prevent a sound decision?

Continuing the fictional example:


Issue

Decision and next action

Owner

Due date

A02 lacks a required document

Confirm missing item and contact applicant

Leasing lead

20 October 2026

B03 linked to a unit not ready

Obtain readiness date before promising move in

Operations lead

21 October 2026

A06 has unknown lead source

Check original record; retain unknown if unresolved

Marketing lead

20 October 2026

These are illustrative role labels. Assign named people in your live action log, and record status, outcome and next review alongside the due date.

Keep ageing applications and units needing attention in the supporting rows. Define the age you are measuring, such as time since submission or time waiting at a stage. A case awaiting a document and one awaiting unit readiness require different action even if both appear in an overdue list.

Carry unresolved actions into the next meeting with their original due dates. Moving the date forward without recording what happened makes a report look current while the work stays where it was.

Compare assets and sources without losing the context

Use consistent dates, stages and counting units across compared assets. Then check what could explain a difference: available units, readiness constraints, enquiry mix or incomplete records. A portfolio total shows where to look; it does not independently tell you which team or channel caused the result.

Keep acquisition source separate from contact channel. Someone can find the property on a portal, ask a question by email and continue on WhatsApp. Those contacts do not create three sources or three signed leases.

State your attribution rule and retain an unknown category when the evidence is missing. Check the underlying counts before acting on a percentage from a small sample. A source comparison with unresolved attribution is a reason to investigate, not a reason to guess where the enquiries came from.

Check the extract before calling it a trend

Reconcile the summary to source rows before the meeting. Look for duplicate enquiries, missing stage dates, broken links and records that arrived late. A current refresh timestamp cannot prove that every upstream system is current. The Government Data Quality Framework offers a useful reference for checking completeness, uniqueness, consistency, timeliness, validity and accuracy.

Choose how corrections will appear. You can restate a previous report or show a disclosed adjustment, but preserve the earlier version and explain the change. Do not let a corrected signature date look like a sudden improvement in the current week's activity.

For connected systems, identify any approval, export or manual update still needed. That helps the team separate an actual slowdown from a record that has not caught up with the work.

Where AI and Lette can help

Once the definitions work, assess the repetitive reporting tasks: gathering available records, preparing a summary and flagging missing information. Those are tasks to evaluate against your connected setup. A person still needs to interpret the result, choose the next action and verify important exceptions.

In a demo of Lette’s property management reporting, check which connected systems can supply leasing activity and which weekly figures you still need to verify manually.

Your PMS remains the system of record; Lette is the system of action across connected work. Trace one enquiry from its original record to the summary, including any staff steps. That will reveal whether the available data supports the decision your meeting needs to make.

FAQs about weekly leasing reports

How should you count enquiries across several assets?

Keep a portfolio enquiry ID alongside asset interest records. One household asking about two buildings can represent one portfolio enquiry and two asset interests. State which unit the report counts. Do not add asset interest totals and label them unique portfolio enquiries.

Should several people on a joint application count separately?

Follow the reporting unit you agreed. If the enquiry represents a household, link each applicant to it without multiplying the enquiry count. Keep the application and lease links traceable so a joint household does not produce a different conversion denominator merely because more people supplied details.

Can you compare a new cohort with an older one?

Only with elapsed time clearly shown. A cohort received last week has had less opportunity to sign than one received months ago. Compare progress at equivalent ages where practical, and retain pending outcomes. Otherwise, the apparent gap can simply reflect how long each group has been observed.

What happens if an old enquiry becomes active again?

Keep its original identifier and history. Document whether it remains part of the original journey or qualifies as a genuinely new enquiry under your rules. Do not restart the date simply because someone replied again. Disclose any rule change before comparing the resulting conversion figures.

Should renewals appear beside new lettings?

Show them separately if both belong in the meeting. A renewal starts from an existing tenancy rather than a new enquiry, so it needs its own denominator and dates. Combining the outcomes can disguise whether a change came from new leasing activity or retention among existing residents.

Use the report to decide what happens next

A useful weekly leasing report gives your BTR team a shared view of activity completed during the week and the enquiries still needing attention. In the worked example, three leases were signed during the week, while nine of that week's new enquiries remained open. The team needs both views to understand what happened and decide where to act next.

Use the meeting to choose those actions. Missing documents need a follow-up with the applicant, while a unit that is not ready needs an answer from Operations before anyone promises a move-in date. Give each action a named owner and a due date, then review unresolved work at the next meeting without erasing the earlier commitment.

Once the report supports those decisions reliably, look at the effort involved in producing it. AI may help gather available records and prepare summaries where your setup supports that work. If colleagues still spend too much time assembling and checking the same information each week, talk to Lette about your leasing reporting needs.

See Lette In Action

See Lette In Action

Modern apartment buildings with lush green park and walking paths under a blue sky.

Ready to simplify your property operations?

See how Lette helps leasing and residential teams automate daily work, respond faster, and scale with confidence.

Property management dashboard showing to-do lists, tenant records, and lease amendments

The AI operating system for residential operators, from first enquiry to renewal.

167-169 Great Portland Street 5th Floor London W1W 5PF

33 Fitzwilliam Place, Dublin 2 Carroll Estates Mews DUBLIN 2 D02 A5W0 IRELAND

info@lette.ai

Lette – AI-powered property management platform

© 2026 Lette AI. All rights reserved.

Modern apartment buildings with lush green park and walking paths under a blue sky.

Ready to simplify your property operations?

See how Lette helps leasing and residential teams automate daily work, respond faster, and scale with confidence.

Property management dashboard showing to-do lists, tenant records, and lease amendments

The AI operating system for residential operators, from first enquiry to renewal.

167-169 Great Portland Street 5th Floor London W1W 5PF

33 Fitzwilliam Place, Dublin 2 Carroll Estates Mews DUBLIN 2 D02 A5W0 IRELAND

info@lette.ai

Lette – AI-powered property management platform

© 2026 Lette AI. All rights reserved.

Modern apartment buildings with lush green park and walking paths under a blue sky.

Ready to simplify your property operations?

See how Lette helps leasing and residential teams automate daily work, respond faster, and scale with confidence.

Property management dashboard showing to-do lists, tenant records, and lease amendments

The AI operating system for residential operators, from first enquiry to renewal.

167-169 Great Portland Street 5th Floor London W1W 5PF

33 Fitzwilliam Place, Dublin 2 Carroll Estates Mews DUBLIN 2 D02 A5W0 IRELAND

info@lette.ai

Lette – AI-powered property management platform

© 2026 Lette AI. All rights reserved.

Modern apartment buildings with lush green park and walking paths under a blue sky.

Ready to simplify your property operations?

See how Lette helps leasing and residential teams automate daily work, respond faster, and scale with confidence.

Property management dashboard showing to-do lists, tenant records, and lease amendments

The AI operating system for residential operators, from first enquiry to renewal.

167-169 Great Portland Street 5th Floor London W1W 5PF

33 Fitzwilliam Place, Dublin 2 Carroll Estates Mews DUBLIN 2 D02 A5W0 IRELAND

info@lette.ai

Lette – AI-powered property management platform

© 2026 Lette AI. All rights reserved.

>