> 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/december.md).

# December

### Administration

End of term reporting (if applicable). The IB requires reporting of core components. 

{% hint style="success" %}
Review ManageBac sample [IB CP Report Card](https://www.managebac.com/career-programme/cp-report-card-sample) and build Report Card template in ManageBac if the school is using Reports module.   
{% endhint %}

Scheduling (if applicable) of January mock examinations for CP2 and scheduling of collaborative planning meetings for spring term/semester.

Review applications for CP programme entry (if applicable) per your school’s admission policy.

Update the programme development plan. 

### Staff and Students

{% hint style="info" %}
Follow up on any parental concerns and teacher concerns on student progress. 
{% endhint %}

Check in with core programme teachers on resources, student engagement and completion of first formal interviews for SL and RP (depending on your internal established timeline.)

### Marketing

Students or teachers currently participating in a specific class could visit ‘target classes’ to promote enrollment. For example, an IBCP student with a Business CRS may want to visit a year 11 Business class. The student can explain and promote the IB CP to students who may have the interest and skill set for the course and who might be unaware of internships and work-related experiences available as part of the CP.

![](/files/t8tiQ1f94jPBWljr2OEe)


---

# 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/december.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.