diff --git a/tasks/client-followup.md b/tasks/client-followup.md
index d4de8f3..d2b0590 100644
--- a/tasks/client-followup.md
+++ b/tasks/client-followup.md
@@ -1,24 +1,43 @@
 # Client & Invoice Follow-up
 
-**Goal:** Keep money flowing and clients informed without wasting time on non-ready items.
+**Goal:** Simple calendar-based system to manage client check-ins, reminders, and followups.
+
+## Core Policy
+
+**Invoices must be sent AND paid before clients receive their devices back.** No exceptions.
+
+## Implementation
+
+Calendar events and reminders handle everything:
+- Set reminder when invoice is sent
+- Set followup event if unpaid after 3 days
+- Set pickup notification event when repair complete (only after payment confirmed)
+- Set quote followup reminder (one-time, 2 days after sending)
+
+## Integration (Pending)
+
+Once the repair tracker is back online:
+- Link invoice numbers to repair tracker events
+- Link shipping tracking numbers to repair tracker events
+- Calendar events reference tracker IDs for easy lookup
 
 ## Priority Matrix
 
-| Status | Action | Frequency |
-|--------|--------|-----------|
-| Invoice sent, unpaid 3+ days | Follow up | Daily check |
-| Repair complete, awaiting pickup | Notify client | Same day |
-| Quote sent, no response 2+ days | Follow up once | Then wait |
-| Repair in progress | No action needed | Skip |
-| Waiting on parts | No action until parts arrive | Skip |
+| Status | Action | Calendar Event |
+|--------|--------|----------------|
+| Invoice sent, unpaid 3+ days | Follow up | Reminder triggers |
+| Invoice paid, repair complete | Notify for pickup | Same-day event |
+| Quote sent, no response 2+ days | Follow up once | One-time reminder |
+| Repair in progress | No action needed | No event |
+| Waiting on parts | No action until parts arrive | No event |
 
 ## Daily Workflow
 
 ### Morning (10-15 min)
-1. Check for unpaid invoices past 3 days
-2. Check for completed repairs awaiting pickup
-3. Check for unanswered quotes past 2 days
-4. Ignore anything in-progress or waiting on parts
+1. Check calendar for today's followup events
+2. Process any invoice payment reminders
+3. Send pickup notifications (payment confirmed only)
+4. Handle quote followups
 
 ### Follow-up Templates
 
@@ -35,7 +54,7 @@ Thanks,
 Motherboard Repair CA
 ```
 
-#### Repair Complete - Pickup
+#### Repair Complete - Pickup (send ONLY after payment confirmed)
 ```
 Hi [NAME],
 
@@ -59,6 +78,8 @@ Motherboard Repair CA
 ```
 
 ## What NOT to Do
+- **Don't release devices until invoice is paid** - no exceptions
+- Don't send pickup notifications before payment is confirmed
 - Don't follow up on quotes more than once
 - Don't check on repairs still in progress
 - Don't bug clients about parts delays (that's our problem, not theirs)
@@ -66,9 +87,10 @@ Motherboard Repair CA
 
 ## Escalation
 Flag these for immediate attention:
-- Invoice unpaid 7+ days
+- Invoice unpaid 7+ days (device held until paid)
+- Client requesting device before payment (explain policy)
 - Client complaint or dispute
-- Repair complete but no pickup after 14 days
+- Repair complete + paid but no pickup after 14 days
 - Any angry/urgent messages
 
 ## Weekly Metrics to Track
diff --git a/tasks/reddit-monitoring.md b/tasks/reddit-monitoring.md
index 002fa2c..a0ef656 100644
--- a/tasks/reddit-monitoring.md
+++ b/tasks/reddit-monitoring.md
@@ -5,7 +5,7 @@
 ## Target Subreddits
 Refer to the subreddit tracking list in the adjacent repository - do not duplicate here. https://git.nixc.us/Nixius/rss-feedmonitor
 
-## Services We Offer (Keywords)
+## Some Services We Offer (Keywords)
 Watch for posts related to:
 
 **GPU Repairs**
diff --git a/tasks/video-editing.md b/tasks/video-editing.md
new file mode 100644
index 0000000..370890d
--- /dev/null
+++ b/tasks/video-editing.md
@@ -0,0 +1,87 @@
+# Repair Video Editing
+
+**Goal:** Cut and edit long repair videos into polished content with captions and AI-generated background music.
+
+**Frequency:** As-needed (per video batch)
+
+**Time Budget:** Varies by video length
+
+## Core Workflow
+
+### 1. Import & Review
+- Import raw repair footage
+- Watch through at 2x or more speed, note key timestamps
+- Identify: intro point, key repair steps, completion/test moment
+- Flag any unusable sections (bad audio, out of focus, etc.)
+
+### 2. Rough Cut
+- Remove dead time, searching for tools, phone interruptions
+- Cut repetitive sections (multiple screws, waiting for heat, etc.)
+- Keep essential steps intact for educational value
+- Target length: depends on platform (short-form vs long-form)
+
+### 3. Captions (If Needed)
+- Auto-generate captions using transcription tool
+- Review and correct technical terms (capacitor, reflow, BGA, etc.)
+- Style: clean, readable font, contrasting background
+- Position: lower third, avoid covering repair work
+
+### 4. AI Music (If Needed)
+- Generate background music that fits repair content vibe
+- Keep it subtle - shouldn't compete with narration/sound effects
+- Match energy to video pace (chill for detailed work, upbeat for time-lapse)
+- Ensure royalty-free/cleared for commercial use
+
+### 5. Export
+- Format: H.264/H.265 for compatibility, or platform-specific
+- Resolution: Match source (typically 1080p or 4K)
+- Audio: Balanced levels between voice, music, repair sounds
+
+## Tools
+
+These are only suggested and not asked for by name the AI generated this list.
+
+| Purpose | Tool Options |
+|---------|-------------|
+| Editing | DaVinci Resolve, Premiere, CapCut |
+| Captions | Built-in auto-caption, Whisper, CapCut |
+| AI Music | Suno, Udio, Mubert, Soundraw |
+| Export | Native to editor |
+
+## Platform Considerations
+
+### Long-form (YouTube)
+- Keep educational value, show full process
+- Chapters/timestamps for navigation
+- Detailed captions help accessibility & SEO
+
+### Short-form (TikTok, Reels, Shorts)
+- Under 60-90 seconds
+- Punch in tight on repair work
+- Bold captions, faster pacing
+- Hook in first 2-3 seconds
+
+## Quality Checklist
+
+- [ ] No awkward jump cuts
+- [ ] Audio levels consistent throughout
+- [ ] Captions accurate (especially technical terms)
+- [ ] Music doesn't overpower other audio
+- [ ] Key steps clearly visible
+- [ ] Satisfying before/after or test moment included
+- [ ] No accidental personal info visible (client data, phone numbers)
+
+## File Organization
+
+```
+/videos/
+  /raw/          # Original footage
+  /projects/     # Editor project files
+  /exports/      # Final rendered videos
+  /assets/       # Music, graphics, templates
+```
+
+## Notes
+- Keep raw footage until video is published and performing well this can just be written into the #media channel in the Discord
+- Save project files for potential re-edits if possible not super required.
+- Possibly Build a library of approved AI music tracks for consistency