Track Your Projects and Investments on EarthCoop
EarthCoop records project and investment lifecycle information so members can distinguish what has been proposed, reviewed, approved, committed, paid, revised or archived. The key rule when reading these screens is simple: a workflow status is not automatically a monetary event.
Track a project you own
Open the current My Projects surface to review projects owned by you or by a group for which your current responsibility grants access. The project record can expose its present review state and the history recorded by the project service.
The current core project review states are:
draft → pending → under_review → approved / rejected / archived
| Status | Meaning |
| --- | --- |
| draft | Project exists but has not been formally submitted. |
| pending | Submitted and waiting for review. |
| under_review | Formal review has started. |
| approved | The review decision is positive. It does not prove that money moved. |
| rejected | Not approved or returned for revision; eligible projects may be resubmitted. |
| archived | Removed from the normal active workflow. |
Review history
Project review actions are stored separately from the current status so later changes do not erase the decision trail. Depending on the action, history can record review start, approval, rejection, revision request, resubmission and archival together with the responsible reviewer and comments supplied by the workflow.
A resubmission changes the current project state but does not make the earlier rejection or revision event disappear. Historical review facts remain useful for audit and accountability.
Approval is not payment
An approved status tells you what happened in the review domain. It does not mean any member balance has been debited, any project account has been credited, or any Active Bahar is available for execution.
For public-project financing, separate records are required for Commitment, Activation and Transfer before value can reach the Active Project Fund. Check the monetary ledger rather than inferring those events from the project badge.
Track an investment
Where the current investment surface exposes your investment records, use the recorded investment state and linked monetary evidence together. An investment record can show the contractual/workflow state of the relationship, while the NajmBahar ledger establishes whether an actual Bahar Transfer occurred.
This distinction matters because:
investment record ≠ Transfer
expected value ≠ guaranteed return
project completion status ≠ automatic payment
Bahar amounts
Bahar is the monetary unit used by EarthCoop. Gol is the subunit of Bahar (1 Bahar = 100 Gol). Interfaces may use smaller-unit precision internally, but values should be understood as Bahar-denominated economic amounts rather than a separate Gol currency.
Returns and valuations
A project or investment contract may display an expected return, profit-share term, asset value, or other economic entitlement. Such a figure is contractual information or a valuation; it is not newly created money and it is not a guarantee that the outcome will be achieved.
When evaluating a tracked investment, consider the project's actual execution, risk disclosures, applicable insurance if any, contractual conditions, and the monetary events already recorded.
Notifications
The current project service sends owner-facing notifications for important project decisions such as approval, rejection and revision requests. Other domain notifications should be interpreted according to the event they actually report; a notification itself is not proof of a money transfer.
Audit checklist
When you need to understand what has actually happened, check the facts in this order:
- Project record — what is the current review/lifecycle state?
- Review history — what decision or revision events produced that state?
- Investment/contract record — what economic relationship was recorded?
- NajmBahar monetary ledger — did Commitment, Activation or Transfer actually occur?
- Project-fund state — is Active Bahar actually available for permitted execution payments?
This separation prevents a UI label from being mistaken for legal authorization, a contractual obligation, or completed payment.