> For the complete documentation index, see [llms.txt](https://guide.fariaedu.com/cp-coordinator-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.fariaedu.com/cp-coordinator-handbook/november.md).

# November

### Administration

* Email teachers to ask about inclusive access arrangements needed (for Individualised Education Plans (IEPs), 504 plans (in the US), or other teacher recommendations).
* Download the handy [IB guide](https://resources.ibo.org/data/d_0_dpyyy_eas_1812_1r_e.pdf?) to registering candidates on their DP courses.
* Set up[ IBIS](https://ibis.ibo.org/) and register students.

{% hint style="warning" %}
Double-check to ensure that students are registered for the correct exams.
{% endhint %}

### Teachers 

Meet with teachers individually and observe IB classes or set up peer observations. Meet informally with teachers afterwards and debrief on the lesson

Collate relevant IA results and monitor progress on core programme: SL, language development, RP and PPS for both CP1 and CP2. 

{% hint style="success" %}
Utilise ManageBac as much as possible for this with[ IA storage and organisation](https://help.managebac.com/hc/en-us/sections/360009305291#internal-assessments) in Classes as well as SL, RP and PPS/ Language Development [project templates](https://help.managebac.com/hc/en-us/sections/360009194772#project-based-learning) through year groups. 
{% endhint %}

Survey CP1 students and parents and review induction process. 

Ask teachers for suggestions for professional development for next term/semester.

### Marketing

Make the CP programme and the CP students visible around the school. 

Download the [CP infographics and IB resources](https://drive.google.com/drive/folders/1DZxlMq7TYUkNrDrtJdahtMKKrCVWcziw?usp=sharing) (shown below) designed to support schools and have staff and students display the infographic in classrooms and in  prominent places.

{% embed url="<https://drive.google.com/file/d/1hQ21Yb6TgnvUJ0cfwU_qUNfqLDB7ivsu/view?usp=sharing>" %}

{% embed url="<https://drive.google.com/file/d/1Nbr8pPcUHLxjQjOflu0sjJXeb5rLnrxF/view?usp=sharing>" %}

{% hint style="success" %}
Celebrate achievements in newsletters, noticeboards, assemblies and at other events. These can include: CRS internships or work-related experiences, service learning projects, PPS workplace opportunities,  visiting speakers and careers fairs.&#x20;
{% endhint %}


---

# 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://guide.fariaedu.com/cp-coordinator-handbook/november.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.