# PC-I Complete Workflow — Project Concept

## Module Overview

**PC-I (Project Concept-I)** is the first and most comprehensive procurement case form. It documents the full concept of a development scheme: location, objectives, costs, benefits, implementation schedule, and compliance checklists. Department submitters prepare PC-I; checkers, department approvers, and P&D approvers review it; and it may proceed through **Pre-PDWP** and **PDWP** meetings before Chairman advice.

This guide covers every wizard step, required fields, AI assistance, and the complete lifecycle from creation to approval.

---

## Navigation

1. **Planning & PC Forms → PC Forms**
2. Click **Generate PC**
3. Select **PC-I**
4. Or open an existing PC-I from the list (Draft, Forwarded, or Deferred)

---

## Wizard Flow — All Steps

PC-I has **17 steps** plus **Signatures & Submit**.

---

### Step 1: General Information

**Purpose:** Link the PC-I to the correct scheme and capture basic project identity.

| Field | Required? | What to Enter |
|-------|-----------|---------------|
| **Scheme** | Yes | Select from dropdown; ADP and UID sync automatically |
| **ADP** | Auto | Annual Development Programme number |
| **UID** | Auto | Unique scheme identifier |
| **Project / Scheme title** | Yes | Official project name |
| **Department** | Yes | Executing department |
| **Sector / Sub-sector** | As shown | Classify the project |
| **Scheme type** | As shown | Capital, revenue, etc. |
| **Start year / Completion** | As shown | Project timeline |

**AI assistance:** Limited on this step—mainly scheme-linked fields.

**Save Draft:** Saves scheme link and all general fields.

**Next Step:** Validates required selections; opens Location step.

---

### Step 2: Location

**Purpose:** Document where the project will be implemented geographically.

| Field | Required? | What to Enter |
|-------|-----------|---------------|
| **Region / District / Taluka** | Yes | Administrative boundaries |
| **Location description** | Yes | Narrative of site(s) |
| **Map coordinates** | If applicable | Pin or describe on map widget |

**Upload:** Location maps or site plans if the form requests attachments.

**Next Step:** Proceeds to Authorities Responsible.

---

### Step 3: Authorities Responsible

**Purpose:** Identify sponsoring agency, executing agency, and operation & maintenance responsibility.

| Field | Required? | What to Enter |
|-------|-----------|---------------|
| **Sponsoring agency** | Yes | Department sponsoring the scheme |
| **Executing agency** | Yes | Agency implementing works |
| **Operation & maintenance** | Yes | Who maintains assets after completion |
| **Contact officers** | As shown | Names and designations |

---

### Step 4: Plan Provision

**Purpose:** Show how the scheme fits in the development plan and funding shares.

| Field | Required? | What to Enter |
|-------|-----------|---------------|
| **Plan reference** | Yes | ADP / PSDP provision details |
| **Funding source shares** | Yes | Percentage by source (must total correctly) |
| **Foreign assistance flag** | If FPA | FPA details |

**Validation:** Share percentages must be valid numbers (0–100).

---

### Step 5: Project Objective

**Purpose:** State what the project aims to achieve.

| Field | Required? | What to Enter |
|-------|-----------|---------------|
| **Project Objectives** | Yes | Clear, measurable objectives |
| **Project Scopes** | Yes | Boundaries of work covered |

**AI — Fill with Agent:** Available on **Project Objectives** and **Project Scopes**. Click **Fill with Agent**, describe your project, review and edit the generated text.

---

### Step 6: Description & Justification

**Purpose:** Explain the project need, design, and justification for public investment.

| Field | Required? | What to Enter |
|-------|-----------|---------------|
| **Brief Descriptions** | Yes | Summary of the project |
| **Project Justifications** | Yes | Why the project is needed now |
| **Sectoral Specific Information** | Yes | Sector-relevant technical context |

**AI — Fill with Agent:** Available on all three narrative fields. Always verify technical facts and cost references manually.

---

### Step 7: Cost Estimates

**Purpose:** Detail capital costs, BOQ items, and total project cost.

| Field | Required? | What to Enter |
|-------|-----------|---------------|
| **BOQ / Cost lines** | Yes | Itemized costs from Bill of Quantities |
| **Total cost** | Yes | Sum of all components |
| **Foreign exchange component** | If FPA | FE portion |

**Actions:** Link to **BOQ Management** / CSR Costing where integrated—import or pick cost lines.

**Upload:** Supporting cost estimates, consultant estimates.

**Next Step:** Cannot proceed if total cost is zero or required lines missing.

---

### Step 8: Annual Operating Cost (Post Completion)

**Purpose:** Estimate recurring costs after project completion.

| Field | Required? | What to Enter |
|-------|-----------|---------------|
| **Annual O&M costs** | Yes | Staff, utilities, maintenance |
| **Manpower recurring** | As shown | Posts and salaries |

**AI — Fill with Agent:** Available on narrative O&M fields.

---

### Step 9: Financial Phasing

**Purpose:** Spread costs across financial years.

| Field | Required? | What to Enter |
|-------|-----------|---------------|
| **Year-wise phasing table** | Yes | Amount per FY |
| **Total phasing** | Must match | Should equal total cost from Step 7 |

---

### Step 10: Demand & Supply Analysis

**Purpose:** Demonstrate need vs. existing capacity.

| Field | Required? | What to Enter |
|-------|-----------|---------------|
| **Demand and Supply Analysis** | Yes | Narrative and figures |

**AI — Fill with Agent:** Available.

---

### Step 11: Project Benefits & Analysis

**Purpose:** Quantify economic and social benefits.

| Field | Required? | What to Enter |
|-------|-----------|---------------|
| **Benefit sections** | Yes | Each sub-section in the form (direct, indirect, employment, etc.) |

**AI — Fill with Agent:** Available on narrative benefit fields.

---

### Step 12: Implementation Schedule

**Purpose:** Timeline for project execution (Gantt-style narrative or table).

| Field | Required? | What to Enter |
|-------|-----------|---------------|
| **Implementation schedule / Gantt chart** | Yes | Milestones and durations |

**AI — Fill with Agent:** Available.

**Upload:** Detailed Gantt chart PDF if required by department policy.

---

### Step 13: Management & Manpower

**Purpose:** Organizational structure during implementation.

| Field | Required? | What to Enter |
|-------|-----------|---------------|
| **Management Structure and Manpower Requirements** | Yes | Posts, reporting lines |
| **RBM indicators** | As shown | Input, output, outcome, impact rows |

**AI — Fill with Agent:** Available on management narrative; RBM indicator rows are manual entry.

---

### Step 14: Additional Scheme / Decisions Required

**Purpose:** Note any linked schemes or pending decisions.

| Field | Required? | What to Enter |
|-------|-----------|---------------|
| **Additional Scheme/Decisions Required** | If applicable | Cross-references or board decisions needed |

**AI — Fill with Agent:** Available.

---

### Step 15: SDG Goals

**Purpose:** Map project to Sustainable Development Goals.

| Field | Required? | What to Enter |
|-------|-----------|---------------|
| **SDG selections** | Yes | Tick applicable SDG targets |
| **SDG narrative** | As shown | How project contributes |

---

### Step 16: Checklists

**Purpose:** Confirm regulatory and procedural compliance before submission.

| Field | Required? | What to Enter |
|-------|-----------|---------------|
| **Checklist items** | Yes | Answer each yes/no or text item |

**AI — PC1 Analyze (AI):**

1. Click **PC1 Analyze (AI)** button on this step.
2. Wait for analysis to complete.
3. Review suggestions in the modal.
4. Fix any flagged gaps before submitting.

**Submit requirement:** All mandatory checklist items must be complete to Submit.

---

### Step 17: Signatures & Submit

**Purpose:** Record preparer, checker(s), and approver signatures; finalize submission.

| Field | Required? | What to Enter |
|-------|-----------|---------------|
| **Prepared By** | Yes | Name, designation, date |
| **Checker** | Yes | Assigned checker(s) |
| **Approved By** | As workflow | Department approver when applicable |

**Actions:**

- **Save as Draft** — keeps PC-I in Draft
- **Submit** — sends to **Forwarded for Checking**

After Submit, the submitter typically cannot edit until the form is **Deferred**.

---

## Complete Workflow — Submitter

1. **Create** — Generate PC → PC-I → select scheme
2. **Edit** — Complete all 17 steps; use Save as Draft frequently
3. **Upload** — Attach PDFs on fields that support annexures
4. **Submit** — After checklists and signatures complete
5. **Track** — Watch status on PC Forms list and Schemes pill
6. **Respond** — If Deferred, read remarks in notification
7. **Resubmit** — Edit (**Modified** label), correct, Submit again

---

## Complete Workflow — Checker

1. Receive notification: PC-I **Forwarded for Checking**
2. Open PC Forms → click the row
3. Review every section in the Details modal
4. **Approve** — optional remarks, signature → forwards to Department Approval or P&D
5. **Defer** — required remarks, optional attachment, signature → returns to submitter

Multiple checker slots may be required before the form advances.

---

## Complete Workflow — Department Checker

1. See PCs only after required checker reviews complete
2. Status: **Forwarded for Approval**
3. Verify department matches scheme
4. **Approve** or **Defer** with remarks

---

## Complete Workflow — P&D Approver

1. Status: **Forwarded to P&D**
2. **Generate Working Paper** from list or modal
3. Schedule **Pre-PDWP** or **PDWP** meeting if needed
4. **Approve** or **Defer** at P&D stage

---

## Business Scenario: Creating a New PC-I

**Situation:** Education department prepares PC-I for a new school building.

1. Hassan confirms scheme UID on **Schemes** page.
2. **PC Forms → Generate PC → PC-I**.
3. Selects scheme; ADP/UID auto-fill.
4. Completes Location (district taluka), Authorities, Plan Provision.
5. Uses **Fill with Agent** for Description draft; edits with actual enrollment figures.
6. Enters BOQ costs from consultant estimate in Cost Estimates.
7. Phases costs over three financial years.
8. Runs **PC1 Analyze (AI)** on Checklists; fixes two missing items.
9. Signs as Prepared By; Submit.
10. Status → **Forwarded for Checking**. Checker Sana receives notification.

---

## Business Scenario: Returning a PC-I for Correction

**Situation:** Checker finds incorrect cost phasing.

1. Sana opens PC-I → **Defer**.
2. Remarks: "Financial phasing total does not match cost estimate—correct Step 9."
3. Hassan receives notification.
4. Opens PC-I (**Modified**), fixes Step 9, Save as Draft, Submit.
5. Status → **Forwarded for Checking** again.

---

*Previous: [PC Form Module](04-PC-Form-Workflow.md) | Next: [PC-II Complete Workflow](06-PC-II-Complete-Workflow.md)*