Explore the beta

For Dining Teams

You shape the food environment. Daki could help you see how it fits.

Dining programs decide what is cooked, where and when, and how it is described. What is harder to see is whether that food is meeting students’ health goals, tastes, cultures and dietary needs, and where it falls short. Daki wants to learn, with dining teams, whether voluntary, aggregated patterns from students could help.

See the questions we are bringing

No pilot is in place. Daki is preparing an independent, Harvard-specific beta for Spring 2027. Neither Harvard University nor Harvard University Dining Services has endorsed Daki, partnered with it, or agreed to a pilot.

The problem

What is hard to see from behind the counter

Most feedback describes what was taken or what someone chose to complain about. It rarely shows what students needed and could not find, or why an option did not work for them.

This is Daki’s framing. Whether dining teams experience it as a problem is the first thing a conversation needs to establish.

  • Needs that go unmet. A student with a particular goal or requirement who leaves without a meal that fits.
  • Options passed over. Food that was available but did not seem right, and the reason why.
  • Missing information. Ingredients or labels a student needed in order to choose.
  • Who is not being served. Patterns that only appear when many voluntary signals are seen together.
Hypothesis

A voluntary feedback loop, in aggregate only

This is step 4 of Daki’s model: when students get more relevant guidance, the same interactions, shared voluntarily, might show a dining program where its food is and is not meeting needs. That is untested.

  1. Students chooseStudents use Daki to find options that may fit them, and choose, pass on, or say nothing fit.
  2. They decide what to shareSharing is voluntary. Only coded fields, never names, identifiers, dietary profiles or free text.
  3. Patterns, not peopleSignals are aggregated, and groups below a minimum size are hidden.
  4. Your team reviewsYou see needs, barriers and mismatches, with their limits stated.
  5. You decideWhether and how to respond stays entirely with the dining team. Daki does not act on it.

What patterns might show

Questions a team could ask, not instructions

Each of these is a hypothesis. Daki would surface a pattern and its limits. Patterns like these could eventually inform menu planning, labelling and communication conversations, if a team finds them useful.

Hypothesis

Unmet needs

Times and places where students with a particular dietary need or goal often find nothing that fits.

Hypothesis

Information gaps

Items where ingredient or allergen details are missing or unclear, flagged by the people trying to choose.

Hypothesis

Preference and cultural mismatches

Recurring requests that suggest parts of the student body do not see their foods or practices reflected.

Hypothesis

Barriers of time and access

Where schedules or hours stand between students and a meal that would otherwise suit them.

Limitations

What these patterns could not tell you

  • Intentions are not demand. A choice, save or view is not a meal eaten. Daki has no transaction or consumption data.
  • Not a health measure. Patterns describe what students say fits them. They are not nutrition or health outcomes.
  • Self-selected students. People who use Daki may differ from everyone else who eats in the hall.
  • Small numbers. Any group below a minimum size would be hidden, which may leave little to show at first.
  • Possible duplication. Some patterns may add nothing to what teams already know.
  • Never a replacement. Nothing here replaces existing records, staff judgement or official allergen guidance.

Requirements

What a pilot would need

  • Authoritative menu data. An approved export or feed of menus, hours and access rules, so Daki shows what the dining team publishes.
  • Allergen and nutrition records. Shown exactly as the dining team provides them, with the team's own guidance.
  • Privacy and security review. Agreement on what is collected, retention, aggregation thresholds and who sees what.
  • Shared questions. Agreement, before anything starts, on which decisions the patterns are meant to inform.

Daki would not scan IDs, take orders or connect to point-of-sale systems.

Pilot questions

What we would like to learn from you

Before building anything for institutions, Daki wants to understand which patterns would be useful, if any. We welcome dining, student-life, wellness and public-health leaders as learning partners.

  1. Where do you suspect your food environment is not meeting students’ needs, and how do you know today?
  2. Which feedback do you already find actionable, and what is missing?
  3. Which patterns about unmet needs or mismatches would be new to you, and which would be noise?
  4. How do wellness, student-life or public-health colleagues currently share what they learn with dining?
  5. Which systems hold the authoritative menu, allergen and nutrition data?
  6. What privacy, security and approval requirements would apply?
  7. What would make a small pilot too much work for your team?
  8. What would you need to see to consider the patterns useful?
Tell us what would be useful or write to maverickyasuda@college.harvard.edu

Principles

How Daki intends to handle student input

  • Aggregated, not individual. Institutions would see patterns, never a person's history, schedule or profile.
  • Small groups hidden. Counts below a minimum size are not shown.
  • Coded fields only. No names, identifiers, dietary or health details, or free text in institution-facing patterns.
  • Institutional data stays authoritative. Menus, allergens and nutrition information come from the dining team.
  • Voluntary for students. People choose whether to share anything.
  • No sale of identifiable data. Student information is not a product.

Help shape a potential pilot

If you lead dining, food-service operations, student life, wellness or public health, we would value a conversation about what would and would not be useful. Students can join the waitlist to take part in the Spring 2027 beta.

The waitlist is a short Google Form. Joining does not give immediate access; it helps Daki recruit students for the independent Spring 2027 beta and follow-up research.

Lead dining, student life, wellness or public health?

We would like to learn what would be useful to your institution, and to talk about shaping a potential Spring 2027 pilot, before anything is built for you.

Or write to maverickyasuda@college.harvard.edu