<aside>
The system consists of five databases and one dashboard.
| Database | Description |
|---|---|
| ‣ | Stores all projects. |
| ‣ | Stores team members, their available capacity, and aggregated workload statistics. |
| ‣ | Parent tasks within each project. |
| ‣ | Individual work assignments under each parent task, including assignees and estimated effort. |
| ‣ | Lightweight reminders that don't require effort estimation. |
| dashboard | Description |
|---|---|
| ‣ | The dashboard consolidates information from all five databases and provides: |
• Task & Task Allocation Gantt Charts • Workload estimation across different time ranges • Task cards for quick project management • Resource utilization reports • Task type analysis | </aside>
<aside>

<aside>

</aside>
Circle Icon (Red Outline) — Read-only property
displays calculated or referenced values.
These properties cannot be edited directly and are primarily used to display system-generated information or values referenced from other databases.
<aside>

</aside>
Edit box Icon (Green Outline) — Optional editable property
Editable fields that provide additional information or descriptions.
Updating these values will not directly affect workload calculations.
<aside>

</aside>
Edit Icon (Yellow Outline) — Required property
Required input fields.
Values entered here directly affect workload estimation, scheduling calculations, and Gantt chart visualization.
</aside>
<aside>


Every database field and dashboard widget includes built-in documentation.
Simply hover your cursor over a field or dashboard tab to view its description and understand how it relates to other properties
</aside>
<aside>
The system follows a hierarchical structure.
A Project can contain multiple Tasks.
Each Task usually represents a project phase or development module.
Examples of project phases include:
Examples of development modules include:
A Task can therefore represent something like:
Project A → Login System → UX Design
or
Project B → Customer Data Integration → Development
Each Task can contain multiple Task Allocations.
A Task Allocation represents the actual work assigned to one team member.
For example, under the parent task Login System – UX Design:
</aside>