Velantra ERP · Pour Card Module

Phase 2 — Scope & Roadmap

Phase 1 delivers the core pour card workflow: BOQ → Sales Order → Pour Card → M-Book → RA Bill → Sales Invoice, with full IS 456:2000 compliance, QC approval workflow, and ERPNext integration. Phase 2 adds the commercial, operational, and government-contract features required for larger enterprise clients.

Phase 1 — Complete ✓ Phase 2 — Planned

Phase 1 — What is delivered

Core Workflow
✓ BOQ Module (XLS upload + manual entry)
✓ BOQ → Sales Order push (ERPNext)
✓ Pour Card creation (5-step office wizard)
✓ Multi-pour planning per element
✓ RMC volume calculator + order
✓ BBS drawing attachment
✓ Site Pour Entry (tablet-first)
✓ Site Post-Pour & curing record
✓ BOQ Mapping & split
✓ M-Book entry (CPWD format)
✓ RA Bill with M-Book selection
✓ Sales Invoice → ERPNext
Quality & Compliance
✓ IS 456:2000 — 19 pre-pour + 11 post clauses
✓ IS 1199 slump test (batching + discharge)
✓ IS 516 cube test reference
✓ IS 456 Cl.5.6 exposure condition
✓ IS 456 Cl.10.3 mix design reference
✓ Cube test result entry (7-day + 28-day)
✓ IS 456 Cl.16.1 acceptance check
✓ QC Inspector approval workflow
✓ NCR raising + closure workflow
✓ PM Override + Hold decisions
✓ Deshuttering schedule (IS 456 Table 11)
✓ Honeycombing severity + NCR trigger
Billing & Traceability
✓ BOQ item code as traceability key
✓ Sales Order linkage throughout
✓ Partial billing per pour sequence
✓ Retention (5%) tracking
✓ Mobilisation advance recovery
✓ GST Works Contract (12% / 18%)
✓ PM approval before invoice
✓ Billing history per BOQ item
✓ CPWD M-Book: Measured by / Checked by
✓ Cumulative BOQ execution tracking
✓ M-Book on hold — NCR linked
✓ Left sidebar navigation (ERPNext style)

Phase 2 — Scope by priority

Grouped by how frequently clients ask about these in demos and during implementation scoping.

🔴 Priority 1 — Client will ask in first demo

Variation Order (VO) / Extra Item Management

High effort

Every real construction contract has deviations from the original BOQ — additional items, rate changes, omissions. A VO module allows raising, approving, and billing extra items separately from the original BOQ scope. Without this, contractors cannot bill for any work outside the original schedule.

📝
Raise VO from site / office
Engineer raises VO with: item description, reason, quantity, estimated rate, IS clause if applicable.
Client will ask: "What if we find rock during excavation? How do I bill for extra work?"
✅
Client / Engineer approval workflow
VO goes through PM → Client approval before work proceeds and before billing is allowed.
📋
VO added to BOQ as extra items
Approved VOs appear as extra BOQ items, get their own item code, and flow through the same Pour Card → M-Book → RA Bill chain.
🧾
VO register and RA Bill integration
RA Bill shows original contract items + VO items separately. Client can see contract value vs. extra items clearly.

Drawing Register & Revision Control

Medium effort

Currently pour cards reference a drawing number as a text field. A proper drawing register tracks every drawing issued to site, its revision history, who received it, and ensures site engineers always pour against the current revision — not a superseded drawing.

📐
Drawing register with revision tracking
Upload drawing PDFs against a drawing number. New revision supersedes old — site access to old revision blocked automatically.
Client will ask: "How do I know the site engineer is using the latest drawing revision?"
🔔
Drawing revision alert on pour card
If a pour card references a drawing and that drawing is revised after the pour card is issued, a warning appears on the site screen.
🔗
Pour card linked to drawing register record
Instead of a free text field, drawing reference on the pour card links to a record in the drawing register — ensuring traceability.
🟡 Priority 2 — Will ask during implementation scoping

Cube Sample Register (Lab Tracking)

Low effort

Currently cube results are entered directly by QA. A sample register adds chain of custody — which cubes were dispatched to which lab, lab's own test report reference number, and reconciliation of lab results vs. in-house records. Required for ISO 9001 QA audits and government project inspections.

🧪
Cube dispatch log
Record: set number, pour card, dispatch date, lab name, lab report ref. Auto-match lab results when uploaded.
📊
Lab result upload + IS 456 Cl.16.1 auto-check
Lab uploads PDF or enters values. System auto-applies acceptance criteria and raises NCR if failed — no manual step needed.

Progress Dashboard — Physical vs. Billing Progress

Medium effort

Project managers and clients want to see overall project health — not just individual pour cards. An S-curve or progress dashboard shows: planned vs. actual physical progress, billing progress vs. physical progress, and early warnings when billing lags or leads physical work.

📈
S-curve: Planned vs. Actual
Derived from BOQ quantities, planned pour schedule, and actual M-Book submissions. Plotted by month.
💰
Billing % vs. Physical % comparison
Flags over-billing risk (billing ahead of physical progress) and under-billing (cash flow issue).
🏗
Element-level completion tracker
For each structural element: planned pours vs. completed pours, % concrete placed, M-Book status.

Subcontractor Back-to-Back Billing

High effort

Main contractors sub-contract portions of work (concrete, formwork, reinforcement). The main contractor needs to process RA Bills from subcontractors, reconcile with their own client billing, and track back-to-back margins. Currently not in scope.

👷
Subcontractor work order and BOQ
Separate BOQ for each subcontractor at negotiated rates. Linked to main contract BOQ items.
📑
Subcontractor RA Bill processing
Subcontractor submits RA Bill in Velantra. Main contractor QS reviews against M-Books. Purchase Invoice raised in ERPNext.
📊
Back-to-back margin reporting
Client billing rate vs. subcontractor rate per BOQ item — shows contribution margin per element.
🔵 Priority 3 — Enterprise / Government contract clients

Site Instruction (SI) / RFI Register

Medium effort

When the site encounters something not covered in drawings — wrong dimension, clash, unclear specification — the site engineer raises an RFI (Request for Information) to the architect or client. Responses are tracked as Site Instructions. Without this log, verbal instructions get lost and become billing disputes.

❓
RFI raise + response tracking
Site raises RFI with drawing ref, query, element. Architect/client responds. Response linked to pour card if it changes the work scope.
📋
SI register with VO trigger
If a site instruction changes scope or quantity, it automatically triggers a VO for billing.

Plant & Equipment Log per Pour

Low effort

For large sites with owned or hired plant (tower cranes, boom pumps, transit mixers, batching plants), linking equipment utilisation to pour cards enables cost allocation, hiring cost tracking, and equipment productivity analysis.

🏗
Equipment deployed per pour
Site engineer logs: equipment type, hours used, hired or owned. Links to pour card for cost allocation.

Contract Milestone Payment Schedule

Low effort

Some contracts (particularly lump-sum EPC contracts) use milestone-based payments rather than measurement-based RA Bills. A milestone payment module tracks: milestone definition, % of contract value, completion criteria, and payment trigger.

🏆
Milestone definition + completion tracking
Define milestones (e.g. "Raft foundation complete"), link to BOQ items, track % completion, trigger invoice.

Phase 2 Summary

Feature Priority Effort Who asks Phase 1 gap note
Variation Order management P1 — Demo High All clients Extra items not billable in Phase 1
Drawing register & revision control P1 — Demo Medium PM / QA clients Drawing ref is free text only
Cube sample register (lab tracking) P2 — Scoping Low ISO 9001 / Govt clients No chain of custody for cubes
Progress dashboard (S-curve) P2 — Scoping Medium Project Directors, Finance No planned vs. actual view
Subcontractor back-to-back billing P2 — Scoping High Main contractors with subs No sub billing module
Site Instruction / RFI register P3 — Enterprise Medium Govt / CPWD / large EPC No SI/RFI log
Plant & equipment log per pour P3 — Enterprise Low Large sites with owned plant No equipment cost allocation
Milestone payment schedule P3 — Enterprise Low Lump-sum EPC clients Only measurement billing in Phase 1
Client meeting guidance: For mid-market Indian contractors (₹10–200Cr projects), Phase 1 is complete and ready to demonstrate. For government / CPWD contracts or contractors above ₹500Cr, raise VO management and drawing register as confirmed Phase 2 items with a clear delivery commitment. Do not position these as unknowns — position them as planned and scoped.