Published 3 June 2026 - 6 min read - by the KanriFlow Team
Consortia with partners in six or more countries lose hours to time-zone confusion and invitations that never reach the right people. How the KanriFlow calendar shows every event in Kyiv and CET time, filters by work package and emails the invitation to every partner contact on the event's work packages.
undefined
The KanriFlow calendar exists to make that synchronisation cost small. Every event lives in one place, shows two clocks, can be filtered per work package and is one click away from each partner's inbox and Google Calendar. This article walks through how each piece works. If you are still looking for a date, start with Meeting Polls; for the case against scheduling by email, see Stop Scheduling Meetings by Email.
Every event states both clocks - Kyiv and CET - so partners never convert hours in their head.
When an event is ready, the organiser clicks Invite Participants. KanriFlow collects the email addresses of every partner contact listed on the event's work packages and sends one invitation in BCC. The subject carries the project acronym, the date and the CET time; the body states the time in Kyiv and CET, the format, the location or meeting link and the work packages, with an Add to Google Calendar button.
One click sends the invitation to every contact on the event's work packages. No distribution lists to maintain.
No partner is going to abandon the calendar they use for the rest of their work. Every event in KanriFlow has a GCal button that opens Google Calendar with the event pre-filled: the title prefixed with the project acronym (for example WIDERA-CAPACITY - Steering committee #5), the correct time, the meeting link as the location and the work packages and grant number in the description. A coordinator running three projects can tell at a glance which consortium a meeting belongs to.
Steering committee scheduling. A quarterly SC meeting across six countries typically costs a coordinator 30-60 minutes of email per occurrence: confirming the time zone, re-sending the details to people who missed them, fixing the link. With the event in the calendar and one invitation to every WP contact, that drops to the few minutes it takes to create the event.
Onboarding new team members. A new partner representative added to the contact list sees the project calendar the day they join and receives the next invitations automatically, instead of a stream of forwarded emails.
Keep partner contacts current. Invitations go to the contacts listed on each work package, so the contact list is the distribution list. Review it at every partner change.
Find the time first, then publish it. For meetings with many participants, run a meeting poll; the confirmed slot lands in the calendar with all its details.
Attach the agenda to the event. Upload the agenda before the meeting and the minutes after it, so the event and its paper trail stay together.
Invite through the calendar, not by forwarding links. Use Invite Participants rather than forwarding a Zoom link in a separate email. The invitation carries the same details everyone sees in the calendar.
Screenshots are from a demo workspace; project, partner and team data are fictitious.
All articles | Create your workspace
KanriFlow home | All EU programmes | Live demo | Contact