Models change. New disciplines join, element classes appear and disappear, and clash sets get re-published. ClashWise gives you four maintenance flows to keep a matrix aligned with its clash sets — plus an AI re-evaluation to refresh rule scoring — all from the matrix's More menu on the Clash matrices page. Editing requires an active Clash Management subscription (a Pro or Business plan, or the trial).
Pick the flow that matches how much has changed:
| Situation | Use |
|---|---|
| New classes appeared; existing rules are fine | Add classes from clash set… |
| Classes were added and removed | Sync with clash set… |
| You want a fresh start from the current model | Regenerate from clash set(s)… |
| Rules are current but priorities/statuses need a rethink | Re-evaluate |
Add classes from clash set…
Adds new element classes to the matrix without touching existing rules. The flow reuses the generation wizard: pick the clash set, select the new classes, and ClashWise pairs each new class against everything already in the matrix (and against the other new classes). Use this when the model has grown but nothing you already configured needs to change.
Sync with clash set…
Reconciles the matrix with the current state of a clash set:
- Rules whose class no longer exists in the set are removed.
- Rules for new classes are added.
- "User edits on still-relevant rules are preserved." — priorities, statuses, contacts, and tags you set on rules that survive the sync stay exactly as you left them.
This is the right choice after a significant model update where classes have both come and gone.
Regenerate from clash set(s)…
Rebuilds the matrix's rules from scratch — and it is destructive:
"All existing rule tolerances, priorities, statuses and contacts will be lost. The matrix's name, status / priority options and contacts list are preserved."
In other words: your configured priority and status options and your contact library survive, but every per-rule assignment is wiped and regenerated. Regenerate supports multiple source clash sets at once, so you can rebuild a matrix that spans several published sets. Only use this when you genuinely want a fresh start.
Remove classes…
More → Remove classes… opens a checkbox list of the matrix's classes. Removing a class removes every rule that references it:
"Heads up. Deleting these classes also removes every clash rule that references them. This can't be undone."
Use it to prune classes that are no longer relevant, keeping the matrix small and readable.
Re-evaluate (AI)
Re-evaluate (on the rules toolbar) asks the AI to re-score the priorities and statuses of your rules based on the pairings — useful after adding many classes, or if the initial suggestions were made before your team refined the priority scale.
- Progress shows as "EVALUATING RULES {done}/{total} · %" with a Stop button.
- Completion reports "Re-evaluation completed. Updated {P} priorities and {S} statuses".
- The editor is locked while it runs ("Editing is disabled until the process completes.").
Manage clash sets…
More → Manage clash sets… controls which clash sets the matrix is assigned to. Assignment is what connects a matrix to analysis: running AI analysis on a clash set applies its assigned matrix, and only sets with an assigned matrix show recommendation columns in the clash grid. You can also assign a matrix from the clash set's own page via the matrix dropdown in the set header (see the Managing Clashes on the Web section).
After you change a matrix: re-run analysis
Editing a matrix does not automatically re-classify clashes that were already analyzed. ClashWise flags this for you:
- In the clash grid, the Matched Rule column shows a stale-analysis warning (⟳) on clashes whose matrix was edited after they were analyzed, advising a re-run.
- To apply your changes, open the clash set and click Run analysis again. Clashes you personally edited and locked keep their values (see the Managing Clashes on the Web section for how the analysis lock works).
Tips
- Prefer Add classes or Sync over Regenerate — they preserve your team's per-rule decisions.
- After any structural change (add/sync/regenerate/remove), give the rules a quick pass in the table view — check the NO CONTACT chip and any rules without a priority — before re-running analysis.
- Sync the matrix at project milestones or whenever a re-publish introduces new disciplines, rather than after every minor publish.
Related topics
- Creating a Matrix from a Clash Set — the wizard these flows reuse.
- Working with the Matrix View — reviewing rules after a sync.
- Priorities, Statuses, Contacts, and Tags — refreshing defaults across rules.
- The Managing Clashes on the Web section — running and clearing analysis, the stale-analysis and lock markers.