Designing an On-Demand Luggage Storage Product: From Partnerships to Pricing

For storage marketplaces, a strong luggage storage product is not just a convenience layer. It is a full-service, trust-first transaction that has to balance location, access speed, security, and price in a way that feels easy for travelers and operationally clean for partners. The best products in this category behave like a marketplace, a logistics network, and a lightweight insurance platform at the same time. That is why launches often succeed or fail on partnership design and pricing architecture, not on the booking UI alone. If you are building for event travelers, layover passengers, or same-day urban visitors, the product needs to solve a very specific problem: where to leave bags safely for a few hours without friction, surprises, or unclear liability.

Demand is real. Travelers increasingly want practical in-person experiences even as AI expands digital convenience, and that creates more movement, more events, and more micro-stays between check-in and check-out. For a broader context on how real-world experiences are becoming more valuable, see our source note on AI and travel meaning. Event-driven travel is also a major driver, which makes luggage storage especially relevant around conferences, sports, trade shows, and city festivals. Our guide on event parking playbooks is useful here because luggage storage shares the same demand spikes, booking windows, and location sensitivity. The practical question for a marketplace is simple: how do you design a supply side that scales fast while still giving travelers confidence?

This guide breaks the product down step by step: which partners to recruit, how to price by hour or day, what insurance and liability language should look like, and where AI personalization can improve conversion without making the experience feel invasive. We will also show how to connect luggage storage to fulfillment workflows, hotel concierge systems, retail counters, and event itineraries. Along the way, we will reference operational patterns from adjacent marketplace categories such as integration-led software, reliability engineering for logistics, and outcome-based pricing procurement because the same principles apply when you are moving from concept to revenue.

1. Define the Use Case Before You Define the Marketplace

Map the real traveler jobs to be done

A luggage storage product works best when it is anchored to a precise use case, not a vague promise of “secure storage anywhere.” The most common jobs are short gaps between hotel checkout and evening departure, city exploration during a long layover, and event-day storage when venues restrict large bags. These are distinct behaviors, and they each imply different inventory, hours of operation, and price sensitivity. If you do not separate them early, your pricing and supply decisions will blur together and create a weak marketplace for everyone.

Think of the product as a sequence of moments: search, trust, drop-off, retrieval, and exception handling. Each moment has a different conversion risk. For example, an airport transfer traveler cares most about speed and pickup certainty, while a conference attendee cares more about proximity to the venue and fast QR-code check-in. You can learn from long-layover planning patterns because the same urgency and time-boxed needs shape storage decisions. For travelers who are already navigating uncertainty, see also practical travel disruption guidance, since operational clarity matters more than raw feature count.

Segment by traveler type, not just location

Most marketplaces start by segmenting supply geography, but demand segmentation is equally important. A city-center tourist, a business traveler, and an event traveler may all search within the same radius, yet they will respond to different value propositions. A tourist may value price and reviews, while a business traveler may care about invoicing and brand trust, and an event traveler may prioritize express drop-off in a crowded, time-constrained environment. This is why the product should support dynamic landing pages by use case, not just by district.

For example, a day-storage offer near a convention center should look different from a same-day airport pickup flow. The event traveler could be shown a “book in 30 seconds” path with clear opening hours, whereas the business traveler might see account-level billing and more explicit insurance terms. This approach mirrors how high-performing marketplaces personalize offers based on context, similar to the strategy discussed in A/B testing product pages at scale and AI transparency reporting. The lesson is to prioritize clarity and trust over novelty.

Set a minimum viable promise

Your minimum viable promise should be specific enough to support operations. A good version might be: “Secure luggage storage within 10 minutes of your search, with open hours that fit same-day retrieval.” That tells the user the product is immediate, proximate, and operationally dependable. It also gives you a measurable standard for supply quality. If a partner cannot support fast retrieval windows or cannot staff the location reliably, they should not be in the first launch cohort.

Launch teams often overestimate how much inventory they need and underestimate how much service inconsistency hurts retention. A better strategy is to define a limited, high-confidence service zone and expand only after your NPS, retrieval success rates, and support tickets stabilize. This is similar to how real-time capacity systems must keep demand and supply in sync, because hidden delays become customer pain very quickly. Your first product version should feel curated, not sprawling.

2. Build a Partnership Model That Can Scale

Hotels: the highest-trust anchor partners

Hotels are often the best anchor partners for an on-demand luggage storage network because they already understand bag handling, front-desk service, and traveler expectations. They also tend to have staff on-site throughout the day, which reduces the risk of inaccessible storage. For a marketplace, hotel partnerships can provide premium supply in dense tourist and business districts with strong trust signals. They may be especially effective near transit hubs where travelers need a convenient handoff before check-in or after checkout.

The downside is that hotels can be slower to onboard and more selective about liability. They may demand detailed SOPs, insurance certificates, training materials, and a revenue share that reflects the service burden. To prepare, build a partner kit with operating hours, bag acceptance rules, prohibited items policy, escalation contacts, and compensation structure. This is where a trust-first approach similar to regulated-industry deployment checklists becomes useful. Hotels do not want a vague partnership; they want a controlled operating model.

Retail, convenience, and pharmacy partners: fast density plays

Retail partners bring scale quickly, especially in city cores and shopping districts. Convenience stores, pharmacies, copy shops, and tourist-heavy retail locations can support short dwell times and improve network density in neighborhoods where hotels are sparse. The key advantage is accessibility. These partners often have longer hours than hotels and are already set up for walk-in customers. That makes them ideal for event travelers who need same-day drop-off within a short radius of a venue or station.

However, retail partners need simpler workflows. They cannot absorb hotel-style complexity, so your product should present a scan-and-handoff process with limited item categories and straightforward compensation. If the partner must think too much at the counter, adoption falls. A well-designed partner portal should let them confirm bag count, storage duration, and pickup status in a few taps. For operational inspiration, the way restaurants improve listings to capture more demand is a good analogy: visibility and simplicity drive conversions.

Venues, coworking spaces, and local operators

Event venues, coworking spaces, and attraction operators can become high-value supply nodes if your marketplace wants to own specific demand peaks. A convention center bag hold program, for example, can serve attendees before hotel check-in, during early arrivals, or between sessions and dinners. Coworking spaces can serve day-pass users, consultants, and founders who need somewhere to keep luggage before travel. This partner class is especially useful for business-heavy destinations where the day is fragmented across meetings.

When you add local operators, you should compare them on service reliability, not just foot traffic. Their opening hours, staffing discipline, and claims history matter more than their brand name. That is why it helps to borrow the thinking behind vendor diligence playbooks and careful vendor assessment frameworks: the marketplace must vet operational maturity, not just signed interest. In luggage storage, a single bad handoff can damage trust across the whole supply pool.

3. Design the Inventory and Service Model

On-demand lockers versus staffed storage

There are two primary inventory models: self-serve lockers and staffed storage locations. On-demand lockers are great for speed, predictable availability, and lower labor costs. They are especially attractive near transit stations, airports, and event districts where travelers want quick access without queueing. Staffed storage, by contrast, creates more flexibility for oversized bags, irregular pickup times, and customer support. Many successful marketplaces use both, then route users based on bag size, duration, and time of day.

Do not assume lockers are always the superior model. Lockers work best when the demand profile is standardized and the item dimensions are predictable. But luggage comes in many shapes, and a traveler may show up with a stroller, musical instrument, or sports equipment that does not fit a standard locker. For that reason, a hybrid model often wins: lockers for speed, staffed locations for flexibility. That mirrors how operational analytics and fleet reliability principles are used together to balance performance and exception handling.

Capacity rules and acceptance standards

Every partner location needs a clear capacity policy. How many bags can be stored at one time? What dimensions qualify as cabin-size, checked-size, or oversized? Are valuables excluded? Can a partner accept multiple items per booking? These questions matter because capacity mismatches are one of the biggest causes of cancellation, refund pressure, and customer complaints. The marketplace should define acceptance rules upfront and present them in both partner materials and consumer-facing listings.

You should also create service-level rules for late pickup and abandoned items. For example, a bag left overnight might trigger a higher holding fee, while unclaimed property after a specific period could follow local legal guidance. Clear policy reduces conflict, especially in time-sensitive settings such as event travel. For adjacent trust and service design, see how trust at checkout lowers friction by setting expectations before money changes hands. Luggage storage needs the same upfront transparency.

Operational workflows from check-in to retrieval

At the operational level, the workflow should be boring in the best way possible. A traveler books, receives a confirmation QR code, arrives, scans or verifies identity, drops bags, and gets a clear retrieval path. The partner confirms item count and storage start time, while the marketplace logs the transaction and keeps support visibility. If a partner is using a POS or partner dashboard, the process should take less than two minutes. Anything longer begins to feel like a manual exception rather than a marketplace service.

You can make this easier by treating luggage storage like a micro-fulfillment workflow. The same integration mindset used in integration-first software and storage security design applies here. The point is not just taking a booking; the point is creating a dependable chain of custody that can scale across many partner types without losing control.

4. Create a Pricing Strategy That Matches Demand and Risk

Hourly, half-day, and full-day pricing

Pricing strategy is where many luggage storage products either win margin or lose trust. The market usually supports three core models: hourly pricing for short stops, half-day pricing for flexible city use, and full-day pricing for travelers with uncertain schedules. Hourly pricing is the simplest to understand, but it can create complexity around minimum charges and extensions. Full-day pricing tends to be easier to operationalize and can better match traveler behavior around check-out and late flights.

A smart marketplace typically uses a mix of the three. For example, you might price a city-center locker at a low entry rate for two hours, then step into a half-day bundle that feels more economical for visitors who plan to explore. Event travelers, by contrast, may respond better to fixed event-day rates because their needs are anchored to the venue schedule. This is similar to how consumer buying behavior changes under pressure, as discussed in price-tracking strategy articles. Clear thresholds help customers decide quickly.

Dynamic pricing without damaging trust

Dynamic pricing can improve yield, but it must be used carefully. If travelers feel manipulated by surge pricing during events or bad weather, they may abandon the product or switch to a competitor. The safest approach is bounded dynamic pricing, where rates change within a transparent range based on demand, proximity, and duration. You can also reserve premium pricing for convenience features like immediate access, 24/7 pickup, or venue-adjacent listings rather than simply charging more because demand is high.

AI can support this by recommending price bands based on historical demand and estimated trip context, but the user should still see a clear explanation of why an option costs more. This is where the mindset from outcome-based pricing procurement and AI transparency becomes important. If the algorithm affects pricing, the product should make that logic understandable enough to build trust.

Partner economics and marketplace take rate

Your pricing strategy must leave room for partner revenue, marketplace margin, payment processing, support, insurance, and acquisition costs. A common mistake is to set customer-facing rates without calculating the operational cost of a failed pickup, rebooking, or lost item claim. The right model starts with unit economics: expected average booking value, partner payout, acquisition cost, support cost per booking, and claim reserve. If the numbers only work on high volume, your product will be fragile.

As a launch rule, establish separate economics for locker partners and staffed partners. Lockers may support thinner margins but higher throughput, while staffed partners may need higher payouts due to labor. You can compare this to the balancing act in deposit systems and revenue diversification under price pressure: the structure has to be sustainable before it can be scalable. If you want enterprise adoption later, your margin model must be explainable and defensible.

5. Treat Insurance and Liability as Product Features

What luggage insurance should and should not cover

Insurance for luggage is not just a legal appendix. It is a conversion lever. Travelers want to know what happens if a bag is damaged, stolen, delayed, or mishandled. Your product should clearly state what is covered, what is excluded, and what documentation is required for a claim. Typical exclusions include prohibited items, cash, jewelry above a threshold, and items that were already damaged when stored. If your policy is vague, support costs rise and conversion falls because the user cannot assess risk.

A practical structure is to offer base coverage with every booking and then optional upsell coverage for higher-value items or longer storage windows. This feels more trustworthy than forcing travelers to buy separate insurance after booking. The important part is that claim steps should be simple and time-bound. For adjacent coverage logic, see how rental coverage works, because users already understand layered protection in mobility products.

Chain of custody and partner responsibility

Liability does not start at the claim form; it starts at the handoff. The marketplace should log who accepted the item, at what time, under what conditions, and with what confirmation method. Photos, bag counts, and QR confirmations can significantly reduce disputes. If a location receives bags manually, the process should still create a digital record. This is especially important if you later scale to enterprise accounts or want to offer stronger insurance terms.

Partner contracts should specify how responsibility is shared for bag acceptance, storage conditions, unauthorized access, and retrieval exceptions. If the partner violates accepted procedures, the marketplace needs clear recourse. For a useful adjacent framework, study cargo insurance strategy updates, because the same concept of chain-of-custody risk applies even though the objects are smaller. The key is making liability operationally visible, not abstract.

Claims workflow and customer support design

Claims should be rare, but the system has to be ready. A good claims workflow lets customers submit evidence quickly, see claim status, and understand timelines. Support teams need a playbook for common issues: late pickup, bag misidentification, partner closure, and weather-related disruptions. If the claims experience is slow or defensive, it erodes the very trust the insurance feature was supposed to create. Better products use automation to gather photos, timestamps, and partner notes immediately after the incident.

This is where AI can help with categorization and triage, but not with final judgment in every case. A human-in-the-loop approach is better for edge cases and fraud prevention. For a useful operating analogy, see human-in-the-loop explainability patterns. The goal is consistent, auditable decision-making that travelers can understand.

6. Use AI Personalization to Increase Conversion and Relevance

Personalized recommendations by itinerary and context

AI personalization can materially improve a luggage storage product when used to reduce decision fatigue. If the system knows the user is near a train station, arriving before hotel check-in, or attending an event with bag restrictions, it can prioritize the most relevant storage option. That means fewer search results, better match quality, and higher booking rates. The best personalization feels like a helpful concierge, not an aggressive recommender engine.

You can personalize by arrival time, search location, device context, and event proximity. For example, if a user searches near a stadium on game day, the system can suggest instant-access lockers, time-limited event bundles, or partners with extended hours. For a business traveler in a downtown district, it might recommend staffed storage with invoice support and predictable retrieval windows. This mirrors the practical use of AI in adjacent consumer tools, such as AI advisor safety patterns and voice-enabled analytics UX, where the promise is relevance without confusion.

Predictive demand, inventory placement, and surge prevention

AI can also help operations teams decide where to add supply before demand spikes. If historical data shows that a convention center, airport corridor, or festival district fills up on certain dates, the marketplace can recruit more partner capacity in advance or temporarily promote nearby listings. This improves fill rates and avoids the worst kind of customer experience: a user who has already decided to buy but cannot find available storage. Forecasting should combine seasonality, event calendars, transit data, and local booking trends.

That said, predictive systems should always have a human override. If the model suggests a rate spike or lower-ranked options during a high-demand event, operations should review the policy to avoid breaking trust. It is useful to read about automating insights into actions because the same principle applies: prediction is valuable only if it leads to a better operational decision. AI should expand good judgment, not replace it blindly.

AI-assisted support and multilingual experiences

Luggage storage is often used by international travelers, and AI can improve support through multilingual FAQs, automatic partner messaging, and simple issue classification. This is not just a convenience feature; it reduces friction at the exact moment when customers are most stressed. A good AI layer can help users understand storage rules, opening hours, size limits, and claim procedures in their preferred language. It can also help partners respond faster without needing a full-time multilingual support staff.

For marketplaces with cross-border demand, this is a major advantage. The ability to localize policy explanations and generate precise retrieval instructions can materially reduce errors. To think about broader AI infrastructure maturity, it is worth reviewing cloud and AI development trends and storage readiness for autonomous workflows. The business case is straightforward: better relevance, less support load, and higher repeat bookings.

7. Integrate With the Traveler Journey and Adjacent Operations

Fulfillment integration for e-commerce and business users

One overlooked opportunity is to connect luggage storage with fulfillment integration. Business travelers, exhibitors, and small teams often carry product samples, booth materials, marketing kits, or returns that behave more like micro-fulfillment items than personal luggage. If your marketplace can support labeling, temporary holding, last-mile handoff, or return pickup coordination, it becomes more valuable to B2B users. This can be especially powerful in convention districts where event attendance, shipping needs, and local storage overlap.

Think of the product as part storage, part transfer point. A venue-adjacent partner might receive exhibit materials in the morning, hold personal bags during the day, and release both after the event ends. That is a stronger proposition than plain luggage holding because it helps buyers reduce dead time and missed connections. The integration-first lesson from document automation platforms applies directly: connectivity is more valuable than raw feature count.

Hotel, mobility, and itinerary integrations

To make the product feel native to travel, integrate with hotel booking confirmations, transit instructions, calendar events, and mobile itinerary apps. A traveler should not have to hunt for storage in a separate mental workflow. Instead, the product can surface storage suggestions as part of the trip plan, such as after hotel checkout or before a late departure. This kind of contextual placement improves conversion because it appears when the need is obvious.

In practice, that means building APIs and embed options, not just a consumer website. Hotels may want a concierge dashboard, venues may want a QR poster or widget, and travel platforms may want an API for nearby storage suggestions. Similar marketplace logic is visible in how listing optimization and seasonal market cycles shape demand capture. The more naturally you fit into the traveler’s plan, the less acquisition friction you create.

Support for event travelers and short-duration demand spikes

Event travelers are one of the best segments for luggage storage because the need is urgent, temporary, and easy to understand. They often arrive before check-in, need to move freely between sessions, and cannot carry bags into restricted venues. For these users, the product should emphasize instant booking, visible walking time to the venue, and guaranteed retrieval windows. This is not the same as general tourist storage; it is operationally closer to parking, shuttle, and access-control products.

You can build event-specific experiences around calendars and venue maps. For example, the product might suggest storage near a conference center 24 to 48 hours before an event, then adjust prices and placement dynamically as check-in times approach. This is similar to how event parking systems manage demand around big dates. When the event ends, the marketplace can encourage return pickups through smart notifications and temporary extended hours.

8. Launch, Measure, and Improve the Product Like a Marketplace Operator

What to measure in the first 90 days

In the first 90 days, track search-to-book conversion, inventory utilization, cancellation rate, average bag value, claim frequency, partner uptime, support tickets per booking, and retrieval success rate. These metrics tell you whether the marketplace is functioning as a dependable service or merely generating clicks. You should also monitor demand by time block and geography so you can see where storage demand is concentrated. If your best supply is always sold out while lower-quality partners sit idle, you have a placement problem, not a demand problem.

A useful way to manage this is to set weekly operational reviews with both product and partner teams. Review the top failed searches, the top complaint categories, and the highest-value routes or venues. This is analogous to the disciplined feedback loops used in reliability engineering and incident automation. The best early signals are usually boring and operational, which is exactly what you want.

Rollout playbook: one neighborhood, one use case, one partner type

Do not launch everywhere at once. Start with one dense district and one primary use case, such as event storage near a convention zone or airport-adjacent day storage near a major transit hub. Then recruit one partner type first, usually hotels or retail, so the operating model stays consistent. Once your workflow is stable, add the second partner type and use those learnings to refine routing and pricing. This staged rollout lowers complexity and gives you better data for product decisions.

The same logic applies to partner recruitment. Start with operators who are already comfortable with service procedures and are willing to follow standardized handoff rules. Build case studies from the initial locations, then use them to win larger or more fragmented partners. For inspiration on phased market expansion and localized fit, see localized value-area planning and diversification patterns in travel hubs.

Optimize through partner feedback, not just demand data

Demand data tells you what travelers want; partner feedback tells you what the supply side can sustain. If a location has repeated staffing gaps, slow retrievals, or poor bag handling discipline, the marketplace should intervene early. Sometimes the best fix is not more demand generation but simpler packaging or a narrower service promise. This is especially true for retail partners who may not want to manage highly variable storage complexity.

Use partner scorecards that combine customer ratings, acceptance speed, compliance with SOPs, and support responsiveness. Tie incentives to operational quality instead of raw booking volume alone. That protects the marketplace from becoming a race to the bottom. You can think of this as applying the same value discipline seen in automation risk management and budget resilience planning: growth only matters if it remains sustainable.

9. Recommended Product Blueprint for a First Launch

Minimum viable feature set

A launch-ready luggage storage product should include location search, date and time selection, bag size filters, transparent pricing, insurance terms, instant booking confirmation, retrieval instructions, and support contact pathways. It should also show walking time from nearby transit and major event venues. If possible, include a partner trust badge based on verification, opening hours, and review history. This feature set is enough to create confidence without overwhelming the user.

Do not launch with too many optional extras. You want a clean path from search to booking to drop-off. Over time, you can add waitlist notifications, multi-bag discounts, business invoices, and storage extension controls. For product teams that want to keep quality high while iterating, the design logic in page testing and AI transparency is worth borrowing.

Pricing and insurance defaults that build trust

Start with simple defaults: one clear base price, a clearly disclosed insurance layer, and a visible cost for extra bags or oversized items. If pricing is too clever, travelers assume there are hidden fees. If insurance is hidden behind a long disclosure, they may assume the product is risky. The best version is upfront and almost boring: here is the price, here is what is covered, here is how to retrieve your items. That simplicity can be a major differentiator in travel and mobility markets.

Make sure the policy pages are readable on mobile, since many bookings happen on the move. Every message should be short enough for a traveler standing outside a hotel or venue. Keep the copy operational, not promotional. That is how trust grows.

Metrics that prove product-market fit

Once live, watch for repeat usage across the same travelers, referral behavior from hotel staff or venue teams, and increasing adoption during predictable event windows. If the product is working, partners will start recommending it because it reduces front-desk friction, and customers will return because it saves time. Strong repeat behavior is especially important in travel, where users may not need storage every day, but they do need a trustworthy option when a trip includes a layover, gap day, or event.

As your network matures, you can explore adjacent offers like package holding, rental returns, and light fulfillment support. That is where a simple luggage product can evolve into a broader urban logistics platform. The key is to earn the right to expand by proving reliability first.

10. Practical Build Checklist for Product and Partnerships Teams

Partnership checklist

Before launch, verify that each partner has the right hours, access control, staff training, and fallback contacts. Confirm whether the site can handle locker installation, staff-only storage, or mixed inventory. Review customer-facing placement so the location is easy to find and the signage is accurate. Finally, make sure the partner understands claims escalation and prohibited item handling.

This is the same kind of structured diligence used in vendor review workflows. If you cannot document the partner’s operating readiness, do not onboard them yet. A smaller, stronger network will outperform a larger, weaker one every time.

Pricing checklist

Confirm base rate, duration bands, oversize fees, cancellation policy, and insurance inclusion before you launch. Then model scenario-based economics for a low-volume day, a typical weekday, and an event surge. If the marketplace loses money on support or claims in the middle scenario, the pricing needs revision. Pricing should reward simplicity and predictability, not complexity.

Test whether users understand the offer in under ten seconds. If they cannot tell what they will pay or what happens if plans change, the page needs work. The most effective pricing strategy is the one that removes hesitation quickly.

AI and integration checklist

Use AI where it improves relevance, forecasting, and support, but keep explanations transparent. Integrate with booking confirmation systems, event calendars, hotel workflows, and mobile itinerary tools. If you can, add multilingual support and automated partner notifications so the service feels smooth in busy situations. The objective is not to wow users with AI; it is to make the service feel instant and well matched to their trip context.

In many ways, your product is doing what modern infrastructure platforms do: coordinating capacity, trust, and timing in real time. That is why borrowing ideas from capacity fabrics and secure autonomous workflows can help a travel marketplace think more clearly about scale.

Conclusion: Build the Storage Product Travelers Can Trust in One Decision

A successful luggage storage product is not built by adding more listings. It is built by creating a dependable service model around the moments travelers actually experience: arrival, waiting, exploring, attending, and leaving. That means recruiting the right partners, shaping prices around duration and context, writing clear insurance rules, and using AI to reduce friction rather than add noise. It also means treating every operational detail as part of the product, because in storage marketplaces, the handoff is the product.

If you want the category to scale, start with trust-first supply and disciplined economics. Then layer in personalization, integrations, and event-aware merchandising once the core workflow is stable. The marketplaces that win will be the ones that combine convenience with clarity, and automation with accountability. That is how an on-demand locker network becomes a durable travel utility instead of just another listing page.

Pro Tip: In luggage storage, the fastest route to product-market fit is not the lowest price. It is the clearest promise: nearest available location, obvious coverage, and a retrieval process that feels safer than carrying the bags around all day.

FAQ

Related Reading

• Event parking playbook: what big operators do (and what travelers should expect) - Learn how peak-demand routing and access control translate to luggage storage.
• Why Integration Capabilities Matter More Than Feature Count in Document Automation - A useful model for building marketplace integrations that actually convert.
• The Reliability Stack: Applying SRE Principles to Fleet and Logistics Software - See how reliability thinking improves handoffs and customer trust.
• Selecting an AI Agent Under Outcome-Based Pricing: Procurement Questions That Protect Ops - Helpful for teams evaluating AI vendors for pricing and personalization.
• Insurance After Attacks: Updating Marine and Cargo Insurance Strategies for Today's Threat Landscape - A strong reference for chain-of-custody and coverage design.