Rooftop-to-Table: Our Playbook for Sourcing Fresh

Rooftop-to-Table: Why We Grow Where We Serve

We grow on our roof because flavor, freshness, and story matter. Bringing ingredients from upstairs to the plate gives guests a clearer connection to what they eat and to the people who make it.

This playbook lays out how we set up our rooftop garden, choose crops that match our menu, build soil and systems for resilience, and run harvest-to-kitchen operations. We also show how we measure impact and scale responsibly.

These are practical lessons we use every day—decisions we make by default, and the trade-offs that keep us honest. Join us below.

Start with an on-site assessment

We begin by walking the roof at different times of day. Key checks: structural capacity (consult a licensed structural engineer — many roofs support 20–80 psf depending on build), sun maps, drainage, and prevailing wind. In one early build we found a south-west corner got afternoon gusts that shredded seedlings; a simple 3–4′ cedar wind screen cut wind stress and improved survival rates.

Permits, building management, and insurance

We get permits and landlord sign-off before buying soil. That saves time and surprises. Typical asks from building managers: water tie-ins, roof penetrations, weight limits, and emergency egress. We add:

Choosing the footprint and access

We prioritize proximity to service elevators, clear 36–48″ aisles for carts, and a secure supply-drop zone for deliveries. If the only access is a stair, we plan modular beds that break down into manageable sections.

Budgeting hard vs. soft costs

We separate budgets into hard costs (structural reinforcements, decking, planters like Lechuza or EarthBox for lightweight containment, irrigation lines, controllers such as Hunter X-Core or Rain Bird ESP) and soft costs (consulting fees, permitting, staff training). Plan a 15–25% contingency for unknowns.

Building the right team

Partnerships reduce surprises. Our core collaborators:

Site-specific choices that mattered for us

Wind mitigation (mesh screens or living hedges), lockable storage near the roof, and a scheduled maintenance lift for heavy deliveries became non-negotiables.

With the roof mapped and partners aligned, we move on to choosing the crops that will thrive in that specific microclimate—and pair best with our menu.

With the roof mapped and partners in place, our next job is matching plants to plates. We make those decisions at the pass—literally—by collaborating daily with chefs so the rooftop reliably feeds the menu.

Daily chef collaboration

We meet with the culinary team every morning or set a weekly planning huddle. Chefs flag high-impact menu needs (pesto basil, cocktail garnishes, delicate lettuces) and we translate that into planting blocks and harvest windows. Real example: a 30 ft² basil block in summer often supplies the bulk of pesto and garnish demand on a 100-cover night.

High-impact crops we prioritize

Scheduling, rotation, and trials

We balance continuous-harvest beds (salad greens, basil) with seasonal or trial plots. Staggered sowing every 7–14 days keeps supply steady. We rotate by plant family to avoid flavor fatigue and pest buildup—brassicas follow roots, herbs rotate out every 6–8 weeks for a fresh block.

Variety choice for urban microclimates

We pick varieties known for heat or wind tolerance (e.g., loose-leaf vs. tight-heading lettuces), and trial seeds in small plots before committing. If a cultivar struggles, we swap rather than over-manage.

Matching yield to portions & minimizing waste

We build simple yield tables (oz per sq ft) tied to portion sizes and set “harvest-to-order” windows. Cut-and-come-again plus small-batch microgreen trays keep waste low.

Next, we tune soil mixes, irrigation, and system controls so that the chosen palette thrives on the rooftop.

We tune the rooftop’s technical backbone so plants are forgiving and maintenance stays lean. Below are the practical choices and routines that make that possible.

Soil vs. soilless: what we use and why

We use two main substrates:

Practical tip: a 50:50 coir:compost blend cut our watering frequency and gave seedlings more resilience in wind-prone zones.

Containers & modular beds

We favor modular 4’x2′ planters on aluminum frames with HDPE liners or fabric Smart Pots for deep-root crops—lightweight, repairable, and reconfigurable. Casters or pallet-mounts let us rearrange beds seasonally without a crane.

Irrigation & fertigation basics

Our rooftop uses pressure-compensating drip lines (Netafim PC emitters), a filtered supply with a pressure regulator, and a proportional injector (Dosatron D25) for soluble fertilizers. Controllers are simple — a Wi‑Fi timer like Rachio or a commercial irrigation controller depending on scale.

Water-saving & catchment

Rainwater is collected into IBC tote tanks with first-flush diverters and a submersible pump to header tanks. Mulch and drip irrigation reduce evapotranspiration; we cap irrigation windows in early morning for efficiency.

Sustainable practices & monitoring

These systems let us focus on reliable harvests and quick pivots—next we’ll walk through the routine that takes produce from harvest into the kitchen.

We unpack the day-to-day choreography that turns rooftop produce into plated dishes.

Harvest timing & cadence

We harvest to peak flavor—early morning for tender lettuces and late morning for sun-warmed tomatoes. Weekly harvest schedules are posted in the shed and synced to a shared Google Calendar so growers and chefs know who’s picking when. Quick anecdote: a heat spike once forced a two-hour earlier start; shifting pickup windows kept our basil from wilting.

Post-harvest handling

We follow a simple cool-clean-label routine:

Inventory & communication

We track harvests in Airtable (mobile forms) linked to QR-coded tags on crates. Chefs get a daily harvest note: yields, oddities, and special requests. For ordering overlays we use a shared Google Sheet for par levels; surplus flags trigger a “surplus” channel in Slack for menu team re-use offers.

Portioning & recipe flexibility

Portioning standards live on the pass: grams per plate (we use an Ohaus Scout scale) and pre-portion trays for service. For variable yields we maintain small recipe buffers—e.g., swap microgreens with pea shoots, or scale vinaigrette ratios by weight, not headcount.

Training, safety & contingencies

We run weekly harvest walks and quarterly plating demos so line cooks treat rooftop produce as a premium item. Food safety: potable water, sanitizer (50–200 ppm chlorine), and batch traceability tied to QR logs. Contingencies: fast-freeze surplus herbs with a FoodSaver vacuum sealer, source backups from our farmer partners, and deploy row covers or beneficials quickly when pests or extreme weather hit.

This workflow keeps the kitchen confident that what arrives from the roof will perform—fresh, traceable, and kitchen-ready.

What we measure (and how)

We go beyond pretty beds. Key KPIs we track:

Each KPI plugs into our Airtable harvest records and a simple Google Data Studio dashboard so chefs and managers see trends at a glance.

Listening to staff and diners

Numbers tell one story; people tell another. We run short post-service check-ins, chef taste panels, and a quarterly diner survey with one open question: “Which rooftop item surprised you?” Those qualitative notes guide crop swaps—if line cooks report a microgreen that bruises easily, we replace it with a sturdier alternative.

Reporting to stakeholders

Our quarterly packet combines: dashboard snapshots, two-page culinary stories, and high-res photos. For investors or partners we add payback timelines and a carbon-miles estimate. Simple, visual reports build trust and justify expansion.

When to scale — bed expansion vs partnerships

We consider expanding when:

We partner when space, regulations, or seasonality make expansion inefficient.

Keeping it authentic and responsible

Standardize SOPs, create short training videos, and pilot each new site. Share our playbook openly but keep menus locally rooted—authenticity survives when each rooftop tells its own story.

Next, we invite you to read how we bring that rooftop story to the table.

Bringing the Rooftop to the Table: Our Invitation

We close by saying: start small, learn fast. Run a pilot plot that lets chefs test varieties and menus; keep the chef at the center of every growing and scheduling choice. Treat logistics as tools for creativity, and let storytelling—about seasonality, people, and place—be part of service.

Rooftop sourcing reshapes culture as much as supply chains. Adapt these practices to your context, measure what matters, and share your wins and setbacks with the community. Join us: experiment, iterate, and bring fresh rooftop stories to your table. We’ll learn together and keep improving.