đ°ď¸ Est. Time: 10 minutes
đŻ Goal: Use five prompts to turn your Monday WIP into an up-to-date Schedule, Priority Board and team update
đ Requirements: Streamtime connected to your AI assistant through the MCP, your meeting notes (ideally from a note-taker connected to your assistant), a Priority Board for your studioâs work, and the permissions listed under each prompt
Monday WIP meetings are where the week gets decided. Then someone has to spend half an hour updating Streamtime so the plan matches what was agreed. Often nobody does, and the team works from a Schedule thatâs out of date by Tuesday.
These are the prompts from our third MCP webinar, where we took a real WIP meeting, handed it to Claude, and got Streamtime up to date in a few minutes. Copy them, swap in your own details, and adjust as you go.
Prefer to watch? The full webinar replay is here.
Each prompt below has a timestamp, so you can skip straight to it.
⨠Still havenât connected to the MCP? You can find the steps to do so here.
Setting the scene: your Monday WIP
Everything in this session happens on one Priority Board, our đĽ Studio WIP board. Think of it as the studioâs wall of work. Jobs move left to right as they progress: Quoted, In Studio, With Client, To be Invoiced and Paid.
Pinned to the board is a run sheet note. Thatâs where we keep our Monday checklist, our board rules and our Top 3 for the week.
Before you start
It works with your permissions. The MCP can only do what you can already do in Streamtime.
Swap anything in [square brackets] for your own details: board names, people, dates.
Pin a run sheet note to your board. Your assistant reads it, so rules like âno work starts on a draft Quoteâ get applied to every change.
Record your WIP in a note-taker your assistant can reach, like Granola. If you donât use one, paste your meeting notes into the chat instead.
Workflow Prompts
Prompt one: read the board before the meeting
âąď¸ Timestamp: 5:40
Before anyone walks into the WIP, it helps to know where things stand. Instead of clicking through every card, your assistant reads each column and checks the Schedule behind it. You get a count by column, any Job that needs attention (like one running well over its planned hours), and who looks busiest over the next two weeks.
Prompt:
Open our [đĽStudio WIP] priority board in Streamtime and give me a quick snapshot before our Monday WIP: whatâs in each column, anything flagged as needing attention, and who looks busiest over the next two weeks.
đ§ Set up:
Use your boardâs exact name, emoji included, so your assistant finds the right one.
Keep your run sheet up to date. Your assistant may point out anything on it thatâs out of date, like a Top 3 item thatâs already done.
Expect leave to show as over capacity. If leave sits on top of work that was already booked, that person can look overloaded. Your assistant canât tell the difference unless you say.
đ Permissions:
Access to the Priority Board: to read its columns, cards and notes. [CHECK] Confirm the permission or board access level.
View Team To Do: so your assistant can see whoâs booked on what.
Prompt two: turn the meeting into a plan
âąď¸ Timestamp: 7:47
The meetingâs happened. Normally the notes go into a doc and the Schedule stays as it was. Instead, hand the meeting straight to your assistant. It pulls out every decision that affects the Schedule or the board, checks each change against whatâs already booked, and flags anything that clashes or breaks a rule on your run sheet. Nothing changes yet, so you can review the plan the way youâd check a colleagueâs work.
Prompt:
Find the Monday WIP meeting for the week of [23 November] in [Granola]. Pull out every decision that affects the schedule or the [Studio WIP] board: who, which job, what moves and when.
Then propose the changes as a table: each to-do to add, move or remove, and each board card to move or update. Check each one against whatâs already booked, and flag anything that clashes or breaks a rule on the boardâs run sheet. Donât change anything yet.
đ§ Set up:
Connect your note-taker (for example Granola) to your AI assistant, or paste your notes in with the prompt.
Name the week, not just the day. If your assistant gets the dates wrong, tell it which week the meeting is for.
Keep âDonât change anything yetâ in the prompt. Itâs your chance to check the plan before anything moves.
Watch for rule flags. In the webinar, Claude flagged that a new Jobâs Quote was still in draft, which broke the run sheet rule. The MCP canât approve Quotes, so a person still does that step.
đ Permissions:
Access to the Priority Board and View Team To Do: to check the proposed changes against the board and the Schedule.
Your note-taker connection doesnât need any Streamtime permissions.
Prompt three: make the changes
âąď¸ Timestamp: 11:20
Happy with the plan? This prompt carries it out: updating To Dos, logging sick days, moving cards and adding the notes you agreed. Itâs the half-hour job that usually happens after the meeting, if it happens at all, and now the Schedule matches the conversation by 10am on Monday.
Prompt:
That looks right. Make the changes in Streamtime: update the to-dos, log [Scout]âs sick days against the [Team Leave & Sickness] job, move the board cards and add the notes we agreed.
đ§ Set up:
Have a Job for leave and sickness, so sick days have somewhere to be logged.
Expect a check-in. With more than 10 changes, your assistant will likely pause and ask you to confirm the batch. Approve it and it carries on.
Check the Schedule and the board afterwards. Open the Schedule for the next two weeks, and check the cards have moved and the notes are there.
đĄ Think about the team behind the changes. Spreading someoneâs work over a couple of days when theyâre back from sick leave stops them walking into a pile-up. Taking time off the Schedule for a paused Job tells people clearly they can stop pushing on it.
đ Permissions:
View Team To Do and Edit Team To Do: to update To Dos and log sick days for your team.
Edit access to the Priority Board: to move cards and add notes. [CHECK] Confirm the permission or board access level.
Prompt four: emoji-code the week
âąď¸ Timestamp: 17:16
The Scheduleâs right now, but a list of To Dos doesnât tell anyone what matters most. A simple emoji code does. Your assistant adds an emoji to the start of each To Doâs description, keeps the existing wording, and adds the key to your run sheet so everyone knows what the emoji mean.
Prompt:
Now emoji-code the to-dos for the jobs we discussed, so the team can see at a glance what comes first. Add the emoji to the start of each to-doâs description and keep the existing wording:
đĽ Hard deadline, has to happen this week
â¸ď¸ Tentative, depends on a client call or approval
⨠New work weâve just won
Then add the key to the run sheet note on the board so everyone knows what they mean.
đ§ Set up:
Choose your own code. Swap the emoji and meanings to suit your studio. Keep it to three or four, so it stays easy to read.
Expect a judgement call. Your assistant may suggest â¸ď¸ for newly won work if its Quote isnât approved yet, which is a fair call.
Check a team memberâs To Do page. The emoji shows at the start of each To Do.
đ Permissions:
View Team To Do and Edit Team To Do: to update To Do descriptions for your team.
Edit access to the Priority Board: to add the key to the run sheet note.
Prompt five: close the loop
âąď¸ Timestamp: 20:05
Before the meeting wraps up, check nobodyâs been pushed over capacity by the changes. This prompt checks the next two weeks, updates the Top 3 on your run sheet, and writes a short person-by-person message for your team channel.
Everyone knows whatâs changed for them without digging through the Schedule.
Prompt:
Last check before we close the meeting. Look at the next two weeks: is anyone over 100% capacity now? Ignore [Sarah and Isobel], their leave is being sorted separately. Then update the âTop 3 this weekâ on the run sheet note, and write a short message I can post in the team channel summarising what changed for each person this week.
đ§ Set up:
Name anyone to leave out, like people whose leave is being handled separately, so they donât cloud the answer.
Keep a âTop 3 this weekâ section in your run sheet note for your assistant to update.
To post the message straight to your team channel, connect Slack or Teams to your assistant as well. Without it, your assistant writes the message in the chat for you to copy.
đ Permissions:
View Team To Do: to check capacity.
Edit access to the Priority Board: to update the run sheet note.
The team message doesnât need any Streamtime permissions.
Related Articles
