> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/getting-started/create-a-project.md).

# Create a Project

{% columns %}
{% column %}
**What will be completed**

* Create a new Project in Transform
* Configure basic project settings
* Use the project setup wizard
* Open the Project dashboard
  {% endcolumn %}

{% column %}
**At a glance**

* **Time:** \~5 minutes
* **Access:** project creation permission\
  See [Understanding Access Levels](/organizations-and-projects/understanding-access-levels.md)
  {% endcolumn %}
  {% endcolumns %}

### Overview

Projects are the delivery containers for transformation work. Projects hold requirements, tasks, tests, and artifacts.

### Key Concepts

* **Organization**: container that holds Projects
* **Project status**: lifecycle state for visibility and reporting
* **Template Project**: optional starting configuration copied from a standard Project

### How It’s Used

Create a Project at the start of an initiative. Use a Template Project when standard defaults are required.

### Benefits

* Clean separation of work by initiative
* Consistent reporting and governance within an Organization
* Faster setup through templates (when enabled)

### Setup Steps

#### 1) Open Project creation

{% hint style="warning" %}
If **New Project** is not available, Project creation access is missing. Review [Understanding Access Levels](/organizations-and-projects/understanding-access-levels.md) or request access from an Admin.
{% endhint %}

{% columns %}
{% column %}
To start creating a Project:

* Sign in to Transform
* Navigate to the Organization
* Click the **New Project** (or **Add Project**) button

The Add Project form will open.
{% endcolumn %}

{% column %}

<figure><img src="/files/uG80vA1cDJklvNW64j7V" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

#### 2) Enter Project information

Provide basic details about the Project.

{% columns %}
{% column %}
To add Project details:

* Enter a **Project Name** (required)
  * Use a clear, descriptive name
  * For example: `{Organization} {initiative}`
* Add a **Project Description** (optional)
  * Brief overview of the Project scope
  * Include key objectives or deliverables
* Select a **Status** from the dropdown (defaults to **Not Started**)

Tip: Include stable context such as an Organization name or initiative name.
{% endcolumn %}

{% column %}

<figure><img src="/files/8PIpsB3MSa3aePUENCBw" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

#### 3) Set Project timeline

Define when the Project starts and ends.

{% columns %}
{% column %}
To set Project dates:

* Click the **Start Date** dropdown
* Select when the Project begins
* Click the **End Date** dropdown
* Select the expected completion date

Tip: Accurate dates improve capacity planning and reporting.
{% endcolumn %}

{% column %}

<figure><img src="/files/tcqrbZEzRRNxhH03e0tU" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

#### 4) Select Template Project (optional)

Copy a template to save setup time (if templates are available in the Organization).

{% columns %}
{% column %}
To use a template:

* Click the **Template Project** dropdown
* Select a template (if available)

What gets copied from templates:

* Project structure and organization
* Custom fields and settings
* Standard workflows

Leave this blank to start from scratch.
{% endcolumn %}

{% column %}

<figure><img src="/files/NcrY0GwI8dsNyA4nfzdx" alt=""><figcaption></figcaption></figure>
{% endcolumn %}
{% endcolumns %}

#### 5) Create the Project

Review entries and create the Project.

* Review the entered information.
* Click **Submit**.

#### After creation

After creation, the Project opens automatically.

Expected results:

* Project name in the header
* Project status indicator
* Empty work area ready for requirements and tasks
* Left navigation for Project sections

<figure><img src="/files/q0Z1vclhWtm7G7Sj2Yr9" alt=""><figcaption></figcaption></figure>

### Best Practices

* Establish naming conventions before creating many Projects.
* Set start and end dates early for reporting consistency.
* Use templates for repeatable governance patterns.

#### Troubleshooting

<details>

<summary>New Project button is not available</summary>

* Confirm Project creation permission exists in the Organization.
  * See [Understanding Access Levels](/organizations-and-projects/understanding-access-levels.md)
* Request Project creation access from an Admin.

</details>

<details>

<summary>Project creation form cannot be submitted</summary>

* Confirm **Project Name** is filled (required).
* Confirm end date is after start date.
* Confirm all required fields are complete.

</details>

<details>

<summary>Project details are incorrect after creation</summary>

* Edit Project settings after creation.
* Update name, dates, and other fields in Project details.

</details>

### Summary

Next steps:

* [Create and Assign Tasks](/transformations/create-and-assign-tasks.md)
* [Add Teammates](/organizations-and-projects/add-teammates.md)
* [Project Settings and Configuration](/organizations-and-projects/project-settings-and-configuration.md)

Support:

* [Contact Support](/resources/contact-support.md)


---

# 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, and the optional `goal` query parameter:

```
GET https://help.transform.ai/getting-started/create-a-project.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
