A Blueprint is a versioned package of how an organization runs, captured from a real working account and applied to others.
Configuration travels. Data never does.
Capture the language, the meetings, the scorecard, the chart, Ollie's configuration, the priority templates, and the operating plans of an org that already works. Apply that package to another organization in one pass, with a preview first and an undo after.
Blueprints is a Labs (beta) feature. Switch Blueprints on in Settings, Labs and it appears in your sidebar at /blueprints.
Everything a blueprint carries is configuration: the shape of the company, never its contents.
| Language | Custom section names, core values, and the vocabulary your organization uses. |
| Meetings | Meeting formats and agendas, including the Delta Meeting. |
| Scorecard | KPI definitions, KPI groups, and KPI dependencies. |
| Structure | Teams, the org chart and its seats, and seat responsibilities. |
| Ollie | The configuration of the intelligence layer. |
| Priorities | Priority templates. |
| Processes | Operating plans. |
People. Live KPI values. Meeting history. To-dos. Keys and billing. Seats travel as roles, never as the people sitting in them, so applying a blueprint never moves a person, a number, or a record into someone else's organization.
Four steps, in order. You can stop after any of them.
Turn a working account into a package.
a. Open /blueprints and click Create blueprint.
b. Name it, then pick the source organization. Choose a real working account: a blueprint is only as good as the org it was captured from.
c. Capture. That snapshot becomes version 1, and the detail view breaks it down by category so you can see exactly what it holds.
Preview first. Nothing lands by surprise.
a. Pick a target organization. You can apply to an org you own, one you coach (an active coach grant), or one that sits in your portfolio.
b. Read the preview. Every asset is classified:
| New | Not in the target yet. It will be created. |
| Unchanged | Already identical. Nothing happens. |
| Safe update | The blueprint moved on and the target never touched it. It updates quietly. |
| Edited locally | The target changed it. Your local edit is preserved unless you choose Overwrite. |
| Conflict | Both sides changed it. You decide: keep the local version, or overwrite it. |
c. Confirm. The apply is recorded as a run, and the target organization is now linked to the blueprint.
New version, then push it to everyone on it.
a. When the source organization changes, capture a new version. Each one carries a summary of what was added, changed, and removed since the last.
b. Open Linked orgs to see every organization running the blueprint and which version each is on.
c. Push the new version to many of them at once: one set of choices, one result per organization. Safe updates land, local edits stay put unless you overwrite them.
d. Changed your mind? Undo the run. It restores every asset the apply overwrote. It does not delete the assets the apply created.
A link for one recipient, a template for everyone.
Share link. Permanent, and multi-use. Whoever opens it gets a frozen copy of that version in their Imported tab. A frozen copy has no source organization, so it cannot capture new versions of its own. Revoke the link whenever you like: copies already imported are unaffected.
Template. Publish the blueprint as a template and it becomes visible to every OTP organization in the Templates gallery.
A brand new org. Someone holding your share link can create an entirely new organization straight from the blueprint. They land inside your way of running a company on day one, with nothing to rebuild by hand.
No, not unless you choose to. Anything the client edited is flagged in the preview as edited locally or as a conflict, and their version is kept. It is only replaced if you explicitly pick Overwrite for it.
Nothing. People never travel in a blueprint, and neither do live KPI values, meeting history, to-dos, keys, or billing. Seats travel as roles: the shape of the chart arrives empty, ready for the target organization's own people.
Yes. Every apply is recorded as a run, and a successful run can be undone. The undo restores each asset the apply overwrote, back to exactly what it was. It does not delete the assets the apply created, so anything genuinely new stays until you remove it yourself.
The preview tells you before anything happens. It compares three things: what the blueprint now says, what the client's org currently has, and what the client last received from you. That is how it can tell a safe update (only the blueprint moved) from a local edit (only the client moved) from a conflict (both did), and give you the choice on the ones that matter.
Yes. Send them a share link and they can create a new organization directly from the blueprint, or publish it as a template and it is available to every OTP organization. Either way they start inside your language, your meetings, your scorecard, and your chart, with none of their data touched, because there is no data to touch yet.
Blueprints is live for every organization. Capture the org you already trust, and see how much of a new one you never have to build by hand again.