Starting to review Scorecard that currently exist on OSE HR wiki page. I'm finding it has too much information and may be overcomplicating the request for having metrics in place. The goal of Scorecard #1 will be to track recruiting, recruiting sources, individual contributions.
There is a dashboard built within the ATS that tracks the candidate lifespan. I believe that using this dashboard is sufficient versus building a separate scorecard to track applications and candidate success rate.

adjusted admin right to Genisia and Xiao ATS access. This will give ability to edit, create and move candidates in ATS.
Reworded the job summary on ATS to include direct links to Wiki page published by OSE. The goal of using the ATS is to create a fluid pipeline and tool from an HR/Recruiter and reviewer aspect. Having a central location for all apps allows HR to track candidate lifespan through the application, interview, testing and interviewing. This is more functional than tracking everything on a spreadsheet. This also gives us the capability of streamlining the review of candidates to other OSE members by sending them limited access to the ATS for them to review initial application.

November 13th- sent confirmation emails to HR team to verify participation. Discovered deficit in communication due to either family obligations and not checking @opensourceecology email.

Emailed rejection notice to HR candidate. Composing email to team to remind the importance of Logging time on wiki.

Call with Marcin.
Discussion around ensuring streamline of work is distributed amongst HR team. Need to send email to HR team to ensure team is logging time in Wiki.
Discussed Scorecard for HR OSE, I'm currently exploring what is already built into our ATS to generate reports for talent pipeline.
Scorecard needs to be created to track team's work i.e. recruiting outreach
Will not be moving forward with HR applicant Gurpeet. Not enough experience to utilize, would take more time developing than what we need. Our HR contributors need to have a solid grasp in the disciplines of HR.

Initiated emails to HR team asking for each individual to take a look at the SOP document that Genisia started that I uploaded onto Wiki. I had issues with the sizing, however Marcin adjusted. The code to include for proper sizing is challenging for me. I think it's just getting comfortable where to put it, I will reference back to what Marcin did and copy and paste in the future.

Other emails sent to the team is to start thinking about how we track our metrics. I spoke specifically to recruiting. The ability to track our pipeline helps us understand how many people we are making contact with, who is pushed forward, who is rejected, who is moved forward and who becomes a permanent contributor and for how long.
I had mentioned what I used in the past, which is cumbersome and specific to my past industry on a mass scale (3k-8k) employees.

I have discovered a possible, easy function in our ATS that may serve this purpose.

Call with Genisia. We discussed the need to start differentiating between the different disciplines at OSE, developer, engineer and so on. Defining clear needs will assist HR in recruiting out of the right talent pool.

Sent out email communication to the Core OSE team to solicit insight on what we / HR should make sure we are screening for. The team has experience in the position and can easily think about what it takes to be a developer/contributor. This will assist us in making sure we are engaging individuals that have the skill, traits, qualities and so forth to be successful on the team.

Sent an email to HR team to let them know the SOP doc Genisia started is on Wiki. This is the first step, we need a central doc that we can start adding in additional steps, merge the developer application steps required and so forth. The SOPs from an HR perspective will include backend steps such as the ATS input and moving the candidate through the ATS. We will need to expand out to include more details about the onboarding process such as welcome documents, schedules to include OSE team meetings, expectations and so such.

Touchbase call with Marcin
-discussion based around new members of the OSE HR Team
- I will create ATS log ins for each HR teammember, this will allow candidate management.
-Marcin will create OSE HR emails for HR team.

sent email communication follow ups to Xaio and Genisia to prompt account creation on Wiki.

touchbase call with Marcin

Introduction call with HR contributor candidate Xuai Yi

Found new ATS; built out job page and loaded in job summaries

researching new ATS with free hosting

recruitment posts

Participate in OSE team call
one on one call with Marcin

1 hour call with Marcin to review ATS

Download open source ATS; currently testing functionality and use

Participate in Dev. team meeting; present recruiting 101

Finish Google slide show for Dev. meeting