Future Features
As I continue to develop the digital credit review platform, several enhancements are planned to improve usability, transparency, and regulatory alignment. Below are some of the upcoming features under consideration:
- Drag & Drop from Snipping Tool: While image uploads and drag-and-drop from file explorer are already supported, future updates may allow direct paste or drag from tools like Windows Snipping Tool, streamlining workflows for users.
- Role-Based Access & Audit Trail: A granular permission system will ensure that reviewers, approvers, and administrators have appropriate access levels. Every action will be logged with timestamps and user identity, supporting internal controls and external audits. Escalation paths for flagged reviews are also being explored.
- Portfolio Dashboard: A centralized dashboard will provide real-time visibility into all loan exposures, including metrics like Loss Given Default (LGD), rating distributions, and sectoral breakdowns. This will support portfolio-level risk monitoring and regulatory reporting.
- Centralised File Storage: Borrower-specific documents—such as annual reports, due diligence files, and other relevant materials—should be stored using a standardized file naming convention to ensure consistency across uploads.
- Automated Document Parsing: I plan to do some personal R&D on NLP tools to extract key financial metrics and qualitative insights from uploaded PDFs or borrower documents. This will help reduce manual data entry and improve consistency across reviews.
- Risk and Industry Classifications: Each borrower review should include classifications such as performing, watchlist, default, and industry-specific risk categories.
- Default, Recovery, LGD: Currently, LGD and recovery estimates are based on a simulated 1-year payment default. Simulations for 2-year or 3-year defaults, including Expected Loss calculations, may be added.
- User Authentication & Sign-Up: While the platform currently focuses on showcasing credit review functionality, a full authentication cycle (including registration confirmation, password reset, and session management) may be added in the future. As I am already well-versed in implementing modern authentication flows, this is not an area where I expect further learning. For this app, the emphasis is instead on building features that deepen my expertise in coding and demonstrate my hybrid skills in credit risk and software development.
- Automatic Market Data Feeds: Future updates may allow the platform to pull in key market references — like EURIBOR, SOFR — directly from external sources. In simple terms, instead of typing these values manually, the system would fetch them automatically.
- Sharing Data Through APIs: I plan to make the information stored in the app available through a simple “digital connection point” (API). This means other tools or systems could connect, retrieve borrower data, and process it further. Put differently, the app won’t just keep data inside — it will be able to “talk” to other software.
- Exploring Cloud Service Concepts: Looking further ahead, I am experimenting with ideas that would make the platform scalable so that different parties could each have their own secure environment within the same system. Think of it like offering the app as a cloud service, where everyone benefits from the same technology but works in their own protected space. For me, this is mainly a learning journey — a way to explore how such architectures work in practice and to deepen my understanding of modern cloud approaches, rather than a direct aim to build a commercial service.