# Onboarding Process Documentation

## Onboarding Document
The [onboarding document](https://docs.alchemist.wtf/mist/join-us/alchemist-builders-onboarding-guide) provides a picture of the organization as a whole if the reader is interested in applying as a builder. It represents the starting point for the whole onboarding process from applicant perspective.
- Content:
- Vision
- Compliance & ethic
- Hierachy
- Tools (general, how we use them, links)
- Meeting Calender
- Routines to achieve transparency
- Feedback loop
- The Builders' stipend
- Application form

## Application Form
The [application form](https://alchemistcoin.typeform.com/to/YUBB53J8) is part of the onboarding document & is used to collect contact details, motivation and ability data quickly, collectively and according to a uniform scheme. This significantly simplifies data processing in the further course and thus accelerates the onboarding process
- Content:
- Name or Pseudonym
- Discord username
- Please categorize your professional field (in order to improve filtering and sorting)
- What is your Github, Behance, or other professional site link?
- Please describe your skill set
- What part of your skill set would you like to expand further?
- What are you most looking forward to working on?
- How did you hear about Alchemist?

## ClickUp Tasks
A clickup task will be created for every submitted application. Each task will be categorized by the selected professional field (question 3 - please categorize your professional field) by the applicant.
The small number next to the application lists indicates the tasks currently in state NEW.

### Clickup Process
We do work with 4 differnt states in order to stay organized.
Please use the comment function for every checklist step, it helps to sustainably record decisions and reasons.
- **status NEW**
- Initial status
- Not processed
- Review
- mark "Review" if done
- Application is appealing
- Change to **status YES**
- Interview
- mark "Interview" if done
- If you want to start onboarding
- mark "onboard"
- change to **status COMPLETE**
- If you do not want to start onboarding
- Change to **status NO**
- Application is not appealing
- Change to **status NO**


## Zaps
The Zapier tool was implemented in the workflow to enable the most efficient process possible. It combines various elements of different tools. With the current limitation of our Zapier account, we need 3 different zaps, mainly to be able to do the automatic categorization in clickup. The limitation has no effect on the execution, it leads just to 3 zaps instead of one.

Example, zap workflow for a designer application:

### Tools included and why:

#### Typeform
- Purpose
- Collect application data according to a uniform scheme.
- The submission of the application should be as simple as possible

#### Clickup
- Purpose
- Provision of a simple but powerful ticket system
- Categorization
- Template usage
- Provide an overview
- Processing through checklists and status changes

#### Discord
- Purpose
- Post an instant notification about a new submission
- Provide link for created task in clickup