Tempio

Test plan template for Real estate

Free download as CSV and Markdown. Nothing sits in front of the file: no form, no account, no email address.

The files

What it is

The test plan with three columns a property campaign needs: which listing or market the test runs in, which stage of the sale it runs at, and an explicit note on whether the sample can support a conclusion at all.

Everything else is the general test plan, unchanged. One hypothesis with a because in it, one variable, a named control, a minimum run, a read date set in advance and a decision rule for every outcome.

When to use it

Use it across campaigns rather than inside one. A single listing rarely produces enough enquiries to decide anything, so the useful unit of testing in property is the same variable applied to many listings in one market over a quarter.

Use it again to build a record of what works in each corridor, which is the argument every listing presentation is trying to make.

Every field, and what belongs in it
TypeHow to fill it
Test IDTextA short stable identifier that travels onto the creative file and the campaign names of every listing in the test, because the unit here is a corridor rather than one property.
HypothesisTextWhat you believe and why, with a because in it, and here the reason is usually about the buyer in that corridor: the floorplan will raise attendance because these buyers are upsizing families.
VariableTextThe single thing being changed, held identical across every listing in the test. A variable that changes with each property is not a variable, it is a set of one-off campaigns.
ControlTextWhat the variant is compared against, named exactly: the way the office would otherwise have run these listings. Both arms must be versions you would have been willing to run for the vendor.
VariantTextWhat is being tried, described so somebody could build it from the assets each listing actually has, because a variant requiring drone footage cannot run on a listing that has none.
AudienceTextWho sees the test, identical on both sides. Corridor radius and life stage do most of the targeting here, so the two arms differ in the creative rather than in the audience.
Where it runsTextThe platform, campaign and placement the test lives in, applied the same way across every listing in the test so the comparison holds.
Primary metricTextThe one number this test is decided on, which should be an inspection attended or a registered buyer. Enquiry counts move easily and predict very little about a sale.
Minimum runTextThe shortest run before anybody looks, expressed as a number of listings rather than a number of weeks, because one property produces too little of anything to decide a question.
Read dateDate (YYYY-MM-DD)The day the result is read, set in advance and outside a holiday period, when attendance is dominated by who happened to be in town.
Decision ruleTextWhat each outcome means, written before the test starts, with the sample caution attached: at these volumes only a large difference should be treated as a result.
OwnerTextThe person who builds the test, reads it on the read date, and gets the agents involved to agree to it before any vendor's campaign carries an arm.
ResultTextWhat happened and what was decided, written on the read date, including the listings whose campaigns were cut short by an early sale. Blank until then.
Listing or marketTextWhether this test runs on one listing or across a market. In property the market is usually the only unit with enough volume to decide anything, so most rows should name one.
Stage of saleTextWhere in the campaign the test runs: pre-launch, launch weekend, open inspections, pre-auction. A variant that wins at launch says little about the pre-auction week.
Sample cautionTextAn honest note on whether the volume can support a conclusion, written before the test starts. A row that says the sample is too small is more useful than one that pretends otherwise.

The unit of testing is the market, not the listing

Almost every property test fails for the same reason: one listing does not produce enough of anything to decide a question. A campaign might generate a modest number of enquiries and a handful of inspection attendances, spread across three weeks, in a market with its own weather.

So the listing or market column pushes the unit up. The useful test is the same variable applied across every listing in a corridor for a quarter, with the control being the way the office would otherwise have run them. That accumulates enough events to distinguish a real difference from an ordinary quiet fortnight, and it produces a finding that is about the corridor rather than about a house.

There is a practical cost: the test takes a quarter and involves several agents, which means the row has to be agreed rather than simply set up. That is why the owner column matters more here than anywhere else.

The ethics of testing somebody else's campaign

Property advertising is usually paid for by a vendor, which puts a constraint on testing that other categories do not have.

The rule that works is simple: both arms have to be versions you would have been willing to run for that vendor anyway. Testing a floorplan-led ad against an exterior-led ad is fine, because both are legitimate choices. Testing a deliberately weak creative to prove a point is not, because the cost falls on somebody who did not agree to it.

Write the rule into the plan and keep to it. It also improves the tests, because it forces both arms to be real options rather than a straw man and a favourite.

Record the stage, because warm and cold behave differently

The stage of sale column stops a finding being over-applied.

A variant that wins at the open-inspection stage is winning against an audience that has already seen the property and is deciding whether to attend. A variant that wins pre-launch is winning against people who have never heard of it. The pre-auction week is different again: a small, warm audience being asked to register rather than to look.

A finding is a statement about a stage. Write the stage in the row and the finding stays usable; leave it out and the office will apply a pre-auction result to its launch creative and wonder why it stopped working.

Say in advance whether the sample can decide anything

The sample caution column is unusual and it earns its place.

Most property tests are thin. Writing down, before the test starts, that six listings is a small sample and that only a large difference should be treated as a result is what stops a modest gap being read as a finding at the read date. Everybody agrees with the caveat in advance and almost nobody accepts it afterwards, which is exactly why it goes in the row first.

It also improves test selection. A team that has to state the sample caution up front will naturally propose fewer tests and bigger ones.

Count inspections and registrations, not enquiries

Enquiry counts move easily and predict very little. A more urgent ad, a lower price guide or a bigger headline will all produce more messages, and a proportion of them are from people who were never going to attend anything.

Read on inspection attendance or registered buyers wherever the office's system records them, and use the system's own words. Where neither is recorded reliably, fixing that is a better investment than any test in the plan, because without it no finding in this category can be trusted.

Seasonality is a larger confound here than almost anywhere

Property markets have strong seasons, school terms, holiday periods and weather, and all of them move inspection attendance by more than most creative variables do.

Run both arms simultaneously across the same listings and weeks rather than sequentially, so the season moves under both. Where the test spans a seasonal boundary, note it. And treat any result read across a holiday period with particular suspicion, because attendance in those weeks is dominated by who was in town.

Keep the findings by corridor

The completed rows are worth more than any single test, and in this category they are worth more than usual, because they answer the question every listing presentation tries to answer: what works in this corridor, at this bracket, for this kind of property.

Store them by market. After a year an office has its own evidence about first images, price guide presentation, inspection timing and creative formats in the streets it actually works in, which is more persuasive to a vendor than anything general.

Before you start the test

Every row has a hypothesis with a because in it. Every row names whether it runs on one listing or across a market, and most should name a market. Every row names the stage of sale. The sample caution is written honestly before the test starts. Both arms are versions you would have been willing to run for the vendor anyway. The primary metric is an inspection attended or a registered buyer. And the decision rule covers the outcome where nothing moves, which with these volumes will be common.

A test that passes those seven is not guaranteed to produce an answer. It is guaranteed not to produce a false one, which in a category this thin is the more valuable of the two.

The general template, and other industries

Templates that go with it

Related reading

Questions

Put frontier AI to work on every ad account you run.

Tempio connects your ad accounts into one workspace and hands your own AI the numbers and the tools. Every change it writes is a draft until you approve it, or until a rule you wrote does.

Request early access
  • Read and draft by default. Approve is a separate permission you grant.