Divine Charles · Fullstack Product EngineerLoading
000%
Getting things ready…

(W/03 · F/01) · Case study

Configurable forms

Loan and onboarding forms that follow a field list, so teams can change fields without rebuilding the whole screen.

01

The problem

Every new loan or identity field meant another hard-coded screen. Teams waited on engineering for small form changes, and borrowers saw forms that did not match what the lender needed that week.

02

The story

Every lender uses different fields on loan and onboarding forms. Waiting on a full screen rebuild for each change was too slow. One shared form system lets product describe the fields and have the product draw them.

03

What changed

Teams can define short and long text, choices, dates, file upload, and media where needed. Each field carries its own label and validation. If a field type is not supported, it fails with a clear error instead of breaking the page. The same pieces can be reused across loan and borrower flows.

04

How it was built

The system was designed so a form is a description, not a one-off page. Shared field types and validation travel with the definition, which means loan and onboarding flows stay consistent without inventing a new form from scratch each time.

05

Outcome

  • New fields do not always need a brand-new screen.
  • Borrower-facing forms stay consistent across products.
  • Validation and empty/error states come with each field.