Editorial methodology
New York changes quickly. Journey v2 combines reviewed place records, official links, route and opening-window checks, automatic event lifecycle rules, and cautious human review without pretending that city information never changes.
Last reviewed
Layer one
Events are stored with valid dates and, where needed, specific occurrence dates. Once those dates have passed, the event stops appearing in current recommendations and moves into the historical catalog automatically.
Layer two
Every week, TodayNYC refreshes a deterministic catalog snapshot and checks event status, required fields, duplicate records, closure and availability flags, official links, and the planning information used by the route engine.
Three-hour engine
Mary starts from a Manhattan area, landmark, supported transport hub, or optional device location. The engine presents a small set of curated two-stop combinations, then rechecks the route to the first stop, the walking link between stages, published opening windows, and whether the complete plan still fits.
Weekend engine
The weekend path combines selected events, a weather outlook, practical city notices, and official source links for the coming weekend. Expired material is not treated as a current recommendation.
The automatic layer has a narrow job: keep date-driven events out of current recommendations after they expire. It does not silently rewrite opening hours, invent queue times, or replace an official source just because a website responds differently on one automated check. Those changes can affect a real visitor’s day, so ambiguous findings are held for review.
Venue and organizer websites are the preferred references for event dates, opening information, access rules, reservations, and temporary closures. Some official sites block automated requests or place visitors in a virtual queue. A failed automated check is therefore treated as a signal to investigate, not immediate proof that a venue has closed or that its listing is wrong.
Travel, entry, and queue times are estimates designed to make a route more realistic. They are not live subway predictions or guarantees of admission. Where waiting conditions vary, TodayNYC can use an editorial range rather than a single optimistic number. Ticketed events, popular venues, and time-sensitive plans should always be confirmed with the official venue before traveling.
A confirmed quick plan can include attributed context about architecture, history, art and music, immigration, politics, crime, and infrastructure matched to its stops or available walking geometry. This editorial layer explains what a visitor may notice along the way. It does not change venue ranking, opening logic, travel time, or the order of the plan.
The three-hour experience is currently strongest in reviewed Manhattan microzones and is not equally complete at every hour. When a full two-stop plan cannot be confirmed, TodayNYC should say so rather than publish a partial route. The free-form Mary chat remains available for follow-ups, but the two primary product starts are the prepared three-hour plans and the current weekend briefing.
Dynamic guides show a visible update date and link directly to current official event information. The sitemap records a page’s last significant update rather than changing every URL’s date simply to make the site appear fresh. This keeps the public page, its structured data, and its sitemap aligned.
Opening hours, weather closures, ticket inventory, transit disruption, age restrictions, and event access can change after publication. TodayNYC helps narrow the options and build a practical route, but the linked official source remains the final check for anything time-sensitive.
Ready to plan?