A change management model-based approach can be used for managing information, such as rows of data, presenting merged information from a pending and/or production datastore with rule-based redirection to an appropriate pending and/or production datastore. Such a model can support versioning, leveraging the pending data storage; can provide for direct or merged views of the appropriate datastore; and can provide a model logic for production data updates, version updates, and/or for change context updates. A unified presentation and update model for change management can merge pending data over the production information based on the context, and allow updates on top of production/date effective versioned information. Based on various rules, the data can be pushed to production or to a change order in the context of either datastore or to a fresh change order itself.