SCP Loan & Subsidy Workflow
Workspace Dashboard
Role-based operational dashboard and reporting.
Automatic Database Sync
Initializing…
0
Applications
Current workspace
Open section →
0
Pending Action
Current workspace
Open section →
0
Generated Documents
Current workspace
Open section →
0
Completed
Current workspace
Open section →
Required Actions
Select an item to open the relevant workstation section.
Workflow Status
Current movement of proposals through the system.
Current Scheme & Access
Operational rules currently applied to this workspace.
Database Health
Master data, users and transaction database overview.
Recent Applications
Most recently updated records visible to this workspace.
| Application ID | Beneficiary | Block | Bank | Status | Updated |
|---|
Default Printable Application Form
The supplied editable Bengali HTML form is the system's default 2-page A4 Application Form. Data is auto-populated from Beneficiary Application Entry.
Default statutory application template: The uploaded editable HTML form is used directly-its Bengali wording, tables, A4 sizing, certificate, Panchayat Samiti/Municipality recommendation, Bank Manager sanction and receipt areas are preserved. The specimen form number is replaced by the system-generated Application ID. Saved beneficiary data is filled automatically into the corresponding fields. The populated form remains editable before printing.
Beneficiary Master
Reusable central beneficiary records
| Action |
|---|
Beneficiary Application Form / উপভোক্তা আবেদনপত্র
Enter every applicant-side field required by the default Bengali A4 Application Form. / ডিফল্ট বাংলা A4 আবেদনপত্রে প্রয়োজনীয় আবেদনকারী-সংক্রান্ত সকল তথ্য পূরণ করুন।
Application ID / আবেদন আইডি: generated automatically as Sl. No./SCP/DD/Block Initial/FY. / স্বয়ংক্রিয়ভাবে তৈরি হবে এবং ডিফল্ট আবেদনপত্রের মুদ্রিত সিরিয়াল নম্বরের স্থানে বসবে।
Application Control / আবেদন নিয়ন্ত্রণ
১। আবেদনকারীগণের বিবরণ / Applicant Details
Age / বয়স is calculated automatically.
System verification field / সিস্টেম যাচাইকরণ ক্ষেত্র; supplied printable template-এ পৃথক ঘর নেই।
Address / ঠিকানা
২। প্রস্তাবিত প্রকল্প / Proposed Project
Default Bank Loan / ব্যাঙ্ক ঋণ = ₹10,000 and Subsidy / অনুদান = ₹10,000. Both are editable for the individual application. Project Cost can also be edited.
৩-৮। Land, Income, Family, Property & Previous Assistance / জমি, আয়, পরিবার, সম্পত্তি ও পূর্ববর্তী সহায়তা
Page 2 Land Certificate Details / দ্বিতীয় পাতার জমি-সংক্রান্ত শংসাপত্রের তথ্য
৯। ব্যাঙ্ক অ্যাকাউন্ট বিষয়ক তথ্য / Bank Account Details
Nodal Bank → Branch → IFSC / নোডাল ব্যাঙ্ক → শাখা → IFSC Bank Master থেকে নির্বাচন করুন। তথ্য ডিফল্ট বাংলা আবেদনপত্রে স্বয়ংক্রিয়ভাবে পূরণ হবে।
Enter DOB, category and income to check eligibility. / যোগ্যতা যাচাইয়ের জন্য জন্মতারিখ, শ্রেণি ও আয় পূরণ করুন।
Beneficiary / Case Register
Read-only transaction register. No Edit, Delete or Approve control is provided at beneficiary level.
| Financial Year | Application ID / UBID | Case No. | Beneficiary | Block's Memo | Bank | Financials | Status |
|---|
Form A Sponsorship Batch
The supplied statutory Form A template contains 13 beneficiary rows on each requisition page. More than 13 proposals are automatically continued on another identical requisition page.
A sponsored Form A uses one Financial Year, one Block/Panchayat Samiti, one Gram Panchayat, one Nodal Bank Branch and one Block's Memo/Date for the whole batch. The Bank enters its own Memo No. and Date from Bank Login after receiving the digital Form A. Individual beneficiary Edit/Delete/Approve controls are not available.
Eligible Beneficiaries For This Batch
0 selected • 13 rows per supplied Form A page
| Select | UBID | Beneficiary | Project | Loan | Subsidy | Status |
|---|
Sponsored Form A Register
| Form A Batch No. | FY | Block / GP | Bank / Branch | Block's Memo | Bank's Memo & Date | Beneficiaries | Pages |
|---|
Form A Batch Processing
Batch-level scrutiny, bank return, District sanction and dispatch. No beneficiary-level approval is used.
Each row represents one sponsored statutory Form A batch. Block's Memo, Bank's Memo and Bank Memo Date belong to the whole batch. Sanction and workflow movement are performed at batch level only.
| Batch | FY | Block / GP | Bank / Branch | Block's Memo | Bank's Memo & Date | Beneficiaries | Status | Batch Action |
|---|
Bank Digital Inbox
Form A batches digitally forwarded by Block / Gram Panchayat to this Nodal Bank Branch.
Bank reviews the digital Form A and beneficiary application records, enters one Bank Memo No. and Date for the whole Form A batch, prints/signs the physical Application Forms and Form A, and forwards the Form A electronically to District Office for approval.
| Form A Batch | Block / GP | Beneficiaries | Block's Memo | Bank Memo | Status | Bank Action |
|---|
Bank Loan Disbursement Entry
Enter beneficiary-wise Bank decisions and disbursement details. The generated statutory Form B is a separate locked reference document.
Beneficiary-wise Bank Loan Disbursement Data
| UBID | Beneficiary | Project | Sanctioned Loan | Bank Decision | Loan Disbursed | Disbursement Date | Rejection / Anomaly | SB Account |
|---|
SB Account Correction
Special District Office control. Other beneficiary master fields remain non-editable.
Only District Office / Administrator can change a beneficiary Savings Bank Account number. Every change is stored with old account, new account, reason, user role and timestamp in the audit trail.
| UBID | Beneficiary | Case / FY | Bank / Branch | Current SB Account | District Action |
|---|
Subsidy Release / DBT
Release admissible Corporation subsidy after duly completed Form B is received from the Bank.
Subsidy is released to the beneficiary's Savings Bank Account only after the Bank Loan has been disbursed and Form B has been received. Margin Money is not used operationally.
| UBID | Beneficiary | SB Account | Subsidy | UTR / Transaction Reference | Status |
|---|
Dispatch & Receipt Register
Track physical movement of Form A, Form B, letters and claims
Dispatch Register
| No. | Date | Case | To | Document | Mode |
|---|
Receipt Register
| No. | Date | Case | From | Document | Remarks |
|---|
Reports
Operational, financial and pendency reports
Environment Management
Keep live beneficiary transactions completely separate from demonstration/testing workflow data.
Production Database
0Beneficiaries
0Applications
0Form A Batches
Protected: Demo reset and demo workflow actions do not modify this database.
Demo / Sandbox Database
Safe workflow testing environment.
0Beneficiaries
0Applications
0Form A Batches
Reset restores the standard sample applications and clears all demo workflow actions.
Demo Reference Data Synchronization
Keep the Sandbox UI, Bank Master and scheme reference data aligned with Production without copying live beneficiaries or workflow transactions.
Environment Security Rules
Separate Data StoreProduction and Demo transactions use different storage/database keys.
User-bound EnvironmentThe environment is assigned by Administrator; the user cannot switch it at login.
Full Demo WorkflowDemo users may create applications, Form A, Bank actions, approvals, Form B and test subsidy workflow.
Visible IdentificationA prominent DEMO / SANDBOX badge is displayed throughout every demo session.
District Branch Setup
Multi-district tenant configuration. Every District Branch works only with its own beneficiaries, masters, workflow and documents.
Tenant isolation: every application, batch and generated document carries a District Code. App Owner may view all districts; a District Branch cannot access another district.
Production Tenant Backend
Server-side district isolation status.
Backend has not been checked yet.
District Transaction Store — Phase 2
Beneficiary, Application, Form A/B, Muster, Forwarding and rectification state is synchronized per District tenant.
Local preview mode. Deploy to PHP/MySQL to activate tenant transaction synchronization.
Normalized Tenant Database — Phase 3
Server-indexed Beneficiaries, Applications, Form A batches and generated-document register for reporting/search.
Deploy schema_v152.sql and connect the PHP backend to activate normalized reporting.
Server Workflow & Document Audit — Phase 4
Form B, Muster Roll, Forwarding Letter and workflow transitions are mirrored into dedicated relational tables with server-side audit events.
Deploy schema_v153.sql and authenticate to the production backend to activate server workflow audit.
Server-Authoritative CRUD — Phase 5
Individual Application, Form A and Form B writes are committed to tenant-isolated relational tables without rewriting the whole District snapshot.
Deploy schema_v154.sql and sign in through the production backend to activate record-level writes.
Server References, Payments & Conflict Control — Phase 6
Central reference sequencing, subsidy/UTR transactions and record-level conflict refresh.
Deploy schema_v155.sql and authenticate to activate server-generated IDs/references and payment transactions.
Server User Management, Rectification & Reports — Phase 7
Production user accounts, document rectification actions and district/statewide reporting are now server-backed.
Deploy schema_v156.sql and sign in through the production backend to activate server-backed administration.
Server Locks, Inboxes, Registers & Reports — Phase 8
Record checkout, direct server inboxes, dispatch/receipt register, filtered reports and deployment health checks.
Deploy schema_v157.sql and sign in through the production backend to activate Phase 8.
Server Workflow Authority, Selectors & Dashboard — Phase 9
Bank Form A forwarding, District approval, Form B dispatch, selectors and dashboard KPIs now read/write directly through the server.
Deploy schema_v158.sql (or migration_v158_from_v157.sql) to activate Phase 9.
Server Form B Return, Completion & Production Lists — Phase 10
Bank Form B return/disbursement, batch completion and large Beneficiary/Case registers are server-authoritative.
Deploy schema_v159.sql (or migration_v159_from_v158.sql) to activate Phase 10.
Production Hardening, Timeline & Statewide Dashboard — Phase 11
Session hardening, record timelines, statewide drilldowns, migration readiness and strict production health.
Deploy schema_v160.sql (or migration_v160_from_v159.sql) to activate Phase 11.
Production Operations & Integrity — Phase 12
Database integrity audit, server maintenance control, session visibility and strict transient Production cache.
Deploy schema_v161.sql (or migration_v161_from_v160.sql) to activate Production Operations.
Final Production Authority & Go-Live Verification — Phase 13
Strict backend authentication, server-first data hydration, installer readiness and end-to-end production verification.
Deploy schema_v162.sql (or migration_v162_from_v161.sql) and use the strict Production build to activate Phase 13.
District Branch Register — App Owner
| Code | District Branch | HQ | Beneficiaries | Batches | Action |
|---|
Block / Municipality & GP / Ward Master
| Type | Block / Municipality | Code | GP / Ward | Code | Action |
|---|
District Bank Branch Master
| Bank | Branch | IFSC | Location | Action |
|---|
LGD & Bank Master Data
Maintain Block / Gram Panchayat and Bank / Branch / IFSC master records in a workstation-friendly layout.
Master changes affect future selections only. Existing beneficiary/case records are not silently rewritten. Deletion is blocked when a GP or Bank Branch is already referenced by transaction data.
Block / Gram Panchayat Master
| Block | Block LGD | Gram Panchayat | GP LGD | Action |
|---|
Full Bank / Branch / IFSC Database
Dakshin Dinajpur Bank Branch Master contains Bank, Branch and IFSC only.
Loading Dakshin Dinajpur Bank Master…
| Bank | Branch | IFSC | Action |
|---|
Document Rectification Center
Safe correction, soft-delete/void, regeneration and revision tracking for Form A, Form B, Muster Roll and Bank-wise Forwarding Letters.
Generated statutory documents are not edited as uncontrolled final files. Correct the source batch/workflow data here, then regenerate the affected document set. “Delete” is implemented as Void / Soft Delete so the previous reference and audit trail are preserved.
0Active Documents
0Voided Documents
0Revision Events
0Linked Batches
| Document | Reference | Revision | Batch / FY | Bank / Branch | Beneficiaries | Status | Last Rectification | Actions |
|---|
Rectification / Revision History
| Date & Time | User | Action | Document | Reference | Revision | Reason |
|---|
User Management & Role Allocation
Create login accounts within one District Branch. The App Owner has all-district access; all other users are district-isolated.
Scope enforcement: App Owner can view all District Branches. Other Administrators are District Administrators. Block/Municipality and Bank users are restricted first by District Code and then by their Block/IFSC.
Registered Users
Passwords are never displayed in the table.
| User ID | Display Name | Environment | Role | Assigned Scope | Status | Last Login | Action |
|---|
West Bengal Gramin Bank - Branch LOV
Maintain branch names for the common IFSC PUNB0RRBBGB. All branches use the same IFSC, but remain separate branch selections and Bank Workspaces.
The IFSC is fixed as PUNB0RRBBGB. Add only the Branch Name. The application Bank/Branch dropdown will show every branch entered here while automatically keeping the same IFSC.
| Bank | Branch Name | Common IFSC | Action |
|---|
Administrator Settings
Scheme rules are versioned; sanctioned historical cases retain their frozen values
Do not expose a Google service-account key inside this HTML file. Use the supplied Apps Script backend as the controlled API.
Central Backend Database
Google Apps Script + Google Spreadsheet server-side database, authentication and scoped synchronization.
NOT CONNECTED
-Backend Environment
-Authenticated Session
NeverLast Central Sync
0Pending Changes
Configure the Production Apps Script Web App URL, deploy the backend, and sign in again to activate server-side authentication.
Statutory Form A
The uploaded FOrm A.html is used as the structural reference for a native HTML Form A, with fields mapped directly into the corresponding statutory locations. Requisition and sanction/office-use pages are auto-populated from the batch/workflow.
Generated Form B
Native A4-landscape Form B integrated from the supplied HTML template and populated from the selected batch.
Form B is generated from the selected Form A batch. Bank loan disbursement amount/date, subsidy, beneficiary banking details and workflow memo fields are populated automatically. Borrower signature/L.T.I. remains blank for physical signing.
Muster Roll
Auto-populated from approved Form A batch and Bank loan-disbursement data.
The supplied Muster Roll template is now the active system template. Recipient, guardian/address, project/project cost, subsidy, Bank memo and disbursement details are populated automatically. Recipient and witness signature columns remain blank for physical signing.
Generated Muster Roll Register
| Muster Roll Ref. | Form A Batch | FY | Bank | Beneficiaries | Status |
|---|
Bank-wise Forwarding Letter
Automatically generated together with Form B and Muster Roll for the concerned Nodal Bank / Branch.
The beneficiary table and document references are generated automatically. The final official body/wording of the forwarding letter is intentionally left as a controlled placeholder until the approved contents are supplied.
Generated Forwarding Letter Register
| Letter Ref. | Form B Ref. | Muster Roll Ref. | FY | Bank / Branch | Beneficiaries | Status |
|---|