Member information, opening hours and service details carry the destination's decisions, yet they rarely reach a board agenda. What a board can actually decide about them.
A tourism organization's board approves budgets, hires directors, and answers for the destination's reputation. Yet the information those decisions run on, the member listings, the opening hours, the service details that visitors and AI assistants alike read, rarely appears on a board agenda at all.
This article argues that it should, and describes what a board can actually decide about it. Not which fields a member record should contain, and not how the operational team should do its work: those belong to the team. The board's role is narrower and more important, framing objectives, assigning responsibilities, resourcing the upkeep, and asking for accounts.
Québec is not starting from zero. The Government of Québec runs SIT Québec, a platform that manages and distributes the tourism data supplied by tourism organizations, feeds Bonjour Québec and the visitor-information network, and publishes open datasets through Données Québec.
That fact shapes everything a board should ask. The question is not whether to build a tourism database. It is whether the information your organization contributes to the existing infrastructure is complete enough, current enough, and validated by the right people, and whether your team has the means to keep it that way.
A board that frames the discussion as "build versus don't build" will answer the wrong question. The productive framing is contribution and quality: how updates arrive, how they are checked, and how the result serves the visitors who plan trips around it.
Data work fails most often because responsibilities are assumed rather than assigned. Four levels are worth separating explicitly.
The board frames. It sets the objective, for example, that the organization's member information be verifiably current before each season, assigns ownership of that objective to the director general, and asks for periodic reports. The board does not design forms or choose software.
Management organizes. The director general decides how the objective will be met: who follows up with members, what the review workflow looks like, what tools are used, and how results are measured against the framing the board set.
Teams and contributors do the work. Member businesses know their own offering. The organization's team clarifies, transcribes into structured fields, validates, and distributes. Their effort is the real cost of data quality, and it deserves to be counted.
Technical partners support. Any tool involved, including ISOD Enrichissement, discussed below, operates under agreed interfaces and validation rules. A partner never replaces the organization's validation responsibility; it prepares work for that validation.
When these levels blur, boards end up debating field definitions while nobody owns the follow-up. Keeping them separate is the single most useful thing a board can do.
Board members do not need to become data specialists. They do need a vocabulary precise enough that decisions mean the same thing to everyone.
Five distinctions carry most of the weight. Completeness: the necessary details are present. Freshness: they still reflect reality. Structure: the information is organized consistently, not described in prose. Validation: the responsible people have checked it. Reuse: it can serve more than one authorized channel without being entered again.
France's DATAtourisme platform is a useful comparison here, as a governance example, not a scoreboard. DATAtourisme aggregates tourism information from more than forty territorial databases, normalises it into a common format, and distributes it for reuse; its own documentation is explicit that it is not a replacement for local systems but a channel between producers and reusers. What the French example shows is the value of shared meaning: producers keep control of their data and its pace, and the common format is what lets a third party like Cartes IGN consume events without re-entry.
What it does not show is a measured lag of Québec behind France, and this article makes no such claim. The comparison is about how governance and shared formats let locally maintained information travel, not about any country's performance.
Data quality is not an abstraction. It shows up in a handful of observable indicators, each of which can be reported without new infrastructure.
Five are worth a board's attention. First, priority information confirmed: what share of member records had their key details, names, dates, hours, booking conditions, confirmed within the current cycle. Second, correction delay: how long an identified error takes to reach the published channels. Third, contribution effort: how much time members and staff spend providing and clarifying updates. Fourth, validation load: how much review the organization's team performs to keep accuracy. Fifth, reuse: how many authorized services the same validated information reaches without re-entry.
These are recommendations for what a management diagnostic could track, not reported results of any product. A first diagnostic would simply establish the starting values, the baseline a later pilot or workflow change would be measured against.
The board does not need those numbers every month. It needs them at decided moments: before a season, after a campaign, or when a tool or partnership changes the workflow. What matters is that someone is accountable for producing them and that the definitions stay stable enough to compare.
Everything above compresses into a mandate a board could adopt in one motion: direct management to conduct a limited diagnostic of the organization's member information, completeness, freshness, validation status, and the effort its upkeep requires, and to report back with a proposed pilot, its scope, its validation responsibilities, and its success criteria, before any commitment is made.
Such a mandate changes no field definitions, purchases nothing, and commits to no vendor. What it does is make the information layer a managed asset instead of an ambient concern, with an owner, a baseline, and a decision point.
If a pilot follows, its terms would be the organization's own: which members participate, what is measured, and what would justify continuing, adjusting, or stopping. A pilot defined this way can be evaluated on its own evidence rather than on a demonstration.
This article is published in the context of ISOD Enrichissement, a product concept co-developed by UPentreprise and Storyline Communication. ISOD proposes a conversational approach: a member business describes an update in its own words, the interaction identifies what is missing or ambiguous, the information is prepared as structured fields, and the organization's team validates before anything is distributed. Integration arrangements with existing systems such as SIT Québec and Tourinsoft would be defined per interface and permission, and remain to be scoped.
That is a description of the approach to be evaluated, not a result. No bookings figure, no time saving, and no AI-citation outcome is claimed here, and any pilot would be measured against the organization's own baseline, the one a diagnostic like the mandate above would establish.
The reason this article exists is that the board conversation is where that evaluation belongs. A tool that proposes to reduce clarification effort and structure member updates should be examined against a framed objective, assigned responsibilities, and declared measurement criteria, the very things a board is positioned to set.
Doesn't the government already handle this? The infrastructure exists, and that is not the problem. SIT Québec manages and distributes tourism data; the open question is how member updates reach it, how they are validated, and who accounts for their upkeep. That is an organizational responsibility no platform can assume.
Isn't this the staff's job, not the board's? The daily work belongs to the team. What belongs to the board is the framing: the objective, the ownership, the resources for the upkeep, and the moments when results are reported. Boards that skip that framing discover the work is happening, or not happening, without anyone being accountable for it.
What would a first step cost? A limited diagnostic asks management to establish the baseline: the current state of member records and the effort their upkeep requires. It requires time from the team, and it commits to nothing else. Any tool decision, including about ISOD Enrichissement, would come after that baseline exists, not before.
The diagnostic above is also the baseline a product evaluation would need. ISOD Enrichissement describes the workflow such an evaluation would apply to, what a member contributes, what your team validates, and what stays with the systems already in place.
The infrastructure exists, and that is not the problem. SIT Québec manages and distributes tourism data; the open question is how member updates reach it, how they are validated, and who accounts for their upkeep. That is an organizational responsibility no platform can assume.
The daily work belongs to the team. What belongs to the board is the framing: the objective, the ownership, the resources for the upkeep, and the moments when results are reported. Boards that skip that framing discover the work is happening, or not happening, without anyone being accountable for it.
A limited diagnostic asks management to establish the baseline: the current state of member records and the effort their upkeep requires. It requires time from the team, and it commits to nothing else. Any tool decision, including about ISOD Enrichissement, would come after that baseline exists, not before.
