Frontline Execution

Tasks is a personal and project to-do surface where you assign work to a named individual. Frontline Execution is the HQ-to-field layer above it: you author one directive, target a slice of the org, and the platform creates and tracks the work per location with a coverage rollup. It runs on the same underlying task records, so completion, checklists and proof are shared — this app adds the campaign, the targeting, the late binding, and the rollup.

Yes. Assignment checks approved leave, the published roster, the person's role, and any certification the campaign requires. Someone on approved leave is never assigned. People rostered at that location for the relevant window are preferred over people who are not, and a tenant can go further and refuse assignment to anyone unscheduled — that setting is off by default, because an unowned obligation is usually worse than an imperfectly owned one.

Yes. A campaign can require a photo, a signature, or both, and the server refuses to mark the work done until the proof is there. Completion can also be fenced to an active shift and to the location itself, using the same geofence clock-in already uses. If review is enabled, completing the work submits it instead of finishing it, and a reviewer accepts it or sends it back. A multi-approver policy and form or survey prerequisites are not supported.

No, by default. Separation of duties is on out of the box and applies everywhere work is reviewed — the review queue, bulk accept, the mobile app, the API, and the AI assistant. Administrators are not exempt. A tenant can turn the rule off for lower-risk work, but it still holds on any campaign that required photo or signature proof: evidence exists so that someone else can look at it.

The work is blocked, not waved through. A training check that cannot be completed is treated as a visible problem rather than as a pass, because an unconfirmable prerequisite is not the same as a confirmed one. A tenant that decides an outage must never stop the floor can switch that to allow, and a manager can record an accountable override on one specific piece of work — with a written reason kept permanently against it.

Three ways. My Day is a single ranked list rather than an inbox, and every row says why it is ranked where it is. There is a hard cap on how many items may present as critical to one person per day, so HQ cannot flag everything urgent. And before a campaign is sent, a workload gauge sums what that audience is already carrying across campaigns, ordinary tasks, unread must-reads and due training — so overload is visible at authoring time, not in a post-mortem.

Yes. Every campaign carries a decision history covering launch, closure, reassignments, handoffs, escalations, training overrides and reviews, with the actor and time on each row, plus a CSV export. Automatic decisions are marked as system rather than attributed to a person, and anything done through the AI assistant is flagged as AI while still naming the person it acted for. The history is retained even if the campaign itself is deleted.

Campaign titles and descriptions translate into each worker's profile language automatically. For the worker's critical path — the instructions, what proof is needed, the blocked-reason list, and a reviewer's send-back note — a tenant nominates up to two pilot languages. Translated content is labelled as machine translated and names the source language, and anything that cannot be translated falls back to the original rather than showing a half-translated screen.

Frontline Execution requires a license and is disabled by default. An administrator opts the business in from the Apps Marketplace, and can then control which surfaces are on — My Day, campaign authoring, and the coverage rollup are each independently switchable.