Build a trans-Tasman food guide around the time you have

A useful inter-city food guide does more than collect restaurant names. It helps a traveler decide where to eat in each stop, without treating Sydney, Wellington or Queenstown as interchangeable. The simplest way to build one is to set the route first, divide the recommendations by city, then group each city's picks by the time a visitor has.

Mate's Table lets people publish venue recommendations and build custom city guides. Its location-based search can be filtered by city, neighborhood or cuisine. Those tools can help creators assemble a route guide, but the editorial work remains yours: choose the trip shape, explain why each place belongs, and make the itinerary usable.

1. Set the route and the reader's time budget

Start with one route, not an all-purpose guide to dining across Australia and New Zealand. For example, define the audience as someone visiting Sydney and Wellington, or traveling between Melbourne and Queenstown. Then decide what kind of trip the guide serves: a short stop, a weekend in each city, or several days with room to explore.

Time budget is a better organizing principle than a long list of “best” venues. A traveler on a short stop needs a few dependable choices near the area they plan to visit. Someone staying longer can use a wider spread of neighborhoods and cuisines. Don't imply that a visitor can reach every recommendation within a set time unless you have checked the route and current conditions.

2. Build the city lists separately

Make a working list for each destination before you combine them into a route. On Mate's Table, search by city and use neighborhood or cuisine filters to narrow the field. The platform covers Sydney, Melbourne, Wellington and Queenstown, among other cities. A creator can also draw on recommendations from locals and city experts rather than relying on a single personal shortlist.

Keep each recommendation attached to its city. Sydney picks should not be presented as a generic Australian dining list, and Wellington choices should retain their local context. If the route includes two cities, make two city guides with titles that clearly signal the destination and trip. Then use the guide text to explain how the picks fit the route. Don't suggest a cross-city sequence is a product feature; the itinerary structure is your editorial plan.

For a sharper selection rule, borrow the discipline of a neighborhood guide: define what qualifies, then make each entry help the reader choose. A narrow brief and clear selection rules are useful starting points even when the guide spans more than one city.

3. Group recommendations by trip length

Within each city, sort the picks into practical bands such as a short stay, a weekend and a longer visit. These are editorial groupings, not claims about how long a meal takes or how quickly a traveler can move between venues. Choose the labels that fit your audience, and use the same labels in every city so readers can compare the options.

• Short stop: Include a small number of recommendations that make sense for the area and the traveler's stated plans. Explain the appeal and what kind of meal it suits.
• Weekend: Add variety across neighborhoods or cuisines. Avoid packing the list so tightly that it reads like a schedule the reader must follow.
• Longer stay: Include additional local picks and less obvious options, with enough context for a visitor to decide what is worth the detour.

For a Queenstown restaurant itinerary, for instance, organize the guide around the length of the stay rather than claiming a fixed route through town. For Sydney–Wellington, repeat the same trip-length structure in both city guides. Readers can then use the relevant section without having to untangle one oversized list.

4. Write the reason beside every pick

A name and address rarely make a recommendation useful to a visitor. Add a concrete reason: a dish to look for, a distinctive setting, a neighborhood connection or the kind of occasion it suits. Keep the claim specific to what you know. If you haven't confirmed current opening hours, menus or availability, don't imply that you have.

Use a consistent test for every entry: would a traveler understand why this place made the guide and when it might fit their trip? Cut entries that cannot pass. A smaller, well-explained list is easier to use than a directory dressed up as an itinerary.

5. Publish the route as a set of useful city guides

Once the selection is ready, publish the venue recommendations and build custom city guides on Mate's Table. Keep each guide focused on one destination, and make the route relationship clear in its title and opening copy. That gives readers a city-specific starting point while preserving the route's broader idea. Do not promise a single combined itinerary experience unless the format you are using supports it.

Finally, check the guide as a traveler would. Can someone identify the right city, find a section for their available time and understand why each recommendation belongs? Local guides and proximity-based search serve different needs, so it is worth being deliberate about the job each entry does. The distinction between a curated guide and map search is especially relevant when a route crosses cities.

The result should not dictate every meal. It should give a visitor a credible local starting point in each stop, with enough structure to make the choice easier. That's the difference between a trans-Tasman food guide and a stack of restaurant names.