✏️
Admin Panel
  • Overview
  • Quickstart
  • Handbook WIP
  • Feature Dependency Graph
  • Ingestion Flow
  • Data Visualization
  • User Permissions
  • Guidance Concepts
  • Offline Workflows
    • External Payment Processing
  • Freetown Phase 2 Admin Panel
    • Overview and Requirements
    • Dashboard Statistic View
    • Payment Module
    • Export Module
    • User Access and Permissions
    • Shape File Uploads
  • Messaging System
  • Contract System
    • Domain Model & Dictionary
    • Initial Notes & Reqs
    • User Stories (WIP)
  • Earnings tool
    • First Deployment Plan
  • Capture matching tool
    • Capture matching challenge
      • Methodologies
Powered by GitBook
On this page

Was this helpful?

  1. Contract System

Initial Notes & Reqs

This document holds the design information about the contract module in the admin panel

PreviousDomain Model & DictionaryNextUser Stories (WIP)

Last updated 1 year ago

Was this helpful?

In the context of Freetown there are contracts between the FCC (Freetown City Council) or EFA (Environment For Africa which is the main contractor of the project) and the CBOs (Community Based Organizations). Other possible contracts are between CBOs and planters or EFA to Nurseries.

Requirements

Statistic View inclusion

As per UX design in document the contract becomes part of the general stats to accumulate planter and tree capture information

Contract create, list, details and edit

Requirement to create, edit, list and view details of the contract

List view:

List view columns: Contract ID, Type, Organization (contract with), Contractor, Amount of trees, Status

Detail view

Contract Attributes in detail view

  • ID (contract number)

  • Organization name

  • Beneficiary name

  • # trees -> agreed amount of total trees and number of already approved trees

  • # planters ->

  • Status (planned, active, under review, closed or finalized, suspended)

  • Last modified or last activity

  • Type → there can be several types of contracts, CBO (org), Nursery (company or org) and possibly planter (individual)

  • Attach signed PDF contract file (per planter)

  • Payment thresholds

    • Weekly Consolidation (m1) vs Weekly Threshold Consolidation (m2)

Domain Model - Planter management requirements: With the contract module we need to be able to include one or more planter in a contract. In the future there will be no longer a direct association between the planter/grower and an organization. This will be done through contract

contract template vs contract (instantiation)

default contract - change in the mobile application

Dashboard Statistic View
https://www.figma.com/file/51iWcFythyfxrP4p4jd5rL/Admin-Panel?node-id=4%3A21
https://www.figma.com/file/51iWcFythyfxrP4p4jd5rL/Admin-Panel?node-id=767%3A633