Pannell Platform · Pre-Scope v2 · 2026-08-07
Employees do the work. Admins glance and act. One grounded exception: the General Foreman's Daily Crew Entry is real field work done on mobile.
Bar is proportional. Several screens are one reusable pattern with states (form fill, checklist stages, lesson player, crew-entry wizard). Push deep-linking is shell routing behavior, not counted as a screen.
Every screen below is linked — tap one to open it in the live wired demo.
Everyone gets these. Content varies by role — one Home, not seven dashboards.
The primary mobile user. Four work surfaces.
Light overview + quick actions, filtered by scope — plus the one field-work screen.
| Role | Scope | Employee screens | Admin / manager screens |
|---|---|---|---|
| Executive | Unrestricted | All (own record) | All 10 · approval override at any level |
| Administrative / HR | Company-wide | All (own record) | All 10 |
| Operations Manager | Their region | All (own record) | All 10, region-filtered · shipped "area review" approval level |
| Project Manager | Their customers | All (own record) | All but Crew Entry, customer-filtered · "PM review" approval level |
| General Foreman | Their crews | All (own record) | Crew Entry · Team Overview · Time Approvals (submit + first-level approve, confirmed in code) · Snapshot · Onboarding Progress |
| Operations Administrative | Safety slice | All (own record) | Day-one rec: Team Overview · Snapshot · Training Compliance — fleet + onboarding later |
| Operations Employee | Self only | All | None |
No offline requirement — but multi-step work must not be lost. The shipped time backend already solves this: server-side draft saves with a resume-at-last-step marker, replace-on-save, and a rejected→draft fix flow. The rule for all mobile surfaces:
Keeping the mobile scope honest: all of this stays in the browser app.
Does the time entry model reshape Enter Time?
Yes — scoped off the shipped path-B backend. Two surfaces: the GF's crew Daily Entry wizard (now the flagship admin-side screen) and simple individual entries (date + start/end + break, auto OT). Not clock-in/out.
Do General Foremen approve time on mobile?
Yes — verified in the shipped backend: GFs submit entries and approve at first level, then PM review → Area Manager review → final; admin/executive override any level.
Intake in-app or mobile web?
In-app. Pre-hires get an invited login and complete intake inside the app before full access unlocks.
Offline tolerance?
Not required. Draft persistence got its own functionality pre-scope (band above) — mirroring the server-side draft pattern the time backend already ships.
Ops Administrative day one?
Recommendation: Team Overview + Team Member Snapshot + Training Compliance — the safety-officer core. Onboarding Progress and fleet views later. Presented to the client only when the build is 100%.
Do employees self-enter individual time everywhere, or only where no GF crew entry runs?
Scope for both — full individual self-entry and the GF crew path are both built. How prominent Enter Time is vs. My Time per customer is rollout configuration, not a build question.
Pin the 7 platform roles onto the shipped time roles.
Directionally clean (worker / GF / PM / area manager / admin / executive) — formalize in the roles & permissions drill-down.