> For the complete documentation index, see [llms.txt](https://charity.childsafetyfund.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://charity.childsafetyfund.org/policies/organization/quickstart-4/quickstart.md).

# Onboarding

CSF is committed to maintaining fair, transparent, and equitable hiring and contracting practices that align with its mission, values, and compliance standards. All personnel and partner selections are made based on merit, qualifications, and organizational need, without discrimination or bias.

This policy applies to all hiring, contracting, and engagement activities for employees, consultants, vendors, and subrecipients.

***

### **Position Development and Posting**

When a position or contract opportunity becomes available:

1. The Designated Officer (or an authorized representative) defines the scope of work, responsibilities, and qualifications.
2. Opportunities are announced internally and externally, as appropriate, to promote equal access.
3. All postings will include a clear description of required competencies, compensation or contract terms, and application procedures.

***

### **Application and Screening**

All applicants must submit a complete application or proposal package by the stated deadline.

* Applications are reviewed for completeness, accuracy, and alignment with CSF’s mission and standards.
* The Designated Officer or review committee evaluates all submissions using consistent criteria.
* Qualified candidates may be invited to participate in an interview, presentation, or assessment process.

CSF maintains documentation for each selection process, including job or contract postings, applications received, interview notes, and evaluation materials. These records are retained in accordance with CSF’s Records Retention Policy.

***

### **Selection and Offer**

Final selection decisions are based on demonstrated qualifications, relevant experience, and overall fit with CSF’s operational needs and values.

* Employment and contractor offers must be made in writing and approved by the Designated Officer or Board designee.
* No verbal or informal offers are binding without a signed agreement.
* For contractual engagements, CSF will execute a written agreement outlining the scope of work, deliverables, payment terms, and applicable compliance requirements.

***

### **Verification Process**

To ensure compliance and public trust, CSF requires:

* Verification of education, professional licenses, certifications, or other credentials as applicable to the role.
* Background or reference checks consistent with position sensitivity and relevant laws.
* Ongoing credential maintenance and disclosure of any disciplinary or legal actions that may impact eligibility.

Failure to disclose or falsifying information may result in disqualification or termination of employment or contract.

***

### **Recordkeeping**

All hiring and contracting documentation will be securely maintained within CSF’s administrative records for at least one (1) year following completion of the hiring or engagement process, or longer when required by applicable regulations or funding agreements.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://charity.childsafetyfund.org/policies/organization/quickstart-4/quickstart.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
