README.md

---
license: cc-by-4.0
pretty_name: Corvana Bank LimitWise working file (remediated)
language:
  - en
task_categories:
  - tabular-classification
tags:
  - ai-governance
  - datasheet
  - datasheets-for-datasets
  - credit-risk
  - fairness
  - calibration
size_categories:
  - 10K<n<100K
---
*The working file behind LimitWise v2: the extract after the Week 3 remediation, as the AI Governance Practicum (Track 1) uses it. The organization, the system, and the people are fictional. The data is real and public: Default of Credit Card Clients, UCI Machine Learning Repository, id 350 (Yeh, 2016), CC BY 4.0.*

**Where the data is.** This repository holds the documents, not a copy of the data. The file itself, `corvana_modeling_extract_remediated.csv` (29,995 rows, 40 columns, MD5 `f79f13a5119f78572e9f6cc3243ea6ae`), is in [drdavidprivacy/practicum-case-packs](https://huggingface.co/datasets/drdavidprivacy/practicum-case-packs), beside its own README with the row and column arithmetic. Every notebook in the course loads it from there by URL: [corvana_modeling_extract_remediated.csv](https://huggingface.co/datasets/drdavidprivacy/practicum-case-packs/resolve/main/corvana_modeling_extract_remediated.csv).

**What is in this repository**

- `README.md`: this page, the dataset datasheet.
- `DATA_REMEDIATION_LOG.md` and `Data-Remediation-Log.pdf`: the modeling team's log of every change made to the extract before the first model was trained (Week 3), the evidence behind sections 2 and 4 of the datasheet.
- `Dataset-Datasheet_Becker-exemplar.pdf`: the datasheet below as a PDF.

**Used by:** the model [drdavidprivacy/limitwise-model](https://huggingface.co/drdavidprivacy/limitwise-model) and the Space [drdavidprivacy/limitwise](https://huggingface.co/spaces/drdavidprivacy/limitwise).

**Datasheet below:** the AI Governance Lead's exemplar (Tom Becker), the answer key to the Week 3 Dataset Datasheet, in the structure of Gebru et al., "Datasheets for Datasets." Students replace it with their own; see "Make this your own" at the end.

---

# Dataset Datasheet: the LimitWise working file (Corvana Bank)

**Analyst:** Tom Becker, AI Governance Lead (exemplar)
**Organization:** Corvana Bank
**System:** LimitWise
**Dataset:** LimitWise modeling extract (30,000 open card accounts with six months of history)


## Section 1: Motivation

**Objective:** Record why the dataset exists. A dataset assembled for one purpose carries that purpose's assumptions into every later use, so the reason it was created is the first thing a reader needs.

*Completed by the AI Governance Lead. Read it, but do not rewrite it.*

### For what purpose was this dataset assembled, and what gap was it meant to fill?

The extract was assembled to build and test LimitWise, the early warning model the bank is considering for its card book: a monthly score of each open account's probability of payment default in the next statement cycle. The gap it was meant to fill is the one the program charter names. The bureau scores and the incumbent behavioral scorecard are backward-looking at the moment that matters most, the months before a customer stops paying, when bills climb and payments shrink, and the credit cycle two years ago ran charge-offs well past plan before anyone called.

### Who assembled it, and on whose behalf?

The modeling team drew the extract from the bank's card servicing records: the application fields, the credit limit, and six months of statement, payment, and repayment-status history for each account. They did so on behalf of the LimitWise program, whose executive sponsor is the Chief Credit Officer, who owns the loss forecast and wants the model feeding it, and whose governance is owned by the Chief AI Officer, who is the approver of record.

### Under what program or budget was it assembled?

Under the LimitWise program, management's response to the board's direction for earlier warning after the credit cycle two years ago. The extract and the prototype were produced within that program. No separate funding was attached to the data, and none is recorded in the program file.

## Section 2: Composition

**Objective:** Describe what is in the dataset as facts with numbers: what one record is, how many there are, what the outcome is, what is missing, and which groups of people the data identifies. This is the section your Week 2 EDA Observation Log was written to feed.

### What does one record represent, and how many records and fields are there?

One record is one open card account: its credit limit, four fields carried over from the application record (sex, education, marital status, age), six months of repayment status, statement balance, and payment amount, most recent first, and a label for default in the following statement cycle. There are 30,000 records and 25 columns as loaded, 23 fields, the account identifier, and the outcome (notebook sections 1 and 2). After the team's remediation the working file has 29,995 rows and 40 columns, 15 of them added beside their sources: 27 model inputs, 12 fields held out of the inputs, and the outcome column (section 12).

### Is the dataset everything, or a sample? If a sample, what is it a sample of, and how was it drawn?

A sample. The data dictionary states that the sample was deliberately drawn to include enough defaults to learn from and that the book default rate runs near 3 percent per cycle, so the extract's rate is about 7.4 times the book's (section 9, check 5). How the 30,000 accounts were drawn is not documented, no sampling memo or extraction query is held, and whether the draw was random within each outcome is open (modeling team response, answer 1). If it was, a defaulting account entered the extract about 9.2 times as often as a non-defaulting one (section 11.1). It is a sample of the bank's open card accounts, and nothing in the program file says in what proportion it stands to the book.

### What is the outcome field, how is it recorded, and what share of records carry the value of interest?

default_payment_next_month, recorded as 1 (default) and 0 (no default), shown in the notebook in words as default and no default. Default, the value of interest, means the account defaulted on payment in the following statement cycle, which the dictionary states is one month. What "defaulted on payment" means operationally, and whether it matches the loss forecast's definition, is not documented. 6,636 of 30,000 records are default, 22.1 percent (section 3), and 6,635 of 29,995 after the team's one row removal, still 22.1 percent (section 12). That is the extract's rate, not the bank's.

### Is any information missing or unrecorded, and where?

No field as loaded has a missing or unrecorded value in any of the 30,000 records (section 4). Two things read like gaps and are not. Coded fields hold values the dictionary does not document, EDUCATION 0, 5, and 6 (345 records), MARRIAGE 0 (54), and repayment-status values 0 and -2 in 25,939 records (section 9, checks 2 and 3), and those are recorded values, not gaps. And one derived field in the working file, PAY_RATIO_RECENT, is empty by construction for 3,175 accounts whose prior statement balance was zero or negative, with PAID_1 recording "no balance" for every one of them (section 11.9). Those are the only empty values in the working file.

### Does the dataset identify groups of people by a protected characteristic, directly or through other fields?

Yes, directly. SEX (1 = male, 11,888 records at 24.2 percent default, and 2 = female, 18,112 at 20.8), AGE (21 to 79, with under 25 at 27.2 percent on 2,685 records and 65 and over at 25.5 on 110, too small to trust), MARRIAGE, and EDUCATION sit in the file as four complete, separate fields (section 7). Sex, age, and marital status are prohibited bases under the Equal Credit Opportunity Act. Through other fields, weakly: the strongest links are between the demographic fields themselves, AGE with MARRIAGE at 0.277, and among the model inputs LIMIT_BAL carries the most information about a group, 0.167 for age, 0.142 for education, 0.116 for sex (section 8c). The notebook tests single fields only, so combinations are untested. One limitation sits on all four fields: the credit limit includes supplementary cards, and the documentation does not say whose demographics a multi-card account carries.

### Are there known errors, oddities, or redundancies in the data?

Five. The six repayment-status fields are the six strongest predictors, 0.423 down to 0.251 (section 8b), and they hold two values the dictionary does not document, 0 and -2, in 86.5 percent of records, with 0 the most common value in every month (section 9, check 3). Value 1 appears 3,688 times in the most recent month and then 28, 4, 2, 0, and 0 in the older months, and there is no field named PAY_1 (section 9, check 3), so the months were not computed by one rule. The six statement-balance fields correlate at 0.80 to 0.95, fifteen pairs (section 8a). And the amounts: 1,930 accounts (6.4 percent) carry a negative balance in some month (section 9, check 4), the largest balance, 1,664,089, and the largest payment, 1,684,259, each exceed the largest credit limit, 1,000,000 (section 5), and 3,931 accounts carry a balance above their own limit in at least one month (section 11.7). Thirty-five patterns repeat in every field except ID, 70 rows, 30 of them inactive in every month and 5 with six months of identical activity (section 9, check 1).

### Does the dataset contain anything that could identify a person, or anything confidential?

One identifier field, ID, which is an account identifier within the extract only, 1 to 30,000 (section 2). No name, card number, or date. The extract is cardholder account data and is confidential to the bank, held under the bank's information security controls. Whether a record could be re-identified by combining the credit limit, the demographic fields, and six months of amounts has not been assessed, and this datasheet records that as a limitation.

## Section 3: Collection process

**Objective:** Record how the data came to exist, and be honest about what is not known. Most of the answers here come from the data science team's written response. Where the team said a question is open, this section says so in the same words.

### How was the data recorded, and by what system or process?

The records were recorded by the bank's card servicing systems in the ordinary running of the accounts: the four demographic fields as recorded at application, the credit limit as the total line including supplementary cards, and the statement, payment, and repayment-status fields for six consecutive statement months, most recent first (data dictionary). The extract was drawn from those records by the modeling team. The repayment-status fields were not computed by one rule in all six months, and the team cannot say what the rules were (modeling team response, answer 3).

### Over what period, and by whom?

Not documented. The extract's documentation does not state the calendar months the six statements cover or when the extract was drawn, and the file has no date field (section 2). The team's written response does not supply a period. Whether the book rate the dictionary gives, near 3 percent, was measured over the same period on the same definition is open.

### Were the people the records describe told their information would be used this way?

Not established. The Use Case Assessment listed the permissibility of using account history for model development among the assumptions to be checked against the cardholder agreement and the bank's privacy notices, and that check is not in the program file. This datasheet records it as a limitation, not a finding either way.

### Which questions about how the data was gathered cannot be answered from the documentation the program holds?

Nine, as the team's written response and section 12 of the notebook list them: how the 30,000 accounts were drawn and the book default rate for the period they cover, what repayment-status values 0 and -2 record in each of the six fields, whether one rule computed all six months and why there is no PAY_1, what EDUCATION 0, 5, and 6 and MARRIAGE 0 record, what "defaulted on payment" means operationally and whether it matches the loss forecast's definition, the unit of the amounts and how a balance or a payment can exceed the largest credit limit, whether the 30 inactive repeated patterns are one account or two and which identifier is correct for the five pairs treated as one, whose demographics a supplementary-card account carries, and whether credit bureau data can be joined.

## Section 4: Preprocessing, cleaning, and labeling

**Objective:** Record what the data science team has now performed on the dataset, before the first model is trained, precisely enough that a reviewer could reproduce it. The data science team's remediation log is the source, and sections 11 and 12 of the notebook are where every number in this section is printed.

### Was any cleaning, recoding, or removal performed? Summarize the changes.

Yes, twelve logged rows, printed before and after in notebook section 11. The enrichment was recorded and the sampling method left open, with reweighting and calibration recorded as modeling-stage decisions and no threshold set on 22.1 percent (R-1). Repayment-status values 0 and -2 were recoded into one named level, "no delinquency recorded, code undefined," in six new fields beside the raw fields (R-2). Five per-month payment-behavior fields were derived from the documented bills and payments under one rule (R-3). The month-rule inconsistency was documented, not fixed (R-4). EDUCATION 0, 5, 6 and MARRIAGE 0 were recoded into one "unknown" level in two new fields (R-5). The label was left as recorded with its operational definition open (R-6). The amounts were left as recorded, no cap and no sign correction (R-7). One row of each of five repeated pairs with identical six-month activity was removed under a written rule, the only row removal (R-8). Utilization and payment ratio were derived from the most recent month (R-9). SEX, AGE, and MARRIAGE were held out of the model inputs and kept in the working file, with EDUCATION kept as an input under monitoring (R-10). No row left the file in that step: the team took the label off the account, not the account out of the file. No bureau data was joined (R-11). The train/test split rule was recorded for the modeling stage, random by row, stratified on the outcome, 80 percent training and 20 percent held back as the test set, fixed seed, after the deduplication: 23,996 training rows and 5,999 in the held-back test set expected, not executed (R-12, section 11.12).

### Which fields were held out of the model inputs, and why? Are they still in the file?

Twelve fields are in the working file but out of the model inputs, and all twelve are still in the working file (section 12). SEX, AGE, and the recoded MARRIAGE_MODEL, because sex, age, and marital status are prohibited bases under the Equal Credit Opportunity Act and Regulation B, 30 candidate inputs to 27 (R-10, section 11.10). The raw MARRIAGE and EDUCATION codes, because their recoded copies carry the model's view and the raw codes are kept for the evaluation-stage test of merged against separate (R-5). The six raw repayment-status fields, PAY_0 and PAY_2 to PAY_6, because "your status was 0" is not a reason a notice could carry, and the raw codes are kept for the merged-against-separated test (R-2). And ID, the account identifier, never a model input (R-8). EDUCATION_MODEL stays a model input with monitoring, pending the test the Chief AI Officer ruled on. Every one of the 29,995 cardholders stays in the training data with all of their other fields. The Chief AI Officer's watch list measures false alarm and miss rates by sex, age band, marital status, and education, and tests whether the remaining inputs recover each field, which is why none of them was deleted.

### Which fields were derived or recoded, and is the raw field still available beside each?

Fifteen fields were added, each beside its source, and the source is available beside every one of them (section 12: 25 columns as loaded, 40 after). STATUS_0 and STATUS_2 to STATUS_6, the six repayment-status fields with documented values in words and 0 and -2 as "no delinquency recorded, code undefined," 17,496 records in STATUS_0 (R-2, section 11.2). PAID_1 to PAID_5, each payment set against the prior month's statement balance as no balance, paid in full, paid part, or paid nothing, five fields because the earliest month's prior statement is not in the extract (R-3, section 11.3). EDUCATION_MODEL and MARRIAGE_MODEL, with 0, 5, 6 and 0 as "unknown," 345 and 54 records (R-5, section 11.5). UTIL_RECENT, the most recent balance over the limit, median 0.314, and PAY_RATIO_RECENT, the most recent payment over the prior statement where that statement was above zero, median 0.078 and empty for 3,175 accounts (R-9, section 11.9). Both are in the same unstated unit as their sources.

### How many records were removed, and under what rule?

Five. 30,000 rows before and 29,995 after (R-8, section 11.8). The rule: identical in every field except ID, with a non-zero balance or payment in at least one of the six months, keep the lower ID and remove the other. Five pairs met it. The 30 inactive pairs, 60 rows, did not and stay in the file, because two unused cards with the same limit and application details can coincide. Nothing else was removed, and the rate of default is 22.1 percent before and after.

### Is every change recorded somewhere a reviewer can reproduce it?

Yes. Every change is a numbered row in the modeling team's remediation log, and each row names the notebook subsection where the before and the after are printed (11.1 to 11.12). Section 12 prints the file after remediation: 27 model inputs, the twelve held-out fields with their reasons, the fifteen fields added, the 3,175 empty values in PAY_RATIO_RECENT, and the nine open items. The notebook runs from the top and reproduces every number.

## Section 5: Uses

**Objective:** Fix what the dataset is for and what it is not for. This section inherits the red lines from the Use Case Assessment and the watch list from the Chief AI Officer's Week 2 memo. It is where the dataset's limits become instructions to whoever uses it next.

### What has the dataset been used for so far?

To build the LimitWise prototype the modeling team produced before any governance file existed, on the extract as it came, which back-tested well against the incumbent scorecard. This week the team has prepared the extract for the next version of the model, which has not yet been trained, and this datasheet documents that preparation. The extract has not been used in any account action, and the Chief AI Officer's condition two, no retraining until the repayment-status codes are defined in writing, has not been lifted.

### What is it intended to be used for?

To train and evaluate LimitWise as an early warning score for existing card accounts, under the posture the Chief AI Officer directed in Week 1: preventive first, outreach and hardship offers with a human reviewing every contact, and nothing that touches an account's terms in the first phase. Evaluation will carry the six watch-list items from the Week 2 memo, each with the tripwire, owner, and review point the memo states: calibration by score band against a holdout that reflects the book, not the extract. The repayment-status codes, defined in writing for each field before any retraining, then model stability with 0 and -2 merged against separated, and a plain-language reason for every value in every one of the six fields before any phase touches an account's terms. The education and marital status codes merged into one level and again treated as missing, with per-group metrics compared. False alarm and miss rates by sex, age band, marital status, and education, and monthly outreach contact rates by group, with groups too small to evaluate flagged and counted, cardholders 65 and over among them (110 records, about 22 in the held-back test set, section 11.12). The four demographic fields trained with and without, and each predicted from the remaining inputs to name any proxy. And reason stability, the top reason for every flagged account compared across two random halves.

### What must it never be used for?

Anything outside the account-level early warning use this program assessed. Per the Use Case Assessment's red lines: the score never triggers an account action without human review, and in the first phase never triggers an account intervention at all. Never used for marketing, new-account underwriting, or collections prioritization. No action on the score during a customer's declared hardship. SEX, AGE, and MARRIAGE are never model inputs, and no reason built on a repayment-status code reaches a cardholder until the code has a plain-language meaning. Because the extract's rate is not the bank's, it must not be used to set a threshold, a loss criterion, or a calibration claim against 22.1 percent until the sampling method and the book rate for the period are documented.

### What about its composition or collection could affect future uses, including fairness and legal obligations?

Five things. The sampling method is unknown, so scores are relative rankings until a book-like holdout or a documented rate arrives, and at the scale of a book scored monthly, a small error rate is a large number of cardholders, which is the arithmetic the Chief AI Officer's memo carries into the validation report. The six strongest inputs carry a level whose meaning is open, so every reason the model gives that rests on "no delinquency recorded, code undefined" is a reason the bank cannot yet put in a notice under Regulation B. The most recent month's status was computed by a different rule from the older months, which is a training-serving risk the derived payment-behavior fields exist to test. Whose demographics a supplementary-card account carries is open, so every fairness measurement by sex, age, marital status, or education is a measurement of the recorded cardholder, not necessarily of the person whose payments produced the outcome. And the label's operational definition is open, so any comparison of LimitWise's default rate with the loss forecast's is a comparison of two definitions until the Chief Credit Officer's office confirms they match.

## Section 6: Distribution

**Objective:** Record whether and how the dataset leaves the organization, and under what terms.

*Completed by the AI Governance Lead. Read it, but do not rewrite it.*

### Will the dataset be shared outside the organization, and how?

No. The extract stays inside the bank's environment. It is held in the LimitWise program file and is available to the program team only. The bank's model inventory classifies LimitWise as high-materiality, and the extract is part of the model package that independent validation will review under that classification, inside the bank.

### Under what terms or restrictions?

Internal use for the LimitWise program, under the bank's information security controls. There is no license because there is no distribution. Any request to use the extract outside the program, including for the loss forecast directly, for marketing, for new-account underwriting, or for collections prioritization, is a new use and requires a new Use Case Assessment.

### Are there legal or contractual limits on sharing it?

Yes. The extract is cardholder account data under the Office of the Comptroller of the Currency's supervision and the bank's own privacy commitments. The cardholder agreement and the bank's privacy notices govern whether account history may be used for model development at all, and the Use Case Assessment listed that permission among the assumptions to be checked. Nothing in that check would permit sharing outside the bank.

## Section 7: Maintenance

**Objective:** Record who looks after the dataset, how errors are reported and corrected, and what happens to it over time.

*Completed by the AI Governance Lead. Read it, but do not rewrite it.*

### Who maintains the dataset, and how are errors reported and corrected?

The modeling team maintains the extract and the remediated working file. Errors, questions about a field's meaning, and requests for corrections go to the team through the AI Governance Office, which records each one in the program file. The written questions the Chief AI Officer forwarded after Week 2, and the team's answers, are the first entries.

### Will it be updated, and will earlier versions be kept?

The extract as loaded is not changed. Every change is made to the working file beside it, and the remediation log records each change, so an earlier state can always be recovered. If the sampling memo, the definitions of repayment-status values 0 and -2, or the operational definition of default is documented later, this datasheet is the document that changes. The open items in sections 2 and 3 are where. A later join of credit bureau data would be a new extract and a new datasheet, not a revision of this one.

### For how long will it be retained, and what happens to it after that?

Retention follows the bank's existing record retention schedule for card account records and model documentation. The specific period is not stated in the program file, and this datasheet records that as an open item for the Chief AI Officer's office rather than inventing one.

---

## Make this your own

This page carries the AI Governance Lead's exemplar so that the repository is complete on day one. Your portfolio should carry yours. Three steps, about ten minutes:

1. On Hugging Face, the **+** menu, then **New Dataset**. Owner: your account. Name: `limitwise-data`. License: cc-by-4.0. Public. Create it.
2. Export your Dataset Datasheet (your Week 3 deliverable) as a PDF and upload it to the new repository under the name `Dataset-Datasheet.pdf` (Files, then Contribute, then Upload files).
3. Upload a `README.md`: copy `README_TEMPLATE.md` from this repository, put your name in it, and replace YOUR-ACCOUNT with your Hugging Face account name everywhere it appears (including inside the metadata block at the top, which otherwise stays as it is). The template links to your PDF. If you would rather have your card render as the page itself, paste the text of your Dataset Datasheet below the metadata block instead.

Then add the new repository to your collection beside your Space and your model repository. Do not upload the Lead's exemplar, the memos, the audit briefings, the notebooks, or the data.