This describes work that is in design. Everything below is what we are building, not something you can switch on today.
Thirty fields were collected. Six of them decide anything. It is six in the evening, the phone is going, and somebody is reading an application off a screen trying to find those six.
Every operator we have talked to has built the same private workaround for this. A mental checklist. A pen that goes round the same three answers. A habit of scrolling straight to the same place and starting there. It works, in the sense that experienced people make it work.
It also runs slightly differently at six on a Friday than it does at ten on a Tuesday, and differently again for the manager covering while you are away.
The information is not missing. It is all there, every time. It just arrives in a different shape every time, and the shape is doing more damage than the volume.
The fix is not a cleverer summary
The obvious thing to build here is software that reads an application and tells you about it. We are not building that, and the reason is the whole point of this piece. This page is part of the same desk-side work as the drafting layer, and it is the part of it that needed the most careful handling.
What we are building presents what the applicant supplied — their own words, unedited — in the same fields, in the same order, every time. Beside it, which of your written criteria were met, worked out by rule from the criteria you wrote down.
That is the entire specification. It removes the re-reading, not the reading. You still read the application, you still decide, and what changes is that you decide from a page that looks the same on a Friday evening as it did on a Tuesday morning — for this applicant and for the one before them.
"At a glance" is the phrase to watch
Every product in this category promises you an applicant at a glance, and the phrase is worth stopping on, because it has two meanings and only one of them is honest.
It can mean: the same fields, in the same order, laid out so your eye knows where to go. That is a layout decision, it is genuinely useful, and it is what we are building.
Or it can mean: the important parts, chosen for you. And that is not a layout. That is a judgement about a person wearing a layout costume. Something decided which of a person's answers you would see first and which you would scroll for, and it did that by having a view about them — while presenting the result as though it were formatting.
So the summary is specified as a fixed structure with no free-text assessment field anywhere in it. Not one. There is no box for a sentence about the applicant, because a box like that gets filled, and once it exists everything downstream comes to depend on it.
Having nowhere to write an opinion is a stronger guarantee than a rule saying do not write one. Rules get exceptions in a sales conversation. Structures do not.
What "met" means, and where it stops
The one computed thing on the page is whether your written criteria were met, and it is worth being exact about what that is.
It is arithmetic against the criteria you wrote in your own pack — the document described in your leasing rules exist. You set the criteria. The rule is applied the same way to everyone. The page says which were met, from what the applicant themselves submitted.
That is the ceiling of what this page will ever say. Met the criteria you wrote is not a view about somebody; it is a comparison you specified, run consistently, shown with the answer it was run against so you can see the working and disagree with it.
Everything past that line is yours. What the answers mean, what they are worth against each other, whether something explains itself once you have made a phone call — that is the leasing judgement you are accountable for, and no part of this page is designed to lean on it.
The trade-off: you will see fields you do not care about
A fixed layout means the page will sometimes show you things this particular firm never looks at, and it will show them in the same position as always rather than getting out of the way.
That is the feature working, not the feature failing. The moment the layout starts adapting per applicant — hiding this, promoting that — the shape stops being stable and you are back to reading a different page each time, with the added problem that something else chose the difference.
You choose which fields your firm collects. The software does not choose them again, applicant by applicant.
Why we think this is the stronger position
There is a version of this product that offers you a view about a person, and it would demo well.
Here is what we would rather have, and it is what this is built around: your own written criteria, applied the same way to everyone, computed from what the applicant themselves submitted, presented in a fixed order with a record of exactly what was shown and when — and the decision sitting with the person who is accountable for it, made from the applicant's own answers rather than from something's impression of them.
That is a defensible way to run a leasing process, and it is defensible on an ordinary Tuesday as much as on the day someone asks you to explain how you decided. Consistency you can point at is worth more than an opinion you would then have to stand behind.
This page will not have a view. There is nowhere in it for one to go, which is the point — the guarantee is the structure rather than our good intentions about how to use it.
Releaser is available to property management firms in the United States and Canada today: one shareable link per property, your screening completed before anyone reaches your calendar, and self-serve booking for the people who meet the criteria you set.
The applicant summary described here is in design. This is what we are building it to be.