Foothill Solutions · Restaurant365 Engagement · Device Operations
Collect every R365 device, wipe it clean, and re-enroll it into the client’s managed domain (Intune or Jamf). One technician, working desk to desk — scheduled by mission and trio so no team ever goes fully dark. This is the working draft; swap in the real daily presence list and the schedule re-flows.
Read this first
Every number below is an estimate, not a measured fact. Treat them as the starting dial settings — we re-measure on the first few real devices and adjust. If any assumption is wrong, the timeline shifts, so they’re stated up front to be challenged.
The parallel idea
The trick isn’t working faster — it’s never standing idle. A wipe is mostly unattended time. You kick one device off, walk to the next desk and start that one, then circle back to finish the first when it lands on the setup screen. Your hands — not the clock — are the bottleneck, which is exactly why the daily number is capped.
Solid teal = you’re hands-on. Hatched = the device works alone while you’re at another desk. Stack the hatched stretches across many devices and the day collapses to roughly the sum of your hands-on minutes.
| Mac — hands-on each5 min kickoff + 10 min enroll | 15 min |
| Windows — hands-on each8 min kickoff + 15 min enroll | 23 min |
| A typical day — 21 Mac + 4 PChands-on only, wipes overlap | ~6.8 hrs |
| With walking between desksa full day, with a small buffer | ~7.5–8 hrs |
Why 25 and not more: a 25-device day already runs about 7.5–8 hours hands-on. Anything past that leaves no buffer for a stuck reinstall or a no-show desk. If a day’s presence is heavier than 25, roll the overflow to the next office day rather than stretching the technician past a full shift.
Per-device runbook
Macs use Erase All Content & Settings (fast, firmware-clean on Apple Silicon). Windows gets a full format and reinstall. Both finish by auto-enrolling into the client’s MDM — which works only if the device is pre-staged in the client’s Apple Business Manager / Autopilot first (see pre-flight below).
Before you touch a single device
Every item below is something that, if skipped, either bricks the hardware or means the device won’t enroll and you have to come back. Knock these out before the office day — most are admin-console work, not desk work.
Scheduling rule
The 176 R365 staff sit in 12 missions, split into 55 trios (mostly 3-person teams). Each day’s 25 devices are chosen to spread across missions and to take at most one person per trio, so every team keeps at least two members working while their colleague’s laptop is being re-imaged.
The rule: on any given day, pick ≤ 1 member from each trio and keep the day’s devices spread across as many missions as possible. A trio is never blocked; a mission is never paused.
| Mission | People | Trios | Min. days to clear | Notes |
|---|---|---|---|---|
| Platform | 20 | 7 | 3 | Largest mission — leads each wave |
| PLG | 20 | 7 | 3 | |
| CV | 19 | 7 | 3 | |
| Modernization | 19 | 7 | 3 | |
| Enterprise | 19 | 7 | 3 | |
| Workforce | 18 | 7 | 3 | |
| Payroll-Growth | 16 | 6 | 3 | |
| AI-Products | 15 | 5 | 3 | |
| Payroll-Compliance | 11 | 4 | 2 | |
| Integrations | 10 | 4 | 2 | |
| DevOps | 6 | 1 | 6 | Single trio — stagger 1/day, don’t block |
| Data-AI-Platform | 3 | 1 | 3 | Single trio — 1/day max |
“Min. days to clear” = if you only respect the one-per-trio rule. DevOps and Data-AI-Platform are each a single trio, so they trickle one person per day — flag them early so they don’t become the long tail.
Sample day · Tuesday
A realistic solo day at the 25-cap. Morning is heavy Mac throughput; a few Windows machines get kicked off before lunch so their 60-minute reinstalls run while you eat. Afternoon finishes the Windows enrollments and the remaining Macs. Every wave pulls from different trios.
Log into ABM / Jamf / Intune / Autopilot consoles. Confirm Wi-Fi, labels, USB installers, tracking sheet open. Sanity-check that today’s 25 are pre-staged.
Roll Macs across several missions — start, move, circle back to enroll. Kick off one Windows reinstall early so it runs in the background.
Continue Macs across fresh trios; return to the morning PC for Entra join + Intune enrollment as it hits OOBE.
Start 1–2 more Windows reinstalls right before stepping away so the unattended ~42m covers the break.
Finish the post-lunch Windows enrollments; push through the next batch of Macs from remaining missions.
Mop up remaining devices, retries, and any that failed first enrollment. Re-run stuck reinstalls.
Confirm every device today shows managed/compliant in the console. Update the tracker. Flag any incompletes to carry into the next office day.
Live tracker
| # | Employee | Mission | Trio | Device | Status |
|---|
Fallback
If live desk-side setup can’t be trusted on the day — e.g. enrollment needs the US team and the timezone gap blocks real-time coordination, or the parallel flow keeps stalling — switch to a pre-staged swap pool. You decouple the user handover (fast) from the slow, coordination-dependent enrollment (done offline). Cost: ~10 swaps/day instead of 25, but zero live dependency and no team blocked.
Wipe and fully enroll the 10 laptops already in the office into the client domain — done ahead of time, during US hours, so coordination isn’t time-critical.
Give each of 10 employees a ready-to-go laptop and collect their old device on the spot. ~5 min per person, no waiting at the desk.
Re-image and re-enroll the collected devices offline, at your own pace, coordinating with the US team whenever their window opens.
The freshly-prepared 10 become the next day’s swap stock for the next 10 employees. Repeat until the fleet is done.
The full picture
Total device load per mission. At the sustainable 25 devices/day (Plan A), the fleet clears in roughly seven working days — but those days are gated by who’s physically in the office, so plan on about three calendar weeks following the daily presence rota. (Plan B’s swap pool runs slower but removes the live coordination risk.)
Lead with the big missions (Platform, PLG, CV) on the highest-turnout days. One per trio, ~25/day.
Work down mid-size missions by daily rota. Trickle the single-trio missions (DevOps, Data-AI) so they don’t tail out.
Catch rarely-in-office staff, WFH machines, and the Windows tail. Final console reconciliation.
Decisions still needed
None of these block drafting the plan, but each one changes the execution. The owner column flags who needs to answer.
Windows goes to Intune/Autopilot regardless. Macs enroll via ABM either way, but the console you verify in (and the enrollment payload) differs. Lock this so pre-staging targets the right MDM.
Devices must be in the client’s ABM/Autopilot and released from any prior MDM before their day, or they won’t auto-enroll. Confirm whether we or the client drive this.
This is the Plan A vs Plan B decision. If real-time US coordination is required, the timezone gap may force the swap-pool fallback.
~30 of 176 are Windows; the device type per person is known. Confirm the list so the daily counts and time math are locked.
Needed to assign the actual mission/trio cohorts to each weekday.
The swap-pool fallback needs ~10 ready devices to start the rotation. Confirm availability and staging space.