> For the complete documentation index, see [llms.txt](https://support.vlex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.vlex.com/vincent-by-vlex-1/vincent-studio/creating-and-managing-ai-workflows-in-vincent-studio/create-a-studio-workflow-by-describing-it-in-plain-language.md).

# Create a Studio Workflow by Describing It in Plain Language

Describe the process you need in plain language and Studio drafts the workflow for you, with steps, inputs, and actions already in place.

#### Summary

Describe the process you need in plain language and Studio drafts the workflow for you, with steps, inputs, and actions already in place. It turns an idea into working AI legal workflow automation in minutes.

#### Why This is Important

Most people who build workflows already know exactly what they want. The hard part has never been the idea, it has been translating that idea into a sequence of tasks, action types, and inputs inside the builder. That translation step is where new builders stall and where a good workflow idea quietly dies.

Prompted creation removes that step. You write one paragraph describing the outcome you need, and Studio hands you a working draft to refine instead of a blank canvas to fill. The skill you need shifts from *construction* to *editing*, which is the skill legal professionals already have.

#### Before You Begin

* You need access to **Studio** and permission to create workflows in your organization.
* Have a rough idea of the outcome you want, the documents the user will upload, and who will use the workflow. You do not need a formal plan, but a clear outcome produces a far better draft.

#### How to Create a Prompted Workflow

1. Navigate to the **Workflows** tab in Studio and start a new workflow as you normally would.
2. Choose the option to describe your workflow in natural language instead of building it step by step.&#x20;
3. Write your description in the input box. Describe the outcome, the input documents, and the audience. For example: `A user uploads an NDA and Vincent reviews it against our firm's playbook, flags any clause that deviates, and drafts a short summary memo for the assigned attorney.`
4. Submit the description. Studio generates a starter workflow with the steps, inputs, and actions pre-populated.
5. Review the generated draft. Every generated workflow lands in an editable **draft** state, so nothing is live until you decide it is.
6. Edit, extend, or discard the draft. You can refine it directly in the workflow builder, or keep adjusting it in conversation with Vincent.
7. When the draft does what you need, publish it exactly as you would publish any other workflow.

<figure><img src="https://1556743161-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MS8Dq_iqEIflAmbaOkI-887967055%2Fuploads%2FBE1qNp5aXNpPVzTcRbyv%2FScreenshot%202026-09-03%20at%204.21.47%E2%80%AFPM.png?alt=media&amp;token=92d4fc76-8d96-4649-b291-e07433f445d9" alt=""><figcaption><p>Describe the workflow you need in plain language and Studio drafts the steps for you.</p></figcaption></figure>

#### What the Generated Draft Will and Will Not Do

Understanding the boundaries of the generated draft saves you from over-trusting it or under-using it.

* **It always lands in draft.** Prompted workflows are never published automatically. Review and publication remain a deliberate, human decision.
* **It uses validated building blocks only.** Generation is constrained to a validated set of step primitives, so the draft is built from the same components you would have chosen by hand.
* **It is a starting point, not a finished product.** The draft captures structure. Your firm's expertise still has to go in: the playbook you upload as a workflow asset, the precise wording of each prompt, the conditions on each task.
* **It does not replace planning for complex processes.** A workflow with ten interdependent tasks still benefits from being mapped out first.

#### How to Write a Description That Produces a Good Draft

The quality of the draft tracks the quality of the description almost exactly. Four things make the difference:

* **Name the deliverable, not the activity.** `Produce a one-page risk memo for the assigned attorney` gives Studio a target to build toward. `Review contracts` does not.
* **Say what the user uploads.** Naming the input document type, for example a non-disclosure agreement or a set of witness statements, lets the draft configure the input and the required documents correctly on the first pass.
* **Say who runs it.** A workflow built for a paralegal is structured differently from one built for a partner. Mention the audience and the draft will reflect it.
* **Describe one process per workflow.** If your description contains the word "and then also", you probably have two workflows. Split them.

#### Best Practices & Pro Tips

* **Use prompted creation as your first draft, then edit like a lawyer.** The fastest route to a strong workflow is to let Studio produce the skeleton in thirty seconds and spend your real effort where it counts, on the prompts and the workflow assets that encode your firm's judgment. Structure is cheap to generate; expertise is not.
* **Keep the generated draft even when it is imperfect.** It is usually faster to correct a wrong action type than to rebuild the workflow from an empty screen, and comparing what Studio inferred against what you actually meant is a fast way to learn how the builder thinks.
* **Save your description.** Paste the plain-language description into the workflow **Description** field or keep it with your team's documentation. It becomes the plain-English specification of what the workflow is supposed to do, which is invaluable when someone reviews or retires the workflow months later.

### Related Articles

* [Workflow Governance: Quality Control and Lifecycle Management](/vincent-by-vlex-1/vincent-studio/vincent-studio-advanced-techniques-and-best-practices/workflow-governance-quality-control-and-lifecycle-management.md)
* [How to Publish and Share Your Vincent Studio Workflow](/vincent-by-vlex-1/vincent-studio/creating-and-managing-ai-workflows-in-vincent-studio/how-to-publish-and-share-your-vincent-studio-workflow.md)

**What's Your Next Step?**

| **New to Vincent Studio?**                                                                                                                                                                                 | **Already a Vincent Studio Customer?**                                                                                                                     |
| ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [See how Vincent can transform your practice. **Request a personalized demo**.](https://vlex.com/book-a-demo?utm_source=website\&utm_medium=organic\&utm_campaign=web_trial_homepage\&campaign_id=4270741) | [If you still have questions or need help with a specific feature, our team is here to assist. **Contact our Support team**.](https://vlex.com/contact-us) |
