HD Sports Zone Bookmark 25O-3 — Manager Schedule Builder Workflow Guide / Safe Use Map

Read-only guide explaining how the manager should use the current schedule builder workflow: build schedule, prepare draft, review conflicts, publish, then employees view the published schedule.

Existing Production / Build Builder Checklist Builder Diagnostics Builder Completion Review Conflicts Employee Portal Builder Inventory Builder Route Catalog Developer Tools

Workflow Guide Summary

This guide is read-only. It explains the intended manager process without changing the live production/build workflow.

Generated Jun 4, 2026 11:24 PM

Read Only Guide Mode

Explains the workflow without changing schedule behavior.

7 Workflow Steps

Manager build, draft, review, publish, and employee-view process.

6 Daily Manager Actions

Plain-language actions the manager should follow.

0 Route Issues

Critical workflow routes needing review.

7/6 Tables Present / Missing

Schedule data tables detected for future builder work.

0/0 Readiness / Guard Issues

Next-phase readiness and guardrail checks.

Preserved Boundaries

Read-only workflow guide No route removal No production route override No schedule logic changes No My Schedule patch No Weekly patch No Weekly Print patch No employee portal patch No manager route override No developer route override No database writes No migrations No middleware created No middleware applied No auth config changes No payroll changes No Time Clock rules changes No POS shifts changes No reservations changes No payments changes No waivers changes No customer profile changes No exports No PDFs No CSVs No employee texts No employee emails No schedule locking changes No hard schedule blocking changes

Manager Workflow Steps

Step 1

Open Manager Simple Menu

Manager action: The manager starts from the simplified manager schedule menu.

What happens: This keeps the manager out of the older diagnostic clutter and gives one clean starting point.

Safe note: Navigation only. No schedule is created here.

Manager Simple Menu
Step 2

Open Build Schedule

Manager action: The manager opens the existing production/build schedule screen.

What happens: This is where real schedule-building currently lives. This phase does not replace or modify it.

Safe note: Do not override production until the exact existing form, buttons, and data flow are fully mapped.

Existing Production / Build Schedule
Step 3

Prepare Draft Schedule

Manager action: The manager builds or adjusts draft shifts using the existing production workflow.

What happens: Draft shift data is expected to be separate from employee published views until the schedule is published.

Safe note: Employees should not see draft/incomplete shifts as final published schedule.

Builder Route Catalog
Step 4

Review Soft Conflicts

Manager action: The manager reviews unavailable blocks, appointments, manager holds, and other soft conflicts.

What happens: Conflicts are warnings/review items so the manager can make informed decisions.

Safe note: Still no hard blocking. The manager remains in control.

Review Soft Conflicts
Step 5

Publish Approved Schedule

Manager action: After review, the manager publishes from the existing production workflow.

What happens: Published schedule data should become visible to employee self-view screens.

Safe note: Do not change publish behavior until the exact draft-to-published flow is fully confirmed.

Existing Publish Workflow
Step 6

Employees View Schedule

Manager action: Employees open their schedule from the employee portal.

What happens: Employees use My Schedule, Weekly Schedule, and Print Weekly to view their schedule.

Safe note: Employee screens remain simple and separate from manager builder tools.

Employee Portal
Step 7

Use Reports / Support Tools

Manager action: The manager uses operations, print, export, and support screens when needed.

What happens: Reports and diagnostics support the workflow but should not clutter daily employee scheduling.

Safe note: Keep diagnostics grouped in Developer Tools Drawer.

Operations Hub

Daily Manager Actions

Action Why Open
Start from Manager Simple Menu This is the clean manager entry point after the 25N navigation cleanup. Open
Build or edit schedule from Production The existing production route is still the live schedule-building workflow. Open
Check conflicts before publishing Soft conflicts help the manager avoid scheduling over unavailable blocks. Open
Publish only after review Draft data should not be treated as final employee-facing schedule until published. Open
Send employees to Employee Portal Employees should use the simple self-view pages, not builder/admin screens. Open
Use Developer Tools only for troubleshooting Smoke tests, route catalogs, and diagnostics should stay out of the daily workflow. Open

Employee View Boundaries

Boundary Details
Employees see only their schedule workflow Employee Portal, My Schedule, Weekly Schedule, and Print Weekly should be the normal employee-facing pages.
Employees should not build schedules Production/build, draft, publish, route catalogs, and diagnostics should remain manager/admin/developer tools.
Employees should see published schedule data Draft/incomplete manager work should not be treated as final employee schedule until the publish workflow completes.
Print Weekly remains simple The print view should remain easy for employees to read without manager builder clutter.

Important Screen Links

Group Screen Purpose Open
Manager Daily Manager Simple Menu Clean manager starting point. Open
Manager Daily Production / Build Schedule Existing real schedule-building workflow. Open
Manager Daily Review Soft Conflicts Review unavailable blocks and conflicts before publish. Open
Manager Support Operations Hub Reports, print, exports, and support pages. Open
Builder Planning 25O-1 Builder Inventory High-level inventory of builder routes/tables/files. Open
Builder Planning 25O-2 Builder Route Catalog Detailed route/screen catalog. Open
Employee Daily Employee Portal Simple employee self-view starting point. Open
Developer Developer Tools Drawer Diagnostics, smoke tests, plans, route catalogs, and completions. Open

Route Checks

Route Status URI Expected / Blocked Action Open
Builder Workflow Guide Passed hd/employee-schedules/builder/workflow-guide EmployeeScheduleBuilderWorkflowGuideController App\Http\Controllers\Hd\EmployeeSchedules\EmployeeScheduleBuilderWorkflowGuideController@index Open
Builder Workflow Guide Alias Passed hd/employee-schedules/access-resolver/builder-workflow-guide EmployeeScheduleBuilderWorkflowGuideController App\Http\Controllers\Hd\EmployeeSchedules\EmployeeScheduleBuilderWorkflowGuideController@index Open
Builder Route Catalog Passed hd/employee-schedules/builder/route-catalog EmployeeScheduleBuilderRouteCatalogController App\Http\Controllers\Hd\EmployeeSchedules\EmployeeScheduleBuilderRouteCatalogController@index Open
Builder Inventory Passed hd/employee-schedules/builder/inventory EmployeeScheduleBuilderInventoryController App\Http\Controllers\Hd\EmployeeSchedules\EmployeeScheduleBuilderInventoryController@index Open
Production / Build Schedule Passed hd/employee-schedules/production Blocked: EmployeeScheduleBuilderWorkflowGuideController App\Http\Controllers\Hd\EmployeeSchedules\EmployeeScheduleProductionRouteRescueController@index Open
Manager Simple Menu Passed hd/employee-schedules/navigation-cleanup/manager-simplified EmployeeScheduleManagerSimplifiedNavigationController App\Http\Controllers\Hd\EmployeeSchedules\EmployeeScheduleManagerSimplifiedNavigationController@index Open
Employee Portal Passed hd/employee-schedules/employee-portal EmployeeScheduleSimplifiedPortalController App\Http\Controllers\Hd\EmployeeSchedules\EmployeeScheduleSimplifiedPortalController@index Open
My Schedule Passed hd/employee-schedules/employee-portal/my-schedule EmployeeScheduleMyScheduleSelfViewController App\Http\Controllers\Hd\EmployeeSchedules\EmployeeScheduleMyScheduleSelfViewController@index Open
Weekly Schedule Passed hd/employee-schedules/employee-portal/weekly EmployeeScheduleWeeklySelfViewController App\Http\Controllers\Hd\EmployeeSchedules\EmployeeScheduleWeeklySelfViewController@index Open
Print Weekly Passed hd/employee-schedules/employee-portal/weekly/print EmployeeScheduleWeeklyPrintSelfViewController App\Http\Controllers\Hd\EmployeeSchedules\EmployeeScheduleWeeklyPrintSelfViewController@index Open
Developer Tools Drawer Passed hd/employee-schedules/navigation-cleanup/developer-tools EmployeeScheduleDeveloperToolsDrawerController App\Http\Controllers\Hd\EmployeeSchedules\EmployeeScheduleDeveloperToolsDrawerController@index Open

Schedule Table Checks

Table Status Rows Purpose Columns Guide Note
hd_schedule_periods Present 2 Candidate schedule week/period source. id, title, starts_on, ends_on, status, source, notes, created_by, updated_by, created_at, updated_at, deleted_at Known table. Future behavior changes must respect existing data.
hd_draft_shifts Present 5 Candidate manager draft schedule shift rows. id, schedule_period_id, employee_id, work_date, starts_at, ends_at, role, location, area, status, has_soft_conflict, soft_conflict_summary, manager_notes, created_by, updated_by, created_at, updated_at, deleted_at Known table. Future behavior changes must respect existing data.
hd_published_schedule_periods Present 1 Candidate published schedule period/week source. id, source_schedule_period_id, title, starts_on, ends_on, published_status, source_snapshot_status, prepared_by, prepared_at, published_by, published_at, published_shift_count, source_draft_shift_count, source_warning_count, source_hard_stop_count, source_summary_payload, internal_notes, created_at, updated_at, deleted_at Known table. Future behavior changes must respect existing data.
hd_published_shifts Present 1 Candidate employee-facing published shifts. id, published_schedule_period_id, source_schedule_period_id, source_draft_shift_id, employee_id, work_date, starts_at, ends_at, role, location, area, published_shift_status, source_had_soft_conflict, source_soft_conflict_summary, manager_notes, source_shift_payload, created_at, updated_at, deleted_at Known table. Future behavior changes must respect existing data.
hd_schedule_audit_logs Present 10 Schedule audit trail. id, schedule_period_id, draft_shift_id, audit_area, audit_action, summary, before_payload, after_payload, performed_by, performed_at, created_at, updated_at Known table. Future behavior changes must respect existing data.
hd_schedule_publish_acknowledgments Present 1 Candidate employee acknowledgment source. id, schedule_period_id, acknowledgment_status, acknowledged_by, manager_name, acknowledged_at, draft_shift_count, hard_stop_count, warning_count, soft_conflict_count, unassigned_shift_count, acknowledged_no_publish, acknowledged_no_locking, acknowledged_no_employee_texts, acknowledged_no_payroll_timeclock_pos, acknowledged_no_exports, acknowledged_guardrails_reviewed, checklist_payload, manager_note, created_at, updated_at, deleted_at Known table. Future behavior changes must respect existing data.
hd_employee_schedule_templates Not Detected 0 Candidate future schedule templates. Not detected Candidate only. Do not create during guide phase.
hd_employee_shift_templates Not Detected 0 Candidate future employee shift templates. Not detected Candidate only. Do not create during guide phase.
hd_shift_templates Not Detected 0 Candidate future generic shift templates. Not detected Candidate only. Do not create during guide phase.
hd_schedule_templates Not Detected 0 Candidate future schedule templates. Not detected Candidate only. Do not create during guide phase.
hd_employee_availability Not Detected 0 Candidate availability source. Not detected Candidate only. Do not create during guide phase.
hd_employee_unavailable_blocks Present 0 Candidate unavailable block source. id, company_id, employee_id, block_type, title, starts_on, ends_on, all_day, starts_at, ends_at, status, employee_note, manager_note, created_by, reviewed_by, reviewed_at, created_at, updated_at Known table. Future behavior changes must respect existing data.
hd_unavailable_blocks Not Detected 0 Candidate unavailable block source. Not detected Candidate only. Do not create during guide phase.

Do / Do Not Rules

Type Rule
Do Use the Manager Simple Menu as the manager’s daily entry point.
Do Build and publish from the existing production workflow until the builder is fully mapped.
Do Review soft conflicts before publishing.
Do Keep employees on Employee Portal, My Schedule, Weekly, and Print Weekly.
Do Not Do not show employees draft builder pages.
Do Not Do not hard-block manager scheduling from unavailable blocks yet.
Do Not Do not add automatic scheduling until templates, roles, availability, and publish flow are intentionally designed.
Do Not Do not mix payroll, Time Clock rules, POS shifts, reservations, payments, waivers, customers, or schedule locking into this module.

Readiness Checks

Check Status Note
Production route exists and is separate Passed Production/build remains the existing live manager workflow.
Builder inventory route exists Passed 25O-1 inventory remains available.
Builder route catalog exists Passed 25O-2 route catalog remains available.
Employee portal remains simplified Passed Employee self-view remains separated.
Draft shifts table status known Passed hd_draft_shifts present.
Published shifts table status known Passed hd_published_shifts present.
Schedule periods table status known Passed hd_schedule_periods present.

Guardrail Checks

Guardrail Status Note
No enforcement middleware created
/home/at4txjiyemp4/public_html/hdsportszone.com/app/Http/Middleware/HdEmployeeScheduleSelfAccess.php 		Passed Workflow guide does not add middleware.
Auth config exists but is not changed
/home/at4txjiyemp4/public_html/hdsportszone.com/config/auth.php 		Passed This phase does not edit config/auth.php.
Bootstrap middleware file exists but is not changed
/home/at4txjiyemp4/public_html/hdsportszone.com/bootstrap/app.php 		Passed This phase does not register middleware.
Production route not overridden by workflow guide
route inventory 		Passed Workflow guide must not replace the actual production/build workflow.
No database writes performed by workflow guide
controller/view only 		Passed Workflow guide only reads route/table state.

Safe Boundaries

  • 25O-3 is a read-only workflow guide.
  • It explains the manager process but does not change the process.
  • It does not create, edit, delete, publish, lock, or schedule shifts.
  • It does not override the production/build schedule route.
  • It does not add automatic scheduling.
  • It does not add templates yet.
  • It does not change employee self-view routes.
  • It does not change payroll, Time Clock rules, POS shifts, reservations, payments, waivers, customer profiles, employee texts, exports, PDFs, CSVs, schedule locking, or hard schedule blocking.

Not Changed

  • No routes were removed.
  • No production/build route was overridden.
  • No schedule rows were created.
  • No schedule rows were edited.
  • No schedule rows were deleted.
  • No publish workflow was changed.
  • No draft workflow was changed.
  • No employee self-view route was changed.
  • No manager simple menu route was changed.
  • No developer tools drawer route was changed.
  • No middleware was created.
  • No middleware was applied.
  • No auth config was changed.
  • No database writes were introduced.
  • No exports, PDFs, or CSVs were introduced.
  • No employee texts or employee emails were introduced.

Next Recommended Phase

25O-4 — Manager Schedule Builder Checklist / Safe Build Prep
Recommended next phase should add a read-only manager checklist for schedule-building readiness before we make any real builder changes.
  1. Keep it read-only.
  2. Use the workflow guide from 25O-3.
  3. Create checklist sections for Start, Build, Draft, Conflict Review, Publish, and Employee View.
  4. Link Production, Soft Conflicts, Employee Portal, Builder Inventory, Builder Route Catalog, and Developer Tools.
  5. Do not create/edit/delete schedules.
  6. Do not add automatic scheduling.
  7. Do not change payroll, Time Clock rules, POS shifts, reservations, payments, waivers, customer profiles, schedule locking, employee texts, or hard schedule blocking.