McDonald's Venezuela

The challenge

McDonald's Venezuela manages a network of company-operated and franchised restaurants, plus excess properties, and needed a single, controlled place to look up the information for each location. Every restaurant carries data that changes over time —format, service segments, regional manager, consultant and property type— along with contract and permit dates whose expiry has to be tracked closely. On top of that, company policies and documents must reach the right people, and restaurant managers need to check the information for their own locations on their own. The challenge was to bring all of it into a single tool, with access based on each person's role and a record of changes to users and roles.

The solution

We built a custom web intranet that centralizes McDonald's Venezuela's restaurant portfolio. Locations are organized into three modules —company-operated restaurants, franchised restaurants and excess properties— and browsed by region, state and city. Each record brings together format, service segments, people in charge, property type, contract and permit with a validity status calculated from their dates, plus a folder with the location's documents. We added a library of policies and general documents organized in folders, and a My Restaurants view so each manager sees only the locations assigned to them. Users sign in with their corporate Microsoft account: first-time users stay pending until an administrator approves them and assigns a role. Permissions are set by role, module and action, and an audit log records the creation, modification, removal and approval of users and roles.

The result

McDonald's Venezuela's entire portfolio —company-operated restaurants, franchised restaurants and excess properties— now lives in a single intranet, with the validity of every contract and permit in plain sight and role-based access through the corporate Microsoft account.

What we built

• Modules for company-operated restaurants, franchised restaurants and excess properties, browsed by region, state and city (3 regions, 25 states and 336 cities), with excess properties organized into manageable groups.
• Complete record for each restaurant with its format (food court, freestanding, mall store or in-store), service segments such as AutoMac, McCafé and Delivery, regional manager, consultant, property type and a link to its location.
• Contract and permit tracking with start and end dates, duration and a validity status the system calculates from those dates.
• Document repository with folders for each restaurant and a Policies and General Documents library, supporting uploads of up to 20 MB and downloads based on each role's permissions.
• My Restaurants view for the restaurant manager role, limited to the locations assigned to each manager.
• Single sign-on with corporate Microsoft accounts (Microsoft Entra ID) and an approval-based onboarding flow: new users stay pending, an administrator approves them by assigning a role, and the system notifies them by email at each step.
• User and role management with permissions by module and action (11 modules and 7 action types), restaurant assignment per user, and a privileged administrator who is the only one able to create roles and is protected from edits and removal.
• Audit log that stores, field by field, the previous and new values of every creation, change, removal and approval of users and roles, filterable by module, action, user and date range.
• Layered architecture with a versioned API (19 controllers and 73 endpoints), 27 data entities with 10 versioned migrations, a Spanish and English interface, and automated builds in Azure DevOps.

Impact and results

• The head office and restaurant managers work from the same source of information about each location.
• Contract and permit renewals can be planned ahead, because the validity of each one is in plain sight on the location's record.
• Restaurant managers look up the data and documents for their own locations on their own, with access limited to what is assigned to them.
• Company policies and documents are distributed from an official repository, and each employee sees only what their role allows.
• Access depends on the corporate Microsoft account and an administrator's approval, with no additional passwords to manage.
• There is a record of who changed what and when for users and roles, which supports internal controls and audits.