---
id: KB-TL-015
url: https://app.codecontract.io/help/trackline/letting-the-ai-build-the-process
idioma: en
categoria: trackline
subcategoria: plantillas
audiencia: usuario
nivel: basico
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-TL-001, KB-TL-006, KB-TL-029]
citadoPor: [KB-TL-018, KB-TL-029]
---

# Letting the AI build the process

_Describe what you need in a sentence and get a draft to correct._

**Responde a:** create a process automatically · i do not know what documents to ask a supplier for · let ai design the process · automatic process template

What stops most people at the start is not the tool: it is not knowing what to ask for. You can describe what you need in a sentence and come away with a draft process built, which you then correct.

## How to use it

1. **Describe what you need: "subcontractor onboarding for a site, with company and worker documentation".**
2. **A draft appears with phases and requests.**
3. **You correct it: remove what does not apply, add yours, adjust what blocks.**
4. **Save it as a template.**

> [!IMPORTANT]
> It is a draft, not a finished template. What it proposes are the usual documents for that case, not those your regulations require or your customer demands. Review it with that in mind before using it with anyone outside.

## What it is really for

Not to avoid thinking, but to avoid starting from a blank screen. Correcting a list that already exists is much faster — and comes out better — than inventing one, especially the first time.

> [!WARNING]
> Whatever it proposes has to pass through someone who knows your case. If the process ends up asking for documents you do not need, you will annoy your suppliers; if it misses a mandatory one, the problem is worse.

> [!NOTE]
> Designing a schema with AI consumes the same as creating the process by hand. Using it costs no more.

**Can I change everything afterwards?**

Yes, it is a starting point.

**Does it get my sector's documentation right?**

It usually gets the usual items right; the specific ones you add yourselves.

**What if I prefer building it by hand?**

Perfectly valid, and from the second process onward it is usually faster.

## Ejemplos

**Someone has to build their first process and does not know what to ask a subcontractor for.**

- Describes it in one sentence
- Corrects the draft, removing two documents and adding one of their own

→ Comes away with a usable process in ten minutes instead of abandoning it at the blank screen.

**Building the first template from scratch feels like a chore.**

- Describes in one sentence what needs requesting

→ A draft comes out that only needs correcting.

**The draft includes documents that do not apply.**

- Removes what is superfluous before saving

→ The final template is shorter than the draft.

**The draft uses generic names.**

- Rewrites them in their sector's vocabulary

→ The supplier understands what is being asked.

**The draft is saved without review.**

- Reviews it fully before launching to anyone

→ No supplier receives a nonsensical request.

**A variant is needed for another supplier type.**

- Describes the variant and adjusts the new draft

→ The second template takes minutes.
