Change control and review, without giving up live editing
Every change to your requirements, tests and signals is now attributed to a work item, reviewed by the people who own what changed, and signed off before the work item can close.
Certified engineering processes, such as ISO 26262, IEC 62304, DO-178C and ISO 9001, all ask the same question of a change: which change request it belongs to, who reviewed it, and who signed it off. Until now Requiremancer could tell you what changed. It can now tell you why, and who approved it.
We built it without taking away what makes the tool fast. Edits are still live, so your team keeps working in the same document at the same time. The review happens on the work item that carries the change, not on a locked copy of your specification.
Every change belongs to a work item
Turn it on in Project settings → Change control, and pick the work item you are working on from the title bar. From then on, every change you make is recorded against that work item. This covers requirements, chapters, specification levels, test cases, suites, signals, and the trace and coverage links between them.
- Captured at the database. Changes are recorded by the database itself, not by the app. An edit from the desktop app, the web app, the REST API, a script or an AI agent is captured exactly the same way.
- One net change per item. Keystroke saves collapse into one before-and-after per item. A reviewer reads the change, not every autosave.
- The Changes tab. Each work item gains a tab listing everything changed under it, side by side, with every id shown by its name. You see the chapter, the owner and the level, not a UUID.
Reviews routed to the right people
When the work is ready, request a review from the work item.
- Who is asked. The owners of what changed become required reviewers automatically. So do any routing rules your project sets: for example, systems engineers review requirement changes, and V&V engineers review test-case changes. You can add more people or whole teams, as reviewers or as observers.
- What a decision covers. A decision is recorded against the exact content it saw. Edit the change after someone approves it, and their approval goes stale; they decide again on what is there now.
- Separation of duties. Nobody can approve a change they contributed to.
Findings on the exact line that matters
Reviewers raise findings on a specific changed field. They can quote the passage, give the finding a category (correctness, completeness, consistency, clarity, traceability, testability, editorial or question), and mark it major or minor.
- Major findings block approval. An open major finding holds the review until it is dealt with.
- The author decides what happens next. The person who requested the review actions each finding: fixed, invalid, moved to another work item, or won’t fix.
- Fixed means fixed. A finding can only be marked fixed after the thing it is about has actually changed.
- A finding keeps its context. Each finding remembers the text it was raised on. After a fix, it shows that earlier text beside the text now, so it never looks as if it is about the new wording.
Each changed item opens straight into the side panel, so the author can make the fix without leaving the review.
Back and forth, without the friction
Real reviews go round more than once. When an item has been through several states during a review, a compact timeline sits above its comparison: one dot per state, each counting the findings raised on it. Click a dot, or use the arrow keys, to step through the revisions. Compare each one with where the work item started, or with the step before it.
The review is live. When the author saves a fix, everyone with the review open sees it arrive as a new state, without refreshing.
Signed off, and visibly so
- Gate the workflow. A workflow transition can require an approved review. Add the condition to, say, In Review → Done, and the move is refused until every required reviewer has approved. The app shows the reason before anyone tries the move.
- Finish in one step. When a review is approved, the requester completes it in one click. By default this also marks the work item complete.
- Last approved. Approval records the approved text of every item it covered. Any item’s history can compare what is live now with what was last approved, so a colleague always knows which wording has been signed off.
Your reviews, in one place
The new Reviews view in Work Items lists every review you are involved in: ones you are asked to review, ones you requested, and ones you observe. It also shows which reviews are waiting on you. In-app notifications tell you when you are added to a review, when a finding is raised or answered, and when a decision is made.
For your agents too
The MCP server gained review tools, so an AI agent working on your behalf can follow the same process:
- read a work item’s change set;
- request a review;
- raise and answer findings;
- read an item’s review timeline.
An agent signs in as you, so it can never approve its own changes either.
What’s next
- Required mode. In required mode, governed content cannot be edited without an active work item, and an emergency bypass is audited.
- Revision-by-revision review. Reviewers will be able to see only what changed since they last looked, and tick items off as viewed.
- Email digests for review activity.
- Re-authenticated electronic signatures with a stated meaning.
- An exportable change record for audit packs.
Change control is off until a project administrator turns it on, so nothing changes for existing projects until you choose to use it.