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 Admin → Apps → All Apps.
• 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, so the obligation and its coverage number survive absence, transfers and turnover: work the holder doesn’t finish is moved by the campaign’s rule once its deadline passes, and a manager can hand it off sooner. For person-assigned ad-hoc tasks, use the Tasks app.

2. Standing it up

1. Go to Apps → Frontline Execution → Settings. Review the defaults — the main surfaces are on. Under Available features, the three surface toggles (My Day, Campaigns, 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, Request queue, Campaigns, Calendar, Coverage, People, 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.

Who does it. Each campaign chooses how the person behind each item is resolved:

• Each location’s manager (default) — the location’s manager is assigned automatically.
• A single named owner — one named person per location.
• Round-robin across the team — spread across eligible people at each location.
• Anyone at the store can claim it — work is posted unclaimed; anyone at the location who qualifies can pick it up.

When the owner is decided is either At launch — resolve the owner when it goes out or When it’s picked up — whoever claims it becomes the owner.

Unfinished work. Work that is still open once its deadline has passed — including work held by someone who has since left — is handled by the rule the campaign chose under If the work is still open when it’s due: Hand it to whoever holds the role now (the default), Put it back in the pool, Hand off to the next shift, or Escalate to the accountable manager. Until the deadline passes, the work stays with whoever holds it.

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 a Training course; work can be claimed without it, but can’t be completed until the course is.
• 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. A campaign launched by hand during one only shows a warning and is never blocked; a scheduled release that falls inside one waits, and goes out when the window ends.

5. Settings

All settings are at Apps → Frontline Execution → Settings, in the order and with the names the page uses.

Available features

Setting	Default	What it changes
My Day	On	The worker’s single ranked list. Turning it off also removes Day Sheet, Reviews, and every work action on the web, mobile, shared kiosks and the API, and pauses the daily digests and due-soon reminders.
Shift pass-downs	Off	The outgoing shift shares open work, counts and notes with the next shift on My Day, Day Sheet, mobile and shared kiosks; the wrap-up after clocking out in a browser offers it as an optional step. The next shift acknowledges the handover. Shifts the system closed are marked, so a missing handover is not read as an all-clear.
Review handover follow-ups	Off	Requires Shift pass-downs. Turn unfinished actions from a saved handover into Tasks items; a person reviews each one before it is created. AI suggests actions while Enable AI features is on.
Recheck stores after a shared ticket is resolved	Off	When a linked Service Desk ticket is resolved, asks affected employees whether they can continue, and shows their answers on Shared blockers. Resolving the ticket never completes their work.
Screen pass-down text	On	Checks handover notes against your organization’s moderation rules before they save, including notes entered on a shared kiosk. Does nothing until your organization’s moderation rules are set up.
Campaigns	On	Lets HQ and managers author and launch campaigns. Also removes Requests, Calendar, Categories, the Translations desk, and campaign Q&A.
Coverage rollup	On	Live per-campaign coverage up the location hierarchy. Also removes People, Shared blockers, Analytics, Remind on the coverage roster, Nudge on the Day Sheet, the coverage lines in the manager digest, and Ask AI’s coverage answers.
Shared kiosks	Off	Workers who identify at a kiosk with their employee ID and PIN can see, claim, complete and report problems with their work for that location. It is a shared device with no login — turn it on only where the tablet is physically controlled.

Work rules

Setting	Default	What it changes
Most critical items one person sees per day	3	Critical items beyond this keep their order on My Day but lose the critical badge, and someone already holding this many can’t claim another critical item. 1 to 50.
Locations needed to group a blocker	3	The same blocker reported at this many locations on one campaign becomes one shared blocker. 2 to 50.
Directive-work budget per person per day (minutes)	60	The budget the workload gauges in the campaign form, the Request queue and Ask AI measure against.
Only allow completing work while on shift	Off	Only workers who are clocked in, or on a scheduled shift (not a draft or on-call standby, with a 15-minute grace window either side), can complete work.
Allow saving work offline	Off	On the mobile site, workers can save photos, signatures and submissions on their device; they upload when connected and must still pass the required checks. Claiming shared work, and submitting work that needs a location check, still need a connection.
Only allow completing work at the location itself	Off	Uses the Time & Attendance geofence. Locations without one are unaffected.
Only assign work to people on shift	Off	Refuses assignment to anyone not on shift — scheduled at the location (not a draft or on-call standby), or clocked in there right now. People on approved leave are never assigned. A location whose roster is still a draft may have work left unassigned.
Someone else must approve submitted work	On	The person who did the work can’t approve it. Even when off, campaigns requiring photo or signature proof never allow self-approval.
If a training check can’t be completed	Block the work until training can be confirmed	Only for campaigns that require a course. The other choice is Let the work through.
Let managers override a training block	Off	A manager can release one piece of work past its training requirement, with a reason recorded permanently.

Release schedule

Setting	Default	What it changes
Release frequency	No scheduled releases — launch anytime	Weekly release or Daily release batch scheduled campaigns, which then publish automatically on the day and hour below.
Release day (weekly)	Monday	Which day a weekly release goes out. Ignored for daily releases.
Release hour (0–23)	6	The hour the release goes out, in your company’s time zone (UTC when the company has none set).
Request lead time before a release (days)	3	Late requests are still accepted, but flagged in the Request queue. 0 turns the cutoff off.
Require approval before a campaign can launch	Off	Manual and scheduled launches need approval through a “Campaign publication” approval workflow. Set up that workflow first, or campaigns cannot launch.

Authoring & language

Setting	Default	What it changes
Content standards for the writing check	(empty)	The campaign’s Check writing button scores drafts against this text. Up to 5,000 characters.
Worker-language pilot	None	Up to two languages (First language, Second language). Matching workers get translated instructions, proof requirements, blocked reasons and review notes. Needs Translate work into each worker’s language.
Warn when translations aren’t ready at launch	Off	Before launch, flags worker languages whose translation isn’t finished yet, and queues the missing ones. Shown while Campaigns is on.
Keep the warning until translations are verified	Off	The warning above stays until a person verifies each language on the Translations screen. It is advisory — it does not block anyone from launching. Applies only when the warning above is on.

Notifications

Setting	Default	What it changes
Send managers a daily execution digest	Off	Each morning, managers get one summary of their span: due, overdue, blocked, awaiting review, and completions. Paused while My Day is off.
Send workers a daily “your day” digest	Off	One morning push to anyone with assigned or claimable work; anyone with no work is skipped. Paused while My Day is off.
Remind the assignee this many hours before work is due	4	Sends once per assigned item; unclaimed work escalates instead. 0 turns reminders off. Paused while My Day is off.

AI

Setting	Default	What it changes
Enable AI features	On	One switch for every AI feature in this app: the Ask AI assistant, the photo proof-check on the review queue, the Check writing pass on campaign drafts, the microphones (dictation on work items and the assistant on shared kiosks), machine translation, handover follow-up suggestions, and the “Describe it and let AI fill the form” bar. With it off, none of them run.
Translate work into each worker’s language	On	Campaign titles and instructions show in each worker’s profile language, including the worker-language pilot. Requires Enable AI features.

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.