Skip to content
RadHR Logo
  • Home
  • About
  • Community
    • Community forum
    • Events
    • Blog
  • Resources
    • Policy library
    • Guides
    • Workshops
    • Themes
    • Newsletter
  • Research
  • Contact
RadHR LogoRadHR Logo
  • Home
  • About
  • Community
    • Community forum
    • Events
    • Blog
  • Resources
    • Policy library
    • Guides
    • Workshops
    • Themes
    • Newsletter
  • Research
  • Contact
RadHR LogoRadHR Logo

POLICY

Sick leave agreement

This is a sick leave policy for a small collective with limited funds. On average, for each 10 days of work, you have the right to one paid sick day. However, we have decided to pool our sick days. Pooling addresses the fact that we do not all have the same health and to alleviate…

04.09.23

Home » Policy Library » Sick leave agreement

Info

Overview

This is a care leave for self / care leave for others / sick pay / mental health support / sickness and disability / wellbeing support policy that's been used for 1–3 years by a self-managed activist group with 5–14 people and a turnover of £100–£300k.

Policy details

Type:
Policy
Used for:
1–3 years
Policy areas:
Care leave for self
Care leave for others
Sick pay
Mental health support
Sickness and disability
Wellbeing support
Known legal issues:
Yes
Legal issue info:
Pooling sick days

Organisation info

Name:
Anonymous
Type:
Activist Group
Structure:
Self-managed
People:
5–14
Turnover:
£100–£300k

Downloads

  • Sick-Leave-Agreement.pdf

Like this policy?

Not sure how to make it fit your group?

Try the free RadHR Policy Adaptation Workshop with your team!

Related Guides

Guides are XYZ, and help with ABC.

How to write a fairer, more equitable pay policy

  • Pay

From flat pay structures to needs based pay systems - how do we live our progressive values, meet everyone’s needs and avoid replicating the systemic inequalities of the corporate world? This guide explores the tricky topic of pay.

Read MoreHow to write a fairer, more equitable pay policy
Pay

Licence

This policy is shared under a Creative Commons (CC BY-SA 4.0) licence.

This means you are free to:

  • Share—copy and redistribute the policy in any medium or format;
  • Adapt—remix, transform, and build upon the policy for any purpose, even commercially.

And if you do, you must:

  1. Attribute—Give credit to the author and source appropriately and say whether any changes have been made from the original;
  2. ShareAlike—Share your policy or document under the same licence, and link to details about the licence.

Notes

From the person/group who shared the policy:

This agreement is based on trust. It assumes a strong trust basis within your group, and a commitment to the cause. It is probably not possible to translate this to a policy that fits within legal frameworks. However, it can inspire (informal) practices.

Contents

  1. For people working on a short-term contract 
  2. For people who are part of the collective
  3. Keeping track
  4. Longer-term illness

Policy

Sick days are understood for physical illness, as well as mental health. They can be used to take care of yourself, but also if you need to take care of others who are ill. 

Taking a sick day is based on trust.

As freelancers, we are not usually entitled to get any sick leave. This is bullshit. 
We aim to cover a minimum of sick leave, however, we very much encourage you to look into the healthcare system where you live and the possibility to get health insurance if needed. This is especially important for possible long term illness. 

For people working on a short-term contract

Anyone who works a minimum of 10 days for the collective is able to claim sick pay. 
We cover 1 day of sick pay for every 10 days of work. No justification is asked. 

If necessary and possible, we will rearrange the work and/or timeline accordingly. 

For people who are part of the collective

We have decided to pool our sick days. For every 10 days of work (done by anyone in the collective), 1 day of sick leave is added to our collective pool of sick days. Pooling addresses the fact that we do not all have the same health and to alleviate the stress of having “enough sick days”. 

Collective members are welcome to use the collective sick days when they are ill until they have recovered. You can and should, of course, take the time you need to get better. No justification is asked, it is based on trust. 

If you are ill for more than a week, we ask you to briefly share the list of tasks that you had on your radar with your team, and note which ones are urgent and should/could be passed on. 

Keeping track

We have a spreadsheet dedicated to our work days, care days and sick days. You should log when you take a sick day. 

The sick days are not paid days that we add on top of our normal work days, but are included within the agreed number of work days (and within the agreed salary). If sick days are not used within a given year they disappear (they are neither remunerated nor cumulative beyond the year).  

While we encourage the use of these days to support strong mental health, they should be used when feeling ill, not as a holiday (see holiday policy).

Longer-term illness

For long-term illness (over a month), we may have to assess what makes most sense for the person ill, the rest of the team, the project and our commitment to funders. This will be reassessed on a case by case basis. 

We ask you – if possible – to be upfront with how long you think you might be ill. 

Here are questions that we encourage the collective’s internal support team, the person’s team and the person ill to explore (together): 

Internal support team: 

  • Can the ill person receive financial support through health insurance? 
  • Is their condition work-related or does the work they do at the collective affect it negatively? 
  • Does their absence or condition affect other team members, and if yes, how? 
  • Would they like to stay involved with the collective’s work for the coming time, and if yes, how? 
  • Are there any tasks they would like to continue doing, or do they prefer to log off completely? 

Person’s team : 

  • Can we rework the timeline of that person’s tasks?
  • Shall we reduce the expectations/ambition of a project?
  • Do we need to hire someone else to finalize a project?

Discussion

Comment on our forum: community.radhr.org

Was this helpful?

Leave a Reply

Your email address will not be published. Required fields are marked *

Join the RadHR community! 💛

Get help, support others and join discussions...

Sign-up now
Find out more

RadHR Logo

Because humans are more than resources...

  • About
  • Community
  • Policies
  • Guides
  • Research
  • Blog
  • Contact

Creative Commons BY-SA 4.0 © 2025 RadHR

Privacy | Accessibility