This is a multipart message in MIME format. ------=_NextPart_000_0A2F_01DA0CB2.349F5460 Content-Type: multipart/alternative; boundary="----=_NextPart_001_0A30_01DA0CB2.349F5460" ------=_NextPart_001_0A30_01DA0CB2.349F5460 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable No concerns from my end, but we should be sure to share w/Collections, = Help Desk, and other impacted stakeholders when we make that change to = ensure all partiers are aware. Also, it will be important to understand = how we will notify clients and where that communication will be stored = to ensure we can provide a copy of that from Help Desk to the client, = should it come up later that a client wasn=E2=80=99t notified.=20 =20 Elizabeth Clark=20 Director, CI & Transformation Long Term Care Insurance, Onboarding =20 TheKey =20 =20 From: kristy.poyner@thekey.com =20 Sent: Wednesday, November 1, 2023 9:25 AM To: 'Timothy Thomas' ; eclark@thekey.com Cc: 'Michelle Kenaga' Subject: RE: Winnipeg Billing periods =20 Hi Tim, =20 Thank you for reaching out. From a billing perspective updating Winnipeg = from Semi-monthly to weekly billing would not be an issue. Adding the CI = team in case there are any other factors of this move that I am not = aware of. =20 Thanks, Kristy Poyner Billing Manager Kristy.Poyner@thekey.com=20 =20 =20 From: Timothy Thomas >=20 Sent: Tuesday, October 31, 2023 2:33 PM To: Kristy Poyner > Subject: Winnipeg Billing periods =20 Hi Kristy, =20 Will there be an opportunity, perhaps on Jan 1, to move Winnipeg to a = weekly billing cycle? This will help line up with payroll this giving us = line of sight on overtime and sync with the rest of Canada. =20 Thanks =20 --=20 Tim Thomas Head of Canada Division Please note my email has changed: tt@TheKey.com (514) 591-9387 =09 TheKey.ca =20 =20 ------=_NextPart_001_0A30_01DA0CB2.349F5460 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} No concerns from my end, but = we should be sure to share w/Collections, Help Desk, and other impacted = stakeholders when we make that change to ensure all partiers are aware. = Also, it will be important to understand how we will notify clients and = where that communication will be stored to ensure we can provide a copy = of that from Help Desk to the client, should it come up later that a = client wasn=E2=80=99t notified. <span = style=3D'font-size:10.0pt;font-family:"Calibri = Light",sans-serif;mso-ligatur