
Potentially—but negotiate the group’s entities and workflows explicitly rather than treating common ownership as permission to share. Hudl’s published organisational terms illustrate why this matters: they address authorised users and restrictions on making products or content available to third parties. Your executed agreement and its applicable schedules require separate review. (hudl.com)
Recommended sequence:
- Inventory contracts, modules, users, renewal dates and local requirements by club.
- Separate shared analytical work from club-confidential recruitment work.
- Request a group entitlement schedule naming participating entities.
- Test central ingestion and local access separately.
- Specify external consultants, temporary staff and newly acquired clubs.
- Agree the treatment of a club leaving the group.
- Compare consolidated cost with the cost of preserving essential local exceptions.
Test permissions with realistic cases: can an analyst see the shared dataset but not another club’s confidential shortlist? Can departing staff be removed without losing institutional reports? Can a local club export its own work at exit?
Report contract savings, implementation costs and operational changes separately. A lower group invoice is not sufficient if the proposed package removes a competition or workflow that one club requires.
Sources cited on this page
- hudl.comwww.hudl.com
