AlbertUS

AlbertUS Operations Dashboard

A static dashboard for the Employbridge / Schnellecke Normal IL (Rivian site) account. It has no build step and no server: GitHub Pages serves the docs/ folder as is.

Page	What it does
Overview	The daily scorecard: the five measures committed for 11/13 (to date, report day, target, status), report day by shift, flags, weekly fill and attendance trend, day-one fallout, commitment status.
Daily log	Log exceptions only (call-off, no-call/no-show, late, left early, excused, safety, PPE) with call-received and relayed times. Everyone else on the roster counts as present. Shows daily headcount by shift, with an override when the schedule differed from the roster.
Starts	One row per shift per start day: requested, sent, arrived, refused at the gate, started.
Roster	Associates, shift, start and end dates, Rivian access status, forklift, PPE and policy checks, 90-day attendance points and standing.
Action plan	Commitments, requests to Schnellecke, topics of concern and gaps we own. These carry into every weekly report.
Pipeline planner	The orientation pipeline planner, unchanged in method. Its settings now save with the rest of the data, and Use site record fills the show, gate, day-one and attendance rates from tracked numbers.
Weekly report	The report builder (see below).
Settings	Site names, workdays, targets, baselines, exception types and points, pre-tracking attendance, and data import and export.

The calculations follow the Schnellecke Scorecard workbook: scheduled is active associates on the roster (not pending Rivian access), attendance is present / (scheduled - excused), fill is started / requested, show rate is arrived / sent, relay is the share of call-outs passed to the shift lead within 30 minutes, and points sum the last 90 days (3 written warning, 4 final, 5 end of assignment). Calendar weeks match Excel WEEKNUM(date, 1): Sunday to Saturday.

Weekly report builder

Pick the week (it defaults to the week holding the previous workday) and the Data through date.
Tick the sections you want: summary, performance by the numbers, charts, attendance by day, start days, exceptions, topics of concern, what we own, commitments, requests, pipeline and next orientation, next steps.
Edit the opening paragraph and summary bullets. The summary is written from the data until you change it; Regenerate from data brings it back.
Enter the starts needed at the next orientation and today’s ready bench. The pipeline section uses the planner’s assumptions to say how many to send, bench and source.
Export: Print or save PDF, Copy for email (pastes formatted into Outlook or Gmail; charts come along as images where the mail app accepts pasted images), Download Word (.doc, opens in Word), or Download HTML.

Untick Show associate names to print initials instead, for example when the report goes beyond the client.

Drafts save automatically per week.

Your data and privacy

GitHub Pages sites are public on the internet, even when the repository is private. So:

docs/data/seed.js holds only non-identifying starting data (start-day counts, targets, the action plan).
private/launch-record.json holds the named roster and start-day notes from the launch. It sits outside docs/, so Pages never publishes it. Keep the repository private.
Everything you enter is saved in your browser’s local storage. It is not sent anywhere and other people who open the site do not see it.

First time: open the site, go to Settings > Import data, and choose private/launch-record.json (download it from the repository first).

Back up with Settings > Export backup (JSON), and import that file to move to another computer or browser. Clearing browser data erases what is stored, so export regularly. If more than one person needs to enter data, pass the export file between you; the site has no shared database.

The page also sets noindex so search engines skip it, but anyone with the link can open it.

Publishing on GitHub Pages

Merge this branch into main (or choose this branch in step 3).
In the repository on GitHub, open Settings > Pages.
Under Build and deployment, set Source to Deploy from a branch, pick the branch, and set the folder to /docs. Save.
After a minute the site is live at https://thinkhale.github.io/AlbertUS/.

Pages for a private repository needs a paid GitHub plan (Pro, Team or Enterprise). On a free plan, either make the repository public (move private/launch-record.json somewhere else first) or keep the repository private and open docs/index.html directly from a local copy; it works offline too, apart from the web font.

Working on it

Plain HTML, CSS and JavaScript, no dependencies. To preview locally:

cd docs && python3 -m http.server 8000
# open http://localhost:8000

File	Purpose
`docs/index.html`	Page shell and navigation
`docs/assets/app.css`	Styles (Employbridge palette, light and dark, print)
`docs/data/seed.js`	Public starting data
`docs/assets/js/store.js`	Saved state, import, export
`docs/assets/js/metrics.js`	Scorecard calculations
`docs/assets/js/charts.js`	SVG charts
`docs/assets/js/ui.js`	Editable tables and helpers
`docs/assets/js/views.js`	Overview, daily log, starts, roster, action plan, settings
`docs/assets/js/planner.js`	Orientation pipeline planner
`docs/assets/js/report.js`	Weekly report builder
`docs/assets/js/app.js`	Router and theme