Product Updates

Lay the foundations of your financial program with Noble’s Scorecard Builder

Scorecards are a fundamental element of any financial program, as these contain the underlying data points and rules that drive decisioning. Yet building these requires both deep domain knowledge to design the modeling, and technical expertise to implement the proposed and embed it into existing systems. One of the core pain points we set out to solve at Noble was to shed credit and risk experts' dependency on technical teams in implementing their risk modeling. The Scorecard Builder is a fundamental platform feature that bridges the gap between domain expertise and technical know-how. It empowers credit and financial experts to independently implement their models via a navigable user interface that automates underwriting and decisioning.

Today, we are proud to announce the release of our embedded reporting


Configure scorecards independently through an intuitive interface.


Accelerate time to market by managing configuration entirely in-house


Build modularly, applying weights and variants according to use case and customer classification.


Configure scorecards independently through an intuitive interface.


Accelerate time to market by managing configuration entirely in-house


Build modularly, applying weights and variants according to use case and customer classification.

Self-service is one of our core product pillars and has been a key item on our product roadmap since we first set out to build the Noble platform. The Scorecard Builder is the first of a few major features released this quarter that deliver on that value proposition. In removing the bottleneck of dev-driven configuration for clients, we expect to see time to market of new programs accelerate significantly – allowing clients to launch and scale credit programs faster. Furthermore, clients can now more easily configure policies built on sophisticated mechanisms rather than just on true/false statements.

Avishai Steiner

VP Product @ Noble

Laying the building blocks to your embedded financial program

Noble’s Scorecard Builder empowers clients to independently configure proprietary customer scoring systems. Scorecards can be configured for different use cases, whether for customer onboarding or credit assignment, via pre-built, code-free blocks.

The following make up the foundational elements for any scorecard built on the Noble platform:



Program pillar

Dashboard highlights

Examples how to leverage insights


Customer data gives visibility into customer base growth over time, approval rates, time to decisioning, volume of credit line assignments, and rejection reasons.

  • Optimize on time to decisioning by simplifying cumbersome workflows
  • Leverage rejection reason insights to better target customers with offers; weed out unqualified customers before they enter your funnel

Data sources

Keep track of total reports pulled per provider and which provider products you’re leveraging most.

  • Identify underutilized data sources and where to optimize on use of provider reports
  • Better manage spend by gaining clear visibility into volume of pulled reports from providers on a pay as you go plan


Monitor usage of the Noble platform by keeping tabs on the number of assessments run, missing component rates, and use over time.

  • Leverage learnings from past evaluations to improve the quality of your credit modeling


An overview of evaluation results and averages scores, as well as a granular review of all customer evaluations and data capture results.

  • Leverage insights on common data capture fails to optimize scorecard build; add fall-back mechanisms to account for identified data gaps

Scorecard building blocks



A mix of proprietary and third-party data points that provide criteria for evaluation


Scaling mechanisms applied to numeric range or non-numeric data within a rule, allowing for normalized grading of that data


Functions that leverage grade handling and weighting to apply calculations to the fetched raw data


Establish the relative importance of one data point over the rest of the data points in any given rule


A group of rules with a united categorization, used to aggregate rules that serve the same use case (i.e. verifying business financials vs. identity)


The calculated score or numerical output of a rule, used to indicate customer creditworthiness


Alternate versions of the same scorecard that can be triggered depending on circumstance and use case

Variant Workflows

Logic that defines the conditions where scorecard variants (in the case of their existence) should be triggered


Score-based classification tags that label customer eligibility based on program scoring thresholds


A figure that shows the distribution of one score relative to the rest in the same label category, allowing you to benchmark one customer relative to a given cohort


Operational Element



Workflow nodes designed to filter out unqualified applications from the workflow, categorizing them as unfit for the specific product use case under evaluation.


Workflow nodes that split a decisioning tree into branches. These can be conditional (true/false) splits into two branches, or multi-branch for cases like customer segmentation where more than two cases apply.


Workflow nodes that order the execution of an operation  at the end of a path or at the point of a split; these can trigger a change in status or journey stage, an approval or rejection, an assignment of credit, or another workflow or scorecard.


The mix of proprietary and third-party data points that provide criteria for workflow nodes to assess customer credibility.


Numerical, logical, and/or string manipulations that are applied to  raw data and built into workflow nodes.

Pre-built scorecards
and workflows

Scorecards and workflows built for other use cases and saved in the system can be called upon at an action node of any other workflow.

Operationalize complex decisioning

Financial models are rarely simple, linear, or one-size-fits-all. Workflows on Noble support the operationalization of all.


Visualize complex logic and multi-layered conditional structures. 


Configure simple or nested conditions, and comparisons against static values or dynamic parameters.


Reduce inconclusions and error rates by driving decisioning even in cases of missing data.


Visualize complex logic and multi-layered conditional structures. 


Configure simple or nested conditions, and comparisons against static values or dynamic parameters.


Reduce inconclusions and error rates by driving decisioning even in cases of missing data.

Get started with Reporting

The Scorecard Builder is a core feature of the Noble platform. All legacy scorecards built previously for live clients will be deprecated and migrated to the new builder. New onboarding clients are now able to freely configure their scorecards without support from the Noble tech team. For a detailed walk-through of the feature, contact us or reach out to support.

Built for cost optimization

Data retrieval occurs gradually on the platform and is pulled sequentially. When a workflow reaches a node, only the data for that specific node is fetched. In cases where a workflow is terminated early, data used at a later stage of the flow will not be fetched for the unqualified applicant. This data fetching logic optimizes on cost by complementing the pay-as-you-go mechanism enabled with most of our data provider partners. It ensures reports are only pulled in cases where there is still value to evaluating a customer, thus reducing wasteful usage of report quotas.

Frequently asked questions

What is a scorecard?

A scorecard is a tool used to evaluate a customer’s eligibility for your financial program. It uses data from both third-party and proprietary sources, variables, and custom calculations to build models that verify customer identity, determine risk thresholds, underwrite for credit, and/or determine credit line assignment.

How do I build a credit scorecard?

How you build your scorecard will vary depending on your business objectives, internal controls, and the credit product being built. Start by clearly defining the objective of your program. Continue by mapping the different scorecard use cases needed to support operations, aligning the varied flows with the different steps of your customer lifecycle – from onboarding through to underwriting, credit assignment and monitoring. Identify the mission-critical data points needed to evaluate the eligibility threshold of customers for your different financial products. Source the data providers that can enrich your proprietary data with 3rd-party data points that fill your data gaps, giving you a more informed view of your customers’ business performance. Then, develop a scorecard framework that builds on top of your selected data mix, applying weighting and grade handling mechanisms to produce a final score.

Once you develop your model, you will need to test and validate before deploying to a live environment. You have two options at this stage: either allocate significant internal development resources to deploy your models entirely in-house, or, leverage the intuitive tools provided by a platform like Noble to simplify the scorecard building process – empowering non-tech teams to easily deploy their modeled scorecards.

What is the purpose of a scorecard?

The purpose of a scorecard is to evaluate customer eligibility for the financial product you are building. The scorecard formula applied by your business determines its risk tolerance threshold.

What are the different use cases for a scorecard?

Scorecards lie at the core of your program decisioning. They are the rules whose outputs ultimately determine eligibility for your financial product. Your program will be made up of many scorecards, accounting for varied use cases, that align with the different risk-bearing steps of your customer journey.

Broadly speaking, scorecards are built into policies supporting the following use cases:

  • Onboarding – verifying customer identity and credibility at the point of onboarding to your platform
  • Underwriting – verifying customer eligibility for credit assignment based on financial performance indicators and historical performance
  • Monitoring – ongoing customer management checks that detect changes to financial health or to ability to repay debt 

Learn more

Can scorecards be used for non-credit programs?

Scorecards are used to power any financial program – beyond just lending. Since they assess risk at varied points throughout the customer lifecycle, they can be tailored to support the build of any digital or embedded financial product.

What is considered a good or low-risk score?

Risk ratings and scoring thresholds vary by client and risk assessing platform. At Noble, scoring  scales are standardized to a range of 1-100. As you build your model in Noble’s platform, you will have the flexibility to set weights to a total of any sum. But upon sending the configuration to production, these will be set to total 100.

There is no standard range within the Noble scale that is considered good or low-risk. These are entirely customizable and subject to your interpretation. From what we’ve observed in live client programs, though, most will flag a 0-60 score as risky, 61-75 as medium risk, and 75+ as low risk.

How does scoring relate to decisioning and assignment?

Scoring determines the grade that ultimately guides decisioning and assignment for any financial product. The grade will automatically assign your customer to a risk band and route him accordingly to the rules, or scenarios, in your workflow that align with his determined profile. Scoring serves as the basis for rejection or approval decisioning, and for assignment of credit where offered.

Frequently asked questions

What is a credit workflow?

A credit workflow concentrates credit management policies, tasks, and decisions along the customer lifecycle into a single digital work process. It is an operational tool that tracks and reports on every customer decisioning instance, from onboarding through to monitoring.

What is the relationship between scorecards and workflows?

Scorecards are individual evaluation components. They produce a single numerical grade that positions customers relative to internal benchmarks, and offer a layered, nuanced format for evaluation through which rules can be normalized (to fit a certain scale) and weighted (to reflect each rule’s importance in the scorecard). 

Workflows are more dynamic evaluation tools that are built modularly to support complex decisioning. They are built from unlimited nodes and components that define the actions to be taken at any decisioning instance. Nodes can contain predefined scorecards within them; scores from these are utilized as inputs for decisioning or for segmenting customers according to risk bands, and trigger the execution of correlated corresponding actions. 

Workflows are mature tools that support end-to-end decisioning throughout the customer journey. Scorecards, on the other hand, do not enable the embedding or triggering of other decisioning components like workflows. When used together, scorecards and workflows deliver the ultimate flexibility in decisioning design.

Why should I leverage a decisioning engine to power my embedded finance programs rather than build in-house?

When considering how to implement embedded financial programs, platforms are faced with a dilemma of choosing to build a decisioning engine in-house or to source one from a third-party vendor. Building, maintaining and scaling these operations in-house is complex, time-consuming, and heavily dependent on advanced development resources. Since domain knowledge is maintained by tech-savvy implementers, models cannot be easily reproduced or iterated on, and cross-organization transparency into decisioning is limited.

Combining internal controls with a third-party decisioning engine like Noble’s offers an alternative way to power embedded programs. In leveraging plug-and-play tools and visualizations like workflows, such engines empower non-tech stakeholders to build robust models faster, to adapt to changes and evolving business needs, and to gain full visibility into reason behind every automated decision made.

What workflows do I need to set up an embedded financial program?

The workflows needed to support an embedded financial program will depend on the products you’re building, the various steps of your customer journey, and on your risk modeling.

Typically, they cover customer journey phases such as customer onboarding, underwriting (if offering credit), and ongoing monitoring. When building workflows, you have the option to either:

  • Build all decisioning instances across the customer lifecycle into a single workflow
  • Create separate workflows to represent each key step in your customer journey

How can workflows be leveraged in risk operations?

Workflows provide a standardized framework to configure and execute on your risk policies. As such, they guide your entire risk operations — enabling you to determine how to review applications, how to segment customers, and what automated actions to take according to categories and risk bands.

Leveraging workflows will help you:

  • Unify risk policies across the entire customer journey
  • Reduce manual review cases and risk of human error by automating decisioning
  • Dedicate more time and resources to your core business
  • Deliver a better customer experience by increasing the accuracy and speed of decisioning

Further reading

We wrote the code, you take the credit

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
This is some text inside of a div block.