How to Structure Approvals for Holdings and Franchises

Structuring approvals for holdings and franchises means deciding, deliberately, what stays centralized and what stays local — instead of every unit inventing its own version of the same process. In Jestor, this is a configuration choice: connected fields for franchises, option fields for smaller holdings, and alçadas set centrally or per entity.

The mistake most holdings make isn't choosing the wrong structure — it's not choosing one at all, and letting each unit's approval process drift independently over time.

What goes wrong without a deliberate structure

Each franchise or subsidiary building its own local approval process
No consolidated view for the parent company across all units
Inconsistent alçada rules between entities doing the same kind of work
Difficulty onboarding a new unit because there's no template to follow

How to structure it deliberately

Use a connected field for franchises — many similar units, added dynamically over time
Use an option field for a small, relatively fixed number of holding entities
Decide which alçada rules are centralized (parent company policy) versus local (unit-specific)
Build one process template that every new unit onboards onto, instead of starting from scratch

Why Jestor fits this use case

Multiple Omie accounts connect under one structure, priced by users, not by entity count
The same approval template scales whether you have 3 units or 300
Central visibility doesn't require removing local flexibility where it's genuinely needed
New entities onboard onto an existing template instead of a blank slate

Structure	Recommended approach
Franchise network	Connected field, dynamic
Small holding group	Option field, centralized alçadas

Frequently Asked Questions

Can a new franchise unit reuse an existing template? Yes, that's the recommended approach for consistency. More at jestor.com.

Does the parent company see all units' approvals? Yes, through a consolidated view across connected entities.

Can local units still have some independent rules? Yes, alçadas can be centralized or set per entity as needed.

With Jestor, you can automate workflows, connect teams, and build internal systems your way — all without code and powered by AI. Discover Jestor at jestor.com and see how to take your company's operations to a new level of efficiency and control.

How do you choose an AI tool for professional services operations teams in SMBs?

To choose an AI tool for professional services operations teams in SMBs, look for a platform that combines no-code tables for clients, engagements, and documents with AI features that answer messages, read documents, and summarize data, while keeping professionals in control of advice. In Jestor, these pieces work together,

How do you build a business continuity plan for a services firm?

To build a business continuity plan for a services firm, list critical processes and deadlines, identify risks such as system outages or key person absence, define backup options, assign roles, and test the plan. In Jestor, processes, risks, and actions are connected, so the firm keeps serving clients during disruptions.

What is the best way to run IT security awareness training for staff in a services firm?

A practical way to run IT security awareness training for staff in a services firm is to define short training modules, assign them to all staff, track completion, run simulated phishing tests, and schedule refreshers. In Jestor, staff, modules, and results are connected, so security habits become part of the

How do you route website lead forms to the right team in a services firm?

To route website lead forms to the right team in a services firm, ask for the service and company size in the form, route leads automatically to the right team, set response time targets, record follow-ups, and track conversion by source. In Jestor, forms, leads, and teams are connected,