AssurePulse — what is accumulating, and how quickly?

The rate-of-change half of AssureLens: unusual application, facility, drawdown, utilisation, refinancing and exposure velocity — compared with the book’s own baselines and the borrower’s observable capacity, so accumulation surfaces while it is a conversation, not a provision.

Engine built · synthetic-testedDesign-partner stage

How it works — one level

AssurePulse in one level: the borrower's event stream (applications, facilities, drawdowns, repayments, filings, plus the AssureMap baseline) flows into AssurePulse — windowed velocity vs the book's own baselines, capacity-adjusted — producing elevation calls, drift results, the explained alert and a worked case

Swipe the diagram horizontally on smaller screens →

What it does

Rate of change, capacity-adjusted, explained

Velocity over 7/30/90-day windows

Applications, enquiries, facilities added, refinancing clusters, drawdown frequency and limit exhaustion — counted deterministically and compared with the entity's own supplied baseline. No baseline means counts are reported, never judged elevated.

Cross-programme accumulation

Facilities opening across different programmes inside one window surface together — the accumulation pattern a single programme's view cannot see.

Exposure velocity per source class

Change in lender-known, bureau-reported and programme exposure between observation dates, side by side — classes may overlap, so deltas are never summed.

Capacity-adjusted velocity

Debt growth against revenue growth, utilisation against operating inflows — in integer basis points with a lender-configured margin. Growth alone is not a signal; growth beyond capacity is.

Repayment and evidence drift

Worsening payment timing against the borrower's own history, bounces, restructuring, past-due progression — plus stale statutory evidence, delayed filings, new charges and contradictions. Clean-with-coverage and clean-without-coverage are different answers.

Explained alerts, worked cases

Every result carries metric, window, baseline, threshold, sources, freshness, confidence, triggering events and limitations. Alerts open append-only cases with assignment, evidence, remediation and a reason-required override — sealed with a content hash.

AssurePulse workbench on the synthetic borrower: elevated facility velocity vs baseline, capacity-adjusted growth failure, repayment drift and the fully explained alert
The AssurePulse panel computed live by the engine — facility velocity at 300% of baseline, debt outgrowing revenue, repayment drift against the borrower's own history, and the LV-8 explained alert. Explore the live simulation →

Swipe the screenshot horizontally on smaller screens →

Signals only — AssurePulse raises evidence-backed, lender-configured alerts; the lender decides. Designed to reduce periodic-review effort; a pilot target, not a promise.

AssurePulse does not claim real-time observation of sources that refresh periodically, does not prevent fraud or default, and does not make lending decisions. Event-driven where source events are available; periodic where sources refresh periodically.

Watch your book’s pulse beside your current process

Shadow mode on one design-partner portfolio — your baselines, your thresholds, your decision.

AssureLocker
AssureLocker Pvt Ltd. (inc. in progress)
3rd floor, Innov8, SKCL Tech Square, SIDCO Industrial Estate, Guindy,
Chennai, Tamil Nadu 600032

AssureLocker is a verification & orchestration platform — not a lender. It supplies verified evidence and risk signals checked against authoritative sources (GSTN, MCA21, EPFO, CERSAI, Account Aggregator) and orchestrates the assessment room. It does not lend, hold or move funds, operate escrow, set advance rates, or make the credit decision — the lender's system of record makes that decision and disburses. AssureLocker Pvt Ltd. (inc. in progress), the provider of AssureLocker, operates strictly as a Technology Service Provider. Every signal is labelled by evidence tier — registry-verified, lender-side, issuer-confirmed, document-signed or self-declared (missing where unresolved); some integrations are in sandbox, lender-side or pilot, and records are written to an immutable registry (hashes only — never raw PII). Signals and figures are point-in-time and consent-bound; confidential to the named parties.

Explainable, evidence-tiered signals — auditable on request. Our algorithmic-accountability approach →

© 2026 AssureLocker Pvt Ltd.. All rights reserved. · Site version: al-20260905-192031-5156ce245