1.1 Daily & Weekly Operating Rhythm

Daily non-negotiables

SLA Morning Check-in (9:00 AM)
Availability Check-in (9:00 AM)

Friday standing tasks

Update Operations Dashboard base on new Cycle Planners completed, New Meetings completed, and Time Tracking Data
Send automated reminders to Juan and Sparsh to fill out the Time Tracker Form (reminders are pre-scheduled — verify they fired)
Review Operations Dashboard for any red metrics that need a note in the Friday update

Time allocation target

Activity	Target allocation
System-building (automations, documentation, new SOPs)	70% of total working time
Recurring operations (SLA check-ins, Friday metrics, sidekick)	30% of total working time

If recurring operations start consuming more than 30% of time, that is a signal to automate more. The goal is to protect system-building time. Phil's scorecard enforces this — the time allocation check is a standing monthly review item.

Per-cycle tasks (every 2 weeks)

Publish new cycle planner in #architect-success with HubSpot Project link and Google Doc link
Run the Measurement Check-in at the 4-week mark after any new automation launch
Update Roadmap on items completed base on Cycle Planners
Update the Cycle Automation Log with any completed automation build
Post bi-weekly Loom progress update to #architect-success (when system changes affect architects)

Monthly tasks

Fill out the 30-Day Scorecard with Phil — covers all 7 input metrics and 7 outcome metrics
Review time allocation — confirm the 70/30 split is holding
Schedule the next Flow Session with one architect (every 40–45 days)

1.1 Daily & Weekly Operating Rhythm

What happens every day, every Friday, and every cycle