Can I edit a tactic after it's been approved?

Short Description Yes — approved tactics can be edited, but certain attribute changes can trigger a re-approval cycle. This article explains which edits are safe and which require a fresh approval.

What this article answers

Which edits trigger re-approval.
Which edits don't.
How to handle a re-approval cycle.

The short answer

Yes, you can edit an approved tactic. Whether the edit triggers re-approval depends on:

Your instance's workflow configuration.
Which attributes you're changing.
Whether the workflow has the Required planned costs on tactics option enabled (cost changes can re-trigger approval).

Edits that commonly trigger re-approval

These attribute changes are the most likely to re-trigger approval:

Planned Cost — if your workflow has cost-change re-approval enabled.
Tactic Type — Tactic Type changes also revert Planned Cost and initial stage to the Model's defaults, so the change is significant.
Custom attributes used as workflow approver criteria — if your workflow routes by a custom attribute, changing that attribute reroutes the approval chain.
Approval Workflow attribute — explicitly switching the workflow restarts the approval cycle.

Edits that typically don't trigger re-approval

Notes and descriptions.
Non-workflow-driving custom attribute values.
Date adjustments within an already-approved range (your instance's rules may vary).
Adding or editing Line Items, as long as totals stay within the tactic's planned cost.

What happens during re-approval

When an edit triggers re-approval, Hive9:

Resets the tactic's status to Pending Approval (or your instance's equivalent).
Regenerates the Approval Tracking grid based on the current workflow.
Notifies approvers per the workflow's notification rules.
Hides the Approve button on the tactic until the new cycle completes.

[SCREENSHOT NEEDED — Tactic Inspection Window during re-approval]

You can continue to make further edits while the tactic is in re-approval, though additional changes may cascade further into the approval cycle depending on configuration.

How to plan for re-approval

If you know an edit will trigger re-approval and you want to minimize disruption:

Make all related edits in a single save rather than several small ones — each save can potentially re-trigger the chain.
Notify your approver(s) before saving so they're ready to act.
Use Snapshots to capture the pre-edit state if you need a record of the prior approved version.

Common questions

Can an admin force-approve to skip re-approval? Admins can approve on behalf of others if their role permits and they meet the team's Can Approve = Yes requirement. They can't bypass the workflow definition itself.

Will my historical Approval Tracking be lost? The live Approval Tracking grid regenerates. Prior approval history is preserved in the tactic's audit log.

Does this apply to Campaigns and Programs too? Yes — the same re-approval logic applies to other plan objects that use approval workflows, including Campaigns, Programs, and Purchase Requests (when configured).