Module 2
Farmer Onboarding & Profile¶
How to register a farmer and build a complete, evidence-backed profile: identity, family, land, location, crops, markets, finances and documents.
Every loan assessment in SaakhSetu is built on the farmer profile. When an assessment is submitted, SaakhSetu takes a frozen copy of the profile, and the Yogyank score is calculated from it. A complete, well-evidenced profile means a fair score and fewer returns for correction.
flowchart LR
A[Onboard farmer<br/>core profile] --> B[Family & household]
B --> C[Land parcels<br/>& soil health]
C --> D[Geo location]
C --> E[Crop details]
E --> F[Market linkages]
A --> G[Financial profile]
A --> H[Documents]
H -.->|verified evidence for| G
H -.-> C
H -.-> F
In this module¶
| # | Page | What you will learn | Mainly for |
|---|---|---|---|
| 2.1 | Finding & Managing Farmers | Searching the registry, profile statuses, deactivating and reactivating | Everyone |
| 2.2 | Onboarding a Farmer | The 4-step onboarding wizard, drafts, and when the farmer code is assigned | Credit Assistant |
| 2.3 | The Farmer Profile & Core Profile | The profile header, the eight tabs, farming history and the newness visit | Everyone |
| 2.4 | Family & Household | Family members and mirrored links to other farmers | Credit Assistant |
| 2.5 | Land Parcels & Soil Health | Parcels, cultivation continuity, retiring parcels, soil test evidence | Credit Assistant, Credit Officer |
| 2.6 | Geo Location | Capturing a parcel's pin and boundary, with consent | Credit Assistant |
| 2.7 | Crop Details | Crop records, planned crops, fallow, irrigation, field visits, completeness | Credit Assistant, Credit Officer |
| 2.8 | Market Linkages | Sales channel, sale transactions, receipts, sales against income | Credit Assistant |
| 2.9 | Financial Profile | Banking, income and its verification, machinery, livestock, labour, allied livelihood, credit history | Credit Assistant, Credit Officer |
| 2.10 | Documents | Uploading, verifying and rejecting documents | Credit Assistant, Credit Officer |
| 2.11 | Profile Readiness Checklist | What to check before starting a loan assessment | Credit Assistant |
Who does what¶
| Task | Credit Assistant | Credit Officer |
|---|---|---|
| Onboard and edit farmers, family, land, crops, markets, finances | ✓ (farmer.create, farmer.update) |
|
| Capture parcel location | ✓ (farmer.geolocate) |
|
| Record irrigation field visits | ✓ (farmer.field_visit_capture) |
|
| Upload documents | ✓ | |
| Verify or reject documents, verify income, classify loans, confirm soil evidence, verify "not yet sold", record newness visits | ✓ (document.verify) |
|
| Verify a "no prior formal credit" declaration | ✓ (credit_history.verify), and never the person who recorded it |
|
| Deactivate or reactivate a farmer | ✓ (farmer.manage) |
These are the default role permissions. Your bank's roles may differ: see 1.6 Role & Permissions.
Principles that run through this module¶
Evidence over declaration
SaakhSetu distinguishes what the farmer declared from what was verified. A declared figure is recorded and shown as Declared. A verified figure needs a verified document or an independent check. Scoring gives more weight to verified evidence.
History is kept, never overwritten
Corrections to location, irrigation, field visits, soil verification, loan classification and similar records add a new version. The earlier one is kept as history. Documents are reviewed once. Parcels are retired, not deleted.
Separation of duties
The person who records something is not the person who verifies it. For example, a no-prior-credit declaration must be verified by someone else.