MSP procurement season — a weighbridge readiness timeline
The wheat + paddy MSP procurement season cycle and the weighbridge-side readiness checklist — from T-90 days through post-season reconciliation, with the five mistakes new yards make.
A practical timeline for procurement officers + yard supervisors
If your yard handles MSP procurement — wheat in March-May or paddy in October-December — the difference between a smooth season and a chaotic one is set in the 90 days before procurement begins. By the time the first truck arrives, the weighbridge, the software, the operators, the credentials, and the portal integrations are either ready or not. This piece is the weighbridge-side timeline for getting ready, written from a vendor's perspective after handling FCI procurement at multiple state-cooperative yards.
What MSP procurement actually is
Minimum Support Price procurement is the Govt of India's commitment to buy specified crops from farmers at a guaranteed price. The Food Corporation of India (FCI) and state-level federations (Hafed, Markfed, NAFED, MARKFED, others) operate procurement yards where farmers bring grain. The yard weighs the truck, grades the grain, issues a slip with the MSP-calculated price, and the farmer is paid against that slip. The weighbridge is the heart of the workflow — it generates the procurement record on which payment is made.
The two procurement seasons
India runs two large MSP procurement seasons every year:
- Rabi (wheat) procurement: typically April through mid-June, with the peak in mid-April to mid-May. Punjab, Haryana, MP, UP, Rajasthan are the largest contributors.
- Kharif (paddy) procurement: typically October through January, with the peak in mid-October to mid-November. Punjab, Haryana, Chhattisgarh, Odisha, Telangana, AP are major contributors.
Other crops have smaller MSP procurements at varying times, but wheat + paddy are the bulk of the weighbridge-related procurement workload at most yards.
Pre-season: T-90 to T-30 days
The 60 days from T-90 to T-30 are when readiness either gets built or skipped. The activities that have to happen:
- T-90: announce the season at your yard. The state federation declares procurement centres open. Local farmer outreach begins. The yard supervisor is named.
- T-75: hardware readiness audit. An engineer visits the weighbridge, runs a corner-load test, checks the cells. If any cell needs replacement or the deck needs maintenance, this is when it is identified.
- T-60: calibration + Legal Metrology stamping. Even if the annual stamping was done at a different time, most yards re-stamp before the procurement season because of the audit visibility. Surveyor + inspector scheduled for the visit.
- T-60: FCI Hafed portal credential refresh. Yard credentials may have lapsed; re-activate them. Sandbox-test the API.
- T-45: software updates. EagleOS or any vendor's software gets a pre-season update with the latest FCI / state portal API schema. Test in sandbox.
- T-45: operator training. New operators trained. Returning operators refreshed on any portal-side changes since last season.
- T-30: dry run. Full mock procurement cycle with a dummy truck. Slip prints, portal acknowledges, payment workflow simulated.
- T-30: physical readiness. Tarpaulins, weighing scales for sample grading, gunny bags, godown space — all checked.
Launch week: T-7 to T+7
The week before and the week after the official season launch are high-anxiety even at well-prepared yards.
- T-7: final readiness walk-through. District Mining Officer or state procurement officer visits. Verifies the yard is ready. Any gaps surfaced now get crisis-fixed.
- T-3: party master synced. The list of registered farmers / parties for the season is loaded into the software. Daily-refresh enabled.
- T-0: season opens. First truck arrives. Slip prints, portal acknowledges, farmer signs, payment is initiated. The most-watched weighment of the season.
- T+1 to T+7: triage. Every unexpected scenario shows up in the first week — barcode scanner glitches, slip-format mismatches, party-master gaps, portal sync delays. The vendor support team is on call.
Peak: weeks 2-6 of the season
Once the launch week is past, the rhythm settles. A well-run yard at peak handles:
- 150-300 trucks per day during peak
- Two operator shifts, sometimes three
- Slip-to-payment cycle of 2-3 days for the average farmer
- Single-truck weighment time under 5 minutes including portal sync + slip print
The risks during peak are operational, not technical: operator fatigue, indicator power issues, cell drift from heavy continuous use, occasional portal sync delays. The technical infrastructure is rarely the bottleneck if the pre-season readiness was real.
Wind-down: last 2 weeks
The official season-end is announced. Procurement continues for stragglers; the bulk of farmers have already brought their grain.
- Daily truck volume drops to 30-60 per day
- Cleanup of pending slips, reconciliation, and audit
- Discrepancies with the central portal flagged for correction
- Final stocktake at the receiving godown
Post-season reconciliation
The 30 days after season-close are quiet operationally but heavy on reconciliation. The yard supervisor + state IT desk + central audit team work through:
- Weight + portal data matching
- Farmer payment reconciliation
- Any disputes from the season — these are resolved with reference to the weighment audit log + CCTV footage
- Lessons-learned for next season
This is also when most software vendors get reflective feedback. EagleOS publishes post-season notes to all customer yards summarising any portal-side changes that affected their season.
Weighbridge readiness checklist
For a yard supervisor or procurement officer, the 12-item pre-season readiness checklist:
- Weighbridge calibrated + LM-stamped within last 12 months
- Cells corner-load tested at T-75
- Indicator firmware on current version
- Windows PC + UPS tested under full load
- Printer ribbons + paper in stock for full season
- FCI Hafed portal credentials active + sandbox-tested
- Software update applied + tested
- Party master sync confirmed working
- Two trained operators per shift; spare for absence
- SMS facility tested with real numbers
- CCTV operational + retention period verified
- Vendor support contact + escalation path documented
Five mistakes new yards make
- Treating the credential refresh as a vendor task. Credentials belong to the yard, not to the software vendor. The vendor configures them; the yard must request them. Confusion here costs weeks.
- Skipping the dry run. The first time a software change is tested should not be on a real procurement truck. A 4-hour dry run at T-30 catches 80% of issues.
- Single operator dependency. A trained operator falling ill on day 3 of the season is a real risk. Always have a backup trained on the same workflow.
- Underestimating CCTV storage. A 30-day rolling buffer at 4 channels = ~3 TB. Many yards plan storage for monthly average truck volume, not season peak. Failure modes appear in week 3.
- Ignoring small portal-side errors during launch week. A 2% portal rejection rate seems acceptable in week 1. By week 3 the cumulative un-reconciled slips become a problem. Address every rejection in real time.
If your yard is preparing for the next MSP season, the EagleOS team handles pre-season readiness as part of the Weighbridge Automation support contract. The FCI Hafed integration article covers the portal side in more depth.
Last updated: June 2026 · Eagle Weigh editorial team
Ready to talk specifics?
This article walks through the principles. The next step is mapping them to your yard.