Hi Anonymous.
I usually hate building these cases because in many organizations the RA function is considered a "money pit" because they don't "make products", "sell products" or "manufacture products" and therefore the work they do only "costs" money. While I know we can all make a great case for how compliance, on-time submissions, first submission approval rates and all the other great metrics we can measure actually "make" the company money by being able to move forward better or having the widest indications, etc. the business folks typically don't like to consider those positives unless they are well-versed in the importance of regulation management.
With that said, I have had some success when approaching this using the idea that personnel involved in the submissions can improve the overall functioning of the business with the following potentially measurable outcomes:
1. Submissions being sent in on time (or early) for the product allow for improved potential for approval of the product on time and hitting the market launch dates in the different countries;
2. Where product markets are being expanded, it is a potential for moving forward to make the market launch on time again;
3. For every week that you are late to getting the submission into the regulator it is costing you ~2% of your planned turnover for the first year - this cost is "real" whether the business folks consider it correct or not.
4. When looking at the workload, determine what is the general level of effort to pull together the documentation that you need to submit, organize the data, submit the data, then answer the question of how much work might be involved in responding to questions or getting the answers for the questions. Again, if this is >80 hrs/wk for the 2 people on the team, you have a basis for the business case in general.
5. Assess what having your team able to back each other up as well as potentially backing you up while on other issues/business for the company provides to the company. Again, people will be out of the office at some point for at least 6 weeks per year on vacation (assuming that all 3 of you get 2 weeks vacation per year - a somewhat unlikely situation in the current work setting). This obviously doesn't account for the time that people will be out of the office either in meetings, trainings, or even just ill. If you can't back up the group it ends up costing days that will hurt your timeline in the future when you are trying to get the product approved.
6. The key metric is often not just what is coming up in the next few years but more about the idea of what is the day-to-day work that you need to cover with the additional headcount. You really need to have a look at what the work is and how many hours will need to be allotted for the work to be done. This includes all of the routine work, all of the regular updates (think any sort of notifications or analysis required by country regulators, how to manage submissions of information even after the approvals, etc.) that will be required and then include things like training, meeting attendance, future work as noted previously, etc.
This becomes a major key point because if you can't support the need for a FTE (full time employee) longer term you will have a hard time with your business case. It might bode well for you to look into the potential of bringing on contract employees if you need specific help at specific times rather than bringing in FTEs unless you can ensure that your workload is going to be supportive of the extra FTE hours. If you aren't sure, maybe a temp or a temp-to-perm type setup might be more palatable to your organization. I don't like the temp or temp-to-perm options because these employees require essentially the same level of training and work as an FTE without the benefit of the person being an FTE and the business being able to eliminate the position extremely rapidly. On the plus side, if the person isn't working out these can be good "proving" ground strategies but the costs can still be considerable especially if you really need the person and just can't show the hiring committee that you need them.
------------------------------
Victor Mencarelli
Global Director Regulatory Affairs
MelvilleNY
United States
------------------------------
Original Message:
Sent: 04-Apr-2022 19:17
From: Anonymous Member
Subject: Seeking business case advise for additional RA headcount in the team
This message was posted by a user wishing to remain anonymous
Hi,
I have recently taken on a role as RA Manager with 2 RA team members. However, our registration pipeline is significant for the next 3 years. I'm looking to develop a business case for additional headcount which can support with day to day registration activities but also help other RA team members while I'm away or occupied with other high-level projects.
Please share some examples or templates on how to manage this successfully. I have reached out to our internal HR head and according to them a business case is required and there is no current template for support functions such as RA.
Thank you.