Documents the assistant writes

You do not pick a template in Alchex. You tell the assistant what you want to put in place, and it writes the document with you from how that process works — the steps, roles and records a good process of that kind has, sized to your organisation.

Building a document together

Start with what you want to do, not with a document. Say We want to implement cryptography or I want the change management procedure. The assistant asks about how you work today — what you encrypt, who approves a change — never about which document, template or section. With each question it gives its opinion on the usual choice for an organisation like yours, so "go with your recommendation" is always a complete answer.

Your answers are kept. Everything you settle is kept with the document it belongs to, so a later document that asks the same thing starts from your answer instead of asking again.

When the design is settled, the document is created. The assistant writes it from what you decided, in your team's library, opens it beside the conversation, and names the document and the team in its reply, so you always know what it made and where to find it. If you can add documents in more than one team, it asks which one first. Asked later where is our cryptography policy?, it finds it.

Every document has the same shape. The assistant writes each one in one standard structure for its type — a policy has Purpose, Scope, Roles and Responsibilities, Policy Statements, Implementation, Exceptions, Compliance, Review and References. Each choice it made for you is marked (recommended default) in the rule it sets, so you confirm it where it applies. Nothing from us is mistaken for something you said.

It is linked to the clauses it covers from the start. The document is created already linked to the requirements its process satisfies, so it shows on Compliance the day it is written.

Changing an answer later updates the document through an ordinary edit you can see, never by overwriting a section you wrote yourself.

Two honest rules. A failure to create says so and creates nothing. Asking for the same document again creates a second, separate document; it never overwrites the first.

Processes come when you ask for them

Creating a document starts nothing on its own. You get a document, not a set of running automations. To have its agent do something on a date, add a schedule on the document's Agent panel — see Workflows in documents.

"Do we actually have to do this?"

Ask, and the assistant reads the clause and answers from its text, naming the clause — it never states that something is required, optional or fine to skip from memory, and it will not change its answer because you pushed back. See Is it required?.

Related

• Creating documents — starting from scratch instead.
• Registers — the logs a document's records live in.
• Controls — a control is a document of type Control.
• Publishing — turning your document into a version people read.