When reviewers can't agree, the workflow knows what to do

Why it matters

Compliance review at scale is a series of decisions that involve people with different mandates. Legal cares about claim risk. Brand cares about consistency. Regulatory cares about jurisdictional language. Marketing cares about message and timing. These mandates are good. They are also a reliable source of disagreement.

In most review platforms, what happens when these stakeholders disagree is informal. Someone notices the conflict. They send an email. They schedule a meeting. They escalate to a manager who may or may not have context. The project waits. By the time the disagreement is resolved, the audit trail of what happened is scattered across inboxes and calendar invites, and the project has lost days of cycle time.

Conflict Manager replaces this pattern with structure. The platform knows when a conflict has occurred. The platform routes it. The Conflict Manager receives a complete picture of what each assignee said, what notes they attached, what file or component is at issue. The decision is made and recorded. The workflow continues. No coordination meeting is required.

In this scenario, the software for regulatory approvals has version tracking and accountability without lost time.

What triggers a conflict

Three configurable triggers route a step to its Conflict Manager. The triggers can be used independently or combined.

No consensus on the configured decision rule. If a step is configured to require unanimous agreement and the assignees disagree, the conflict triggers. If a step is configured to require a majority answer and no clear majority emerges, the conflict triggers. The decision rule itself is defined per step, so different steps can have different consensus requirements.

Deadline expiration. If a step has a defined deadline and not all required assignees respond before it passes, the unanswered or stalled decision can route to a Conflict Manager rather than blocking the project indefinitely. The Conflict Manager either makes the call or escalates further.

Reviewer-flagged uncertainty. Where appropriate, individual assignees can flag a decision as one they are not confident making alone. Rather than forcing them to commit to an answer they would rather not own, the workflow routes the question to the Conflict Manager with the reviewer's reasoning preserved.

Each trigger is configurable. Steps that require speed might use majority logic with a Conflict Manager fallback. Steps that require certainty might use unanimous agreement with a Conflict Manager who hears any dissent. Steps that involve specialist judgment might rely on reviewer-flagged escalation. The rules match the work.

Who plays the conflict manager role

Aproove does not prescribe who the Conflict Manager has to be. The role is assigned during workflow configuration, and customers shape the assignment to fit their organization.

A few common patterns:

• Manager-as-resolver. The Conflict Manager is the team manager above the assignees. Brand team disagreement escalates to the brand director. Legal disagreement escalates to associate general counsel.
• Operations-as-resolver. A designated operations or program management role (compliance ops, project director, account lead) handles cross-functional conflicts where no single team owns the decision.
• SME-as-resolver. A subject matter expert is brought in to adjudicate decisions that require specialist knowledge. A regulatory specialist breaks ties on regulatory questions. A brand director adjudicates brand disputes.
• Tiered escalation. Multiple Conflict Managers can be configured in sequence. The first Conflict Manager attempts resolution; if they cannot or do not act in time, the conflict escalates further.

The choice depends on your organizational structure, the nature of the work, and how much authority you want concentrated in any single role. Different workflows can use different patterns. The same Conflict Manager can serve multiple workflows for conflict management in-software.

What the conflict manager sees

The Conflict Manager does not have to reconstruct what happened. They arrive in the file with the full context already attached:

• Who was assigned to the step, and who answered.
• What each assignee answered (Approved, Rejected, Needs Changes, Escalate, etc.).
• Why they answered the way they did (their Notes, Tags, and any comments they added).
• The specific component(s) of the file at issue. If the disagreement is about a specific paragraph, image, or page, that component is highlighted.
• Any prior history relevant to the decision. Earlier rounds of review, related decisions, AI Agent findings if applicable, all visible.
• The decision they need to make, with the same decision buttons the original assignees had access to (or an expanded set, if configured).

The Conflict Manager makes the call inside the same Review Interface the original assignees used. Their decision is captured with attribution, optional e-signature confirmation, and full audit trail.

How resolution flows back into the workflow

The Conflict Manager's decision becomes the step's decision. The workflow continues from where it was waiting. There is no manual step to reopen the project, no back-channel notification to the original assignees, no "we decided this offline, please update the system." The platform handles all of it:

• The decision is recorded in the project audit trail.
• The original assignees are notified of the resolution and the rationale (if the Conflict Manager chooses to share it).
• The workflow advances to the step that the resolved decision routes to.
• Any downstream actions (workflow Actions, AI Agent triggers, notifications) fire as they would have fired if the original step had resolved without conflict.

The conflict, once resolved, is part of the audit record permanently. A regulator or auditor reviewing the project sees not just the final decision but how it was reached, including the disagreement and how it was resolved.

Benefits

• Disagreements stay inside the workflow. No email chains, no meeting invites, no back-channel coordination. Conflicts route, resolve, and record automatically.
• Stalled projects do not stall indefinitely. Deadline-triggered escalation means a missed answer becomes a Conflict Manager task, not a frozen project.
• The right person resolves the right conflict. Conflict Manager assignment is configurable per step, so the resolver matches the kind of decision being made.
• Reviewers can flag uncertainty without blocking. Rather than forcing reviewers to commit to answers they would rather not own, the platform supports reviewer-initiated escalation.
• The audit trail captures the conflict, not just the resolution. Regulators and auditors see the full decision chain, including the disagreement that triggered escalation.
• Tiered escalation handles complex hierarchies. Multiple Conflict Managers can be configured in sequence for organizations that require layered resolution.‍
• No coordination overhead. The platform notifies, surfaces, and routes. Project managers do not spend their day brokering disagreements.

Who it's for

• Compliance, legal, and regulatory operations leaders managing multi-team review programs where stakeholder disagreement is a regular occurrence.
• Project and program managers in marketing operations, agency engagements, and enterprise content programs who currently spend significant time mediating decisions.
• Brand and creative governance teams balancing competing inputs from market teams, regional teams, and external partners.
• Operations leaders evaluating workflow platforms against the reality that multi-stakeholder review produces conflict, and that conflict resolution is a meaningful share of operational time.‍
• Audit and compliance teams who need defensible records of how disagreements were resolved, not just the final outcome.

Under the hood

Conflict Manager operates within Aproove's workflow engine as part of the Step Group configuration. Each step in a workflow can be configured with a Step Group containing one or more Step Guests (assignees). The step's decision rule (configurable as "All answers are" for unanimous logic, or "At least one answer is" for majority or first-decision logic) determines when the step resolves cleanly. When the rule cannot be satisfied (assignees disagree under unanimous logic, no majority emerges, or a deadline passes without sufficient response), the step enters a Decision Conflict state. A separate Deadline Conflict state can be triggered when configured time windows expire. Conflict states route to a designated Conflict Manager (configured per step, can be a single user, a role, a contact group, or a metadata-resolved value). The Conflict Manager receives the full task context including all original assignees, their decisions and Notes, the file components in question, and any AI Agent findings on the file. Their resolution decision becomes the step's decision and triggers downstream workflow actions. All conflict events (entry into conflict state, Conflict Manager assignment, resolution, escalation) are captured in the project audit trail. Conflict Manager assignment can be tiered, with secondary Conflict Managers configured to receive escalations if the primary does not respond within a defined window.