ManyRows
Start free

Change control

Governed types route every edit through a proposal, named approvers and an immutable revision.

Change requests

A change request holds a staged working copy of the record, the way a branch holds a change to code. Edit freely inside it; nothing reaches the live record until it is approved.

In the API

Immutable revisions

Applying a change request welds a numbered revision onto the record: a complete, read-only snapshot with the approval reason attached. Revision 1 to N, browsable and diffable forever.

In the API

Named approver rosters

Set default approvers per type. Every named approver signs, and the last approval applies the change atomically — there is no half-applied state.

Minor and major classes

Classify a change when it is submitted and route it to the roster that class demands. A minor correction and a redesign do not need the same room full of people.

Change packages

Bundle several change requests that only make sense together and decide them as one. Approve the package, not eleven separate tickets.

Comments and request changes

An approver can send a request back with a reason instead of rejecting it outright. The discussion lives on the change request, next to the diff it is about.

Awaiting me, and cycle time

Every approver gets one list of what is waiting on them. Submitted-at stamps give you the in-review age of each request and the cycle time across all of them.

Propose a reversion

Open a change request pre-filled from an earlier revision. Going back is a governed change with the same approvals as going forward, not an untracked overwrite.

Change lock

Hard-freeze a record against every edit, with a reason required to lock it and to unlock it. A lock stops the change, it does not merely escalate it.

Obsolescence and supersession

Retire a part, point it at its replacement, and work the still-used list from a dedicated page that hands off to the swap tool.

Audit trail

Every record carries its own history: who changed what, when, and under which change request. Sub-resources and configuration changes are audited too, not only the record body.

Keep reading
Bills of materials Multi-level structures where the line between parent and child is a real record, not a text field. Quality and compliance Checks, dispositions, certificates and traceability, against any record in the project. Collaboration and admin Who can see what, who is watching it, and how the rest of your stack finds out. The guided tour The whole product in one scroll, with screenshots, from a project to a governed change.
Start free

Want this for your product data?

Spin up a workspace and start building. It only takes a few minutes.

Start free See pricing All features