CONNECTED BUSINESS OPERATIONS
Keep company hours clear about their current scope
Opening hours are currently company-level information, not independent weekly schedules for every location.
Company hours have a company-wide source
The current location schema has no independent weekly schedule per branch.
Not independently maintained
A clear responsibility in your daily work
A shared business record serves colleagues preparing an offer and people reading the published explanation. Keep those audiences distinct. Check what information is being changed, where the result appears and who should review it. One representative example is more useful than assuming an internal edit has already produced the intended public or commercial result.
Keep the source information clear
The current location model stores identity, address and access details, but does not contain its own weekly opening-hours schedule. Hours are a company fact displayed through the company panel. Start by checking whether the business genuinely shares those hours across the locations you intend to present publicly. A location record contains its own identity and access information: Japanese name, optional English content, address, nearby station, walking time, nearby landmark and optional coordinates. Keep these facts consistent with the physical place. A different entrance or meeting point deserves a clear explanation rather than an ambiguous address.
- Identify which opening hours are shared company information and which locations require a different explanation.
Review the relevant presentation
A location’s own page can present the company panel alongside that place’s access information. Review the wording so readers do not mistake a shared company schedule for a separately maintained branch calendar. Different branch hours, holiday exceptions or staff rotas are not established by the current location schema and should not be advertised as already managed here. Locations move through draft, review and published states. Public pages use a restricted projection of published information; private discussion and internal follow-up belong to the operational record. Check the published route and language after changing a location's name, description or access instructions.
- Review the company panel and the actual location page together, including any risk of misunderstanding.
Do not infer a separate branch calendar
Review visitor expectations when locations do not share the same hours.
Not part of the current location schema
Not implemented hereCheck the actual use
Open each relevant public location destination and compare the shown company information with the actual visitor expectation. If locations operate on different schedules, resolve how that difference will be communicated before promising an automated per-location solution. Accurate limitations are more useful than a precise-looking schedule that the product does not independently maintain. Opening hours are currently company-level information rather than a structured weekly schedule on each location record. If branches differ, explain those differences in appropriate public copy and verify the result. This module does not establish per-branch holiday rules, live occupancy or appointment availability.
- Confirm the published wording with the responsible location owner before directing visitors to it.
A concrete workflow
Prepare the context
Identify which opening hours are shared company information and which locations require a different explanation.
Review the decision
Review the company panel and the actual location page together, including any risk of misunderstanding.
Check the result
Confirm the published wording with the responsible location owner before directing visitors to it.
An illustrative working example
Illustrative working example
A company has two locations, but one workshop accepts visits only by arrangement. The team checks the shared company-hours panel and clarifies the workshop’s actual access expectations. It does not claim that Tsumira currently maintains a separate holiday and weekly timetable for every branch.
Questions about this topic
Can every location have its own weekly hours here?
Not in the current location schema. Opening hours are company-level information; per-location weekly schedules are not implemented there.
Are branch holiday exceptions already managed?
Do not assume this. Independent branch schedules and exception calendars need separate product work and verification.
Does this publish every edit automatically?
Do not assume so. Review draft, review and published state and inspect the actual enabled website destination.
Can AI changes bypass review?
No. Treat proposed wording or updates as reviewable work and respect the user’s actual editing and publication permissions.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
Google Calendar
Workflow concept: Compare visitor expectations with company-level hours; no branch timetable is assumed.
Google Drive
Workflow concept: Review the preparation step before using an external source: Identify which opening hours are shared company information and which locations require a different explanation.
Slack
Workflow concept: Check the actual destination before sharing this result: Review the company panel and the actual location page together, including any risk of misunderstanding.