Evergreen Thai shared dishes arranged for a downtown Toronto group meal

University Avenue / Discovery District

Catering for University Avenue Hospitals & MaRS, Toronto

Plan catering for University Avenue hospitals, clinics, MaRS and Discovery District offices in downtown Toronto: shift timing, hospital access, menus, quantities.

Downtown Toronto Locations 2026-04-27 Published by Jackson

A hospital department meeting at noon, a research-group lunch at MaRS, a clinic in-service that runs across two shift breaks: catering along University Avenue has to survive tighter schedules and slower building access than a typical office order. Food that reaches the lobby on time but the breakroom 15 minutes late has failed. Catering for University Avenue hospitals and Discovery District offices is a delivered group meal planned around shift timing, department-level handoff, and mixed dietary needs, so a team with 20 minutes to eat can serve itself and get back to the floor. Evergreen Thai Kitchen & Bar has cooked for hospital, research, and campus teams from 175 Dundas St W, a few blocks from the hospital row, since 2007.

Why University Avenue and the Discovery District need their own catering plan

University Avenue packs more distinct catering situations into a few blocks than almost any corridor in the city, and the same order can succeed at one address and fail at the next. Between Queen and College the avenue lines up hospitals, professional offices, provincial and civic buildings, UofT-adjacent departments, and, at the College Street end, MaRS and the innovation offices of the Discovery District. Planning corporate catering in Toronto for this corridor means planning around how each of those groups eats, not just what they eat.

The demand types along the avenue and into the district:

  • hospitals and clinics with staggered breaks and security desks
  • professional offices and government departments with boardroom lunches
  • research labs and innovation teams with workshop schedules
  • training sessions and in-service days that run across two breaks
  • campus-adjacent meetings that mix faculty, staff, and students
  • condo and event rooms near Queen’s Park

Each group needs a different service flow even when the tray list looks identical. A hospital breakroom needs covered food that survives an hour of staggered arrivals. A MaRS workshop needs a self-serve table that resets fast between sessions. A civic boardroom needs an exact room-ready time and a clean setup.

The corridor also shares one physical constraint: slower building access than a typical office tower. Lobby security, visitor passes, freight elevators, and department-level routing add real minutes to every delivery, so the plan starts with logistics and only then moves to the menu.

Catering for University Avenue hospitals and clinics

Hospital and clinic catering is a scheduling problem before it is a menu problem. Teams at Toronto General, Mount Sinai, SickKids, Princess Margaret, and Toronto Western eat in 20 to 30 minute windows between rounds, meetings, and shift changes, and a department rarely eats as one wave. Food has to be warm at the start of the first break and still worth eating at the end of the last one.

What hospital teams consistently ask for:

  • warm food rather than cold sandwich trays
  • vegetarian and vegan options that feel like real meals
  • every tray labelled for fast self-serve
  • a quiet, compact setup that fits a breakroom counter or meeting table
  • mixed-diet coverage in one delivery, not two caterers on the same floor
  • arrival timing that holds even when the meeting starts 5 minutes late

Build the menu for staggered breaks. Curries, fried rice, Pad See Ew, and Basil Stir Fry hold their texture in covered trays for an hour; Crispy Calamari and Spring Rolls are best served to the first wave and should not carry the meal. Tom Kha or Tom Yum soup in a vegetarian preparation works well for evening shifts in the cooler months.

Label trays with the words a nurse reads in two seconds: “Vegetarian,” “Vegan,” “Mild,” “Spicy,” “Contains nuts.” A busy department should be able to serve itself without a 10-minute briefing from the organizer, because the organizer is often back on the floor before the second wave arrives. Size the order to the full headcount rather than to the number who will be in the room at any one moment; staggered eating does not reduce total appetite.

Hospital delivery timing, security, and handoff

For hospital deliveries, schedule arrival 15 to 25 minutes before the lunch window opens. The drive from 175 Dundas St W to most University Avenue hospitals takes 8 to 12 minutes, but the lobby, security desk, visitor-pass check, and elevator queue add another 5 to 10, and the difference between a 12:00 and a 12:15 lunch matters when staff must be back on the unit by 12:30.

Hospital delivery checklist:

  • confirm the receiving department, floor, and named contact
  • give a receiver phone and a backup, since department lines go unanswered at noon
  • describe any security or visitor-pass procedure at the lobby
  • note whether the driver should use a freight or service elevator
  • set the room-ready time, not just a delivery time
  • reconfirm headcount and timing the day before
  • for orders of 30 or more, give the kitchen 3 to 5 days

Most late deliveries in this corridor come from handoff ambiguity rather than kitchen timing. “Toronto General, 12:00” is not an address; “Toronto General, Eaton wing, 6th floor lounge, ask for Priya at the unit desk, backup phone below” is. Assign one owner for day-of communication so the driver never has to guess who to call.

The same discipline applies to the clinics and medical offices set back from the avenue on Elm, Gerrard, and Murray, where a small reception desk is the only handoff point. The office catering checklist for downtown Toronto covers delivery notes, loading docks, and dietary intake in more depth, and the advice transfers directly to hospital buildings.

Catering near MaRS and Discovery District offices

MaRS and the surrounding Discovery District offices order for reasons that hospitals rarely do: client meetings, startup all-hands, cross-functional workshops, and appreciation events for research and innovation teams. The hard part is not cuisine selection but execution under a fixed agenda, so the plan starts by naming the event intent.

Define the intent first, because each one changes the tray priorities:

  • Office lunch: speed and self-serve flow, 4 to 5 dishes, room-ready 10 minutes before the break
  • Client or partner meeting: clean shared setup, milder spice as the default, one standout dish such as Massaman Curry or Chicken Satay
  • Workshop or training day: portion stability across sessions, easy reset, food that holds between a late-running morning and the break
  • Team social or appreciation event: abundance and variety, appetizers alongside mains, Mango Salad and Pineapple Fried Rice for colour
  • Hybrid anchor day: mixed preferences and a faster reset, since attendance swings with who came in

Then design for service flow. Seated meetings and casual buffet-style tables serve differently, single-wave and staggered arrivals need different holding times, and a 15-minute setup window rules out anything that needs assembly. Logistics at MaRS and the College Street buildings are simpler than at the hospitals, but still confirm the entrance, elevator or lobby process, receiver and backup contact, and acceptable delivery window before choosing dishes.

Research and lab groups on the UofT side of the district, from the medical sciences buildings to the departments around Queen’s Park, follow the same intent-first model; the catering near UofT page covers department lunches and campus delivery details, and the TMU, UofT, and University Avenue catering guide handles student groups and faculty events.

A stable menu for this corridor has four parts, and the order in which they are chosen matters. Physicians, nurses, researchers, and admin staff bring vegetarian, vegan, and mixed-diet members to almost every department, so the vegetarian tray is a headline, not a side.

The structure:

  1. one or two broad-appeal mains (Cashew Chicken, Basil Stir Fry, Green Curry, or Panang Curry)
  2. one substantial vegetarian-friendly tray with full volume (Mixed Vegetable Curry, Tofu Basil, or Vegetable Pad Thai)
  3. one rice or noodle base (jasmine rice, Vegetable Fried Rice, or Pad See Ew)
  4. one balancing side or freshness component (Mango Salad, Golden Tofu, or Spring Rolls)

A sample order for 25 hospital staff built on that structure: one large tray of Green Curry with tofu over jasmine rice, one large tray of Vegetable Pad Thai, one tray of Basil Stir Fry with chicken for the mixed-diet share of the team, one tray of Golden Tofu as a labelled vegan layer, one tray of Spring Rolls for the first wave, and steamed jasmine rice as the shared base. The mistake to avoid is a counter crowded with small appetizer platters that satisfies nobody.

Vegetarian and vegan versions of the noodle, curry, and rice dishes are available on request; ask when ordering, because fish sauce and oyster sauce are in the kitchen and vegan trays have to be flagged at order time. Thai curries at Evergreen use coconut milk rather than dairy, which suits dairy-free staff. When a department needs a fully vegetarian Chinese and Thai layer, Vegedelight, the sister restaurant next door on Dundas, can add vegetable stir-fries, tofu and mushroom claypot dishes, and vegetable dumplings to the same delivery, which avoids two caterers arriving at the same floor. The mixed dietary preferences guide covers how to split vegetarian and non-vegetarian volume for a half-and-half team.

Quantity, budget, and recurring department lunches

Quantity fails when it is estimated from the invitation list instead of real attendance and event format. Size the order from a headcount range, expected appetite, and whether the food is the main meal or a snack spread, then add variety. For hospital teams, size to the full department even though it eats in waves; for MaRS workshops, size to confirmed attendees plus a small buffer for drop-ins.

Common mistakes in this corridor:

  • choosing dish names before confirming logistics
  • sizing vegetarian volume only to the declared vegetarians, when non-vegetarian colleagues share those trays just as often
  • ignoring staggered attendance when setting the room-ready time
  • treating budget and quantity as separate decisions
  • leaving nobody in charge of the handoff phone

The guest count and budget catering guide lists tray counts for 10, 20, 30, and 50 guests and the planning ranges to attach to them.

Recurring lunches are where this corridor differs most from the Financial District. Many departments, clinic teams, and research groups book weekly or biweekly office catering in Toronto as a standing order, which locks in the dietary headcount, a dish rotation, and a delivery slot so that reorders take one call. Rotate one dish per week so the template never feels repetitive, keep the vegetarian anchor constant, and give 48 to 72 hours of notice for changes in team size, holiday closures, or a special event. Group orders over CAD 200 within 5 km of 175 Dundas St W qualify for direct group delivery, which covers the whole avenue and the Discovery District.

A reusable planning flow for every order

One standardized flow prevents most of the failures that show up in this corridor, and it takes 5 minutes to run before each order:

  1. Confirm the headcount range and the attendance risk.
  2. Consolidate dietary notes in one message, not across several emails.
  3. Decide the service format: shared trays, a mixed setup, or boxed meals for a session that eats at desks.
  4. Validate the building details: entrance, floor, handoff contact, backup phone.
  5. Confirm the room-ready time and the setup surface.
  6. Name one owner for day-of communication.

For tower and hospital orders, the recommended data fields are the building name and full address, the department or company with floor and suite, primary and backup contacts, the preferred handoff point (lobby, concierge, reception, or unit desk), and the target in-room readiness time. Teams that supply those fields consistently see far smoother reorders.

Match the plan to the scenario: a boardroom lunch prioritizes exact room-ready time and clean shared setup; a workshop prioritizes easy self-serve flow and portion stability; a hybrid anchor day prioritizes mixed preferences and a fast reset; a campus or condo event prioritizes handoff clarity and practical tray formats.

After the meal, capture a 2-minute debrief: was the food room-ready on time, did the dietary labels match what people needed, what was the leftover ratio versus attendance, and did the serving flow work. That record turns the next order into a repeat rather than a rebuild, and it is the reason a good short-distance kitchen keeps hot food arriving hot for a department year after year.

Why a Dundas Street kitchen works for this corridor

Short routes are the practical advantage for University Avenue and Discovery District groups. Evergreen Thai Kitchen & Bar sits at 175 Dundas St W, steps from St Patrick station and a few blocks from the hospital row, so the drive is measured in minutes rather than across-town traffic, and a meeting that starts late still gets food at temperature. The kitchen has served downtown hospital, research, civic, and campus-adjacent teams since 2007 and is open Monday to Saturday from 11am to 9pm and Sunday from 3pm to 9pm, which covers evening shift meals and after-hours workshop dinners.

Party trays, buffet-style setups, and boxed meals on request scale from a 10-person clinic meeting to a 100-person research symposium; for 500 or more, contact the kitchen early to confirm capacity and timing. Whatever the size, the order goes better when the department, floor, receiver phones, room-ready time, and dietary notes arrive with the request.

To plan a hospital, clinic, MaRS, or Discovery District order, get a catering quote with your building, headcount range, timing, and dietary notes, or call 416-581-8668 to set up a recurring department lunch.

FAQ

Questions people usually ask before they order in this situation.

How long does catering delivery take to University Avenue hospitals?

Driving from Evergreen Thai at 175 Dundas St W to Toronto General, Mount Sinai, SickKids, Princess Margaret, or Toronto Western typically takes 8 to 12 minutes, plus 5 to 10 minutes for the lobby, security desk, and elevators. Schedule arrival 15 to 25 minutes before the meal starts and name the receiving department and contact so the driver clears the building quickly.

Can a hospital department or research group set up a recurring weekly lunch?

Yes. Many University Avenue departments, clinic teams, and research groups run weekly or biweekly standing orders. A standing order locks in the dietary headcount, dish rotation, and delivery slot, so reorders take one call. Changes for team size, holiday closures, or special events need 48 to 72 hours of notice, and larger orders of 30 or more should give 3 to 5 days.

What details does a hospital or MaRS catering order need?

Send the building or hospital name, department or company, floor and room, receiver phone plus a backup, preferred handoff point, room-ready time, headcount range, dietary notes, and budget range. For hospitals, add any visitor-pass or security procedure at the lobby. Handoff ambiguity, not kitchen timing, causes most late deliveries in this corridor.

Can vegetarian and vegan options be included for hospital and research teams?

Yes. Vegetarian and vegan versions of curries, noodles, and rice dishes are available on request; state vegan needs when ordering because fish sauce and oyster sauce are used in the kitchen. Thai curries use coconut milk, not dairy. For a fully vegetarian Chinese and Thai layer, Vegedelight next door on Dundas can be added to the same delivery, with a separately labelled vegan tray.

How do we plan catering around shift changes and staggered breaks?

Choose dishes that hold quality for an hour in covered trays, such as curries, fried rice, and stir-fries, rather than crispy items that fade. Set the room-ready time for the start of the first break, label every tray so each wave can self-serve without a briefing, and size the order to the full headcount even though nobody eats at once.

Testimonial

Google review highlights plus the live Google Business Profile map.

Use this section as the trust block near the bottom of the page: real review quotes people can click through, plus the live map listing where visitors can see the business profile, directions, photos, and public review activity.

Google Business Profile

Evergreen Thai Kitchen & Bar

The embedded map below points to the business profile instead of only the street address, so visitors can check directions, photos, and Google review context from the listing.

CallOrder onlineQuote