# Project Creation & Management (Issuer Admin)

#### 5.1 Creating a New Project

**Prerequisites:**

* You must be an issuer admin for an organization
* Your organization must be approved by platform admin
* You must have selected an organization (use the organization switcher if you manage multiple)

**Steps to Create a Project:**

**Step 1: Navigate to Project Creation**

1. Log in as an issuer admin
2. Ensure the correct organization is selected (check sidebar)
3. Navigate to **Projects → Create New Project**

**Step 2: Complete Basic Information**

**Required Fields:**

* **Project Name**: A clear, descriptive name for the asset
* **Tagline**: A short, compelling description (1 sentence)
* **Description**: Detailed overview of the asset and investment opportunity
* **Property Type**: Select from dropdown (Office, Retail, Residential, etc.)
* **Asset Class**: Real Estate, Infrastructure, Commodities, etc.

**Location Information:**

* **Address**: Full street address
* **Coordinates**: Latitude/longitude (auto-filled if available)

**Step 3: Financial Details**

**Asset Valuation:**

* **Purchase Price**: Original acquisition cost
* **Appraised Value**: Current appraised value
* **Expected Exit Value**: Projected value at exit

**Performance Metrics:**

* **NOI (Net Operating Income)**: Annual net operating income
* **Cap Rate**: Capitalization rate (%)
* **Target IRR**: Internal rate of return target (%)
* **Target Annual Return**: Expected annual return (%)

**Investment Terms:**

* **Target Amount**: Total fundraising goal
* **Currency**: USD, EUR, etc.
* **Investment Term**: Duration in months
* **Start Date**: Fundraising start date
* **End Date**: Fundraising end date

**Step 4: Use of Funds**

Define how the raised capital will be used:

```json
{
  "property_acquisition": 60,
  "renovations": 20,
  "operating_capital": 10,
  "legal_fees": 5,
  "platform_fees": 5
}
```

* Each category with percentage allocation
* Must total 100%

**Step 5: Token Class Configuration**

Create at least one token class for the project:

**Token Class Fields:**

* **Class Name**: e.g., "Class A Preferred"
* **Token Symbol**: e.g., "PROP-A"
* **Price Per Token**: Price in USD (or selected currency)
* **Minimum Investment**: Minimum investment amount
* **Maximum Investment**: Maximum investment amount (optional)
* **Voting Rights**: Yes/No
* **Transferable**: Yes/No
* **Lockup Period**: Months before tokens can be transferred
* **Distribution Frequency**: Quarterly, Annual, etc.
* **Projected Yield**: Expected annual yield (%)
* **Asset Backing**: Description of asset backing

**Multiple Token Classes:**

* Projects can have multiple token classes (e.g., Class A, Class B)
* Each class can have different rights, pricing, and terms
* Useful for creating tiered investment opportunities

**Step 6: Media & Gallery**

**Hero Image:**

* Upload a primary hero image for the project
* Recommended: High-quality, professional photo (1920x1080px)

**Gallery Images:**

* Upload multiple images showcasing the asset
* Supports: Property photos, renderings, floor plans
* Drag and drop to reorder images
* Add captions/descriptions for each image

**Video:**

* Add a video URL (YouTube, Vimeo)
* Optional but recommended for major projects

**Blueprint/Floor Plan:**

* Upload technical drawings or floor plans
* PDF format recommended

**Step 7: Legal & Compliance**

**Offering Type:**

* Reg D 506(b)
* Reg D 506(c)
* Reg A+
* Reg CF

**Jurisdiction:**

* Primary legal jurisdiction
* Securities law compliance region

**Issuer Entity:**

* Legal entity name issuing the tokens
* May differ from organization name

**Legal Disclaimers:**

* Required disclosure text
* Risk factors
* Investment suitability warnings

**KYC/AML Status:**

* Current compliance status
* Required for all projects

**Step 8: Blockchain Details**

**Smart Contract:**

* Smart contract address (if already deployed)
* Blockchain network (Ethereum, Polygon, etc.)

**Service Providers:**

* Escrow provider name
* Transfer agent name

#### 5.2 Saving as Draft vs. Submitting

**Save as Draft:**

* Saves all progress without submitting for review
* Project remains in "draft" status
* Only visible to you and platform admins
* Can be edited at any time
* No approval required

**Submit for Approval:**

* Submits project to platform admin for review
* Changes project status to "submitted"
* Can no longer be edited without revoking
* Enters the approval workflow
* Platform admin receives notification

**Best Practice:**

* Save as draft frequently while working
* Only submit when project is complete and ready for review
* Ensure all required fields are filled
* Upload all necessary documents and images
* Double-check financial calculations

#### 5.3 Required vs. Optional Fields

**Required Fields (Must be completed before submission):**

* Project name
* Description
* Property type
* Asset class
* Location address
* Target amount
* At least one token class
* Legal offering type
* Jurisdiction

**Optional Fields (Recommended but not required):**

* Tagline
* Hero image
* Gallery images
* Video URL
* Blueprint
* Purchase price
* Appraised value
* NOI, Cap rate, IRR
* Smart contract address
* Escrow/transfer agent details

#### 5.4 Form Validation & Error Handling

The system validates your input in real-time:

**Validation Rules:**

* Currency values must be positive numbers
* Percentages must be between 0-100
* Dates must be in valid format
* Token prices must be positive
* Min investment ≤ Max investment
* Use of funds must total 100%

**Error Messages:**

* Red text appears below invalid fields
* Submit button is disabled until errors are resolved
* Hover over error icons for detailed explanations

***


---

# Agent Instructions: 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:

```
GET https://docs.treem.io/getting-started/project-creation-and-management-issuer-admin.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.