Team · Stand Up
The daily stand-up, in writing
Each person files one written check-in a day — what they finished, what they are on, how loaded they are, what is blocking them — tagged with the clients it was for. Read the whole team in a minute instead of holding a meeting.
Team · Stand Up
A fifteen-minute stand-up costs a six-person agency an hour and a half a day, and the one thing anybody needed to hear was said in the first ninety seconds. Stand Up in AI Marketing Dashboard turns that meeting into a written check-in each person files on their own clock: what they finished, what they are on today, how loaded they feel, and whether anything is blocking them — tagged with the clients it was for. The team lead opens one screen and knows where the day stands, without pulling six people out of focused work to find out.
A stand-up is a synchronisation problem, not a meeting problem. Stand Up solves it in writing: each person files one check-in per calendar day, whenever their morning actually starts, and the whole team's answers stack up on a single feed that a lead reads in a minute. Nobody waits their turn, nobody repeats themselves for the person who joined late, and a designer who works 7am to 3pm is not dragged into a 10am call to say two sentences.
That matters more in an agency than almost anywhere else, because the people on a stand-up are rarely working on the same thing. Half the room sitting through the other half's client updates is the specific waste the daily meeting creates, and a written feed removes it while keeping the visibility that made the meeting worth having in the first place.
The default form is the classic four: what did you work on last, what are you working on today, how much is on your plate, and are you blocked. An administrator can rewrite all of it — add an intro line, add or remove questions up to twelve, reorder them, and pick the kind each one is: a short text answer, a long one, a 1-5 scale with your own labels at each end, a yes/no flag that asks for detail when the answer is yes, or a fixed set of choices.
Editing the form is an admin decision and stays one, so a check-in means the same thing across the whole agency rather than drifting per team. Marking a question required is how you make sure the answer you built the form for is the answer you get, and the composer will not accept a submission that skips it.
The blocker question is a flag, and a raised flag carries its own explanation: the writer answers yes and then says what is in the way. On the feed those answers are marked, counted in the day's insight band, and reachable through a Blockers-only filter that strips the day down to the people who need something from somebody else.
A client waiting on brand assets, an ad account nobody has been granted access to, a developer blocked on a staging password — these are hours of dead time that usually go unnoticed until a deadline moves. Written the morning they appear and visible to whoever can unblock them, they cost an email instead of a week.
Every check-in carries a workload answer on a scale you label yourself — light through overloaded — and the day's insight band shows the team average beside the submitted count and the blocker count. It is a feeling, not a metric, and it is deliberately kept that way: the number is what the person says about their own week, which is exactly the signal a utilisation report cannot give you.
Read across a fortnight it tells an owner the two things capacity spreadsheets never do — who is heading for burnout while still delivering, and which account is absorbing more of somebody's week than anyone planned. Hours belong in the timesheet; this is the human reading beside them.
A person's day is rarely one account, so a check-in is tagged with every client it touched — including the agency's own internal work, which is a first-class scope rather than an afterthought. The feed then filters to a single client, which turns the stand-up into an account-level record: what moved on this client today, who moved it, and what stopped.
That is the view an account manager takes into a client call, and the view a new lead reads to catch up on an account they have just inherited. It comes free from the tagging people already do when they file the check-in.
The day's band counts how many of the team have filed so far, and a waiting-on row shows the faces of the people who have not — so chasing a stand-up is a glance rather than a message to everybody. When the last person files, the row says so instead of leaving you to count.
Each person also carries a streak of consecutive weekdays with a check-in, with a grace period for the day still in progress so an unfinished morning never resets it. Weekends do not break a streak, because a stand-up is a working-day habit and the counter should agree with that.
Answers are stored as self-describing snapshots: each one keeps the question it was answering and the wording that question had on the day. Change the form next quarter and last quarter's check-ins still read exactly as they were written, rather than being re-labelled by a question nobody was asked. A stand-up you cannot trust to stay true is not a record.
A date pager walks back through the loaded history, the day's feed can be filtered by client or narrowed to blockers, and the view exports to CSV when somebody wants the month in a spreadsheet — for a retrospective, a capacity review or a conversation about scope. Stand Up is deliberately an agency-internal surface: nothing here is ever shared into a client portal.
