The Pulse Library

The pulse library

Every organisation starts with the three core pulses. The pulse library sits alongside them: a set of ready-made, locked-question pulses you add only when they fit your stack. An agentic coding pulse is useful signal for a software team and noise for a marketing team, so nothing from the library is added automatically. You choose.

This article covers how the Pulses page is organised, what's in the library, how to add or clone a pulse, the two kinds of pulse it holds (recurring and one-off), which plans include the library, and what happens when a pulse's run is over.

Three tabs: My pulses, Library, Archive

The Pulses page has three tabs:

My pulses is the pulses your team runs now: the core pulses, anything you've added from the library, and your own custom pulses. Pause, reschedule or clone from here.
Library is where new pulses come from: every ready-made pulse, plus the starting points for building your own. The Add a pulse button on My pulses brings you here.
Archive holds pulses that have finished their run, with their history intact. More on that below.

What's in the library

Six ready-made pulses, each with a distinct job. Two run on a cadence, four are one-offs.

Recurring:

Pulse	Job	Default cadence
The Agentic Coding Pulse	Is delegating work to this tool a net win, after checking time?	Daily
The AI Adoption Sentiment Pulse	How does AI adoption feel across the organisation?	Monthly

The Agentic Coding Pulse asks about today, so it arrives daily. Its questions and its cadence go together: a question about today asked once a week would collect one day in seven and report about a fifth of the hours actually saved. You can still change the cadence, and if you do, read the reported hours with that in mind.

Discovery (one-offs):

Pulse	Job
The Current AI Use Pulse	What are people already using, and does it help?
The AI Risk Pulse	What do people understand about the rules, and what has gone into public tools?
The AI Opportunity Pulse	Where does the repetitive work sit, and what would people hand over?
The Agent & Automation Pulse	Which of that work could software take on?

Your three core pulses appear in the library too, marked Included, so the whole catalogue is in one place. Category chips (Discovery, Operational, Agentic, Sentiment, Custom) and a search box narrow the list, and Preview on any card shows every question exactly as your team would see it, before you commit to anything.

Two pulses are parked, so their cards don't appear and they can't be added:

The Comparison Pulse, which put two tools head to head. It was the one pulse you couldn't have built yourself in the editor, and that made it the odd one out in a page that's meant to show you what good pulses look like. It comes back once it can be built the same way everything else is.
The Agent Review, which asked how often you had to step in and fix an agent's work. The questions are right; what's missing sits underneath them. It's asked once per agent, and an organisation can be running hundreds of agents created by people all over the business, with no way to tell one from another. "The invoice one" isn't something a person can answer a survey about, so the answers wouldn't be readable. It comes back with agent tracking.

Organisations that added either before it was parked keep it, with its report and its history intact.

The library will grow. If there's a pulse you wish existed, tell us on the feature-request board.

Two kinds of pulse

Everything in the library is one of two shapes, and the difference decides what the card, the builder and the report look like.

Recurring pulses have a cadence. They come round on a schedule, the same person answers repeatedly, and the value is the trend.
One-offs have no cadence. They open, each person answers once, and they close. The card says One-off where a recurring pulse names its cadence ("Daily", "Monthly"), and once it's open it also shows how far along it is ("62% of your team have answered").

The four Discovery pulses are the one-offs. In the builder they get When this runs in place of the cadence controls: a closing date, a completion target, and whether people may leave required questions blank. Switching one on is what starts the asking and starts the clock.

They close on whichever comes first, the date or the target, and you can also Close now from the pulse's row on My pulses. A closed one-off is a paused pulse: nothing more is delivered, the answers stay readable in Reports, and archiving and deleting work exactly as they do for anything else. Reopen on the same row starts the asking again, and anyone who already answered isn't asked twice.

The full walkthrough, including what people see and how to read the Baseline Report, is in taking your AI baseline.

How to add one

Open the Pulses page and switch to the Library tab (or hit Add a pulse on My pulses).
Preview the card you're interested in, then hit Add.
None of them need anything set up in advance, including the Discovery four, which reach everyone whether or not they have a tool assigned.
The pulse is created paused and opens in the builder. Review the schedule (or, on a one-off, the closing date and target), adjust it if you like, then switch it on. Nothing reaches your team until you do.

Each library pulse can be added once per organisation.

Clone to edit

Library cards also offer Clone to edit: it creates your own editable copy as a custom pulse and opens it in the builder, where the questions, name and everything else are yours to change. The same option sits on your existing pulses in My pulses. A clone of a one-off is still a one-off, with its own closing date and target to set.

The library's entry cards cover the two ways to start from nothing: Create a custom pulse from a blank page, or Describe the pulse you want and get a draft you edit before you save it (see building a custom pulse).

A clone is a new pulse with its own reports; the original keeps collecting under its own name.

Which plans include the library

The library is a Pro feature. Standard includes the three core pulses; every library pulse, custom pulses, cloning and the Archive come with Pro. Where something needs Pro you'll see a small Pro chip beside it: on Standard the chip marks what's locked, and during a free trial (trials run on Pro) it labels which plan a feature belongs to, so nothing surprises you when the trial ends.

You can still browse the whole library on Standard. Every card stays visible with its preview, so you can see what's there before deciding.

If a Pro organisation moves to Standard, nothing is deleted: archived pulses and their responses are kept, and reports for past periods still read from them. The Library and Archive tabs lock, and Pro pulses stop delivering, until your plan includes them again. If you need something from the Archive in the meantime, contact support and we'll sort it out with you.

Questions are locked. The schedule is yours.

Library pulses work exactly like core pulses: the questions are locked, and delivery is yours to run.

Why locked? Because the reports depend on it. The net-time calculation, the keep-or-kill share and every gauge read specific answers to specific questions. Reworded questions would quietly break the comparison between this month and last, or between this baseline and the one you take in six months. Locked wording is what makes the numbers dependable over time.

What you can change: the cadence (or, on a one-off, the closing date, the completion target and whether questions can be skipped), the description, the delivery window, and the header colour. A Reset to default link takes the schedule back to the recommended cadence. The name stays as it is: reports and plan rules recognise a pulse by its name, so included and library pulses keep theirs. If you want a different name or different questions entirely, Clone to edit gives you a copy that's fully yours (Pro), or Pro plans can build a custom pulse from blank.

Retiring a pulse: the Archive

Pulses wind down. Their data shouldn't vanish with them, so the lifecycle is deliberate:

An active pulse can't be removed. If you archive one, the same confirmation pauses it and archives it in one step.
A closed one-off is already paused, so it archives without a second step. Reopen it first if you want more answers; unarchive brings it back closed, ready to reopen.
A paused pulse with no responses can be deleted outright. There's nothing to lose.
A paused pulse with responses moves to the Archive: it stops delivering, leaves My pulses, and its responses stay readable in Reports (archived pulses sit in their own group in the report's pulse list).
Unarchive brings a pulse back to My pulses, paused, ready to reactivate whenever you like.
Delete for good only happens from the Archive. It removes the pulse and every answer it collected, and reports for past periods will change, so we ask you to type the pulse's name to confirm. One thing survives, by design: statistics your organisation has already contributed to industry benchmarks are aggregates, not copies of your data, so they stay in the benchmarks and can't be traced back to you.
The three core pulses are never deletable. Pause or archive them, yes; delete, no. Every organisation keeps its baseline.