The short answer

Start with the property, not the cabin. Deeper investment makes sense only when the land, market, approval path, infrastructure and owner brief point to a workable operating idea. Structure selection, delivery planning and guest preparation follow from that evidence.

A cabin gets the photographs. The project lives in the less visible work around it: access, approvals, utilities, site planning, service and demand.

That order comes from the original UNIKOST one-page site. It now lives in an article that can be sourced, corrected and connected to deeper field guides as the work develops.

The first zoning call guide turns the parcel and operating idea into questions a local planning office can classify.

We kept the useful decision logic. Former supplier names, addresses, performance promises and unverified project claims stay out of this public edition.

Four working rules

The order matters more than the catalogue.

01

Land before catalogue

Review access, demand, approvals and infrastructure before choosing a structure.

02

A destination is a system

The unit has to work with the site, service model and the way guests will use the place.

03

Curate the technical pathway

Test each design against the site brief, the delivery route and the applicable rules.

04

Opening is part of delivery

Construction handover is one milestone. The project opens when the team can reliably host its first guest.

01

Land & feasibility

Qualify the land before designing the destination.

Beautiful land gets attention. The first review has to look past the view and into the practical questions: guest and delivery access, land use, usable terrain, utilities, wastewater, life-safety access and environmental constraints. It also needs a believable reason for guests to make the trip.

A recognizable demand driver or existing guest flow

A plausible planning and operating pathway

Physical access that matches the delivery concept

Infrastructure scope that can be priced and phased

An owner brief with clear goals, constraints and decision authority

Signals worth investigating
  • A memorable landscape or an existing reason to visit
  • Usable area, practical access and room to phase
  • A credible utility or infrastructure strategy
  • An owner with a defined operating role
Questions to resolve early
  • Delivery and emergency access are still unclear
  • Local hospitality use has not been reviewed
  • Wastewater, power or water remain unpriced
  • The concept depends only on the unit, not the reason to stay

A first screen identifies the questions worth taking to local professionals. It cannot serve as a permit opinion.

02

Positioning

Define what guests are travelling for.

A visual mood is only the beginning. Name the guest, the occasion, the expected stay, the role of the landscape and the level of service. A two-key retreat might use the same structure as a wellness cluster or a lodge expansion. The plans behind those projects will still be different.

Architecture should make the hospitality idea easy to read. It cannot invent that idea after the plan is already fixed.
03

Project definition

Build the project logic before selecting the product.

Skip false precision in the first business case. Write down the demand hypothesis, positioning, first-phase key count, shared amenities, site and infrastructure scope, delivery limits, staffing model, contingency and decision points. That becomes the brief for comparing structures.

The owner defines

Purpose, property, capital and operating role.

Who makes decisions, what already exists on site, what success means and who will ultimately host the guest.

The project process resolves

Feasibility, concept, systems and sequence.

What must be tested, which specialists are needed, what belongs in the first phase and how the work reaches opening.

04

Structures & compliance

Choose a technical pathway, then judge the floor plan.

The same guest brief may be expressed through a structure placed on a light engineered foundation or through an eligible design re-engineered as a single-chassis Park Model RV. These are different product and approval pathways, and they should remain separate in the project analysis.

Light foundation

Review the applicable building-code route, engineering, foundation, utilities, site inspection and local occupancy requirements.

Explore structure systems
Wheeled chassis

Review model eligibility, ANSI A119.5 engineering pathway, manufacturer program, transport envelope and separate local placement and operating rules.

Explore UNIKO
05

Site & service design

Design an operating system, not a collection of units.

The masterplan has to work on an ordinary operating day. Trace guest privacy, arrival, housekeeping, maintenance, waste, parking, lighting and emergency access through the same plan. Phase one should feel complete on opening day and still leave a sensible route for growth.

06

Execution

Coordinate the handoffs before they become gaps.

Put supplier scope, local design responsibility, site work, utilities, permits, production, logistics, placement, connections, commissioning and the punch list into one written sequence. Several companies may share the work. Every task still needs an owner, an input, a deadline and an acceptance point.

01

Screen

Is there enough evidence to spend time on this property?

02

Feasibility

Can demand, approvals, infrastructure and the owner brief support one coherent direction?

03

Concept

What should this place be, for whom, and what belongs in the first phase?

04

Technical path

Which structure class and delivery method fit the site reality?

05

Delivery

Are scope, responsibilities, sequence and local professional inputs defined?

06

Opening

Can the team deliver the promised guest experience consistently?

07

Hospitality readiness

Prepare the first guest while the place is being built.

Work on the booking flow, service standards, recovery procedures, team roles, housekeeping rhythm and opening content before handover. A finished structure marks the end of construction. Opening day depends on a prepared team and a guest experience that holds together.

See the full project process

Frequently asked

Questions to settle early.

Should I choose cabins before reviewing the land?

Usually not. Keep a preferred model as a reference, but expect access, approvals, utilities, site work, climate, transport and the intended guest experience to change the shortlist.

Is a Park Model RV automatically approved for a glamping site?

No. Product-standard compliance and site permission are separate questions. Local land use, placement, utility, fire, health and operating rules still need to be confirmed for the specific property.

Does every project need to open at its final size?

No. The first phase can stand on its own, test demand and operations, and leave the infrastructure and site logic needed for later growth.

When should hospitality planning begin?

Begin before the final design is locked. Guest arrival, housekeeping, service access, storage, communications, maintenance and team training all change the physical brief.

Do utilities need to be installed before the first review?

No. Use the first review to document what exists, identify realistic extension or off-grid options, and define the infrastructure strategy well enough to price and test.

Do I need zoning approval before I submit the property?

No. Share confirmed facts, items under review and open questions. Qualified local professionals still need to check the site-specific path.

Can I ask about structures without a full development engagement?

Yes. Structures-only has its own qualification path. We still need basic site information because transport, placement and service connections affect model fit.

What launch date should I enter?

Enter the date by which you need a decision. It is not an opening promise. Approvals, design, infrastructure, production, logistics and operating readiness all affect timing.

Editorial note

The foundation chapter will keep changing.

This chapter keeps the useful decision sequence from the former one-page site and removes outdated commercial claims. Later chapters take individual questions deeper, add jurisdictional boundaries and link back to the relevant step here.

Review status: Editorial framework published and humanization-reviewed. Jurisdiction-specific requirements remain in research and are not represented here as project approval advice.