FieldCampWork with HQ standards in a franchise branch
See how HQ-managed records look in a FieldCamp branch, what your branch can edit, how to propose a change to HQ and what an HQ push does to your edits.
When HQ pushes a brand standard, its records arrive in your branch workspace as HQ-managed copies. You work with them on the usual settings and price book pages, but HQ's rule for each record decides what your branch can change. This guide is for people working inside a branch. For the HQ side, see set up and publish brand standards.
To see your branch's copies, switch to the branch workspace first.
Recognize HQ-managed records
FieldCamp marks every record that came from HQ. Your branch's own records have no mark.
| Mark | Meaning |
|---|---|
| Locked by HQ | HQ's rule is Same everywhere (branches can't change). You can't change the fields HQ sends. |
| HQ standard · editable here | HQ's rule is Branches can edit. You can change your copy, and HQ sees your version as a difference from its standard. |
| Proposal pending | Your branch has asked HQ to change this record and is waiting for an answer. |
You see these marks in settings lists such as job types, skills, equipment, tax, document templates, contracts and terms & conditions, and in the price book list, where a small icon shows the same information. The company settings page shows a banner when HQ manages your company branding.
Marks on a price book item
HQ can set a different rule for each part of a price book item, so an item's detail page can mark individual sections:
- Locked by HQ on a section means HQ owns its fields.
- HQ range with two prices, for example HQ range $90–$110, means HQ lets your branch set its own price within that range.
- No mark means the fields belong to your branch.
What your branch can change
| HQ's rule | What you can do |
|---|---|
| Locked by HQ | Use the record, but you can't save changes to the fields HQ sends, and you can't delete it. |
| HQ standard · editable here | Change your copy and save it. If you delete it, the next push from HQ adds it back. |
On a price book item, some fields are always yours: Cost, Taxes and Zone pricing, including department prices. Any field HQ set to Branch sets this is also yours. A price inside HQ's range saves normally. A price outside the range, or below HQ's margin floor, still saves, but HQ sees it as a difference.
A lock covers what HQ sends, such as names, descriptions and prices. Settings that connect a record to your own branch, such as which departments it applies to, generally stay yours.
Propose a change to HQ
If HQ's version doesn't work for your branch, send HQ a proposal. HQ can adopt your change for the whole network.
For a locked record
Make the change and save
Edit the record as usual and save. Because HQ locked the fields you changed, FieldCamp refuses the save and opens Send this change to HQ?
Check the changes
Under Changes to propose, each field shows HQ's value and your new value. Fields that only your branch can own are listed as Not proposable (branch-only).
Give a reason
Under Why should HQ make this change?, explain the change, for example that your technicians need more time for the job. A reason is required.
Send it
Click Send to HQ.
If you close the dialog without sending, nothing is sent to HQ, and the locked change isn't saved. On some price book items, FieldCamp saves the fields your branch owns and shows Saved — except what HQ owns, so you can send only the HQ-owned fields as a proposal.
For a record your branch can edit
After you save a change to an HQ standard your branch can edit, FieldCamp may ask Saved for your branch. Also send it to HQ? Your change is already saved. Click Send to HQ to propose it, or Not now to keep it local.
Some editors, such as the price book item page, the job forms editor and a department's Job setup tab, also show a Propose change button next to the mark. It becomes available once your branch has changed its copy. Until then it shows "Edit it first, then propose".
Your branch can have one open proposal per record. To send a different one, withdraw the open proposal first.
Track your proposals
Go to Settings > Company > Proposals to open Proposals to HQ. It lists every change your branch asked HQ to make, with the fields, your reason, the status and HQ's note. Filter by Open, Approved, Declined or All.
- While a proposal you sent is open, click Withdraw to take it back.
- A department's Job setup tab, under Settings > Company > Departments, also lists the proposals for that department's records.
FieldCamp notifies you when HQ decides. If HQ approves, it adopts your change into its own record, publishes a new version and pushes it to the branches that run the standard, including yours. The proposal shows Adopted as with the version number. If HQ declines, its note explains why, and a record your branch can edit keeps your local value.
What an HQ push does to your edits
| HQ's rule | Effect of a push |
|---|---|
| Same everywhere (branches can't change) | HQ's version replaces your copy. |
| Branches can edit | Fields you changed stay as you set them. Fields you didn't change get HQ's updates. A missing record is added back. |
| Don't send | Your record isn't touched. |
On a price book item, HQ never overwrites your cost, taxes or zone pricing, or a price inside HQ's range. HQ can still choose Revert to standard to put its version back on a specific record in your branch. If HQ grants your branch an exception for a record, pushes leave that record alone until the exception ends. For how HQ reviews these differences, see push standards and manage branch changes.
Related articles
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.
Franchise network performance reporting
Compare revenue, collections, jobs and visits across franchise branches with the HQ dashboard, benchmarks, same-store growth, analytics and saved boards.