Flows

The Project Management Institute (PMI) says 31% of complex projects fail to achieve their full intended benefits, per its 2026 Pulse of the Profession. A lending platform go-live depends on bureaus, payment partners, data owners, and regulatory dates that the software vendor does not control. A plan that tracks only the vendor’s build can miss the real critical path.

Quick answer  Go-live is set by the longest chain of dependencies, and much of that chain sits outside the software build. For Indian lenders, it runs through data migration, third-party onboarding, regulatory readiness, security sign-offs, and testing. Map each dependency, name its owner, and get lead times in writing before you commit to a date.

Key Takeaways

• Define the first live product and defer non-essential scope before the timeline is committed.
• Treat integration onboarding, data migration and security review as critical-path workstreams.
• Use explicit entry and exit criteria for testing, reconciliation and operational readiness.
• Track decision latency because unresolved business choices can delay go live as much as technology.

What Sets the Go-Live Date

Go-live follows the critical path: the longest sequence of tasks that must finish in order. Shortening a task that is not on that path does not move the date.

PMI’s 2026 report adds context. It found that 81% of project professionals say projects have become more complex in recent years. Teams that manage complexity effectively were five times more likely to succeed. Their success rate was 88%, against 14% for teams that were only slightly effective or ineffective.

Two practices stand out in the report:

• Scenario planning: used by only about one in five practitioners.
• Structured frameworks: projects using one succeeded 72% of the time, against 61% without. Still, 35% of professionals used none on their latest complex project.

Which Workstreams Sit on the Critical Path

The table lists workstreams that often decide the date for an Indian lender. Confirm each lead time in writing.

Workstream	What it depends on	Who controls it	What to confirm
Product and workflow setup	Lender decisions on product rules, fees, and approvals	Lender business teams	Sign-off dates for each product
Data migration	Source data quality and reconciliation	Lender and vendor	Mock load schedule and sign-offs
Credit bureau reporting	Credit information company (CIC) formats and testing	Lender, bureau	Test file acceptance
Account Aggregator (AA)	Registry onboarding and checklists	Lender, technology partner, Sahamati	Written onboarding estimate
Security and vendor review	Due diligence and contract terms	Lender risk and legal teams	Review and approval dates
Regulatory readiness	Reporting formats and disclosure rules	Lender compliance	Rule-by-rule test results
Testing and training	Stable build and trained staff	Lender operations	Exit criteria for testing

Why Do Regulatory Dates Act as Fixed Constraints

Some dates cannot move. Plan backward from them.

• July 1, 2026: RBI’s credit reporting amendment took effect. Lenders report on the 9th, 16th, 23rd, and last day of each month. Incremental files are due within four calendar days.
• June 15, 2025: RBI’s Digital Lending Directions required reporting of digital lending apps on its portal.
• November 1, 2025: multi-lender offer display rules took effect for lending service providers working with several lenders.
• May 13, 2027: core duties under the Digital Personal Data Protection (DPDP) Rules apply.

A platform that goes live without the reporting formats in place creates a compliance task on day one.

How Do Third-Party Onboarding Steps Add Time

External onboarding often has its own queue. Sahamati, the self-regulatory organization for Account Aggregators, revised its Central Registry onboarding process effective April 20, 2026.

For new requests, the notice requires:

• A standard onboarding email with documentation and contact tables.
• Updated Customer Experience and Legal Adherence checklists.
• JSON version 2.0 with standardized entity IDs.
• The name of the technology service provider and any associated Account Aggregator.
• Five named contacts: Support, AA Program, Implementation, Escalation, and Governance.

The notice gives no timelines. Ask your technology partner for a written estimate, and treat it as a dependency, not a task your vendor can compress.

How Do Data Migration and Testing Affect the Date

Migrating loan data is rarely a single step. It needs mapping, mock loads, reconciliation, and sign-offs.

RBI’s Master Direction on IT Governance, Risk, Controls and Assurance Practices took effect on April 1, 2024. For banks and Top, Upper, and Middle Layer NBFCs, it requires:

• A documented data migration policy that preserves integrity, completeness, and consistency.
• Sign-offs from business users and application owners at each stage.
• Audit trails and change management with a way to recover from failed changes.

Each sign-off needs an owner who is available on the day. Calendar conflicts with month-end, audits, and reporting dates can push a go-live by weeks.

What Do Security and Vendor Reviews Require

RBI’s Master Direction on Outsourcing of Information Technology Services took effect on October 1, 2023. It covers banks and Middle, Upper, and Top Layer NBFCs.

Due diligence is risk-based and covers financial, operational, legal, and reputational factors. The agreement must address audit rights, sub-contracting, incident reporting, business continuity, and exit.

Start this review early. Contract changes can restart legal review, and the platform cannot go live until the terms are final.

How Do You Build a Realistic Go-Live Plan

Follow these steps:

1. List every dependency, including those outside the vendor’s scope.
2. Name an owner for each, with a backup.
3. Get lead times in writing from each outside party.
4. Sequence the critical path and mark the fixed regulatory dates.
5. Add buffer at external dependencies, not spread across all tasks.
6. Set exit criteria for each stage, such as reconciliation targets and test results.
7. Consider a phased go-live, such as by product or branch, to reduce exposure.

Review the plan at each stage gate. A change in one dependency can move the whole date.

Go-Live Readiness Checklist

• Is every product configured and signed off by its business owner?
• Have mock data loads reconciled, with stage-wise sign-offs recorded?
• Do bureau files pass testing for all four reporting dates?
• Is Account Aggregator onboarding complete, with all contacts named?
• Are vendor contract terms final and reviewed by legal?
• Do reports for digital lending and asset classification run on test data?
• Are staff trained, with named support for the first month-end?
• Is there a rollback plan and a decision owner for cutover?
• Is the cutover date clear of month-end, reporting dates, and audits?

Bottom Line

The software build is one input to the go-live date. Data, outside parties, regulatory dates, and sign-offs usually decide the rest.

Lenders that map dependencies early, secure lead times in writing, and plan backward from fixed dates can commit to a date they can defend.

FAQs

What determines the go-live date of a lending platform?

The longest chain of dependent tasks, called the critical path. It often includes data migration, outside onboarding, regulatory readiness, and sign-offs.

Which fixed dates should an Indian lender plan around?

Include the July 1, 2026 credit reporting schedule and the digital lending requirements already in force. DPDP core duties start on May 13, 2027.

Should a lender go live in phases?

A phased go-live can limit exposure, for example by product or branch. It still needs reconciliation and exit criteria at each phase.