Once you've set up the Excel + In Parallel pairing and run a pull to refresh Excel from In Parallel, Claude can do more than read. This guide is the advanced playbook for the other directions — seeding a Workspace from a spreadsheet, pushing Excel edits back into In Parallel, and reconciling when both sides have changed — plus a read-only standup and the practices that keep two-way sync safe.

Every move below is a copy-paste prompt. Fill in the placeholders (in <angle brackets>) and send.

Read this first if you only know the pull flow. Use the In Parallel MCP with Excel is deliberately one-way — Claude reads In Parallel and rewrites Excel, and never changes your In Parallel data. This guide adds write-back: prompts that create and update In Parallel records from your spreadsheet. That's more powerful and more consequential — so the golden rule below is not optional.

Excel and In Parallel are both valuable sources of data, and they play complementary roles. In Parallel maintains the shared context — it joins your meetings and keeps up with execution reality (decisions, drift, goals, accountable actions). Excel lets project members update details and add progress notes in a tool they already use. Claude syncs the two — the .xlsx project plan and the shared context In Parallel maintains — so neither has to become the other.

That's what makes this worthwhile from both sides: it keeps the threshold for adopting In Parallel low — minimal change to how your team already works, and Excel keeps working the way it always has — while making the data in your spreadsheet better than ever, refreshed against reality and traceable to its source.

Golden rule: preview before every write. Always ask Claude to show the diff or plan and pause for your approval before it creates or edits In Parallel records — or overwrites Excel. Keep the In Parallel connector's write tools on Needs approval, and read the proposed changes before you say go. Every prompt below is written to enforce this.

Use this when you have an Excel plan but no matching Workspace yet, and you want In Parallel to become the execution source of truth going forward.

"I manage a project plan in Excel — <FILENAME>.xlsx in this folder (sheets: <e.g. Project Plan, Goals, Risks>). I want In Parallel as the execution source of truth and to keep the two in sync via Claude.

Please: (1) read the file and summarise its structure — sheets, columns, the tasks/goals/risks — and show me your understanding before changing anything. (2) List my In Parallel Workspaces and tell me whether a match already exists; if not, propose a Workspace (name, category, sub-projects) from the plan — but don't create anything yet. (3) Propose the mapping: which columns become action items, goals, decisions, and risks/open questions; how status and due dates translate; and how you'll record each row's In Parallel record ID. (4) Ask any clarifying questions, then wait for my approval before creating the Workspace or writing any records.

Once I approve, create the Workspace, seed it from the plan, and add a Mapping sheet capturing each row's In Parallel record ID and the last-synced date."

The Mapping sheet is what makes every later push and reconcile unambiguous — don't skip it.

The read-only direction — In Parallel → Excel — has its own detailed walkthrough. The short version:

"The source of truth is the In Parallel <WORKSPACE> Workspace (and sub-projects <…>). My Excel file <FILENAME>.xlsx is a snapshot from <DATE> and is stale. Pull the latest — execution plan, drift report, goals, action items, decisions, open questions — reconcile, and update the file (statuses, due dates, new workstreams, completed/cancelled items, goals and risks). Highlight changed cells, add a Changelog sheet, and save the result as a new dated file. Ask any scope questions first."

Full flow, screenshots, and the recurring-refresh setup: Use the In Parallel MCP with Excel in Claude.

Use this when you've edited the plan in Excel — added tasks, moved dates, closed work — and want In Parallel to match. Because this writes to your execution layer, the prompt makes Claude show its full plan and wait.

"I've edited <FILENAME>.xlsx since the last sync. Diff it against the In Parallel <WORKSPACE> Workspace and show me — as a table — exactly what you'd change in In Parallel: new action items to create, statuses and due dates to update, items to close or cancel, and goals or decisions to add or revise. For each, give the Excel row and the target In Parallel record (using the Mapping sheet).

Show me the full plan and wait for my approval. Then apply only the approved changes, and update the Mapping sheet's record IDs and last-synced date."

What to check in the preview before you approve:

The hardest case: Excel and In Parallel have both moved since the last sync. Here Claude surfaces conflicts and you decide, rather than one side silently overwriting the other.

"Both <FILENAME>.xlsx and the In Parallel <WORKSPACE> Workspace have changed since the last sync on <DATE>. Reconcile them: for each item show the Excel value vs. the In Parallel value, flag conflicts, and recommend a winner with a one-line reason. Default rule: In Parallel wins on execution status and dates; Excel wins on planning intent and scope. Present this as a table and pause for my decisions before writing to either side.

Then apply my choices to both sides, refresh the Changelog sheet and the Mapping IDs, and save a new dated Excel copy."

Work the conflict table top to bottom, overriding the recommended winner wherever your judgement differs. Nothing is written to In Parallel or Excel until you've decided.

No file changes — just a one-screen read of reality when you need to brief someone fast:

"Give me a one-screen status of the In Parallel <WORKSPACE> Workspace and its sub-projects: overall plan health, overdue action items, stale decisions, top risks and open questions, and anything blocking. No file changes — just the summary, with links."