Playbooks
A playbook template is a reusable, ordered set of steps, such as everything a product launch needs and when each piece is due. When you run one, Marcora creates a running playbook: one dated step for each template step, on a page where your team can write, run and tick off the work.
Before You Start
- Find it under Content > Playbooks.
- Playbooks are for Admins and Creators. Collaborators don't see Playbooks.
- Running a playbook template doesn't use Studio Credits. Writing its content steps and running its action steps do. See Pricing.
- Action steps work in the step owner's connected apps, so connect them first. See Connected Apps.
Find Your Playbooks
The cards at the top of Playbooks switch between three lists. The page opens on Running when your team has a running playbook, and on Templates when it doesn't.
- Running: playbooks still in progress. Each row shows its template, its anchor date, N of M steps done, the Next up step with its due date and owner, and how many steps are overdue. Select a row to open it.
- Finished: playbooks where every step is done or dismissed. A row says Complete, or Stopped if any step was dismissed.
- Templates: your playbook templates. Each row has N running, Run playbook (once the template has steps) and a More actions menu (three dots) on its right. They're always shown, with no need to point at the row. On a phone they sit below the template's name. Select N running to see only that template's running playbooks. Select Clear filter to see them all again.
Create a Playbook Template
- Open Content, then select the Playbooks tab.
- Select + New template. The editor opens with Untitled playbook template.
- Enter a name in Playbook name, and optionally a description.
- Optionally, fill in the settings: What the anchor date is (such as launch day), a Default project, and Variables that are filled in once each time the template is run. Type a variable in any step's title, prompt or instruction, like {Feature name}. In a content step's prompt you can also select { } Insert variable, or + New variable… to add one.
- Select + Add step, and choose its Kind:
- Content: Marcora writes it. Describe what Marcora should create in the prompt box. Below it, you can choose a Blueprint and targeting, and select Collections to pick context collections. These are defaults that each run starts with and can change. To give the other content steps the same targeting and collections, select Copy this step's targeting & collections to other steps.
- Action: the step's owner asks Marcora to carry out an instruction using their connected apps. Type the instruction in the Ask Marcora box, such as "Save the launch post to my Launch folder in Google Drive".
- Checklist: a person ticks it off.
- Give the step a Step name. Under Due, choose No date, Before anchor, On anchor date or After anchor, and enter the number of days. Once the anchor has a name, these options use it, such as Before launch day. To add a time of day, select the clock icon next to the date.
- Optionally, set an Owner, mark it Optional step or Off by default, or select the earlier steps it Builds on. The owner can be a teammate, or a name you type, such as an agent or someone outside your team. An action step's owner must be a teammate. A content step can also Use this running playbook as a source (see How It Works).
- Repeat for each step. Drag steps to reorder them.
- Choose Private or Team, then select Save. Nothing is saved until you do.
To keep each running playbook's content together, choose Each use starts a new project under Default project. You can enter a Project name pattern, such as {Feature name} launch. If you leave it blank, the project takes the running playbook's name.
To preview due dates, enter a date under Preview dates as if the anchor date were. If you change it, it's saved as the template's default anchor date. You can still pick a different date each time you run it.
Save Plans as a Playbook Template
- On the Plans tab's board, select Add to playbook template.
- Select the plan cards you want to include.
- Select Add N to playbook, where N is the number you selected.
- Choose a playbook template, or select Create new playbook template.
Run a Playbook
- On the Templates list, select Run playbook on the template's row. You can also open the template and select Run playbook. It appears once the template has steps.
- Optional: pick the anchor date. Each step's dates are set from it.
- Optional: choose a Project. The template's default project is filled in for you. To put this running playbook's content in a new project, select Create a new project… and check the New project name. It's already selected if the template starts a new project each time.
- Fill in any variables under FILL IN ONCE.
- Optional: describe it in What's this running playbook about? Every content step is written with it.
- Clear any optional steps you want to skip, and select any steps marked off by default that you want to include.
- Optional: check each content step's settings for this run. Select Edit prompt to change its prompt (Reset to template undoes the change), or change its owner, blueprint, targeting or Collections. To give the other content steps one step's targeting and collections, select Copy this step's targeting & collections to other steps. If some already have their own, choose Replace on all N or Only fill the N empty steps in the panel that opens below it. None of this changes the template.
- Select Run playbook · N steps, where N is the number of steps you kept.
The running playbook's page opens. Marcora names it after the template and the anchor date's month, or the current month if there's no anchor date. To rename it, select the name. Each step is also a plan on your Plans board, labelled with the template's and the running playbook's names. If you created a project, the page links to it next to Project:.
Work Through a Running Playbook
The running playbook's page shows its status, anchor date, project and topic, and progress as N of M steps complete. Steps, in order lists every step with its date and status. Select Content only to list just the content steps.
Each content step shows the first lines of its piece. Select Show full piece, or Expand all for every step. Select Open in editor to edit a finished piece, or Open step to write one now.
- Write every content step at once: select Generate all. Marcora writes the content steps that are left, waiting for any step a piece builds on. It skips steps that are dismissed or already written, and steps you neither created nor are assigned. Running a playbook creates all of its steps, so if you ran it, Generate all writes your teammates' steps too. It never runs action or checklist steps. You can leave the page while it runs, or select Stop after current step. If it stops before everything is written, a banner says how many steps were generated and how many weren't, such as Stopped at your request. 2 generated, 1 not started.
- Run an action step: the step's owner selects Run. The Ask Marcora window shows the instruction. Select Run again to start a Marcora conversation that carries it out. Anyone else who can see the step selects See instruction to read it. Only the owner can run it.
- Tick off a checklist step: select Mark done.
- Record a result on a checklist step: select Mark done with a link or note (or Add a link or note once it's done). Enter a Result link, a Note or both, then select Save and mark done. The step then shows Open result → and your note.
Once an action step's conversation has started, its button says Open Marcora, and the window offers Open Marcora conversation.
To change the topic, select Edit in What this running playbook is about. Select Ask Marcora to adjust this running playbook to have Marcora change its plans, such as their due dates or titles. Every running playbook made from a template is listed on that template's Running playbook history tab.
Use an Existing Document for a Step
If you already have the piece a content step needs, use it instead of having Marcora write it.
- On the running playbook's page, find the content step and select Use an existing document.
- Search for the document, or pick it from the list.
- Select Use this document.
The document becomes the step's content, as if Marcora had written it. Nothing is generated. To swap it later, select Use a different document on the step, pick another, then select Replace the document. The document it replaces stays in your library.
The list offers documents only, not context items or uploaded files. Only the step's owner, or the person who created it, can give it a document. It isn't offered on a dismissed step or while Marcora is writing the step.
Approve an Action Step's Changes
Marcora asks the step's owner before it makes a change in a connected app. Reading doesn't need approval, and nor does saving an email draft in your own mailbox.
- In the conversation, find the Approve this action card. The conversation's status shows Awaiting approval.
- Check the app, the account and each detail Marcora will send.
- Select Approve & continue, or select Decline.
After you approve, Marcora carries out that exact request. Once the result is confirmed, Marcora marks the step done with a link to the result and a short note. If you decline, nothing is sent and the step stays open. An approval expires after 15 minutes.
Do a Step on Its Date
Content and action steps can start by themselves. A content step has an Auto-draft on start date switch and a Start setting: Marcora starts writing the draft that many calendar days before the due date, at the step's due time. It's 3 days unless you change it, and can be 0 to 365. An action step has a Do it on its date switch: Marcora starts its Marcora conversation at the due date and time. Marcora checks for due steps every minute, so a step whose time has already passed starts at the next check.
- The switches appear in the template editor, the Run “
” window, the Add a step window, and on each step of a running playbook. - Only the step's owner can turn one on. In the template editor and the Run “
” window, that includes a step with no owner. In the template editor, the switch can't be turned on for a step someone else owns. On a running playbook, anyone else sees "Only this step's owner can enable doing it on its date." - In a template, the switch is a preference. It carries over only when the step's owner runs the template. Choosing a different owner for a step in the Run “
” window turns its switch off. - Under the switch, the step shows its time (9 AM if none is set) and the time zone captured when you turn it on. A step with no date shows No date: not armed.
- Starting a step this way uses Studio Credits.
- An action step started on its date still waits for your approval before any change in your connected apps. Select Open existing Marcora conversation on the step to approve it. An approval expires after 15 minutes, so if you miss it, ask Marcora in the conversation to prepare it again.
- While it waits, the step shows Waiting for generation to start and the time zone. Once it's tried, it shows Started, or Could not start, Could not confirm or Skipped with the reason.
- A content step waits for the content steps it Builds on. If an earlier step's draft isn't ready, failed or was dismissed, the step shows Waiting with the reason, such as "Waiting for “Messaging doc”: its draft failed. Regenerate it, or remove it from Builds on." Waiting doesn't use up its try. It starts by itself once the earlier draft is ready, or once you remove that step from Builds on. If it builds on a checklist or action step that isn't done, it waits too, but you start it yourself once that step is done.
- If you turn the switch on after a content step's due date has passed, the step shows Overdue and doesn't start by itself. Select Generate now to write it. A step that is waiting for an earlier step doesn't turn overdue.
- Each step is tried once. Changing the switch or the date afterwards doesn't start it again. If it didn't start, check for any work it already did, then start it yourself with Open step, Generate all or Run. Once an action has run, the step shows "Started. Changing this switch or date will not start another attempt." If you then try to turn the switch on again, it says "This action has already run. Date scheduling cannot start another attempt."
- It's skipped if the step no longer qualifies at its time: for example, it's done, dismissed or already has a draft, or its owner is no longer an Admin or Creator on the team. The step then shows Skipped with the reason, such as "A draft is already linked to this step."
- Turning the switch off before the step starts cancels it, and the step shows Turned off. Reassigning the step turns it off too. If the step's creator edits it, it shows Settings changed, and its owner has to turn it on again. The owner can edit their own step without turning it off.
Choose Due-Today Reminders
On days you own unfinished plans or playbook steps that are due, Marcora reminds you in two ways: a Due today item in your notification bell for each one, and one email around 9 AM in your saved time zone (UTC if none is set).
- Open the account menu (your avatar, top right) and select Notification Settings.
- Under Due-today reminders, select or clear Email me what's due today.
To change the emails for one running playbook, open it and choose Use default (it shows your default, such as Use default (on)), On for this playbook or Off for this playbook under Due-today email reminders. Each person's own Notification Settings still apply.
- The email's subject says how many items are due, such as 1 item due today. It lists each one, grouped by team, with a link to the plan and its time if it has one.
- To stop the emails from the email itself, select Turn off due-today emails.
- The email also needs your main Email Notifications setting on. You get at most one a day.
- Bell items appear even with the email turned off. Select one to open the plan.
- A step owned by a typed name, rather than a teammate, isn't included.
Add a Step to a Running Playbook
- On the running playbook's page, select + Add step below Steps, in order. To add it after a particular step, point at that step in the list, or press Tab to reach the button below it, and select + Add step here. On a touch screen it's always shown, faintly. On a phone it isn't shown: use + Add step and choose where it goes under Position.
- Under Kind, choose Content, Action or Checklist.
- Enter a Step name.
- Fill in what the kind needs: a Generation prompt and an optional Blueprint for a content step, or the Ask Marcora instruction for an action step.
- Check the Position: At the end, or after a step you choose.
- Optionally, set the Due date, the Owner, the earlier steps it Builds on, Optional step, Use this running playbook as a source, or the step's automatic start (Auto-draft on start date or Do it on its date).
- Select Add step.
The step joins this running playbook only. The playbook template stays as it is. Any variable in the step, like {Feature name}, is filled in with this running playbook's value. The new step counts toward its progress. If it's a content step, Generate all writes it like any other.
How It Works
- A running playbook's status is Not started, In process or Complete. A content step counts as done once its piece is produced. An action or checklist step counts once it's done. While a playbook is running, dismissed steps drop out of the count. If every step is done or dismissed and at least one was dismissed, its status is Stopped.
- Plans from a playbook start in Accepted, because running it is the decision to make them.
- A step that builds on an earlier one waits for it: Marcora writes it once that step is done.
- An action step's conversation reads the step's plan and the earlier steps it builds on.
- A content step with Use this running playbook as a source is written with the running playbook's current schedule: each step's title, owner, dates and status, plus its topic and variables. It doesn't get other steps' documents. Use Builds on for those. Private steps are left out, and the document ends by saying how many, with a link to the running playbook and the time it was written. It doesn't update by itself, so write the step again to refresh it.
- A project made for a running playbook starts with you as its only member. It's private if the template is private.
- A step marked Off by default is optional and starts unselected when someone runs the template.
- A time of day is saved and shown exactly as entered, such as Mon, Nov 24 · 9:00 AM. It isn't converted between time zones.
- An owner name you type is offered again on your team's other steps.
- Playbook templates made before steps had kinds still open. Their steps are content steps.
- Team templates are visible to your team. Any Admin or Creator who can see one can edit or run it. Only the creator changes its visibility.
- To retire a template, select Archive on its page, and restore it from View archived. To delete one, open the More actions menu on its row and select Delete playbook template. Plans already created from it stay, and its running playbooks are labelled Deleted template.
Troubleshooting
Generate all stopped and the banner offers Get more credits. Your team ran out of Studio Credits. Add credits, then select Generate all again to continue with the steps that are left.
Generate all is unavailable. Every content step in the running playbook has been written or dismissed.
Generate all runs, but some steps aren't written. It writes only the steps you created or are assigned. Generate all stays available while any content step is unwritten, and its count includes steps you can't write. If you ran the playbook, you created every step, so it writes them all.
While Generate all runs, a step says Waiting for step N. It builds on an earlier step, and Marcora writes it once that step is written.
"Edit and save this step as an instruction for Marcora before running it." The action step was set up before action steps took an instruction, so Run is unavailable. Open its template, check the step's Ask Marcora box and select Save, so later running playbooks can run it. In this running playbook, add a new action step with + Add step.
Approve & continue is unavailable, with "Available when Marcora pauses for your approval." Marcora is still working. Wait until it pauses, then approve.
"This approval expired. Ask Marcora to prepare it again." More than 15 minutes passed. Ask Marcora in the conversation to prepare the change again.
The playbooks list shows "Couldn't load playbooks". Select Try again.
"This step belongs to someone else, so only they can give it a document." Only the step's owner or creator can use an existing document for it. Ask them, or have the step reassigned to you.
"That document is no longer available to you. Pick another." The document was deleted, or you no longer have access to it.
Opening an action step shows "This step isn't available to you." The step was removed, or it isn't shared with you.
Related
- Content Plans: the board where a running playbook's plans appear
- Marcora Agent: the conversations where action steps run
- Blueprints: the templates a content step can use
- Connected Apps: the apps action steps work in
- The
create_playbookandinstantiate_playbookMCP tools do the same jobs from Claude or ChatGPT.