Automating the club's communication

Context

Le Crès Volley-Ball, 6 senior teams. I sit on the club’s board. Match communication relied on the goodwill of a few volunteers, every week, after work.

The problem

The same templates, the same information, the same sources: six identical visuals to redo by hand every week, while the fixtures are already published by the federation. Anything that repeats can be handed to a machine.

What I did

• Needs analysis with the volunteers: what repeats, what changes, who validates what.
• Automatic retrieval of fixtures from the official source, with no re-typing.
• Stories generated in the club’s brand from a template built once, through the Canva connector I had tested earlier, and delivered every Friday to the shared folder.
• A semi-automated communication pipeline: information pulled in, applied to the template, reviewed by the club’s civic-service volunteer in charge of communications, then published on social media.
• A monthly partner newsletter, generated on the same principle.
• Support for the volunteers so they stay in control: they validate, they no longer produce.

The result

Nobody opens a layout tool any more: 6 stories a week, zero clicks to produce them, about 3 hours given back every week to volunteers. 180 partners receive a monthly newsletter the club had never had. The chain then extended to live match streaming, and its building blocks (Canva connector, reviewed generation pipeline) are reused across my other projects.