# Project Editing & Revision Workflow

#### 6.1 Editing Draft Projects

Projects in "draft" status can be freely edited:

**To Edit a Draft Project:**

1. Navigate to **Projects** (issuer dashboard)
2. Find the project with "Draft" status
3. Click **Edit** button
4. Make your changes
5. Click **Save Draft** or **Submit for Approval**

**What Can Be Edited:**

* All fields and sections
* Media and documents
* Token classes
* Financial information

#### 6.2 The Revoke & Re-Submit Process

Once a project is submitted or approved, it cannot be directly edited. To make changes, you must use the **Revoke** feature:

**When to Use Revoke:**

* Project is in "submitted" status and you need to make changes
* Project is "approved" but requires updates
* You received "revision requested" feedback from admin

**How to Revoke a Project:**

1. Navigate to **Projects** (issuer dashboard)
2. Find the submitted/approved project
3. Click **Revoke** button
4. Confirm the revocation
5. Project status changes back to "draft"
6. Project is removed from public view (if it was approved)
7. Edit the project as needed
8. Re-submit for approval

**Important Notes:**

* Revoking an approved project removes it from investor view immediately
* All revoke actions are logged in the audit trail
* You can provide a reason for revoking (optional)
* Platform admins are notified of revocations

**The Re-Submission Process:**

After revoking and editing:

1. Complete all necessary changes
2. Review the entire project for accuracy
3. Click **Submit for Approval**
4. Add submission notes (optional but recommended)
5. Project re-enters the approval queue
6. Platform admin reviews the updated version

#### 6.3 Handling "Revision Requested" Status

When a platform admin requests revisions:

**You Will Receive:**

* Email notification (if enabled)
* In-app notification
* Admin notes visible on project detail page

**Steps to Address:**

1. Read the admin notes carefully
2. The project automatically returns to "draft" status
3. Make the requested changes
4. Address all admin feedback points
5. Re-submit with notes indicating changes made

**Example Response:**

```
Changes made per admin feedback:
- Updated NOI calculations to reflect actual historical data
- Added supporting documentation for property appraisal
- Corrected token class voting rights description
- Uploaded additional property images as requested
```

#### 6.4 Version Control & Change History

All project changes are tracked:

**Audit Trail Includes:**

* Date/time of each change
* User who made the change
* Status transitions
* Submission/revocation events
* Admin review actions

**Accessing Change History:**

* Platform admins can view full history in Admin → Project Detail
* Issuer admins can view their own submission history
* Change log is permanent and cannot be deleted

#### 6.5 Best Practices for Project Management

**Before Submitting:**

* ✅ Review all financial calculations with your finance team
* ✅ Have legal counsel review compliance sections
* ✅ Ensure all images are high-quality and properly licensed
* ✅ Double-check token class terms and conditions
* ✅ Upload all required documents
* ✅ Test all external links (videos, websites)

**When Revising:**

* ✅ Clearly document what changes were made
* ✅ Address all admin feedback points
* ✅ Re-check related sections that may be affected
* ✅ Update the submission date if relevant

**Ongoing Management:**

* ✅ Monitor project status regularly
* ✅ Respond promptly to admin requests
* ✅ Keep investor documents up-to-date
* ✅ Update financial metrics if conditions change significantly

***


---

# 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-editing-and-revision-workflow.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.