--0000000000002851560630cc51d5 Content-Type: multipart/alternative; boundary="0000000000002851510630cc51d3" --0000000000002851510630cc51d3 Content-Type: text/plain; charset="UTF-8" Hi All, I've updated the SOC model through Feb 2025 performance. The model is still using the same baseline methodology, but it is now updated to distribute the delta in billed hours in February throughout the rest of the year. I've also made 2 enhancements to the model: 1. *Using Monthly Current Tier instead of Current Tier* - I have updated the baseline metrics to reference the monthly current tier for clients instead of their most recent current tier, still using the same time period. This allows the baselines to lock in instead of update as clients' most recent current tier adjusts. - I have also updated the actuals to reference the monthly current tier so it does not impact historical look backs on actuals. 2. *Rounding up SOC volume* - In the original version, I was simply letting excel round. I have updated this to always round up. This is because if the model outputs 1.4 starts needed, you would need 2 starts to hit compared to 1 client. - This slightly impacts the org wide volume, but primarily impacts the by site view. Most sites' total increased by 10-15 SOC annually due to rounding up instead of allowing general rounding rules. As a reminder, this model is predicting SOC needed to reach the billed hours total by the end of the year as each month's delta is being evenly distributed. This means that hitting the month's SOC model target does not guarantee the hours target would be reached since the existing delta is ramped, not immediate. For example, in order to hit the immediate target in Feb as an organization with catch up in census etc, we would have needed 1,099 SOC vs the 823 the model states is needed with the ramped approach. Happy to hop on a call to go through this with anyone, please reach out! Thanks, Sarah -- Sarah Powers Director, Strategic Analytics TheKey.com [image: TheKey] --0000000000002851510630cc51d3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi All, I've update= d the SOC model through Feb 2025 performance. The model is still using the = same baseline methodology, but it is now updated to distribute=C2=A0the del= ta in billed hours in February throughout the rest of the year. I've also made 2 enhancements to the model: 1.=C2=A0 Using Monthly Current Tier instead of Current Tier =C2=A0I have updated the ba= seline metrics to reference the monthly current tier for clients instead of= their most recent current tier, still using the same time period. This all= ows the baselines to lock in instead of update as clients' most recent = current tier adjusts. I have also update= d the actuals to reference the monthly=C2=A0current tier so it does not imp= act historical look backs on actuals. 2.=C2=A0 Rounding up = SOC volume In the or= iginal version, I was simply letting excel round. I have up