📥 Master Schedule Loader — Guide

The Master Schedule Loader is a safety net. When the weekly Master Schedule drops, it lets you drag the file in and push the rolling 3-week look-ahead into the schedule app in one step — so if a manual Monday load is ever missed, the window is always recoverable. You never need to read any code or touch a spreadsheet formula.

1. What it does & when to use it

The loader reads the PARAGON-NEI-UG entry sheet from a Master Schedule workbook, parses the look-ahead, and writes each super’s jobs into the schedule store the look-ahead app reads.

• Weeks 1–2 load daily (the Mon–Fri headcounts for the first two weeks).
• Week 3 is left empty on purpose — that’s the supers’ to fill in.
• It’s a recovery tool, not the everyday path. Use it when a master drops and you want the look-ahead refreshed quickly, or to catch up a missed Monday load.

2. Before you start

• The current Paragon Master Schedule .xlsx — e.g. Paragon Master Schedule 6-22-2026.xlsx from P:\009 - Active Project Schedule.
• The loader: paragontulsaresults.com/master-loader.html
• The look-ahead, to confirm results afterward: lookahead-sandbox.html (for sandbox tests) or lookahead.html (production).

3. Loading to the sandbox (the safe test)

The loader always opens pointed at the SANDBOX store — an isolated copy that supers and the CEO report never see. Always do a sandbox pass first.

1. Open the loader. Confirm the banner reads “SANDBOX TARGET” (amber).
2. Drag the master .xlsx onto the drop zone (or click to choose it).
3. Review the preview (see section 4). Fix the Week Of date if needed — it’s editable.
4. Find the action bar — a strip pinned to the very bottom of the window (it stays put as you scroll, it is not at the end of the preview). It holds the Sandbox/PRODUCTION toggle and the load button. On Sandbox the load button is amber.
5. Click ⬆ Load weeks 1–2 to store and confirm the dialog.
6. Read the green result line — it lists what loaded per super (e.g. “Jared 4 · Randy 6 …”) plus any rows sent to unassigned.
7. Click the lookahead-sandbox link in the result, set the same Week Of, and spot-check a super: weeks 1–2 filled, Week 3 empty.

4. Reading the preview

5. Edit protection — the rule that matters

This is the safeguard that makes re-loading safe. The loader never overwrites a row a person has edited.

• When the loader writes a row, it tags it as loader-origin.
• When a super changes a day in the look-ahead and saves, that row becomes a human row.
• On the next load of the same week, the loader refreshes only its own rows and keeps every human row untouched.

You’ll see this in the result line as a “kept” count — e.g. “Jared 3 (1 kept)” means 3 rows refreshed from the sheet and 1 edited row was protected.

6. Loading to production (the live store)

1. With a good preview loaded, click the PRODUCTION button on the target toggle.
2. The banner turns red (“PRODUCTION TARGET”), and in the bottom action bar the load button itself turns red (it’s amber on Sandbox) with a red accent line. This is your cue that the next load is live.
3. Click ⬆ Load weeks 1–2 to store and confirm the first dialog.
4. A second prompt appears. Type LOAD PROD exactly to proceed. Anything else cancels — nothing is written.
5. The result line and the “open” link now point at lookahead (production). Verify there.

Edit protection works on production too: a prod re-load keeps supers’ edits and refreshes only loader rows.

7. What does & doesn’t get loaded

8. Troubleshooting & FAQ

I can’t find the Load button.

It’s not in the scrolling page — it lives in the action bar pinned to the very bottom edge of the window, so it stays in place as you scroll. Look for the dark strip at the bottom: Sandbox/PRODUCTION toggle, then the ⬆ Load weeks 1–2 to store button (amber on Sandbox, red on Production). If you don’t see it, press Ctrl+- to zoom out, or make sure the window isn’t taller than the screen.

The Load button is greyed out.

No app sections were found in the file. Confirm you dropped a real Master Schedule with the PARAGON-NEI-UG sheet, and that the preview shows the crew sections (Site / Utility / Concrete / Asphalt / NEI / FSL / United Golf).

A crew shows up under “unassigned.”

The crew name on that job isn’t one the app maps to a super yet. The row still loads (under unassigned) so nothing is lost. The fix is to add that name to the app’s name list — note it and pass it along; it’s not an error.

I loaded the wrong week / wrong file.

Re-drop the correct file (or fix the Week Of date) and load again. Because loaded rows are refreshed in place per week, a corrected re-load supersedes the bad one — and any field edits are kept.

I clicked PRODUCTION by mistake.

Nothing is written until you both confirm and type LOAD PROD. Click Sandbox to switch back, or just don’t complete the typed prompt.

Week 3 is empty after loading.

That’s correct — Week 3 is intentionally left for the supers to fill in.

Did my file get uploaded somewhere?

No. The .xlsx is parsed entirely in your browser. Only the resulting schedule data (job names, crew names, headcounts) is saved to the store.

9. Quick reference card