- November 4, 2026
- 12
- Business Storage, Guides, Self Storage
Governed Industry Leadership library image. The source inventory does not state its production method. It is editorial context, not evidence of the fictional example, a deployment, or a measured result.
By Jared Mastroianni
One facility reports a 72 percent lead-conversion rate. Another reports 41 percent. The first looks stronger until someone asks what each site counted.
Facility A starts with reservations and calls a lead converted when a rental agreement is created. Facility B starts with every phone call, web form and walk-in, then waits for the rental to be accepted. Facility A excludes duplicate contacts. Facility B counts them as separate opportunities. A customer who contacted two locations and rented at a third appears once in one report and three times in another.
The percentages are real calculations. The comparison is not.
A multi-location operator needs more than a funnel label. It needs a lead-to-rental episode contract: a versioned definition of the journey start, eligible population, identity rule, facility and channel attribution, conversion event, time window, exclusions and reconciliation evidence. Without that contract, the dashboard measures local data-entry habits as much as customer response.
Conversion is an episode, not a status
A status describes what a record says now. A conversion episode describes a bounded sequence of events.
The distinction matters because one customer journey can produce a web inquiry, phone call, reservation, facility tour, unit change and completed rental. Those records may sit in different systems. Some may be duplicated. Some may be corrected. A status such as rented cannot explain which inquiry received credit, when the clock began, which facility owns the result or whether the episode belongs in the report.
Create an episode identifier before computing the metric. Bind that episode to the governing source records without overwriting them. Record the first eligible event, subsequent touches, reservation activity, final rental event, outcome time and disposition. Preserve the rule version that formed the episode.
This does not require one giant customer record. It requires a controlled measurement object whose lineage can be reviewed.
Define the start event precisely
“Lead created” is not precise enough. One facility may create a lead after a completed web form. Another may create one after a missed call. A third may wait until a manager qualifies the customer’s need. A fourth may create a new record every time the same person asks about another unit size.
Name the eligible start event and its required evidence. Examples include a submitted inquiry with usable contact information, an answered inbound call meeting the approved purpose, a documented walk-in request or a reservation created through an authorized channel. The portfolio must decide which events qualify; this article does not supply a universal definition.
Also define what does not start an episode. Spam, employee tests, vendor calls, abandoned forms with no usable contact path, duplicate delivery events and system retries may be excluded when the approved contract says so. Exclusion needs a reason code and source evidence. It should not be a manager’s after-the-fact judgment about whether a lead looked promising.
The U.S. Government Accountability Office’s data-reliability guide defines reliability for its audit context through accuracy, completeness and applicability for the intended purpose. It also notes that inconsistent interpretation of entry rules across sites can undermine comparability. That guide governs government audit work, not self-storage sales reporting. The useful operating lesson is narrow: a record can be accurate in its source system and still be unsuitable for a portfolio conversion comparison because the population or purpose differs.
Define the conversion event separately
Do not let reserved, lease generated, signed, paid, moved in and access activated collapse into one word.
Choose the event that means conversion for this metric and cite the governing record. If the portfolio selects accepted rental, define the evidence required for acceptance. If another report measures reservation completion, give it a different metric name and contract. Do not improve a rental-conversion rate by substituting an earlier stage.
Corrections need treatment too. A rental may be canceled, transferred, reversed or corrected to another facility. The original event is not erased. The episode records the later disposition and the rule determines whether the published observation is revised, superseded or retained with an annotation.
The W3C PROV ontology distinguishes entities, activities and agents, and provides relationships for generation, use, derivation and invalidation. A self-storage operator does not need to implement PROV to use the principle: the reported conversion should remain traceable to the source events and transformation that produced it.
Resolve identity without guessing
The same person can appear with different names, phone formats, email addresses or household contacts. Different people can share a name or contact channel. A portfolio metric cannot solve that ambiguity by merging whatever looks similar.
Use the organization’s approved record-linking process. Give every match a basis and state: confirmed, probable and held, conflicted, or unrelated. If identity remains unresolved, keep the episode unresolved. Do not silently drop it from the denominator or count it twice.
This article does not replace the separate cross-site customer-linking control. It consumes that control’s result. Identity confidence, marketing consent, account authority and facility attribution remain different questions.
Declare which facility gets credit
A customer may first contact Facility North, tour Facility East and rent at Facility South. A call center or digital channel may assist all three. The portfolio needs two distinct dimensions:
- origin facility or channel: where the eligible episode began; and
- rental facility: where the accepted rental occurred.
Do not force those fields to match. The origin view helps evaluate response and demand. The rental-facility view helps explain where the customer ultimately found the right unit or service. At the portfolio level, the episode should convert once unless the contract deliberately defines another unit of analysis.
Transfers require their own rule. A customer moving from one portfolio facility to another may represent retained business, a new rental, a facility-level loss and a facility-level gain. Those can all be useful observations. They should not be blended into ordinary new-customer conversion without disclosure.
Put the window and cohort on the number
A conversion rate needs a time basis. “October conversion” can mean leads created in October that eventually converted, conversions recorded in October regardless of lead date, or leads created and converted within October. Those are different cohorts.
Use an explicit start timestamp, facility time zone, reporting cutoff and allowed observation window. Keep late conversions attached to their episode. When the window is still open, label the cohort provisional rather than treating unfinished journeys as final failures.
The W3C RDF Data Cube recommendation describes statistical observations through dimensions, measures and attributes. Dimensions identify what an observation applies to, measures state what was observed, and attributes help interpret values such as units or status. The standard concerns publishing multidimensional data on the web, not self-storage funnel governance. Its structure is still instructive: a percentage should travel with facility, cohort, channel, time window, contract version and status.
Reconcile the denominator before ranking sites
The denominator is not “whatever leads are left after cleanup.” It is the complete eligible episode population under the contract.
Before release, reconcile:
- expected source systems and channels against what actually arrived;
- raw start events against created episodes;
- duplicates, retries and merged records against their reason codes;
- unresolved identities and facility mappings;
- converted, open, expired, disqualified and canceled dispositions;
- episodes outside the reporting window;
- source totals against facility and portfolio rollups; and
- the released dataset against the dashboard output.
Show unknown and not-evaluated populations. A facility with a failed web-form connector does not have zero web leads. It has incomplete coverage. A facility that failed to classify old records does not have a stronger conversion rate. It has an unresolved denominator.
Use a lead-conversion episode contract
| Contract element | Required decision | Release evidence |
|---|---|---|
| Purpose | Name the exact decision the metric supports | Approved metric owner and use statement |
| Start event | Define the first eligible event and required fields | Source event ID, channel and timestamp |
| Episode identity | Define deduplication and record-linking states | Match basis, confidence state and unresolved queue |
| Conversion event | Name the exact accepted outcome | Governing rental event and acceptance evidence |
| Attribution | Separate origin from rental facility and assisted channels | Stable facility/channel IDs and rule version |
| Window | Set cohort basis, time zone, cutoff and observation period | Cohort ID and open/final status |
| Exclusions | Use governed reason codes; preserve excluded records | Exclusion code, source and reviewer |
| Reconciliation | Compare source events, episodes and dashboard totals | Variance record, verifier and release decision |
The package includes a printable contract and a blank CSV register. The contract is a reporting control, not a sales script or a customer-identity authority.
Practical lead-conversion episode tools
Use this contract before comparing lead conversion across facilities. It defines a reporting episode; it does not authorize customer-record linking, contact, pricing, rental acceptance, or account action.
Download the governed episode registers
Download the blank lead-conversion episode register CSV
Download the explicitly fictional Harbor Ledger Storage Group example CSV
A fictional portfolio example
The following example is entirely fictional. Harbor Ledger Storage Group, its facilities, customers, records, counts, systems, dates and outcomes do not describe a real operator or result.
Four fictional facilities report 200 raw inquiry records for a monthly review. The episode build identifies 18 system retries, 11 confirmed duplicate contacts and five employee test records. Six records remain held because the approved identity process cannot determine whether they belong to existing episodes. The released denominator is not 200 and it is not whatever remains after deleting inconvenient rows. It is the population produced by the approved contract, with every removal and hold reconciled.
One fictional customer first submits a web inquiry attributed to Harbor North, later tours Harbor East and completes an accepted rental at Harbor South. The episode converts once at the portfolio level. The origin dimension remains Harbor North; the rental-facility dimension is Harbor South; Harbor East is recorded as an assisted touch. No facility is allowed to create a second portfolio conversion from the same governed episode.
At the reporting cutoff, the six unresolved identity records remain visible as held. The portfolio does not assign them to the best-performing or worst-performing site. The monthly dashboard publishes the eligible count, converted count, open count, held count, contract version and coverage status together. The fictional example demonstrates the method, not a benchmark.
Govern the definition before coaching the result
Managers should absolutely improve response time, follow-up quality and customer service. But a ranking built on inconsistent episodes can send coaching to the wrong facility. It can reward a site for starting later in the journey, penalize a site for capturing more complete demand or hide a broken channel behind a cleaner percentage.
Define the customer journey once, preserve local facts, separate origin from outcome, keep unresolved records visible and reconcile every release. Then the portfolio can use conversion as an operating measure instead of a contest over who configured the funnel most favorably.
Sources
- U.S. Government Accountability Office, Assessing Data Reliability, GAO-20-283G, official government audit guide published December 16, 2019; accessed November 4, 2026.
- World Wide Web Consortium, PROV-O: The PROV Ontology, W3C Recommendation; accessed November 4, 2026.
- World Wide Web Consortium, The RDF Data Cube Vocabulary, W3C Recommendation; accessed November 4, 2026.
Claim boundary
This article presents an authored operating method, not a claim that modSTORAGE, Facily.ai or any customer has deployed the contract or achieved a conversion, revenue, occupancy or customer result. GAO guidance governs government audit work, and the W3C Recommendations describe general provenance and multidimensional-data models; none is a private self-storage sales standard, certification or legal requirement. Every facility, customer journey, record, count, system and outcome in the example is fictional.
