> For the complete documentation index, see [llms.txt](https://aerogcs-docs.aeromegh.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aerogcs-docs.aeromegh.com/4-project/4.1-create-project.md).
# 4.1 Create Project
For creating a new project click on the '+' symbol present on the dashboard near to project. This tab allows us to create a new project with project details such as Project name, client name, and Plan name.
Entering details of Project
Project creation requires you to enter three different data fields.
a) **Project Name:** This is the name of the project. Any alphabet with up to 50 characters long can be entered as the project name.
b) **Plan Name:** This is the plan name. You can define a proper plan name. For example, Field01 can be a plan name. This will be a character input of up to ten characters.
A newly created project may contain several plans with different types of vehicles and flight types. Plan can be created in offline mode also. Plans created in offline mode can be synchronized with the cloud so that the user can retrieve them whenever it's required. The user can create a number of plans with different vehicle types and flight types respectively.
---
# 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://aerogcs-docs.aeromegh.com/4-project/4.1-create-project.md?ask=&goal=
```
`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.