Artificial Intelligence Policy Tracker
Voluntary guidance Data governance and quality Singapore Voluntary standard

Manage data quality, model development and monitoring across the lifecycle

Download: JSON · MarkdownUnder Singapore Model AI Governance Framework, Second edition, Part on operations management

Source-linked · linked to the official source, not yet confirmed by a reviewer (a factual check against the official source, not a legal review or legal advice)
What this label means
Verified
— a named reviewer opened the official source and confirmed the record; the date and the reviewer are shown.
Pending review
— linked to the official source and in the queue for a reviewer to confirm.
Source-linked
— linked to the official source, not yet confirmed by a reviewer.
Verification policy and current standing · a factual check, not legal advice.
No change recorded as of 26 Sep 2026 · official source last checked
On this page 9 sections

In brief

Manage data quality, model development and monitoring across the lifecycle is a voluntary measure under the Singapore Model AI Governance Framework in Singapore (Second edition, Part on operations management). Covers data lineage and quality, minimising bias in datasets, model explainability, repeatability, robustness, regular tuning and active monitoring after deployment. The record carries 1 evidence example and mappings to 1 framework.

Jurisdiction
Singapore
Nature
Voluntary guidance
Source reference
Second edition, Part on operations management
Who it binds
Provider / developer, Deployer / user organisation
Evidence examples
1
Framework mappings
ISO/IEC 42001:2023
Controls that meet it
3
Official source
Open official text
Verification
Source-linked

What does it require?

Covers data lineage and quality, minimising bias in datasets, model explainability, repeatability, robustness, regular tuning and active monitoring after deployment.

Practical action

Maintain data lineage records and a model monitoring plan.

Who does it apply to?

Voluntary for any organisation building or deploying AI.

Which controls meet this duty?

Satisfies: the control, operated properly, does the work the duty asks for. Supports: it contributes but the duty needs more. Each control page lists every other duty it serves, so work done once can be counted once.

  • satisfiesProcessData governance lead · once per ai system
    Data governance and dataset documentation

    Serves 8 recorded duties · evidence: Dataset documentation sheet, Data quality and bias check report, Dataset approval for use

    Data lineage and dataset bias minimisation.

  • satisfiesTechnical measureAI system owner · continuous
    Post-deployment monitoring and drift detection

    Serves 10 recorded duties · evidence: Post-market monitoring plan, Monitoring dashboard or periodic monitoring report, Monitoring review decision

    Active monitoring and regular tuning after deployment.

  • supportsTechnical measureQuality or testing lead · at launch and on material change
    Accuracy, robustness, fairness and security testing

    Serves 15 recorded duties · evidence: Pre-release test report, Test plan and acceptance criteria, Release test sign-off

    Repeatability and robustness evidence before release.

Templates that cover this duty

Generated from the records. Free · no account · links emailed to your work address. This duty is cited in each file with its source reference and a link back here.

What evidence would a reviewer expect?

Evidence examples
EvidenceTypeNotes
Data lineage and model monitoring recordsrecord

Framework mappings

Original editorial crosswalks. They cite clause numbers only and reproduce no standard text; confidence reflects how direct the mapping is.

See every Singapore duty mapped this way →

Framework mappings table
FrameworkReferenceNoteConfidence
ISO/IEC 42001:2023Clause 8 Operation; Annex A data controlsOriginal editorial mapping.medium

Frequently asked questions

Is this a legal requirement?

No. It is voluntary guidance under Singapore Model AI Governance Framework; following it is expected or recommended rather than required by law.

Who must comply with this obligation?

Voluntary for any organisation building or deploying AI.

What evidence shows compliance?

A reviewer would expect: Data lineage and model monitoring records.

Which frameworks map to this obligation?

It is mapped to ISO/IEC 42001:2023 Clause 8 Operation; Annex A data controls. These are editorial crosswalks with a stated confidence, not official mappings.

Which controls satisfy this obligation?

Accuracy, robustness, fairness and security testing; Data governance and dataset documentation; Post-deployment monitoring and drift detection.

What should an organisation do in practice?

Maintain data lineage records and a model monitoring plan.

Cite this record

AIPolicyTracker (2026). “Manage data quality, model development and monitoring across the lifecycle (Singapore Model AI Governance Framework)” [AIPT-OBL-0056, verified 26 September 2026 by Bhaskar Bhatt]. https://aipolicytracker.org/id/AIPT-OBL-0056 (accessed 8 November 2026). Data licensed CC BY 4.0.

Permanent id AIPT-OBL-0056: it never changes or gets reused, and its address keeps working if this page moves.

Cite the official text alongside it: Model AI Governance Framework (Second Edition), Personal Data Protection Commission Singapore and IMDA, https://www.pdpc.gov.sg/help-and-resources/2020/01/model-ai-governance-framework.

BibTeX
@misc{aipolicytracker2026_managedataqualitymodelde,
  author       = {{AIPolicyTracker}},
  title        = {{Manage data quality, model development and monitoring across the lifecycle (Singapore Model AI Governance Framework)}},
  year         = {2026},
  howpublished = {\url{https://aipolicytracker.org/obligations/singapore-mgf-operations-management}},
  url          = {https://aipolicytracker.org/obligations/singapore-mgf-operations-management},
  urldate      = {2026-11-08},
  note         = {Data licensed CC BY 4.0. Accessed 8 November 2026}
}

Change history

No change to this record's tracked fields has been recorded since 15 October 2026, when field-level history began.

Similar obligations in other instruments

Disclaimer: informational only, not legal advice. Verify every claim against the linked official sources and consult a qualified lawyer before acting.