One webinar in. A blog for every practice. Two stamps, then publish.
{{ teamPill }}
HOW A RUN WORKS · SEVEN STAGES, TWO STAMPS
{{ ov.num }} · {{ ov.t }}{{ ov.own }}
{{ ov.role }}
{{ ov.help }}
Voice profiles
{{ voSummary }}
One record per practice. This is what the engine is told before it writes a word. A partner's correction belongs here, the day it arrives, not in a notes file.
{{ v.name }}
{{ v.status }}
{{ v.bylineLabel }}{{ v.zoneLabel }}{{ v.score }}
{{ v.oneLine }}
Partner note. {{ v.partnerNote }}
Open. {{ v.todo }}
WHAT THE ENGINE IS TOLD · EDIT TO CORRECT
{{ v.text }}
EVY'S FEEDBACK · STAGED FOR THE 1:1
{{ fbSummary }}
{{ fbRead }}
{{ it.id }}{{ it.state }}{{ it.meta }}
Evy: {{ it.evy }}
Proposed: {{ it.proposal }}
PRACTICE TRACKER · {{ trkRunName }} · WHERE EVERY BLOG STANDS
{{ trkSummary }}
WHICH RUN
{{ trkDriveNote }}
WHOSE LIST
{{ trkWhoNote }}
Practice
Draft → Sam doc → Sam ✓ and Hero → Evy → Published
Bottleneck reads from the Holding column: the stage with the most rows is the one to unblock. "Sam doc" turns on when the proof copy lands in the Drive folder; say "sync Sam's folder" in chat to pull her edits and initials back in.
DRIVE PIPELINE: 1 With Sam → 2 Ready for Evy → 3 Approved to Send → 4 Sent · Done. One move per person, forward only. A post Evy cannot approve in 15 minutes goes to 5 Rework with one line why; click RE-RUN here, Lisa regenerates back into 2, marked RESENT. One trip per post. Nothing ever moves backward to Sam; writer feedback is a team-meeting item.
HANDOFF · EMAIL TO IGOR (ZFORT)
{{ igorEmail }}
Written from current state: only READY TO PUBLISH drafts appear. Evy: export each .docx above, drop the set in the practice folders, paste this into the email. Attachments travel as a shared folder (Outlook blocks the .docx set).