# Approval Workflows: Stopping Bad Edits Before They Go Live

> Which profile changes need approval and which should go straight through, who approves, what they check, and why Google has a four day queue of its own.

Source: https://gmbsoftware.co/profile-edit-approval-workflow/  
Site: GMBSoftware  
Updated: 19 November 2026

---

Short answerAn approval workflow decides which profile changes go live immediately and which wait for a second pair of eyes. Keep the list short or people route around it. In most organisations only four things need approval: the business name, the primary category, the address, and anything applied in bulk. Hours, photos, posts and review replies should go live without a queue, because delay on those costs more than the occasional mistake.

A profile edit approval workflow fails in one of two ways. Either everything needs approval, so branch managers stop bothering and the data rots. Or nothing does, and somebody renames forty profiles on a Friday.

## What genuinely needs a second look

Change | Approval? | Why |

Business name | Always | Names must match the real world. This is where policy breaches start. |

Primary category | Always | It affects what you match, and a change can trigger re-verification. |

Address or service area | Always | Re-verification, citation knock-on, and a suspension risk if wrong. |

Anything in bulk | Always | The error is usually in the filter, and a second person spots that fastest. |

Hours and special hours | No | Local knowledge, time sensitive, cheap to correct. |

Photos | No | A queue here simply means no photos get added. |

Review replies | No, with training | Speed matters. Train once, spot check weekly. |

Posts | No, with a template | Give people a pattern rather than a gatekeeper. |

Four things need a second look. Everything else should go live.

## Who approves

One named person with a named deputy, not a committee and not a mailbox. The deputy matters more than people expect: a single approver on holiday turns a one-day change into a two-week change, and that is exactly when somebody edits the profile directly in the dashboard to get around the process.

The approver needs the authority to say no and enough context to say yes quickly. A marketing coordinator who has to ask a director about every category change is a delay, not a control.

## What the approver actually checks

-
### Is the new value true?
Does the name match the sign, is the category what the business is, is the address somewhere customers can go?

-
### How many profiles does this touch?
For bulk changes, the count and the filter are the whole review.

-
### Are the exceptions excluded?
The branches that are genuinely different, named in advance.

-
### Is there a rollback?
An export of the current values, taken before the change.

## Google has its own approval queue

Separately from yours, Google runs one. Its page on [Google updates](https://support.google.com/business/answer/3480441) explains that suggested edits may need your review, that you have **four days to accept or reject** once notified, and that if you do not respond Google may publish the change anyway when other public information supports it. It also notes that some policy-driven edits are applied without prior review.

That four day window has to live inside somebody's week. If your internal approval cycle is a fortnight, Google's queue will resolve itself before you reach it, which means the decision gets made for you.

## Designing the queue so it gets used

- **Fast by default.** Target same-day approval, and say so.

- **Visible.** Whoever requested it can see where it is without asking.

- **Explained.** A rejection says why, in one line, or the next request repeats the mistake.

- **Logged.** Who asked, who approved, what changed, when it went live.

- **Escalating.** Nothing sits for more than three days without going to the deputy.

Fast, visible, explained, logged, and escalating.

## Emergencies need a bypass

Floods, power cuts, a burst pipe, a death in a family business. Somebody has to be able to mark a location temporarily closed at nine on a Sunday without waiting for a workflow. Name that person, give them the access, and audit the bypass monthly rather than removing it. A process with no emergency route gets broken in an emergency, and then everybody knows it can be broken.

## Franchise networks

Franchises are the hardest case, because the brand wants consistency and the franchisee owns the business. A workable split: the brand approves name, category and anything bulk across the network; the franchisee controls hours, photos, posts and replies for their own site. Write it into the franchise agreement rather than the software, because software settings are easy to change and agreements are not.

## A worked workflow

A dental group with 18 practices. Practice managers can change hours, add photos, reply to reviews and post, with no queue at all. Anything touching the practice name, the primary category or the address goes to the group marketing lead, who has agreed to decide the same day, with the operations director as deputy.

Bulk changes are rarer and go to both: the marketing lead proposes, the operations director sees the filter and the count before it runs. One person is allowed to mark a practice temporarily closed at any hour without asking, and that bypass is reviewed at the monthly operations meeting.

In the first year the queue rejected eleven changes. Nine were practice managers trying to add "Emergency Dentist" to the practice name, which tells you exactly what the next training session should cover. Two were genuine category changes that turned out to be right and were approved after a conversation. Nothing else was ever stopped, which is why hours and photos were deliberately left outside the process.

## What to do with rejected changes

Rejections carry information. If three branch managers all ask to add the same category, either they are right and the category list is wrong, or the training is unclear. Review rejected requests quarterly and look for repeats, because a pattern of rejections is nearly always a process problem rather than a people problem.

## Logging, and why it is not optional

Every approved change should leave a line: who asked, who approved, what changed, from what to what, and when. Without it, the first time a profile behaves oddly you will spend an afternoon reconstructing history from memory and email. With it, the answer takes thirty seconds and usually turns out to be a change nobody remembered making.

## When to loosen it

After six months, look at what the queue actually caught. If a category of change has never been rejected, take it out of the queue. An approval step that has never prevented anything is pure delay, and removing it is the most reliable way to keep the remaining controls respected.

### Approvals that do not slow the work down
Route the changes that matter to the right approver, let the rest go live, and keep a log of every edit.

[Tasks and approvals](/tools/smart-tasks/) [Multi-location tools](/tools/multi-location-management/)

## Frequently asked questions

**Q: Which profile changes should need approval?**
The business name, the primary category, the address or service area, and anything applied in bulk. Hours, photos, posts and replies should go straight through.

**Q: Why not approve everything?**
Because people route around slow processes. A queue that delays hours and photos simply means hours get stale and photos stop being added.

**Q: Who should be the approver?**
One named person with a named deputy, holding enough authority to decide quickly. A single approver on holiday is how the process gets bypassed.

**Q: Does Google have its own approval queue?**
Yes. For certain suggested edits Google notifies you and gives four days to accept or reject, after which it may publish the change if other public sources support it.

**Q: Should there be an emergency bypass?**
Yes. Someone must be able to mark a location temporarily closed outside working hours. Audit the bypass monthly rather than removing it.

## Sources
The Google documentation behind the guidance on this page. Google changes these pages without notice, so check the date on any figure before you rely on it.

- [Understand Google updates on your Business Profile](https://support.google.com/business/answer/3480441)
- [Understand what happens to your Business Profile edits](https://support.google.com/business/answer/3038311)
- [Manage your Business Profile owners and managers](https://support.google.com/business/answer/3403100)
- [Manage your business category](https://support.google.com/business/answer/7249669)
