Tenant Utility Data Copy Pack

Collect tenant-paid utility data consistently (without endless chasing) and turn it into a scalable operating system for real estate portfolios.

Carbon75 minute setup12 templates included
TenantsUtility DataScope 3Leased Assets

What this pack is

A plug-and-play implementation kit you can set up in 60–90 minutes to establish:

  • a tenant roster + responsibility mapping (who pays for what)
  • a standardized outreach request that gets replies
  • alternate submission formats (reduces friction)
  • an intake QA checklist + evidence storage rules
  • an escalation ladder (so coverage increases predictably)
  • a monthly operating cadence (so this becomes a system, not a campaign)

Complete value chain intelligence:

  • Cost reduction: improves utility cost visibility, reduces billing disputes, supports CAM/opex transparency, and helps identify operational waste
  • Risk mitigation: reduces reporting gaps, audit exposure, and "we can't prove it" problems; prevents tenant relationship chaos by standardizing the motion
  • Carbon impact reduction: increases coverage and quality for Scope 2 and Scope 3 leased-asset emissions accounting (Category 13 for lessors / Category 8 for lessees)

Beginner rule: The goal is not perfect data on day 1. The goal is a repeatable system with coverage that improves every month.

When to use this pack

Use this pack if any of these are true:

  • Tenant utility data is scattered across inboxes and PDFs
  • You rely on guesses or allocations because you can't get tenant-paid utilities
  • You can't tell which tenants pay utilities vs landlord-paid vs unknown
  • You're stuck in "polite reminders" and response rates don't improve
  • Your team can't scale collection across a portfolio
  • You want a reliable foundation for both cost controls and leased-asset emissions

What's included

  1. Portfolio folder structure (evidence + intake)
  2. Tenant Utility Responsibility Map (quick classifier)
  3. Tenant Data Roster (tracker)
  4. Tenant Outreach Email (standard request)
  5. Alternate Formats Follow-up (makes it easy to comply)
  6. Tenant Data Escalation Ladder (30–45 day)
  7. Monthly Tenant Data Intake Checklist (QA + labeling)
  8. Tenant Utility Data Intake Log (per month)
  9. Exceptions / Blockers Log (what's stuck and why)
  10. Proxy/Allocation Decision Note (what you do when data can't be obtained)
  11. Tenant Follow-up Email (QA Clarification)
  12. Optional: Lease leverage checklist (how to align leasing/PM)
  13. Monthly Tenant Utility Data Close Agenda

60–90 minute setup

Step 1 — Create the portfolio folder structure (10 minutes)

Create a stable place for evidence so nothing gets lost.

Recommended folder structure:

Beginner rule: Evidence must have stable links. If links break, the system breaks.

Step 2 — Build the Tenant Data Roster (15–20 minutes)

Start with your top sites by utility spend. For each site and utility type, capture provider + account #. If unknown, write "Unknown" and assign an owner.

Step 3 — Send the initial outreach (10 minutes)

Use the Tenant Utility Data Request Email. Start with the simplest ask: bill PDF or portal export for electricity usage (kWh).

Beginner rule: ask for one utility first (electricity) before expanding to gas/water.

Step 4 — Stand up intake + QA (15 minutes)

Copy these into your sheet (each as a tab):

  • Tenant Utility Data Intake Log (monthly)
  • Exceptions / Blockers Log

Then use the Monthly Tenant Data Intake Checklist to ensure submissions are usable.

Step 5 — Install the escalation ladder (10 minutes)

Copy the Tenant Data Escalation Ladder and decide who owns escalation at each stage.

Step 6 — Start a lightweight cadence (10–15 minutes)

Schedule recurring:

  • Weekly (optional) "Tenant data follow-ups" (15 minutes)
  • Monthly (required) "Tenant utility data close" (30 minutes)

Operating cadence

Weekly (optional, 15 minutes)

  • Follow-ups due this week
  • Unblock stuck tenants (alternate formats)
  • Escalate anything beyond 21 days

Monthly (required, 30 minutes)

  • Intake and QA all submissions
  • Update coverage metrics (by tenant count + by leased area)
  • Resolve exceptions (or document proxy decisions)
  • Lock the month's dataset version (basic governance)

KPIs

Track these monthly:

KPITargetWhy it matters
Coverage by leased area (%)Trending upArea with measured tenant utility data
Coverage by tenant count (%)Trending upTenants providing data
On-time submission rate (%)>70%Received by target date
Data quality mix (%)TrackMeasured vs Allocated vs Proxy vs Unknown
Avg days to receive dataTrending downInitial request → receipt
# blocked tenantsTrending downAnd blocker types
Escalations required (#)Trending downShould decrease as system matures

Definition of Done

You've implemented tenant utility data correctly when:

  • Every tenant is in a roster with responsibility + contact + method + status
  • Tenant submissions follow a predictable request + follow-up + escalation ladder
  • Evidence is stored with stable links and a consistent folder structure
  • Each month has an intake log with period dates, usage, and quality labels
  • Blocked tenants are managed via an exceptions log (not forgotten)
  • Proxy/allocation decisions are documented with limitations and revisit dates
  • Monthly coverage metrics improve over time (especially by leased area)

Included Templates

These templates are your implementation artifacts. Copy them from the Template Vault or use the links below.

Change log

v1.0 (2026-01): Latest release