Start It on Weekends

The Weekly Build Calendar

Companion to "The Calendar Is Your First Asset."

The blank sample week. Bands run morning to night. Write each recurring block with its name, not "work on business." The taught shape: one Saturday deep block of five to six hours (the engine), one Sunday deep block of four to five hours taken in the morning, two weekday deep blocks of two hours, and one admin batch of two hours in a shallow window. Fifteen to seventeen committed hours, ceiling twenty.

Block key

B = build (deep work: offer, product, route planning)
A = admin batch (bookkeeping, supply orders, messages, invoices, in one sitting)
H = household (protected, given in exchange)
R = recovery (guarded midweek night, kept empty on purpose)

The week

Band	Mon	Tue	Wed	Thu	Fri	Sat	Sun
Early morning
Mid morning
Midday
Afternoon
Early evening
Night

Block totals

Deep blocks (B) planned: count / hours	/ hrs
Admin batch (A): count / hours	/ hrs
Committed total (target 15–17, ceiling 20)	hrs
Recovery night guarded (empty on purpose)
Household blocks promised in exchange (H)

The cancellation rule

A block can move within the week, never vanish. Life will eat a Saturday; a kid gets sick, the job erupts. The block moves to Sunday morning or a weeknight, the same week, before you close the calendar app. Keep the move-or-keep promise for a month and the blocks start feeling as real as the job's meetings.

☐ Recurring beats ad hoc: every block is a named weekly event, same day, same time
☐ The cancellation rule held all week: no block vanished
☐ The calendar is shared: household sees the blocks and knows what they are

The three calendar rules

Recurring beats ad hoc	Blocks are weekly recurring events, same day, same time, with a name
The cancellation rule	Move within the week, never vanish (above)
The calendar is shared	If you live with anyone, they see these blocks, know what they are, and were consulted before the first one went in