CONNECTED BUSINESS OPERATIONS
Location records that connect the place to its public information
Maintain addresses, access directions and bilingual location descriptions with a reviewed path to public pages.
A clear responsibility in your daily work
A branch name alone does not help a customer find the entrance or a colleague maintain accurate directions. Tsumira gives each location a record with its own identity, access information and publication state.
Explore each function
See what each capability does, how it works and where it fits into your team’s workflow.
Location directory
Keep location identity, address and practical access information together before publication.
Opening-hours scope
Opening hours are currently company-level information, not independent weekly schedules for every location.
Public location pages
Combine reviewed place details, access guidance and the right public destination.
Make each place identifiable
Create a stable slug and Japanese name with optional English content. Record the address and useful access details such as a station, walking minutes, nearby landmark or coordinates when those facts are known. 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.
- Give each location a maintained identity and route.
Coordinate updates around the location
Keep operational discussion and follow-up associated with the location record instead of hiding a changed entrance in a private message. Decide who checks physical facts and who approves the corresponding public wording. 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.
- Use the location as the context for internal coordination.
Publish accurate practical information
Review the location's status and public projection before sharing its page. Company information supplies opening hours today; individual branch schedules need clear explanatory copy rather than an unsupported assumption of structured per-location hours. 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.
- Public access information must match the real place.
A concrete workflow
Prepare the context
Collect the actual address, entrance details and useful landmarks, then assign responsibility for checking changes.
Review the decision
Prepare the location record and maintained language fields. Keep uncertain access details out until a responsible person confirms them.
Check the result
Review publication and the reachable public page, including how company opening hours and branch-specific explanations appear.
An illustrative working example
Illustrative working example
A firm moves its meeting entrance to another side of the same building. The location owner updates access directions and colleagues discuss the change against the record. The team previews the public page and checks the company-hours panel before sharing the revised link with customers. It does not treat a text correction as live occupancy or availability data.
Questions about this topic
Can we keep more than one location?
The location directory supports separate records and public identities. Give each real place its own accurate address and access explanation.
Are opening hours stored separately for each branch?
Not as structured weekly schedules today. Hours are company-level information; differences require appropriate explanatory content and careful public review.
Do coordinates provide live maps or tracking?
Optional latitude and longitude record a place's position. Their presence alone does not establish live tracking, occupancy or a particular mapping integration.
Can internal notes appear on the public page?
Public rendering uses an allowed projection of published location information, distinct from internal discussion. Still review the public result before announcing a change.
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 Drive
Workflow concept: Review authoritative address and access information before publishing a place.
Microsoft Teams
Workflow concept: Review the preparation step before using an external source: Collect the actual address, entrance details and useful landmarks, then assign responsibility for checking changes.
Slack
Workflow concept: Check the actual destination before sharing this result: Prepare the location record and maintained language fields. Keep uncertain access details out until a responsible person confirms them.