Export Audio
iHouseDesign Operations
Field Guide · Tia Lodewyk · June 2026 · Confidential
Operations Field Guide

What ThisRole Actually Requires.

June 2026 · Operations Field Guide · Tia Lodewyk

What went wrong before. What success looks like here. Built from EcoThread, iBrain evidence, and direct communication from Arseni.

Evidence-backed Direct but not punitive Built from EcoThread + iBrain June 2026
Section 0 / Why This Exists

The Explicit
Version.

Every previous operations hire did not fail because they were bad people. They failed because the expectations were never made explicit enough, early enough, and visibly enough. This is the explicit version: what great operations looks like here, what has repeatedly broken, and what Tia needs to own so the company does not depend on Arseni noticing every dropped thread.

Section 1 / The Role

The Role
In Plain Language.

This is not a job description. Every week, Tia will meet ambiguity: missing access, private DMs, unclear owners, half-finished SOPs, silent contractors, client promises nobody has turned into tracked work, and people waiting for Arseni to decide. Success means making those conditions visible, assigned, verified, and harder to repeat.

First 30 Days

Prove you can find the system, run the system, verify access, and identify where work dies when Arseni is not watching.

First 60 Days

Own the weekly pressure rhythm: blocked work, missing owners, private decisions, stale promises, escalation thresholds, and proof of completion.

First 90 Days

Make operations less dependent on memory by turning repeated exceptions into decision trees, checklists, and visible review loops.

Section 2 / Principles

Principles Mapped
To iHD Reality.

15 cards. Each pairs a principle from the local EcoThread corpus with iHouseDesign communication evidence. Thin evidence is flagged instead of dramatized.

01
Ownership and accountability

"I'm not only accountable to protecting the business, protecting the employees, protecting the clients."

Leila Hormozi / How WORLD CLASS Leaders Hold Employees Accountable

Podcast Audio
0:00

What This Means At iHouseDesign

Operations is protection. It protects clients from dropped promises, contractors from unclear instructions, and Arseni from becoming the only person who notices problems.

Real Situation From The Database

The contractor-payment workflow was moved away from Arseni because personal invoice handling had become a business bottleneck. If ops owns the flow, ops owns closure.

"Arseni was personally receiving and paying every contractor invoice. That is a bottleneck that stops new client work. Ops owns this completely." — 2026-06-02, Arseni, team-payments

Who
Arseni, ops, contractors
When
June 2026
Confidence
Verified

What Tia Should Do Differently

Treat every recurring flow as owned until it is completed, verified, recorded, and escalated only when the rules actually require escalation.

02
Ownership and accountability

"Everything needs a DRI."

Dan Martell / Stop Working Hard — 12 Laws of Business

Podcast Audio
0:00

What This Means At iHouseDesign

A process without one named owner becomes everyone's background anxiety and nobody's actual work. Tia should force ownership into the open: one owner, one next step, one due date, one proof of completion.

Real Situation From The Database

In onboarding, Arseni explicitly split ownership: Mujtaba sets up access, Tia confirms it works. That is a DRI-style handoff, not a vague collaboration.

"Mujtaba... your job in onboarding is the setup steps. Tia's job is to confirm everything works." — 2026-06-02, Arseni, IHD onboarding/offboarding

Who
Tia, Mujtaba, Arseni
When
June 2026
Confidence
Verified

What Tia Should Do Differently

When a task touches two people, write the split. Setup owner is not verification owner. Verification owner is not escalation owner unless explicitly assigned.

03
Onboarding and first 90 days

"Expectations plus measurement times feedback."

Leila Hormozi / How I Manage A $100M Team (3 Part Formula)

Podcast Audio
0:00

What This Means At iHouseDesign

Onboarding cannot be "I sent the docs." It has to define what complete means, how we know it is complete, and what happens when the person is blocked.

Real Situation From The Database

Tia named the exact problem in the onboarding thread: onboarding depended too much on memory, assumptions, and reactive fixes. That diagnosis is strong and should become her operating standard.

"Onboarding is currently too dependent on memory, assumptions and reactive fixes instead of a standardized and verified system." — 2026-05-22, Tia, IHD onboarding/offboarding

Who
Tia, Mujtaba, Arseni
When
May–June 2026
Confidence
Verified

What Tia Should Do Differently

For every new person, maintain a visible checklist that tests accounts, channels, SOP acknowledgement, and one real workflow before onboarding can be called complete.

04
Onboarding and first 90 days

"General onboarding and technical onboarding."

Leila Hormozi / Your worst employee is your own fault

Podcast Audio
0:00

What This Means At iHouseDesign

There are two onboarding failures: the person does not understand the company, or the person cannot technically do the work. iHD has repeatedly confused access setup with readiness.

Real Situation From The Database

Arseni challenged Mujtaba on whether onboarding is real leadership if there is no screenshare, no questions, and no check that the person can actually operate.

"If you don't screen-share with Tia... and you don't ask questions... then you're probably not 'leading'." — 2026-06-02, Arseni, IHD onboarding/offboarding

Who
Tia, Mujtaba, Arseni
When
June 2026
Confidence
Verified

What Tia Should Do Differently

Require a live workflow test. If someone cannot show the work on screen, the onboarding is not done.

05
Systems over heroics

"Did I run the system? Did the system work?"

Leila Hormozi / Success Is Hard Until You Build Systems Like This

Podcast Audio
0:00

What This Means At iHouseDesign

A system only matters if people run it when nobody is watching. Documentation that nobody searches for is not an operating system — it is decoration.

Real Situation From The Database

Arseni explicitly said the onboarding-checklist issue was not lack of documentation. The failure was that nobody searched, remembered, or acted on the existing documentation.

"Who is doing keyword searches about onboarding checklists? Nobody... Knowledge is not the bottleneck. Desire is. Desire to search. Desire to act." — 2026-05-28, Arseni, IHD onboarding/offboarding

Who
Tia, Mujtaba, Arseni
When
May 2026
Confidence
Verified

What Tia Should Do Differently

Before asking Arseni, search the known systems, document what you checked, and then either act or escalate with evidence.

06
Systems over heroics

"You need to build systems that outlive you."

Leila Hormozi / Success Is Hard Until You Build Systems Like This

Podcast Audio
0:00

What This Means At iHouseDesign

The goal is not to be indispensable — it is to make the company more capable than before you arrived. A system that requires you to run it every day is not a system. It is a job.

Real Situation From The Database

Arseni's question — "how does iHouseDesign survive when I'm not watching?" — applies equally to every person in the company. Tia should ask the same question about her own role.

"What I need you to solve: how do we make ihousedesign survive when I'm not watching?" — 2026-05-29, Arseni, Tia Lodewyk

Who
Arseni, Tia
When
May 2026
Confidence
Verified

What Tia Should Do Differently

After running any process three times, document it. After documenting it, test whether someone else can run it from the documentation alone.

07
Systems over heroics

"AI systems work when your processes are defined."

Dan Martell / How to Build AI Systems to ACTUALLY Achieve Your Goals

Podcast Audio
0:00

What This Means At iHouseDesign

iHouseDesign runs on AI-assisted ops. That only works when the underlying processes are clear. Undefined workflows produce bad AI outputs and good excuses.

Real Situation From The Database

Arseni described the automation layer — iBrain, Claude, morning digest — as dependent on people actually running the underlying system. The AI catches patterns; the operator must act on them.

"What I cannot automate easily is... pressure... enforcement... escalation... urgency... maintaining momentum... forcing clarity." — 2026-05-23, Arseni, Operational - Tia

Who
Arseni, Tia, ops
When
May 2026
Confidence
Verified

What Tia Should Do Differently

Treat the iBrain digest as a starting point, not a complete picture. The digest surfaces signals — ops converts those into actions, owners, and deadlines.

08
Communication and visibility

"Over-communication is not a weakness. It is a discipline."

Leila Hormozi / Why Communication Is Key

Podcast Audio
0:00

What This Means At iHouseDesign

Arseni should never have to ask "where does this stand?" The answer should be visible before he thinks to ask. That requires outbound updates from ops — not reactive replies.

Real Situation From The Database

Multiple past failures trace back to an assumption that silence means progress. Silence means nothing. Progress means a visible message, a logged action, or a completed task.

"Every stuck invoice, every unsent estimate, every 'hold on let me ask Arseni' — that's the pattern." — 2026-04-23, Arseni, ihouse business

Who
Arseni, ops, contractors
When
April 2026
Confidence
Verified

What Tia Should Do Differently

Log the status of every recurring task before Arseni asks. If it is blocked, say so immediately. If it is complete, send the evidence.

09
Communication and visibility

"Private decisions are public liabilities."

Leila Hormozi / Why Communication Is Key

Podcast Audio
0:00

What This Means At iHouseDesign

DMs and WhatsApp are allowed for speed. But the decision, blocker, approval, or proof of completion must return to the shared record — Telegram thread, Asana task, or SOP. If it is private, it did not happen.

Real Situation From The Database

Work has repeatedly moved through private channels and then the organization could not reconstruct what happened, what was decided, or who owned what next.

"If you're not going into Telegram, Trackabi, or Teams, not flagging inconsistencies, then you're not doing the REAL job." — 2025-10-19, Arseni, Recurring invoicing

Who
Arseni, ops, invoicing team
When
October 2025
Confidence
Verified

What Tia Should Do Differently

Every private decision that affects work gets a summary posted to the shared thread within the same day. Short is fine. Nothing is not.

10
Communication and visibility

"Name the problem before it names you."

Leila Hormozi / Why Communication Is Key

Podcast Audio
0:00

What This Means At iHouseDesign

Fast does not mean cruel. It means patterns are named early enough that the business is not quietly damaged for months.

Real Situation From The Database

The database has direct examples of people being removed or warned after repeated non-closure. It does not always include the full private context, so this is evidence of pattern recognition pressure, not a complete HR history.

"If this pattern continues, we won't be working together." — 2025-10-19, Arseni, Recurring invoicing

Who
Arseni, Asif, invoicing team
When
October 2025–March 2026
Confidence
Plausible — flag for Arseni review

What Tia Should Do Differently

Document patterns early: missed channel, missed deadline, no follow-up, no evidence, repeated rescue. Do not wait until frustration becomes the evidence.

11
Hiring and firing fast

"Accountability is the solution and it doesn't start with them."

Leila Hormozi / If Your Team isn't Performing, Watch This

Podcast Audio
0:00

What This Means At iHouseDesign

Before judging a person, check the system: did they know the expectation, was it measurable, did they receive feedback, and did anyone verify execution?

Real Situation From The Database

The Dropbox cleanup issue involved fired or failed people still having access. That is not just a personnel issue — it is an offboarding system failure.

"I am also removing fired/failed people such as Asif and Ane from the same dropbox folder that NOBODY cares to do ever." — 2026-05-28, Arseni, IHD onboarding/offboarding

Who
Arseni, Tia, Mujtaba
When
May 2026
Confidence
Verified

What Tia Should Do Differently

When someone leaves, verify access removal across Dropbox, email, Asana, Telegram, hosting tools, client assets, and recurring trackers.

12
Operations as a growth function

"That is not what an operator does."

Leila Hormozi / What an Operator REALLY does

Podcast Audio
0:00

What This Means At iHouseDesign

Operations is not more documents, more trackers, or more meetings. Operations is the force that makes the work move when conditions are unclear.

Real Situation From The Database

Arseni told Tia directly that the role is not spreadsheets or organizational theater. The valuable work is pressure, escalation, ambiguity reduction, and throughput protection.

"Your role is NOT 'maintain spreadsheets.' Your role is closer to... operational pressure system... escalation layer... follow-through engine... ambiguity destroyer..." — 2026-05-23, Arseni, Operational - Tia

Who
Arseni, Tia
When
May 2026
Confidence
Verified

What Tia Should Do Differently

Spend less time polishing operating artifacts and more time making stuck work impossible to ignore.

13
Operations as a growth function

"Increase revenue through operations."

Leila Hormozi / 5 EASY hacks...

Podcast Audio
0:00

What This Means At iHouseDesign

Ops is a revenue function when it removes delay, rework, missed invoices, forgotten estimates, and founder bottlenecks.

Real Situation From The Database

Arseni linked invoice handling directly to growth: when he is personally handling payments, new client work is slowed. Payment operations is a growth lever.

"That is a bottleneck that stops new client work." — 2026-06-02, Arseni, team-payments

Who
Arseni, ops, contractors
When
June 2026
Confidence
Verified

What Tia Should Do Differently

Prioritize workflows that unblock sales, production, invoicing, client delivery, and contractor payment. Those are not admin details — they are throughput.

14
Operations as a growth function

"Lack of infrastructure in businesses."

Leila Hormozi / 6 SIMPLE things to go from $1M to $10M

Podcast Audio
0:00

What This Means At iHouseDesign

Infrastructure means the company can still act when Arseni is not present to interpret every exception.

Real Situation From The Database

Arseni described the real bottleneck as the team freezing whenever an exception appears. That is the exact place where Tia's role becomes valuable.

"Your team stops moving the moment they hit an exception they haven't seen before... That's the actual bottleneck." — 2026-04-23, Arseni, ihouse business

Who
Arseni, Mira, production team
When
April 2026
Confidence
Verified

What Tia Should Do Differently

Create decision trees for repeat exceptions: invoices, estimates, client non-response, missing approvals, access blockers, and contractor silence.

15
Ownership and growth

"You are responsible for strategy, executing, leading, managing, holding them accountable."

Leila Hormozi / The secret to scaling your business

Podcast Audio
0:00

What This Means At iHouseDesign

The coordinator role is not passive administration. It is active leadership inside small operational loops.

Real Situation From The Database

Arseni gave Tia the plain-language question behind the whole role: can iHouseDesign survive when he is not watching? That is the success standard.

"What I need you to solve: how do we make ihousedesign survive when I'm not watching?" — 2026-05-29, Arseni, Tia Lodewyk

Who
Arseni, Tia, Mujtaba
When
May 2026
Confidence
Verified

What Tia Should Do Differently

By day 30, identify the five places where work dies without Arseni, assign owners, define next actions, and create a visible weekly follow-through ritual.

Section 3 / Recurring Failures

The Recurring
Failure Patterns.

The DM Problem

Work moves privately, then the organization cannot see what happened. DMs are allowed for speed — but the decision, blocker, file, or proof has to return to the shared record.

The Training-Skip Problem

Someone receives access or a document, but nobody verifies they can perform a real workflow. Training is only complete when the person can show the task on screen or complete a real job.

The Meetings-Instead-of-Systems Problem

A meeting creates clarity once. A system preserves clarity when the same issue repeats. The goal is to leave behind a rule, checklist, owner, or decision tree.

The No-Plan-B Problem

When a person disappears, a file is inaccessible, or a client changes the situation, work freezes. Tia's job is to make exceptions survivable before they become emergencies.

Call-First / Operational Standard

The Call-First
Operational Standard.

This is not escalation. This is the baseline.

The 15-Minute Rule

If a teammate does not respond within 15 to 30 minutes on an active operational topic, call directly on Telegram or Teams. No prior permission required. No "are you available" message first. No second text asking if they saw your first text.

Waiting until the end of the day to chase an urgent logjam is already a failure. If a decision or piece of information is needed today and the channel is silent, the call happens within 30 minutes of the silence. This is not aggression. This is how operations works.

The 15-to-30-minute window applies to active operational topics — a blocked invoice, a missing file, an overdue ticket with a same-day consequence. It does not apply to low-priority questions that can wait.

The Escalation Ladder — No DMs

The escalation ladder has two steps only. There is no DM step.

Step one: post in the relevant public Telegram project channel. Tag the person directly. Make the question visible to everyone in the channel.

Step two: if no response within 15 to 30 minutes, jump to a Microsoft Teams group call. Do not send another message. Do not move to a private DM. Make the call.

Why Teams group calls: Teams is used at iHouseDesign specifically because group calls are easy and everyone on the call can hear the conversation. If Mohammed ignores the call, Mujtaba will hear it and can answer. If Mujtaba doesn't know, Mira might. The group call forces a resolution that no private DM ever can.

Why no DMs: Private DMs hide accountability and delay resolution. When a conversation happens in a DM, nobody else can see whether a question was answered, whether a commitment was made, or whether the person went silent. DMs are reserved for sensitive personal matters only — payment issues, personal emergencies, one-on-one feedback. Operational questions live in public channels and group calls. Always.

Call channel hierarchy: The most natural place to call is Telegram — it is where the work conversation already lives. Second is a Teams group call, especially when multiple people can answer the same question at once. Third is WhatsApp, which is more personal. Some people live on WhatsApp and will respond faster there than anywhere else. Choose the channel the other person actually uses. And in every channel, record the call. Almost mandatory. Recording preserves the decision, the commitment, and the blocker. A recorded call is evidence. An unrecorded call is a conversation.

What a Vague Answer Means

A vague answer is not an answer. Half-answers, "I'll check," "should be fine," and "I think so" without a follow-up date all count as unanswered questions.

A call does not end until one of three things is established:

A specific name: who is responsible for this

A specific date: when it will be done

A specific hard blocker: what exactly is preventing it and who needs to remove it

If Mohammed says "the server is slow" — the call continues. Slow how? Since when? What specifically cannot be done because of it? Is there a workaround? Has Hendra been told? When does it get fixed? The call continues until there is a name, a date, or a hard blocker with a specific owner.

"I'll check and get back to you" without a time attached is a soft non-answer. The response is: "When exactly? I need this by 3pm today." If they cannot commit to a time, that is the blocker and it gets escalated immediately.

Why This Matters at iHouseDesign Specifically

This agency lost months of billable work and thousands of dollars in invoices because contractors were allowed to go silent in text channels without consequence. Mohammed stalled a data extraction project for months citing a server issue. Asif ignored a technical question for five weeks. In both cases, nobody called. Nobody forced a public answer. Nobody made the silence visible.

Text messages allow silence to be invisible. A group call makes silence impossible. When ten people can hear that Mohammed is not answering, Mohammed answers.

Calling people to get clarity is not confrontational. It is the job. If you are not comfortable initiating a two-minute call to find out why an invoice is blocked, you are not yet operating at the level this role requires.

Section 4 / What Arseni Needs

What Arseni
Actually Needs.

The repeated ask is not softer administration. It is visible momentum: pressure without drama, escalation without panic, follow-through without waiting for rescue.

Operational pressure "What I cannot automate easily is... pressure... enforcement... escalation... urgency... maintaining momentum... forcing clarity." — 2026-05-23, Arseni
Visible ownership "Ops owns this completely." — 2026-06-02, Arseni
Survival without founder supervision "How do we make ihousedesign survive when I'm not watching?" — 2026-05-29, Arseni
Search and act before escalation "Knowledge is not the bottleneck. Desire is. Desire to search. Desire to act." — 2026-05-28, Arseni
Exception handling "Every stuck invoice, every unsent estimate, every 'hold on let me ask Arseni' — that's the pattern." — 2026-04-23, Arseni
Section 5 / First 30 Days

Your First
30 Days.

7
Day Seven
  • Verify access to email, Telegram, Asana, Dropbox, accounting references, SOP locations, and core trackers.
  • Run one live onboarding verification on yourself: prove you can find the SOP, complete a real workflow, and leave evidence.
  • Create a visible list of missing accesses, stale documents, and unclear owners. Mark anything not proven as unverified.
14
Day Fourteen
  • Own the onboarding/offboarding checklist: setup owner, verification owner, evidence required, escalation threshold.
  • Pick two recurring workflows and convert them into proof-based weekly routines.
  • Start the DM-to-record habit: any private decision that affects work gets summarized into the shared thread or tracker.
30
Day Thirty
  • Produce a work-dies-here map: five recurring places where work stalls unless Arseni notices.
  • Create decision trees for the top three exception patterns: invoice/estimate ambiguity, missing access, silent contractor follow-up.
  • Run a 30-day review with Arseni using evidence: what was closed, what repeated, what still depends on him.

30-Day Review Matrix

CriterionPassFlag
Escalation and Logjam BreakingInitiated at least one voice or group call per week to force clarity when text communication stalled. Called contractors directly when Telegram messages went unanswered beyond 30 minutes on an active topic. Never accepted a vague answer as a final answer.Relied solely on messaging throughout the trial period. Zero phone calls initiated to chase humans or unblock deliverables. Waited until end of day or longer before escalating a stalled operational topic. Accepted "I'll check" without a committed time.
Source Audio / Podcast Sources

The Podcast
Sources.

Verified MP3 enclosures from the local EcoThread podcast rows. Precise quote-level timestamps should be added in a second pass.

How World Class Leaders Hold Employees Accountable

Leila Hormozi / Build with Leila Hormozi / Ep 21 / used in cards 01 and 11

Stop Working Hard — 12 Laws of Business

Dan Martell / The Martell Method / used in card 02

The Formula to Managing a $100M Team

Leila Hormozi / Build with Leila Hormozi / Ep 4 / used in card 03

Exactly How To Onboard New Hires

Leila Hormozi / Build with Leila Hormozi / Ep 238 / supports onboarding section

How Systems Are The Real Secret to Success

Leila Hormozi / Build with Leila Hormozi / Ep 306 / used in cards 05 and 06

How to Build AI Systems to ACTUALLY Achieve Your Goals

Dan Martell / The Martell Method / used in card 07

Why Communication Is Key

Leila Hormozi / Build with Leila Hormozi / Ep 60 / used in cards 08, 09, 10

What Does An Operator Actually Do?

Leila Hormozi / Build with Leila Hormozi / Ep 51 / used in card 12

Not all extracted principles had a verified podcast MP3. Some were found in YouTube transcript rows or had weak enclosure metadata — no audio was invented for those.

Appendix / Source Audit

Source
Audit.

Local transcript extraction prioritized Leila Hormozi, Alex Hormozi, and Dan Martell because those had strong local source metadata. Andy Frisella, Patrick Lencioni, Gino Wickman, and Sam Carpenter did not return strong local metadata matches in this pass.

ThemeRaw Keyword MatchesPrinciples Selected
Ownership and accountability1,0403
Onboarding and first 90 days1,1913
Systems over heroics8,9713
Communication and visibility3,3353
Hiring and firing fast4123
Operations as a growth function6,4023

Evidence cards matched to iHouseDesign database: 15. Verified: 14. Flagged for Arseni review: 1.

Section 6 / Daily Schedule

Your Day — 2.5 Hours,
15-Minute Blocks.

DISPATCH runs every morning at 8:30am and posts to the Telegram ops channel before your shift starts. It handles all scanning, flagging, and first nudges automatically. Your 2.5 hours begin where DISPATCH stops. You never scan what DISPATCH scans. You act, call, decide, file, and close.

0:00 to 0:15 — READ DISPATCH + BUILD ACTION LIST

Read the morning DISPATCH report posted to the Telegram ops channel. Write your action list for the day in priority order — client emergencies first, escalation calls second, invoice actions third, everything else after. This block has one output: a written list, even if it is three lines. If DISPATCH shows nothing flagged, post "DISPATCH CLEAN" in ops channel and move to Block 5.

0:15 to 0:30 — CLIENT EMERGENCY RESPONSE

Respond to every client emergency DISPATCH flagged in tech@. One message per emergency — acknowledgment only, not a solution. "Saw this, looking into it, update within 4 hours." BCC ar@ihousedesign.com on every reply. If no emergencies — check any open client thread from yesterday without a reply.

0:30 to 0:45 — CONTRACTOR ESCALATION CALLS

Call — not message — any contractor DISPATCH flagged for 48-hour non-response. Fathom on. Two minutes maximum. One question: "You have X overdue tickets. What is your blocker and when will it be resolved?" Log outcome in ops Telegram channel immediately after the call. If no answer — log that too. No follow-up messages. The call is the escalation.

0:45 to 1:00 — ASANA ACTION LAYER

DISPATCH identified overdue tickets and sent first nudges. Your job is what requires judgment. For every ticket DISPATCH reopened due to missing Dropbox proof — check if the contractor responded with a file. If yes — verify the file exists and follows the naming convention: [number]. [status] - [Client Name] - [description].pdf. Close the ticket and note it in ops channel. If no response — add contractor to tomorrow's escalation call list.

1:00 to 1:15 — DD TELEGRAM GROUP SCAN

Open in order: DD support with David, DD support without David, DD design with David, DD design without David, DD newsletters with David, DD newsletters without David. Last 24 hours only. One goal: find any client request or maintenance task not yet in Asana or your personal maintenance log. If found — add it immediately. If nothing found — three minutes, move on. Do not read old history. 24 hours only.

1:15 to 1:30 — INVOICE WORK

First ten minutes: variable invoice items only. Standard DD items are DISPATCH-verified. Your job: maintenance hours, custom design pricing, anything not on the fixed rate card. If you can determine hours yourself — add them and flag invoice as ready for Arseni review. If you need approval — one message only: "DD May invoice ready. Maintenance hours question: [task list] = [X] hours. Confirm or adjust." Last five minutes: file any invoice sent in the last 24 hours. Correct naming convention: [number]. [paid/sent/draft] - [Client Name] - [description].pdf. Correct folder: Dropbox/INVOICES/INVOICES. Post screenshot of filed location to ops channel. This closes the loop.

1:30 to 1:45 — EXPENSE EXCEPTION ACTIONS

Review DISPATCH expense anomaly flags. For each flagged item — one decision: expected and you can document why, needs one question to Mujtaba or Hendra, or needs Arseni. One message per anomaly maximum. You do not investigate yourself — you route it and log that you routed it. If no anomalies — check the known subscription list and confirm any subscription not billed this month was not accidentally cancelled.

1:45 to 2:00 — CONTRACTOR DELIVERABLE SPOT CHECK

One contractor per day, rotating. One question only: did the hours logged yesterday produce something visible? Check one source — Dropbox, Asana comment, or Telegram message. If yes — note it and move on. If no visible output — add to private ops notes with date and hours billed. After four consecutive days of no visible output from one contractor — flag to Arseni with the evidence log. Build the pattern before escalating.

2:00 to 2:15 — OPEN LOOP CLOSER

Check your carry-over list from yesterday. Every item promised and not delivered either gets closed in this block or gets a documented reason why it is blocked and who is responsible for unblocking it. Nothing carries over a second day without a written reason. If no carry-overs — use this block for any outstanding task from your 30-day checklist.

2:15 to 2:30 — BRIEF — DAILY SUMMARY

Post to Telegram ops channel. Fixed format — do not improvise it:

DATE: [date]
DISPATCH FLAGS ACTED ON: [list or "none"]
CALLS MADE: [contractor — outcome]
INVOICES FILED: [number — client — Dropbox path confirmed Y/N]
ESCALATED TO ARSENI: [list or "none"]
BLOCKED: [item — reason — who unblocks]
ONE THING I NOTICED: [one observation not in DISPATCH report]

The last line is mandatory. It is the only proof you are thinking, not just processing. If that line is empty — the day was empty.