Applying for chartered status

We're building pathways to chartered membership and fellowship for everyone in our sector, take the first step to onto yours now

&nbsp

To become a CIMSPA Chartered Member or Fellow you must first be a CIMSPA member in a management category.

&nbsp

PLEASE NOTE: Application to become a CIMSPA Chartered Member or Chartered Fellow is currently only available for those working in management roles. The applicant has 6 months in whcih to complete the chartered application from the receipt of payment. The applicant may only be referred once within a single application. If you are a CIMSPA member and you are ready to take the next step in your career by getting on the road to chartered status, there is a two stage process to follow which is detailed below. Email your CV to info@cimspa.co.uk to begin your application.

Your application

Stage 1

The stage 1 application includes:
Uploading your CV and a covering letter through the tahdah application process, which should include:

An outline of your employement.

An outline of your education.

Previous qualifications.

Sector events that you have attended.

Stage 2

The stage 2 chartered assessment process is completed either by:

A remote video interview

A written exercise

During stage 2 you will be required to demonstrate how you meet with a set of detailed assessment criteria, drawing on examples of your knowledge and experience from working within the sport and physical activity sector.

You can download a copy of the chartered assessment criteria from the links below:

This site uses cookies to store information on your computer. See our Cookie Policy for further details on how to block cookies.

I am happy with this

Cookies

What is a Cookie

A cookie, also known as an HTTP cookie, web cookie, or browser cookie, is a piece of data stored by a website within a browser, and then subsequently sent back to the same website by the browser. Cookies were designed to be a reliable mechanism for websites to remember things that a browser had done there in the past, which can include having clicked particular buttons, logging in, or having read pages on that site months or years ago.

NOTE : It does not know who you are or look at any of your personal files on your computer.

Why we use them

When we provide services, we want to make them easy, useful and reliable. Where services are delivered on the internet, this sometimes involves placing small amounts of information on your device, for example, your computer or mobile phone. These include small files known as cookies. They cannot be used to identify you personally.

These pieces of information are used to improve services for you through, for example:

recognising that you may already have given a username and password so you don’t need to do it for every web page requested

measuring how many people are using services, so they can be made easier to use and there’s enough capacity to ensure they are fast

analysing anonymised data to help us understand how people interact with our website so we can make them better

First party cookies

These are our own cookies, controlled by us and used to provide information about usage of our site.

We use cookies in several places – we’ve listed each of them below with more details about why we use them and how long they will last.

Name

Purpose

Typical Content

Expires

blahCMS:CurrentLanguage

Its purpose is for our CMS to know what language you are viewing the site in.

Is usually a 4 digit number used to identify the current language in the CMS. Defaults 1804.

ASP.NET_SessionId

The ASP.NET session state is a technology that lets us identify different users of the site by a session ID.

Session IDs are a 120-bit random number that is represented by a 20-character string. The string is formatted so that it can be included in a URL and it does not have to undergo URL encoding.

On Session End.

whoson

Is a cookie put onto the system by the whoson client we install. It is used to track a user on a site in order to be able to use livechat so the admin can help a user on particular pages.

Stores a number to use as a Unique Identifier for a user currently online.

Third party cookies

These are cookies found in other companies’ internet tools which we are using to enhance our site, for example Facebook or Twitter have their own cookies, which are controlled by them.

We do not control the dissemination of these cookies. You should check the third party websites for more information about these.

Provider

Name

Purpose

More info

Google Analytics

_utma _utmb _utmc _utmz

These cookies are used to collect information about how visitors use our site. We use the information to compile reports and to help us improve the site. The cookies collect information in an anonymous form, including the number of visitors to the site, where visitors have come to the site from and the pages they visited.

Log files

Log files allow us to record visitors’ use of the site. The CMS puts together log file information from all our visitors, which we use to make improvements to the layout of the site and to the information in it, based on the way that visitors move around it. Log files do not contain any personal information about you. If you receive the HTML-formatted version of a newsletter, your opening of the newsletter email is notified to us and saved. Your clicks on links in the newsletter are also saved. These and the open statistics are used in aggregate form to give us an indication of the popularity of the content and to help us make decisions about future content and formatting.