Frontline Execution App Overview

Frontline Execution

1. What it is

Frontline Execution lets HQ author an operational directive once — a promo changeover, a store reset, a safety walk, a daily opening checklist — target it to the right locations and roles, and fan it out automatically. Every frontline worker sees one ranked My Day list of what to do this shift, and managers watch completion roll up live across their span.

• Enablement: Licensed and off by default. An admin enables it from the Apps Marketplace.
• What it is not: Frontline Execution is not a personal task manager. Work is anchored to a place and a role, not to a person. The assignee re-resolves when someone is absent, transfers, or ends their shift — the obligation and its coverage number survive regardless. For person-assigned ad-hoc tasks, use the Tasks app.

2. Standing it up

1. Go to Apps → Frontline Execution → Settings. Review the defaults — most features are on. The three surface toggles (Enable My Day, Enable Campaigns, Enable Coverage Rollup) control which sidebar sections appear for your users.

2. Import your location tree. Go to Import in the Admin section of the sidebar. Upload a CSV of your locations (hierarchy import) and a CSV of employee-to-site assignments. The import page shows a dry-run preview before writing anything. Without a location tree and people attached to it, campaigns have nowhere to fan out.

3. Set up campaign categories (optional). Go to Settings → Campaign categories. Categories are publication programme labels — “Planogram”, “Safety”, “Weekly Bulletin” — that color the publishing calendar and let you filter campaigns. They are separate from the owning department.

4. Grant access. Any employee with access to the app sees Overview, My Day, and My requests. Managers and above also see Day Sheet, Reviews, Campaigns, Calendar, Coverage, Shared blockers, and Analytics. Admins and app admins see Settings and Import.

5. Confirm it works. Create a campaign in draft, target a test location, and launch it. The targeted worker should see it on their My Day list. Use Starter campaigns on the Campaigns page to seed three editable drafts if you want a template to start from.

3. How it fits together

Campaigns and items. A campaign is the HQ directive — the aggregate. When you launch it, the platform fans it out into one item per targeted location. Each item is the durable obligation: it is bound to a place and a role, not to a person. The person holding it (current assignee) can change — through a claim, a reassignment, a handoff at shift end — without the obligation moving. That is what makes coverage survive turnover and absence.

A campaign has one of three work types:

• Task — the worker completes a piece of work, optionally with photo or signature proof.
• Inspection — the worker fills out an inspection template bound to the campaign.
• Post — the worker reads and acknowledges the directive (a read-receipt).

Example: HQ creates a campaign called “Spring Endcap Reset” with work type Task, priority Important, targeted at the “All Retail Stores” audience and the “Merchandising Associate” role. On launch, the platform mints one item per store. At Store 247, the rostered associate sees it on My Day, claims it, photographs the finished endcap, and submits. The store manager reviews the photo and accepts it. Coverage for Store 247 moves to Done; HQ watches the chain-wide number climb on the Coverage page.

Assignment strategies. Each campaign chooses how the person behind each item is resolved:

• Location manager (default) — the location’s manager is assigned automatically.
• Single assignee — one named person per location.
• Distributed — spread across eligible people at each location.
• Claim pool — work is posted unclaimed; anyone at the location can pick it up.

Resolution can happen At launch (the person is resolved immediately) or At execution (resolved when someone claims it on the floor).

Unfulfilled policies. When an obligation goes unfinished — the assignee’s shift ends, they leave, or they release it — the campaign’s policy governs what happens next: Reassign by role (pick the next eligible person), Return to pool (unclaim it), Hand off to the next shift, or Escalate (notify the manager).

Separation of duties. By default, the person who did the work cannot approve it. This is controlled by the Someone Else Must Approve Submitted Work setting. Even when turned off, campaigns that require photo or signature proof never allow self-approval.

Requests. Any employee can submit a campaign request — “stores can ask too” is a real pattern, not just HQ departments. Requests land in the Request queue, visible to managers and above, where they are approved or declined. An approved request mints a draft campaign. If the tenant has configured an Approval Workflow for Frontline Execution, decisions route through that engine instead of the queue’s direct buttons.

Blockers. A worker who cannot complete an item reports a structured reason: Stock hasn’t arrived, Missing fixture or supplies, Equipment is down, Not enough staffed time, Instructions unclear for this location, or Something else. When enough locations report the same problem on the same campaign (controlled by the Locations Needed to Group a Blocker setting, default 3), it appears on the Shared blockers page and can be escalated as a single Service Desk ticket.

Integrations with other apps:

• Tasks / Inspections — campaign items mint a Task or Inspection as the fulfillment record; notes and activities are shared.
• Training — a campaign can require completion of a Training course before work is claimable.
• Approval Workflows — publication approval and request approval both route through the generic approval engine.
• Calendar — campaigns and blackout periods project onto the shared calendar.
• Service Desk — blocker escalations can open a ticket.
• Time Clock Kiosk — workers who identify at a kiosk can see and act on their day’s work (when Show Work Lists on Shared Kiosks is enabled).
• Asset Library — campaigns can attach reference documents (planograms, spec sheets, SOPs) from the library.

4. Running it

Creating and launching a campaign

1. Go to Campaigns → New campaign.
2. Fill in the name, work type, priority, target audience, expected role, assignment strategy, and dates.
3. Attach reference documents from the Asset Library if needed.
4. Use Check writing to score the draft against your content standards (if configured).
5. Launch the campaign. If publication approval is required, submit it for approval first.

A launched campaign cannot be edited. A material change closes the original and mints a successor, so that work people already acted on is never rewritten under them.

Reviewing submitted work

Go to Reviews. The queue lists everything submitted within your span, oldest first, with proof shown inline. You can accept or reject items individually, or select multiple items and use Bulk accept to clear a batch at once.

Monitoring coverage

Go to Coverage. Each campaign shows the percentage of items completed across your locations, sorted worst-first. Drill into a campaign to see per-location status. Use Remind to send a nudge to assignees at locations that haven’t completed yet. Export to CSV for reporting.

Using the Day Sheet

Go to Day Sheet and pick a location. This page shows everything landing on that store today across all campaigns, grouped by status, with who holds each piece. It prints for the morning huddle. A “What changed” brief shows new, completed, blocked, and reassigned work over a configurable lookback window (4, 8, 12, 24, 48, or 72 hours).

Managing the publishing calendar

Go to Calendar. Every campaign with a start date appears here, colored by department. Admins can create blackout periods — no-send windows that warn authors but never block a launch.

5. Settings

All settings are at Apps → Frontline Execution → Settings.

Setting	Default	What it changes
Enable My Day	On	Shows the worker’s ranked list. Also gates Day Sheet, Reviews, and every action on a work item.
Enable Campaigns	On	Lets HQ author and launch campaigns. Also gates the Requests intake pipeline and Calendar.
Enable Coverage Rollup	On	Shows live per-campaign coverage. Also gates Analytics and Shared Blockers.
Max Critical Items Per Person Per Day	3	Caps how many critical-priority items appear on one worker’s My Day. Prevents HQ from flagging everything urgent.
Require On-Shift to Complete Work	Off	When on, workers can only complete work during a scheduled shift.
Require On-Site to Complete Work	Off	When on, work can only be completed inside the location’s geofence. Applies only to locations that have one configured.
Someone Else Must Approve Submitted Work	On	The doer cannot approve their own work. Even when off, campaigns requiring photo or signature proof never allow self-approval.
If a Training Check Can’t Be Completed	Block	For campaigns requiring a course: Block holds the work; Allow lets it through.
Let Managers Override a Training Block	Off	A manager can release one piece of work past its training requirement, with a written reason recorded permanently.
Remind Assignees This Many Hours Before Work Is Due	4	Hours before deadline to send a nudge. Set to 0 to turn reminders off.
Allow Completing Work Offline	Off	Lets workers mark work done with no signal; actions sync when connectivity returns. Claiming and photo proof still need a connection.
Enable AI Assistant	On	Ask AI answers questions about campaigns, coverage, and today’s work.
Worker-Language Pilot	(empty)	Comma-separated language codes (e.g. “es, vi”). Translates the worker’s critical path into these languages only. Empty means the worker path stays in the original language.
Hold Launch Until Someone Verifies Each Translation	Off	Requires a person to review and verify each language on the Translations screen before launch. Only applies when Warn When Translations Aren’t Ready at Launch is also on.
Translate Work Into Each Worker’s Language	On	Campaign titles and instructions render in the worker’s profile language.
Show Work Lists on Shared Kiosks	Off	Workers at a Time Clock Kiosk see and act on their day’s work at that location.
Locations Needed to Group a Blocker	3	How many locations must report the same problem before it appears on Shared Blockers.
Only Assign Work to People Scheduled to Work	Off	Refuses assignment to anyone not on the roster. A location with no published roster will have work left unassigned.
Directive-Work Budget Per Person Per Day (Minutes)	60	The workload gauge flags overload when estimated work exceeds this budget.
Send Managers a Daily Execution Digest	Off	Each morning, managers get one summary: due today, overdue, blocked, awaiting review, and yesterday’s completions.
Send Workers a Daily ‘Your Day’ Digest	Off	Each morning, anyone with work waiting gets one push with how many things, where, and how many are critical or overdue.
Release Cadence	None	Batch campaigns into scheduled releases. None means launch anytime. Weekly or Daily batch work for release at the configured day and hour.
Release Day (Weekly Cadence)	Monday	Which day a weekly release goes out. Ignored for daily cadence.
Release Hour	6	The hour the release fires, in the tenant’s local time.
Require Approval Before a Campaign Can Launch	Off	A campaign must pass the configured publication approval workflow before anyone — or the scheduled release — can launch it.
Request Lead Time Before a Release (Days)	3	Requests should arrive this many days before the release they target. Late requests are flagged, not blocked.
Content Standards for the Writing Check	(empty)	Paste your writing guidelines. The campaign’s Check writing button scores drafts against this text.
Warn When Translations Aren’t Ready at Launch	Off	Pre-launch readiness flags worker languages whose translation hasn’t completed yet.

6. More help

• Frontline Execution FAQ — specific setup and operating questions, limits, and troubleshooting.
• Ask AI — the assistant answers questions about Frontline Execution from these articles.