Push franchise standards and review branch changes

Push a published FieldCamp standard to branches, preview with a dry run, review branch changes, grant exceptions, answer branch requests and restore versions.

After you publish a brand standard, four tabs on the same standard let you send it to branches and keep track of what happens next: Send to branches, Changed by branches, Branch requests and History. You find them in the franchise console under Brand standards, next to the Set up tab.

Only the Owner, Admin or another role that can publish and push standards, with access to the whole franchise, can push, grant exceptions or decide branch requests. Other roles see these tabs read-only.

Send a standard to branches

The Send to branches tab pushes the latest published version. If nothing has been published yet, publish from Set up first.

Open Send to branches

Open the standard and click Send to branches.

Choose the branches

Under Push to branches, every branch with its own workspace is ticked. Untick any branch you want to leave out. The HQ branch isn't listed, because standards are authored from HQ's workspace.

Run a dry run

Click Dry run to see what a push would do in each branch without changing anything.

Push

Click Push to branches. FieldCamp confirms how many branches it pushed to.

What a push does to each record

Record rule	What the push does in a branch
Same everywhere (branches can't change)	Replaces the branch copy with HQ's version.
Branches can edit	Creates the record if the branch doesn't have it. Otherwise it updates the fields the branch hasn't changed and keeps the branch's own changes.
Don't send	Skips the record.

A push also skips a record when the branch has an exception for it, when the record belongs to a department that isn't active in that branch, or when it needs an add-on the branch hasn't connected.

Read the push result

The Push result panel shows one line per branch with the number of records applied, drifted and skipped. Under each branch it can also show:

which fields were updated from HQ
branch wording that a locked record will replace (dry run) or has replaced
how many branch overrides were kept, and how many conflicts kept the branch's value
records that couldn't be written, with the reason

Recent pushes lists earlier pushes and dry runs with their version and branch count. Where a push replaced a branch's own value on a locked record, the old value is listed with a Restore button. Restore works only after you change that record to Branches can edit and publish, otherwise the next push would overwrite it again.

Review changes made by branches

The Changed by branches tab shows which branches changed an overridable record since the last push. It also covers price book items whose price is outside HQ's band or below the margin floor.

Check drift

Click Check drift. If no branch has changed anything, FieldCamp says All branches in sync.

Bring branches up to date

A branch that hasn't received the latest version shows a line such as "Downtown is on v2 — latest is v3". Click Push now to push the latest version to that branch only.

Review each changed record

Each row shows the branch, the record and why it differs, such as Edited by the branch, Changed by the branch and by HQ, Deleted on branch, Priced outside HQ's band or Below HQ's margin floor. A table compares each field across HQ at last push, HQ now and Branch.

Decide what to do

Choose Revert to standard, Accept as exception or Snooze until. Each one asks for a note under Why, which is the only record of the decision.

Action	What it does
Revert to standard	Overwrites the branch's copy with the published standard.
Accept as exception	Stops reporting this record as changed for this branch. Optionally pick an end date under Until, or leave it with no expiry.
Snooze until	Hides the row until the date you choose, then it comes back on its own. A date is required.

Accept as exception and Snooze until aren't offered for a record the branch deleted. Revert it, or push again, to add it back.

Manage exceptions

The EXCEPTIONS section lists every exception with its branch, record, reason, end date and status: Active, Needs review, Expired or Revoked. While an exception covering a whole record is active, pushes leave that record alone in that branch.

If you publish a version that changes the departments a record targets, its exceptions move to Needs review. Click Keep it to agree the exception again against the new version, or Revoke to end it. Revoking starts reporting the branch's changes again, and the history of the decision is kept.

Answer branch requests

A branch can ask HQ to change a governed record. The Branch requests tab lists these proposals. Filter by Open, Approved, Declined or All. Each proposal shows the branch, the record, the branch's reason, and each changed field from HQ's value to the branch's.

Approve writes the branch's changed fields into HQ's own record, publishes a new version and pushes it. A note is optional. The version is built from the latest published version with only this record changed, so unpublished work in your Set up draft isn't included.
Decline needs a note explaining why. The branch keeps its local value, so an overridable record keeps showing on Changed by branches.

An approval pushes the new version to the branches that already received this standard, plus the branch that made the request. It doesn't add branches you left out of earlier pushes. Use Send to branches to reach them.

If HQ changed one of the proposed fields after the branch sent its request, approval stops and the proposal goes back to Open with a note showing what changed. Review it again before approving.

Restore an earlier version

The History tab lists every published version with its number, record count, date and who published it. To roll back:

Choose the version

Click Restore to draft on the version you want.

Confirm

Confirm Restore to draft. The working draft is replaced with that version's records.

Publish and push

Branches don't change until you publish from Set up and push from Send to branches.