> For the complete documentation index, see [llms.txt](https://process.mad.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://process.mad.co/operations/people-operations/probation.md).

# Probation

## Month 1

Probie gets used to our way of doing things and gets familiar with our tools – Google Suite and Team Drives, Asana, Visual Studio, Officevibe, etc.&#x20;

We should expect some mistakes and lots of questions!

Assign a peer to help with Onboarding.&#x20;

Review along with peers and direct superior and inform if current performance would pass the probationary period

If yes…great!

If no…discuss areas for improvement to ensure a pass.

## Month 2

Same drill as Month 1

## Month 3

Before the end of Month 3, Probie and Team Lead will meet to discuss performance and next steps.

If it’s a Non-Pass, Team Lead will explain the reasons for the result and why the fit isn’t there.  Next step is immediate removal after confirming the last pay calculation (if last day doesn’t fall on a payday)

If it’s a Pass, new KPI’s will be discussed and agreed between Member and Team Leader.  Member will then receive a confirmation email and a copy of new KPI’s.

Insurance form for filling in and added to corporate policy. Confirmed Hätter will also be added to the Netflix account

Unlimited Leaves now apply!

IMPORTANT: salary adjustment is **NOT** automatic. Depends on Probie’s performance and proof of added value to the role, team and organization.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://process.mad.co/operations/people-operations/probation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
