“Keep bundled services together when the source requires it” is a specific information-maintenance task. The service catalogue editor needs to connect the public detail with business-approved catalogue text, then decide what a visitor should be told. The aim is a clear, supported result that can be checked after saving.
Set the boundary of this ai service extraction check
To keep bundled services together when the source requires it, first distinguish the affected public detail from neighbouring information that serves a different purpose. Compare each extracted service with the actual source menu or approved offering. Record the question in ordinary language before editing. This keeps the review focused when several profile fields appear to need attention, and lets a second person understand why this change is being proposed.
Build a usable source note
The source note for “Keep bundled services together when the source requires it” should identify business-approved catalogue text, the relevant date or version if known, and the person able to confirm the arrangement. Preserve distinctions between consultations, follow-ups, seasonal options and price units instead of flattening them into invented standalone services. Keep a source claim separate from the wording you plan to publish. When one part remains unconfirmed, write down that gap explicitly instead of allowing the rest of the evidence to imply that everything has been established.
Test the likely misunderstanding
Consider “Keep bundled services together when the source requires it” as a hypothetical editing exercise: several directories can repeat the same old claim because they copied one source. Agreement among copies is weaker than independent accountable confirmation. This is an illustrative decision test, not a report about a real business. Ask the service catalogue editor to explain which part of the current display could produce that misunderstanding and which supported detail would prevent it. A cosmetic rewrite alone may leave the underlying confusion intact.
Prepare the public-facing change
For the actual edit to keep bundled services together when the source requires it, preserve the smallest useful distinction and avoid changing unrelated approved facts. Record origin and date, and preserve unresolved disagreement rather than counting repeated claims. If the platform supports a dedicated field, use it for its intended purpose. Where explanatory text is needed, put the qualification close to the information it limits; visitors should not need to discover it in an unrelated section.
Finish with a reproducible check
Treat “Keep bundled services together when the source requires it” as complete only after reviewing what the public record now shows. Compare the saved result with business-approved catalogue text, including any formatting or truncation introduced by the platform. Record the affected field, the visible outcome and any remaining question for the service catalogue editor. A submitted update and a visible correction are separate milestones; retain the distinction so that a later editor does not assume a pending change is already live.
Before marking this task complete
- Can a new visitor understand the result of “Keep bundled services together when the source requires it”?
- Is the relevant ai service extraction detail supported by business-approved catalogue text?
- Are the service catalogue editor’s unresolved questions kept separate from the approved change?