> For the complete documentation index, see [llms.txt](https://policies.aic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://policies.aic.io/respectful-communications-policy.md).

# Respectful Communications Policy

### Purpose

AIC expects professional, respectful and clear communication across all work.

This policy exists because communication standards directly affect trust, inclusion, delivery quality and customer confidence.

### Policy Statement

AIC does not tolerate abusive, discriminatory, intimidating, humiliating or hostile communication.

This applies to all communication channels, including:

* email
* meetings
* calls
* messaging platforms
* collaboration tools
* documents
* code reviews
* customer correspondence
* supplier correspondence
* social media where connected to work

### Communication Principles

Communication should be:

* clear
* factual
* respectful
* proportionate
* timely
* relevant
* inclusive
* professionally worded

### Expected Standards

Everyone working with AIC should:

* challenge ideas without attacking people
* assume professional intent unless evidence suggests otherwise
* avoid inflammatory language
* avoid personal insults
* avoid discriminatory language
* avoid sarcasm that may undermine or humiliate
* give feedback constructively
* document important decisions
* escalate serious issues properly
* adapt communication where accessibility needs exist

### Unacceptable Communication

The following is unacceptable:

* abusive language
* discriminatory comments
* threats
* intimidation
* sexualised comments
* racist, sexist, homophobic, transphobic or ableist language
* deliberate humiliation
* aggressive messaging
* repeated hostile criticism
* exclusion from necessary communications
* sharing offensive material
* retaliatory messages

### Code Reviews and Technical Challenge

Technical challenge is encouraged.

Personal attack is not.

Code reviews should focus on:

* correctness
* maintainability
* security
* performance
* readability
* standards
* evidence

Code reviews must not include:

* personal insults
* ridicule
* hostile tone
* gatekeeping
* discriminatory assumptions
* unnecessary aggression

### Customer and Supplier Communication

AIC representatives must communicate professionally with customers, suppliers and partners.

Commercial pressure, delivery stress or disagreement does not excuse abusive or discriminatory conduct.

### Escalation

If communication becomes inappropriate, the matter should be escalated to the relevant manager, delivery lead, commercial lead or company director.

### Consequences

Breaches may result in:

* management intervention
* removal from communication channels
* removal from a project
* supplier escalation
* formal disciplinary action
* contract action


---

# 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:

```
GET https://policies.aic.io/respectful-communications-policy.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.