Data values of two sets of attributes within a record (record level)DAMA: 24

Consistency (Record-Level)

The degree to which data values of two sets of attributes within a record comply with a rule.

Created: 10/30/2025
Business Impact
Positive Impacts
  • •Ensures logical sense and adherence to business rules within individual data records.
  • •Prevents internal contradictions within a record that could lead to processing errors or misinterpretation.
  • •Improved data quality at the most granular level, forming a reliable base for aggregation.
  • •Reduced exceptions in automated data validation and processing.
Negative Impacts (if poor quality)
  • •Illogical data entries (e.g., shipment date before order date) leading to process failures or incorrect calculations.
  • •Increased manual effort to identify and correct internal inconsistencies within records.
  • •Reduced reliability of individual records used in decision-making or customer interactions.
  • •Poor performance of AI models if training data contains internally inconsistent records.
Technical Description

%

Examples
Good quality vs poor quality indicators
Good Quality Examples

Logistics: In an employee record, 'HireDate' is always earlier than or equal to 'TerminationDate' (if the latter is present).

HR: An employee's age calculated from 'DateOfBirth' is consistent with their listed 'AgeGroup' category.

Finance: In a loan application record, the 'LoanAmountRequested' is less than or equal to the 'MaximumLoanAmountAllowed' for that loan type.

Poor Quality Examples

Logistics: A shipment record shows 'DateShipped' is earlier than 'DateBooked'.

HR: An employee record has a 'TerminationDate' that is before their 'HireDate'.

Finance: An invoice record has a 'DueDate' earlier than its 'IssueDate'.

Local Network
Quick Stats
Dependent KPIs0
Improvement Standards5
CategoryData values of two sets of attributes within a record (record level)
API Access
GET /api/dq-dimensions/9402e27e-7a07-48bf-814b-e22f57d6b0d7