1Open your team's Vision screen

Go to EOS Components and pick the Vision tab. The heading reads Vision.

The same screen also has a home of its own in the app. Everything in this article works the same way in both places.

What is on the screen

The sections run down the page in this order: Core Values, Core Focus, BHAG, Marketing, then Plans.

The marketing section is labelled Marketing on the page. Its pencil is named Edit Marketing Strategy.

Plans has its own row of tabs: 3-Year Picture, 1-Year, Q1, Q2, Q3 and Q4, plus a picker for the year.

Empty sections still show up

A section you have never filled in does not disappear. It keeps its box, its name and its edit pencil.

An empty BHAG reads "No BHAG defined yet". An empty 3-Year Picture reads "Ready for clarity!"

So a half-written V/TO shows you where to pick up, instead of hiding the gaps.

2Start the interview

Where you find it depends on whether your team has any vision written yet.

If your vision is still empty

A card sits in the body of the page headed Create your vision with AI. Under it: "Answer a guided questionnaire and we'll draft your 3-year vision and mission so you can review, edit, and save."

Press the Create your vision with AI button on that card.

If you already have a vision written

The card is gone. Open the Helpful Tools menu at the top right of the page and pick Refine with AI.

What opens

Both paths open the same thing: the Vision Agent, a tall panel down the left side of the window.

It covers your sidebar while it is open. Nothing about your sidebar changes — it is only covered, and it comes straight back when you close the panel.

The Vision page next to it dims. It is still your real page, and you will watch it fill in as you go.

What the panel tells you first

The header reads Vision Agent over the line "Let's refine your vision."

Then the plan: "Answer a few questions about where the company is headed in three years. AI drafts your vision and core purpose from your answers — you approve or refine every word."

A chip reads ◷ About 6 minutes. That clock is a character in the text, not an icon.

Under it, three cards say who does what: You answer, I'll draft, You approve.

The first card sizes the job for you: "20 questions in 5 short groups. Skip any you're not sure about."

First time through

Press Start → at the bottom. You land on the first question.

Coming back to a run you already started

A card reads Pick up where you left off, with how many you have answered and the group you stopped in.

Press Resume to carry on where you were.

Press Start over and the card asks you first, right where it stands. Nothing is cleared until you confirm, and Keep my answers puts the card back the way it was.

3Answer the questions, one at a time

There are twenty questions in five groups of four: Financials, Employees, Customers, Products + Services, then Press.

You see one question at a time. A cue above it tells you where you are, like Group 2 of 5 · Employees.

There is nothing to save

The opening screen promises it: Your answers save as you type. There is no Save button anywhere in the interview.

Once you are answering, that line becomes your count and your receipt: 5 of 20 answered · saved.

Nothing greys out or spins while a save happens. You keep typing.

Skipping is fine

Every question offers Skip this one at the left and Next → at the right.

A skip does not count as an answer, and nothing warns you about it.

Watch the page fill in

Look at the dimmed page beside the panel. The 3-Year Picture section lights up and gets a Filling in badge.

Each group adds one row there when you finish it. Answering one question inside a group adds nothing — rows fill by group.

You do not have to answer all twenty

Once you have five answers, an offer appears under the question: Don't want to finish all 20? followed by Draft now with what I have.

Below five answers it is not on the screen at all. It is not there and greyed out — it is simply not there.

Pressing it goes straight to the drafting and skips the review in Step 4.

Leaving in the middle is safe

The ✕ at the top right of the panel closes it. Nothing asks you to confirm, and every answer is kept.

Come back to the Vision screen later, open the interview again, and the resume card knows exactly where you stopped.

4Look over your answers before it writes

Finish the last group and the panel hands you everything you said, under the line "Done asking. Take a look."

Your answers are grouped under their group names. Each row shows the question, your answer, and a control on the right.

[Annotation-draft note: no screenshot for this step. In this session, finishing all 20 questions — or skipping the 20th — did not open this review screen; repeated presses of Next/Resume on the last question left the interview on that same question instead of advancing to Step 4. Reproduced three times. Flagged in findings.md as a defect candidate, not a wording issue — the prose above is left as the feature is meant to work.]

An answered row offers Edit. Press it and you go back to that question with your answer already in the field.

A skipped row reads "Skipped — AI will infer this from your other answers", and its control reads Answer instead.

A skip is never an error. Nothing turns red, nothing says required, and nothing stops you moving on.

At the bottom sits your count and one button: Generate my draft.

5Approve the vision it drafts

Press Generate my draft.

The wait

The panel changes right away, before any draft exists. It ticks off ✓ Reading your answers, then ✓ Finding the thread, then shows Drafting your vision… still working.

The bottom reads Usually about 10 seconds.

The page lights up in the same order the panel says: 3-Year Picture badged Reading, then Our Vision badged Writing, then Core Purpose badged Queued.

Changed your mind? Cancel stops the drafting and puts you back on the review with every answer intact. It does not close the panel — the ✕ does that.

If you took the shortcut and skipped the review, Cancel is how you get to it.

The draft

The header now reads Vision Agent · Step 2 of 3 over "Here's your draft. Change any word."

Two boxes hold the draft: Purpose and Description.

The draft itself shows up on the page, not in the panel. Our Vision lights up with a Just drafted badge, at full page width.

Type in either box and the page changes as you type, before anything is saved.

Don't like it at all? Regenerate writes a fresh draft from the same answers. One thing to know first: the old wording does not come back with undo.

Happy with it? Press Approve & continue →. The page marks Our Vision as Approved and the panel moves to the last step.

6Approve your core purpose

The header reads Vision Agent · Step 3 of 3 over "Last one. One sentence."

There is one field. No second box, no formatting bar.

The line above it says why: "The one sentence your team can repeat from memory. Change anything you like."

Edit it, and the page's Core Purpose line follows along as you type.

Press Approve & save. The panel closes, your sidebar comes back, and the page returns to full brightness.

Where what you approved lands

Everything the interview wrote is saved on your Vision page.

Your core purpose sits under Core Focus, on the Purpose / Cause / Passion line.

No message tells you it saved

That is on purpose. Nothing pops up, and there is no "Saved" text anywhere.

The sections the interview just wrote carry a brief highlight instead, and that highlight is your confirmation. It fades on its own.

Sections that did not change carry no highlight, so what is new is easy to spot.

1Add someone who is already in your organization

Open your team, go to the Members tab, and press Add member.

The picker opens on a search box reading “Search people”, with one line of guidance under it: “Search by name, or enter an email address to invite someone new.” Both paths live in this one control from the start — you never have to fail a search to find the invite option.

It opens with everyone your organization already knows listed, so on a small team you often don’t have to type at all. Pick a person and they join straight away — no invitation and no waiting, because they already have an account.

Anyone already on this team stays in the list, marked Already a member and not selectable, so you can see they’re there instead of wondering why your search turned up nothing. On a team that already holds everyone in your organization — often the top-level one — every row reads that way, and inviting a new address is the only thing the picker can do for you.

2Invite someone who isn’t in ResultKit yet

Type their email address instead. When nothing matches, the picker says “No one was found with that name or email address.” and offers a button reading Click here to invite with the address you typed set inside it.

Underneath it, one line says what happens next: “They’ll get an email invitation.” The invitation is for the team whose tab you’re on, so if that isn’t the team you meant, switch teams before you send rather than after.

Beneath that sits Add a personal note (optional), a box that prompts “Say why you’re bringing them in — one or two lines in your own voice.” Whatever you write goes at the top of their invitation email. Leave it blank and the standard invitation goes out on its own. A counter beside the label tracks the 500 characters you have to play with.

The note is worth the fifteen seconds. It is the difference between an invitation that explains itself and one that lands cold.

Press the invite button and the person appears on the team as a pending tile at once, without waiting on the server — so the tab always shows what you just did.

3Track the invitation while you wait

An invitation nobody has accepted yet shows as a dashed tile: an envelope where the avatar goes, the email address where the name goes, the line “Invitation sent · awaiting signup”, and a Pending chip.

There is no name and no @login on it, because there isn’t one yet. The section’s count pill includes the tile, so the number on the tab counts the people you’re waiting on as well as the people who have joined.

Changed your mind, or mistyped the address? Remove on the tile cancels the invitation. Once cancelled it cannot be accepted — the link stops working rather than quietly letting someone in later.

The same tile also carries Resend Invite, which sends the link again without changing anything else about the invitation.

4What your teammate does

They get one email, headed by whatever note you wrote, above the standard invitation text and a single Accept invitation button.

That button opens one screen showing who invited them and which team they’re joining, with their email already filled in and locked — the link is what proves the address is theirs, so there is no separate “confirm your email” step to sit through.

They set a name and a password, or use Continue with Google or Continue with Microsoft, and they’re in. That is the whole thing: one email, one screen.

If they’d rather sign in with Google or Microsoft, it has to be the same address you invited. Picking a different account is refused with a message naming the provider they picked, and no account is created.

1Open your Accountability Chart

In the sidebar, open EOS Components and pick the People tab.

People is a set of tiles, not the chart itself. Choose the Accountability Chart tile and the chart opens on its own page.

The page heading reads Accountability Chart. On a team that is not running EOS it reads Ownership Chart instead.

2Read the chart

One seat sits at the top. In EOS that is your Visionary.

Everything else hangs off the seat it reports to, and those lines cross team boundaries. A seat on your Operations team can report to a seat on the root team, and the chart draws it that way.

You get the same chart whichever team you are currently switched to. Switching teams changes your team context, never the chart in front of you.

What a seat card shows

Each card carries the seat's name, the things it is accountable for, and the person who holds it with their avatar.

A seat nobody holds reads Vacant. That is a real state, not a gap — a vacant seat is a role you have defined and not yet filled.

Someone else's change arrives on its own

If a colleague gives someone a seat while you have the chart open, that seat updates in front of you.

You do not reload, and the chart does not blank out and redraw.

3Narrow the chart to one leader's branch

A chart big enough to be true is too big to read at once. So you narrow it.

A seat with people reporting to it carries a small chip along its bottom edge counting them — 5 direct reports, or 1 direct report when there is only one.

A seat with nobody reporting to it carries no chip at all. Not a zero, not a greyed one — nothing.

Focusing

Click the chip and the chart redraws around that seat. It becomes the top card, and everything outside its branch leaves the canvas.

Double-clicking the card does the same thing. A single click does not — that opens the seat.

Finding your way back

A bar appears at the top left naming the path you took, starting at Accountability Chart and ending at the seat you are in.

Every name before the last one is clickable. Click one and you re-focus there, part way back up.

The seat you are in is the last name in the bar, and it does nothing when clicked.

At the right of the same bar sits Exit focus, carrying an ESC badge. Press it, or press Esc, and the whole company comes back.

4Choose how much of the chart to show

The page header carries a Levels control. It reads how many levels deep the chart is showing.

Step it down and the deepest row leaves the canvas. Step it up and the row comes back.

It stops at both ends. At the chart's full depth the up button greys out, and at one level the down button greys out.

Focusing resets it. Narrow to a branch and Levels re-reads that branch's own depth, not the number you had set.

Zooming and moving around

The canvas carries a zoom cluster at its bottom right: minus, the current percentage, plus, and Fit.

Zoom runs from 10% to 300%. Pinching on a trackpad does the same thing, and the percentage moves as you pinch.

Fit resizes the chart to the width of the canvas. It shrinks as far across as it needs to, and never zooms past 100%.

Scrolling over the canvas moves the chart rather than zooming it. Dragging the empty background between the cards moves it too, which is what the header's drag to pan readout is telling you.

Your place is kept

Zoom in on a seat, open it, then close it again. The chart is exactly where you left it.

That holds whether you changed anything or not, and whether you closed the panel or pressed Esc.

5Open a seat and define what it is accountable for

Click a seat card to open it. The sheet has three tabs: Seat definition, Process and Notes.

It opens on a coaching line: Define the seat, not the person. Under it, the advice to aim for three to five specific accountabilities you would hand to the next person who sits there.

The five roles list

The section is headed ACCOUNTABILITIES, over the line Top 5 roles required of this seat. Under the rows sits an empty box reading Accountability….

Type into it and press Enter. The role lands in the list at once and the sheet stays open.

The cursor drops into a fresh empty box underneath, so you can type the next one without touching the mouse.

Pressing Enter on an empty box adds nothing. No blank row, and the sheet stays where it is.

Putting them in order

Drag a row by its grip and drop it where you want it. The new order is saved as it lands.

The grip also opens a small menu carrying Move up and Move down, which do the same thing one row at a time.

The panel beside it

The right half of the sheet is a Live preview, headed with a line about how this seat will appear on the chart.

It shows the card as you are building it, so you watch a role land on the card as you commit it.

Hide preview at the top folds it away when you want the room.

Files a seat carries

The Process tab holds the process and playbook documents for that seat, and its count sits on the tab.

Those files are what the Process/Playbook Index prints in Step 11.

6Rename a seat where you read it

The seat's name at the top of the sheet is the field. Click the words and type over them.

Press Enter and the sheet closes, with the new name already on the card in the chart. The save finishes behind you.

Click away instead and the name commits in place, on a sheet that stays open with your other edits untouched.

If you cannot edit that seat, none of this is on your screen. The name is plain text — nothing to click, and nothing hinting there is.

7Give a seat to someone

Open the seat and use the Owned by picker.

It offers everyone in your organization — the root team and every team beneath it. Not just the team you happen to be switched to.

That is the point of it. The right person for a seat often sits on a different team, and you can still pick them.

Click their row, or type a few letters and press Enter on the highlighted one. Either way the field and the seat card show them straight away.

Someone who cannot edit the seat sees its owner as plain text, with no picker to open.

8Add a seat under any seat you can edit

Every seat you can edit carries an add-seat control. Use it and a blank new-seat form opens.

The form already knows which seat the new one reports to, so you never pick the parent yourself.

It is blank every time. A seat you created a moment ago leaves nothing behind in the next form.

Which team the new seat belongs to

The new seat belongs to its parent's team, not to whichever team you were switched to when you made it.

Your own team context does not change either. You stay where you were.

It appears even if it is deeper than what you were showing

Add a seat one level below the depth on screen and Levels steps up by itself to take the new level in.

The seat can still land below what is on screen. Pan down if you do not see it straight away.

Only one seat can sit at the top

A team already holding a top seat will not take a second one, and says so.

9Move a seat

Open the seat you want to move. Under Reports to sits its parent seat, with a Change link at the right.

Press Change, pick the seat you want above it, then press Save seat.

The chart redraws with the seat in its new place immediately, and it is still there after a reload.

Where a seat can and cannot go

Anywhere inside your organization is fine, including onto a seat that belongs to a different team.

Across organizations is not, and the move is refused with a message saying so.

The one seat at the top of the chart cannot be given a parent. That refusal is what keeps the chart to a single top.

A seat that has somehow been left stranded at the top alongside it can be given a parent the same way, which is how you fix one.

10Archive a seat, and what it takes to bring it back

Choose Archive on the seat. The confirmation names it — Archive "QA Lead"? — and asks "Archive this seat and all descendants? This action cannot be undone."

Confirm and the seat leaves the chart at once, with the save finishing behind you.

It takes the reporting line with it

Archiving a seat archives everything reporting to it as well, in one go.

Archive a Finance seat with four seats under it and all five leave the chart together.

The seat at the very top of the chart cannot be archived at all.

Bringing one back is a team admin job

Restoring an archived seat is the one seat action that needs team admin rather than seat edit rights.

Someone who owns a seat can archive the seats beneath it and cannot bring them back.

A restore covers the one seat it names. Anything archived below it stays archived.

11Print the chart

The Print control sits in the page header, after the Levels stepper.

Anyone who can see the chart can print it. There is no admin gate on it.

It opens a menu of three: Simple Visual Chart, Full Seat Summaries and Process/Playbook Index.

The visual chart asks how much you want

Choose Simple Visual Chart and a prompt opens headed Print accountability chart, over "Choose how much of the chart to print."

Whole chart is already selected, so pressing Print without touching anything takes all of it.

Pick Down to a certain level instead and a levels deep stepper appears beside it. It will not go past the depth your chart actually has.

What comes out

You get a PDF download rather than a print dialog.

It breaks up one branch section to a page, with a title page in front. Examp.ly's whole chart comes out as five pages.

Every page carries Printed from ResultKit.com at the left and Page 1 of 5 at the right.

The other two download straight away

Full Seat Summaries gives you a page per seat — nineteen of them for Examp.ly — carrying its title, its owner, what it reports to, the seats reporting to it, and its accountabilities, measurables, process documents and rocks.

Process/Playbook Index gives you a page per seat listing that seat's process documents as links you can click.

Neither asks how much you want, and neither carries the printed-from line. That belongs to the visual chart.

What the file is called

The name leads with your organization, never with a team — for example Examp.ly-Accountability-Chart-Full-Summaries.pdf.

All three files follow that pattern, and the chart word changes to match a team that is not running EOS.

12Ask the assistant to set up a chart

A team with no chart yet does not have to start from an empty canvas.

Ask the assistant to set up the accountability chart, naming the team you want it for. Name the team — it does not assume the one you are looking at.

It creates a starter set of seats and reports what it made: how many, and the name of the seat at the top.

On the EOS team in the picture below that reads five seats created, with Visionary at the top.

Ask on a team that already has a chart and it does not build a second one. It talks you through adding seats by hand instead.

Asking for a single seat

Ask the assistant for one new seat and it offers you a choice before it creates anything.

You can create it now with a name and a parent, or define the whole seat card first — the function, five roles and the level.

[Screenshot not captured this pass — see findings.md. Live-driven testing found the assistant no longer surfaces "create it now" vs. "define the full seat card first" as an explicit on-screen offer; it infers the path from phrasing instead, so there was no distinct A/B moment left to photograph. The behavior this section describes is otherwise unverified against the live app in this pass.]

1Build a template

Everything a review asks comes from its template.

To create your first template, open Quarterly Conversations and Reviews - the screen this article calls Reviews for short - and go to the Templates tab.

Create New Template asks for a Template Name, Reviewer Instructions - the notes the reviewer reads while they’re writing - and Organization Sharing.

Open the template to add your prompts.

Drag them to reorder, edit or delete them in place. Core Values Alignment is always there and can’t be removed.

The four icon controls on a template are, left to right, Preview Template, Copy Template, Edit Template, and Archive Template. Archive is the red bin, and it is one-way - there is no archived-template list and nothing to restore from, so treat it as delete.

One thing to know before you preview: Preview Template opens the Template Preview drawer, and the core values it lists belong to whatever team you’re currently switched into — not the org the template was built in.

2Decide who can use it

The template’s permissions drawer grants roles one person at a time: + Add viewer… under Viewers for someone who should read it, + Add collaborator… under Collaborators for someone who should be able to change it. Select organizations… is separate from both, and shares the template wider.

3Start the review

In Reviews, press + New Review. If that button isn’t there, you’re not allowed to create reviews here.

The sheet asks for five things: Reviewee Name, Reviewer Name, Template, Type, and Team.

The reviewee list only holds people below you on the accountability chart - your direct reports and the people under them, never your peers.

If that list comes up short or empty, the sheet says why instead of leaving you staring at a blank box.

Type is worth a second look: it’s set here, on the review itself, and doesn’t come from the template.

Formal Review and Quarterly Conversation are the two choices, and either can come from any template — the template’s own name, even “Quarterly Conversation,” never decides which one you get.

4Write your side

The review opens with up to three tabs: Self-Assessment, Reviewer Assessment, and Comparison.

Each assessment holds the template’s prompts, the Core Values Alignment ratings with a comment box under each value, and the GWC Evaluation. Both end in Save Draft and Submit.

The reviewee always sees their own tab. The reviewer’s view of it opens once the reviewee submits — so in practice the reviewee goes first.

The pencil (Edit review) opens a drawer that saves as you type: it reads Saving…, Saved, Unsaved Changes, or Save failed — will retry, and the form holds its position under your cursor while it does.

Below the assessments sit three more panels. The reviewee’s seat accountabilities are listed so whoever is writing can see what the role actually asks for. Attachments takes supporting files through Upload File. Action Items is where the conversation turns into work - type into New action item… and press Add.

5Close it out

The reviewer submits their assessment, and normally that’s that. If the reviewee never filled in their side, you’re not stuck. A dialog asks: “The reviewee has not completed their portion. Do you want to finalize it without them completing a self-review?”

Yes closes it. The other button — “No, save my changes but don’t mark the review closed” — keeps everything you wrote without finishing anything, which is the one to press if you’re still waiting on them.

Sign-off captures Initials: the Sign Off card reads “Both assessments are in. Enter your initials to sign off and finalize this review.” On the skip path above there is no initials field - that dialog has only its two buttons - so ResultKit fills them in from your name on your behalf. Once it’s signed off, the tabs carry the record themselves: a green check where a side was submitted and a struck circle where it was skipped. The tab keeps its name - open the skipped one and the panel says The self-assessment was skipped for this review. Nothing about it is hidden.

6Read it back and print it

Once the review is signed off, both sets of answers will show up side by side, in the words each person actually wrote, with bullets and bold intact.

The printer icon (Print review) opens a print-ready copy of the review and starts printing on its own. The PDF is named for the person, the review type, and the date, and long reviews print in full rather than getting cut off at one page.

1Sign in with your login name or email

On the sign-in screen, type your login name or your email into the one identifier field. Case doesn't matter either way.

Type your password and press Sign in, or press Enter.

The button reads "Signing in..." while it works, and won't take a second click.

2Read a refusal for what it actually says

A wrong password and an identifier nobody uses get the identical answer: "The login name or password is incorrect."

Other refusals name something more specific. An outage says sign-in is temporarily unavailable, never that your password is wrong.

An unconfirmed email says so directly: "Confirm your email address to continue."

Several failed attempts in a row get a wait message, not a lockout notice.

3Land back where you were headed

Follow a link to a specific page while signed out, and you land on the sign-in screen with that destination held.

Sign in, and you arrive at the page you were originally headed to — never a home screen you have to navigate from all over again.

4Start an organization with your email

Open the signup screen to create a brand-new organization.

As you type your name, the preview on the left fills in your seat.

Type an organization name, and the preview's title and top row fill in too — before anything is saved.

Five fields are asked for: your name, your work email, a login name, a password of at least 8 characters, and your organization's name.

Click Create account or press Enter in the last field. The button reads "Creating {your organization}…" while it works.

5Confirm your email with the code

Submitting doesn't sign you in right away — it sends a 6-digit code to the email you gave.

Enter the code, and your organization, its Leadership Team, and your Owner seat are created together in that one act.

Leave the screen before entering it, and nothing has been created at all.

6Start an organization with Google instead

Click Sign up with Google and pick your account in the chooser that opens.

Whatever you'd already typed in the organization-name field carries over rather than being lost.

Not captured: this step requires completing a real Google sign-in, which this pass did not do. The organization-name-only claim above is BDD-verified but not yet confirmed against the pixels.

The organization-name step is the only thing left: one required field, never pre-filled on your behalf.

Submitting it creates your organization, your Leadership Team, and your Owner seat together.

7Sign in with Google or Slack

Click Sign in with Google or Sign in with Slack above the password fields.

Approving the provider signs you into the same account you already have — never a second, duplicate one.

You're never asked for your ResultKit password this way, and nothing about your teams changes.

8Sign in with Microsoft

Click Sign in with Microsoft and it routes you silently, with no "work or personal?" question ever asked.

It sends you to your organization's connection if you've typed a matching work address. Otherwise it uses the connection you last used on that device, or the personal-account connection.

A customer organization's own work accounts only work with Microsoft once that organization has been set up for it.

Until then, its people use Google, a password, or a personal Microsoft account instead.

Observed directly: clicking Sign in with Microsoft routes to a genuine Microsoft consent screen rather than failing immediately — this pass did not complete the sign-in, so whether the return trip finishes successfully is still unconfirmed.

1Turn on two-factor authentication

Open Security settings, under Settings. Two-factor authentication starts off, with a control to turn it on.

{{shot:01-security-off|Two-factor authentication starts off, with a way to turn it on.|no-annotation:the exact control label isn't given in the BDD, and the off state itself is what this shot shows}}

Click it to begin setup.

2Know there's no way back if you lose your device

There's no recovery path if you lose the device your authenticator app is on. There are no backup codes, and no administrator can clear your second factor for you.

Losing that device locks you out of your account. Turn this on knowing that going in.

3Scan the code or enter it manually

Setup shows a scannable code for your authenticator app, and a manual-entry key if you'd rather type it in.

{{shot:02-2fa-setup|Setup shows a scannable code and a manual-entry key at the same time.|no-annotation:both options are the subject at once, and there's no single control to box}}

Enter the code your app generates to finish. Get it wrong, and two-factor authentication stays off — nothing is half turned on.

4Answer the code challenge at sign-in

From then on, a password alone doesn't get you in. The code challenge replaces the sign-in fields on the same screen, before any session exists.

{{shot:03-code-challenge|The code challenge replaces the sign-in fields on the same screen, before any session exists.|no-annotation:exact field labels for this screen aren't given in the BDD}}

Enter the wrong code too many times and you're rate-limited and told to wait. You're never locked out for good over a mistyped code.

Sign in with Google or Microsoft instead, and you skip the challenge entirely. The provider handles your second factor, and your security settings say so.

5Turn it off

Turn two-factor authentication off the same way you turned it on, in Security settings. Password sign-ins stop asking for a code right away.

6Choose whether to be remembered

Remember me sits on the sign-in screen, checked by default. It decides whether your session outlives closing the browser.

Uncheck it on a machine that isn't yours. The choice holds even if you finish signing in through a provider instead of typing a password.

7Sign out

Open the account menu and choose Sign Out. It takes effect at once, with no confirmation to click through.

Signing out ends your session both in ResultKit and on the identity platform underneath it.

1Ask for a reset

From the sign-in screen, click Forgot password? to reach the Reset password screen.

Type either your login name or your email into the one field. Press Enter or click Send code — both do the same thing.

The message "If that account exists, we've sent a 6-digit code to its email address. Enter it below." appears at once, before anything is actually sent.

That message and the screen it sends you to next are identical whether or not the account is real. Nothing on screen ever says which.

2Enter the code and set a new password

You land on the Set a new password screen, with fields for Verification code, New password, and Confirm new password.

Enter the 6-digit code from the email, type your new password into both fields, and press Enter or click Reset password.

You land on the sign-in screen with the reset acknowledged. Sign in with either your login name or your email — whichever one you used to request the code, or the other one; both still work.

3If the code doesn't work

A code that's wrong gets "That code isn't right." — you stay on the screen to try again.

A code you've already used once gets "That code has expired. Request a new one." A code is only good for one reset.

Not captured this pass: reproducing a spent code requires reading the code out of a real inbox, which wasn't available. The BDD-verified prose above stands unphotographed.

Your original password still works if a second attempt with the same code gets refused — the refusal changes nothing.

Submitting six requests in fifteen minutes gets a rate-limit message instead. Even that message says nothing about whether any account exists.

1Open the team's Rocks board

In the left sidebar, open EOS Components and choose Traction.

The page opens on the Rocks sub-tab. Its siblings are Personal Rocks and Meeting Pulse.

It opens there every visit. Traction never remembers which sub-tab you left on.

Personal Rocks are a separate thing with their own guide. Everything below is the team's board.

2Set a Rock under the goal it advances

Press + New Rock in the toolbar. Every goal group also carries its own Add Rock button.

Starting from the goal's own button fills the goal in for you.

The drawer's title line is the name field. Its placeholder reads "Name your rock".

Below it, Advances names the Rock's one-year goal.

The tip card reads "Make it a rock, not a wish" and names this quarter's last day.

It always names the quarter containing today, even when you are viewing a different quarter.

Press Add rock. The tile appears under its goal before the save finishes.

3Break the Rock into milestones

Open the Rock from its tile and go to the Milestones tab.

Type the milestone's name and a target date, then press Add milestone.

The row appears the instant you press it, and the save runs behind you.

Nothing pops up to confirm it. The milestone simply appears.

The board behind the sheet already carries it, with no refresh.

4Read the board week to week

Each one-year goal heads its own group. The eyebrow above the name reads 2026 GOAL.

Between the goal and its Rocks sits the label Q3 2026 ROCKS TO ACHIEVE THIS GOAL.

Every Rock shows its name, its due date, a progress bar, a status badge and its owner.

Its milestones list beneath it. Done ones are checked and struck through.

The All, On Track and Off Track pills narrow the board. The goal headers stay put either way.

The people filter reads Everyone until you pick someone. It lists everyone on the team, with a Me row at the top.

The switcher on the right re-lays the same Rocks four ways, Mindmap view included.

5Flip a Rock On Track or Off Track

Click a Rock's status badge. Its tooltip reads "Click to flip status".

The badge flips at once and the save follows. No toast appears.

There are only two answers — On Track and Off Track, with no third state.

A Rock nobody has checked in on reads On/Off Track? until someone does.

Each one-year goal's badge is the same control. Clicking it sets the goal, exactly as a Rock's badge does.

The keyboard works too. Move focus to the badge and press Enter.

6See what the Rock ladders up to

Open the Rock and choose its Alignment tab.

The tab draws the line. ADVANCES · 1-YEAR GOAL above, THIS ROCK — wearing a YOU ARE HERE pill — in the middle, its milestones below.

Nothing else is on it — no project, no measurable, no list of surfaces.

To re-point the Rock, press Change alignment. The picker offers the team's one-year goals and nothing else.

Pick one and confirm. The Rock moves under its new goal on the board behind you, with no refresh.

The tab behaves the same way when you open the Rock from the Level 10.

7Report milestone progress in the weekly prep

Each week, the Milestones section of your 3-Step Prep lists the milestones you own.

Each sits under its Rock and the year goal above it, and reads Milestone · due end of quarter.

Set a status and leave a comment.

A #hashtag in that comment creates a linked action tied to the milestone, due end of week.

Own no milestone this week? The section shows an empty state and you move on.

Submitting carries what you entered into the Level 10's Rock review.

8Close the quarter

Open the Quarterly and its Review Prior Quarterly Rocks section.

A Rock reads differently here. Its badge is REALIZED / ACHIEVED or NOT (YET) ACHIEVED.

A realized Rock is checked and struck through. A Rock's badge here never reads On Track or Off Track.

With edit rights you set either state in the moment. Without them you can read it but not change it.

Every Rock still unfinished offers a Carry forward checkbox. A realized Rock is shown as done and offers none.

Select the ones still worth pursuing and confirm — the button counts your pick, reading Carry 2 Rocks into Q3 2026.

Each carried Rock is copied into the next quarter under the same owner. The originals stay in the closed quarter.

1Open your Rocks tab

Personal rocks live in your Personal Planner, on the Rocks tab — it sits between Quadrants and Sequencer.

The tab opens on Personal, with a Personal | Company toggle sitting just after the quarter pills. Personal is the rocks you set for yourself; Company is the team rocks you happen to own, grouped by the team each one belongs to.

The strip below the toolbar is the one thing worth reading before you write anything down. It counts the quarter in weeks — WEEK 8 OF 13, "5 weeks left · quarter ends Sep 30" — which is a useful reality check when you're about to promise yourself something.

2Set the rock

Press + Add Rock. The drawer opens headed NEW PERSONAL ROCK with the quarter beside it, so you always know which quarter you're writing into.

The callout at the top is doing real work: "Make it a rock, not a wish. A great rock is specific, measurable, and achievable in 90 days. State the result, not the activity — what's true on September 30 that isn't true today?" If you can't answer that last question about the thing you're typing, you have an activity rather than a rock.

What does done look like? is where you settle it. The prompt asks you to "describe the finish line so future-you can call it done or not done", and future-you is the one who'll be grateful — the wording you choose here is what you'll be arguing with in week twelve.

Owner is you and Due defaults to the last day of the quarter.

Below that, Milestones is optional — "Break the quarter into checkpoints — one every 2–3 weeks keeps the rock honest." Two blank checkpoint rows are waiting, each with its own due date already guessed at partway through the quarter. Name them or skip them; the note under the section says so plainly: "You can add or edit milestones any time after creating."

The panel on the right builds your tile as you type and tells you what happens next: the rock starts as On/Off Track?, and you set it On Track or Off Track at each weekly check-in.

Press Add Rock and it appears on the Personal side.

3Answer the question every week

A new rock arrives wearing an amber ON/OFF TRACK? badge. That badge is a question, and answering it is the only upkeep a personal rock asks of you.

Click it and it reads ON TRACK. Click it again and it reads OFF TRACK. There is no third answer and no half-measure, which is the point — a rock you're privately unsure about is off track.

Off Track isn't a failure state. It's the flag that gets the rock talked about while there's still quarter left to do something about it.

4Find it alongside the team's rocks

Your personal rocks also have a home on Traction, under the Personal Rocks tab — it sits beside Rocks and Meeting Pulse.

The heading says what you're looking at: "Rocks teammates have made visible to the team, plus rocks you assigned." Rocks are grouped by person, your own group first and tagged YOU, and each tile carries a line saying why you can see it — Your rock, on the ones you set.

This tab is also where the status badge is at its most useful, because you're seeing your own rocks in the same view as everyone else's.

5Decide who can see it

On Traction, next to the status badge sits a small chip that names, in plain words, who can currently see the rock. On a new rock it reads Just you.

Click the chip and the WHO CAN SEE THIS ROCK panel opens in place, offering three answers.

Just you is where every rock starts — "only you see this rock".

Specific people — "only the people you pick can see it" — opens a PEOPLE YOU PICKED list with an + Add person button and a search box over your teammates. This is the one to reach for when a rock is really between you and your manager.

Visible to team puts the rock in front of your teammates on Traction. Choosing it opens a TEAMS list with a search box, Entire organization at the top, and your teams beneath it.

The chip updates the moment you choose, so the tile always tells the truth about itself.

1Open the Custom tab and see your labels

From the Prioritizer, click the Custom tab. Your columns show your own categories, and any labels on a card sit in a row of colored chips beneath it.

A card can carry more labels than fit. When it does, the extra ones collapse into a plain gray +1 chip.

Each card's labels sit beneath its other details as colored chips.

A card with more labels than fit shows a neutral +1 instead of crowding the row.

2Filter by clicking a label on a card

Click any label chip on a card. That chip turns solid, and the board narrows to only the To-Dos wearing that label — every other card animates off the board.

Click the same chip again to bring everything back.

The clicked chip goes solid, and the board keeps only the matching cards.

3Filter from the trigger instead

You don't need a card in front of you to start a filter. Click All labels at the top right of the board to open the same filter from a search list.

Type to narrow the list, or just click a label's row. The board updates as soon as you do — there's no separate step to apply it.

The All labels control sits at the top right, above the board.

Each row shows the label's color and how many To-Dos carry it, board-wide.

4Combine labels with ANY or ALL

Pick a second label, and an ANY / ALL switch appears next to your selections. ANY shows work carrying either label; ALL narrows to only the To-Dos wearing both.

The switch only appears once two real labels are selected.

5Clear the filter

A ghost Clear control appears next to your selections any time a filter is on. Click it to bring every To-Do back at once.

Clear removes every selected label in one click.

6Add a To-Do into a column

Click the Add control at the top of any column. It opens the same Add From Anywhere window you'll see across the rest of the app — not a cramped inline box.

Type a name and save. The new To-Do appears in that column right away, before the save to the server has even finished.

Add sits at the top of every column, above its cards.

The modal opens pre-set to land the new To-Do in the column you clicked from.

7Adding while a filter is on

If a label filter is active when you save a new To-Do, it inherits every selected label automatically — you'll see it as a removable chip in the modal's LABELS row before you save.

Don't want it? Click its × to take it off before saving. Remove it, and the To-Do still saves — it just won't show up under the current filter.

The new To-Do picks up whichever label is currently filtering the board.

When a new To-Do lands hidden this way, the column it landed in shows a short amber notice explaining that newly added items won't show while a filter is on.

The notice reads "Newly added items will not show up while your filter is on" — it's never a mystery why a card you just added isn't there.

8Mark a To-Do done

Click the circle on any card. It fills in and the name strikes through immediately — the save to the server happens after, in the background.

The same instant response happens in the Not categorized list, for anything you haven't sorted into a column yet.

The circle fills and the name strikes through the moment you click — no waiting.

Not categorized gets the same instant response as any column.

1Filter the list by label

Press All labels ▾, above the list. A popover opens with every label, a search field, and a No labels row.

Tick a label and the list narrows at once. Tick a second one and an ANY / ALL toggle appears — "has either" or "has both."

Every selected label shows as a chip in the toolbar, with a live count. Clear drops every filter in one press.

You can also start a filter from a To-Do's own chip. Click it and the chip goes solid to show it's active.

2Reorder the list

Drag a To-Do within its own priority group and the list reorders live. No confirmation needed.

Drag it across a priority group instead, and the move is refused. A message explains why, linked to more on prioritization tags.

3Apply a label and watch it stick

Open a To-Do's Item sheet and tick a label, or create a new one. The chip appears on the tile at once.

You don't wait on the save to finish, and it won't flicker while it settles.

1Open the Day/Week tab

From the Prioritizer, click Day/Week (nested under Personal Planner). Your work is laid out in four gray columns — Today, This Week, Next Week, Later — each with its own header at the top.

2Mark a To-Do done

Click the circle on any card. It fills in and the item leaves the column immediately — the save to the server happens after, in the background.

3Show Completed is off by default

With Show Completed off, a finished item stays off the board — whether you just checked it off this second or it was completed yesterday. Nothing you've finished clutters the view.

4Turn Show Completed on to see everything you've finished

Flip the switch on, and every completed item reappears at once — including one you finished a moment ago in this same session — right alongside your open items.

5Add a To-Do into a column

Click the Add control at the top of any column. It opens the same Add From Anywhere window used across the rest of the app — not a cramped inline box — pre-set to land your new entry in the column you clicked.

6Save it — it appears before the server answers

Type a name and press Enter, or click Save. Either way, the new To-Do appears in its column right away — indistinguishable from a card that's been there for weeks.

7Assign someone while you add it

Type @ and a teammate's name right in the entry before saving, and the new To-Do lands already assigned to them.

8Drag something in from anywhere in ResultKit

Open the Compass dock and drag any item onto a Day/Week column. It settles into whichever time bucket you dropped it on — Today, This Week, Next Week, or Later.

1Open the Quadrants tab

From the Prioritizer, click Quadrants (nested under Personal Planner). You'll see four boxes — Urgent | important, Not urgent | important, Urgent | not important, Not urgent | not important — with a Not categorized list running down the left side for anything you haven't sorted yet.

2Every card in Not-categorized is readable right away

Nothing in the Not-categorized list waits on a drag to show its content — every card's title and controls are there the instant the tab finishes loading, no matter how many you have waiting to be sorted.

3Drag a card from the Compass dock into a quadrant

Open the Compass dock and pick up an item. As you drag it over a quadrant, that whole box lights up with a ring and a "Drop into" tag telling you exactly where it will land if you let go.

4Release it — it lands, sorted, right away

Let go, and the card appears in that quadrant immediately — on your day plan, categorized, and still there the next time you load the page.

5Move a card between quadrants

Pick up any card already on the board and drag it toward a different quadrant. Its old spot shows a dashed "Moving…" placeholder, and the quadrant under your pointer rings itself the same way a dock drag does.

6Reorder a card within its own quadrant

Drag a card up or down inside the same quadrant it's already in. That quadrant still rings itself the same way, so you always know it's about to accept the drop.

1Open the Rocks tab

From the Prioritizer, click Rocks (nested under Personal Planner, between Quadrants and Sequencer). You'll land on the Personal side by default — the rocks you set for yourself, with a quarter runway strip showing which week you're in. If you own a personal goal or have a company goal assigned to you, it shows in a strip above your rocks.

2Switch to your company rocks

Click Company in the toggle next to the quarter pills. Nothing else on the page moves — the swap doesn't touch the URL or refetch anything, it just shows the other half of what you own.

3If you don't own any company rocks, the Company side says so plainly

When you own a company rock, it shows up here grouped by Organization / Team — one group per team where you own something. If you own none for the quarter, the side just says so, in a plain line rather than the coaching copy the Personal side uses. Either way, the note above links straight to Traction if you want the full company view.

4Flip a rock's status at your weekly check-in

Click a rock's status badge to flip it between On Track and Off Track. It flips immediately — color and progress bar both — before the save even finishes.

5Complete a milestone

Click the open circle next to a milestone to check it off. The rock's progress percent recomputes immediately, and the milestone's text strikes through.

Not captured this run — see the notes doc, Appendix D, finding D.6. Creating milestones from this drawer doesn't currently save them (a real, reproducible API gap, not a hard-to-reach state), so no rock in the demo org had a milestone to check off. The paint-before-response behavior is confirmed in the code (handleToggleMilestone in my-rocks-view.tsx) but unphotographed.

6Add a personal rock

Click + Add Rock. It always creates a personal rock, whichever side of the toggle you're on. Type the result you're committing to and watch the live preview on the right update as you type — a new rock starts with the amber "On/Off Track?" badge, since you haven't checked in on it yet.

7Your new rock appears at once

Click Add Rock and the drawer closes — your new rock is already on the Personal side, before the save confirms. If you started the drawer from the Company side, the tab returns to Personal first, so the new tile is never created somewhere you can't see it.

1Open Assigned by Me

From My Work, click Assigned by Me. You'll see only items you assigned to someone else — never your own work, never something someone else asked of you — starting with To-do and Review items only.

2See a finished delegation by turning on Done

A completed delegation doesn't just disappear — turn on the Done status filter and it's still there, so you can confirm it actually got finished.

3Narrow to one person's delegations

Use the Accountable filter to see only what you've asked of one specific person — type-ahead search finds them by name.

4See who hasn't responded yet

The response filter separates delegations the other person has acknowledged from ones still sitting untouched — set it to Not accepted yet to see what needs a nudge.

5Reorder by dragging

Drag a row to a new position to reprioritize your own list of delegations — this only works under the default sort; switch to a different sort and the drag handles go away, since a manual position stops meaning anything once the server is doing the ordering.

6Delegate something new with an @mention

Type into the entry row at the top, @-mention the person you're asking, and submit — the new item appears already assigned to them, no separate step needed.

7Add several untracked delegations to a team at once

Open the shortcuts menu and choose Track All Under A Team to bulk-assign a team to every delegation that doesn't have one yet, instead of setting it row by row.

1Open an item

Click any item card, row, or title anywhere in ResultKit. A panel slides in from the right, over the page you were on.

Four tabs sit across the top: Details, Comments, Steps, and Alignment/Spaces. Details opens first.

2Edit the Details tab

An eyebrow at the top names the project or team the item belongs to. Below it, one row of pills: status, due date, and assignees.

Click any pill to change it. The change shows at once — you don't wait for a save to finish.

If your change gets refused, the field puts itself back to what it was before.

3Add a label

Past the status row sits a line of label chips, then a +Label button. Press it to open the label picker.

Pick a label and it appears on the item at once, in the sheet and on the card behind it.

4Mention or invite someone

Type @ in the item's name or description to bring up a picker of people across your whole organization, not just this item's team.

Type an email that matches nobody, and the same line offers to invite that person — even if they've never signed in before.

5Format the description, and attach a file

Click into the description and a sticky toolbar appears above it: Heading, Bold, Italic, Link, bulleted and numbered lists, Quote, Code, and Mention.

Below the description sits an Attachments section. Press Upload File to add a file from your computer, or Add Link to attach a URL.

6Close it

Press Done, the ✕, the backdrop behind the panel, or Esc — all four close the sheet the same way.

Nothing you typed is waiting to be saved. It was saved the moment you typed it.

1Read the comment feed

Open the Comments tab. Discussion and system events sit together under day headers, oldest first.

Choose Comments to see just what people wrote, or Updates to see what changed.

2Post a comment

A composer sits at the foot of the tab, with a seven-button toolbar above it: Bold, Italic, Strikethrough, Insert link, Bulleted list, Mention, and Attach. Type your comment and press ⌘ or Ctrl with Enter to post it — plain Enter just starts a new line.

You can edit or delete your own comments from their own ⋯ menu. Nobody else's comments carry that menu for you.

3Break the item into steps

Open the Steps tab. A progress bar and a line like "0 of 1 done · 1 remaining" sit above the list of steps.

Give a step a due date and an owner from the pills in that row before you add it — a step is a real item, not a checklist line.

4Open a step on its own

Click a step's name and it becomes the open item in the same panel, with its own Details, Comments, and Steps tabs.

Use your browser's Back button to return to the item the step belonged to.

1See what the work is for, and where it lives

Open the Alignment/Spaces tab. The Alignment section names what this item ladders up to — a Rock or Milestone, or the project and column it sits in. An item can also be Unaligned, and the tab says so plainly rather than showing an empty line.

Below it sits Appears on — every place this item currently shows up, filtered to what you're allowed to see.

2Realign it

Press Change alignment to open a picker: pick the team, then Traction, Project/Process, or Other, then the Rock or Milestone you want.

3Add it to another surface

Press Add to a surface… to put the item in one more place, without taking it off any of the others.

Neither adding nor removing has a save step. Each change commits the moment you confirm it.

1Find your team's roadmaps

Open the Swimlane Roadmaps tab on the Projects plugin page. The scope control above the list opens on This team.

It lists only your current team's saved roadmaps, with a count showing how many.

2Widen the list to see other teams

Click Organization to see every roadmap you can view across your organization. Click All ResultKit to reach across every organization you belong to.

The list clears at once, and three skeleton rows show while the wider list loads.

Other teams' roadmaps carry a label so you know whose they are. A same-organization team's roadmap shows just that team's name.

A roadmap from another organization shows both the organization and the team together. A root team shows only the organization's name, and your own team's roadmaps stay unlabeled.

The count above the list always matches what that scope lists. Widening it never surfaces a roadmap you couldn't already view.

3Open a roadmap on another team

Click a roadmap's title to open it.

If it belongs to a different team than your current one, the global Switch team selector changes to that team. Everything you open next follows it.

Opening a roadmap that already belongs to your current team changes nothing about the selector.

The Swimlane Roadmaps breadcrumb takes you back to the list with your scope selection intact. The selector stays on whichever team the roadmap switched you to — it doesn't silently switch back.

4Share a roadmap with a direct link

Paste a roadmap's link directly into your browser. It opens the same way clicking its title would.

If you can view that roadmap's team, the Switch team selector switches to it. The roadmap then loads in full.

If you can't view that roadmap's team, the page reads "This roadmap could not be loaded." with a Back to Swimlane Roadmaps button.

No title, lanes, or work render — not even for a link from another organization entirely. The selector stays exactly where it was.

5Rename or delete a roadmap

Every roadmap row carries a small actions menu with Rename and Delete.

Only the roadmap's creator or an admin of its team sees that menu. A root-team admin sees it on every team's roadmap beneath them, because admin rights inherit down.

Anyone else viewing the same row has no menu there at all — not a greyed-out one.

They can still open the roadmap. Only managing it is withheld.

Clicking Delete opens a confirm dialog naming the exact roadmap.

It warns that the roadmap will be removed for the whole team. It also reassures you that the projects and work it shows are untouched.

6Start a new roadmap

Click New swimlane roadmap to start one.

It's always created in your current team, no matter which scope pill the list happens to be showing.

If your team has no saved roadmaps yet, the list shows an empty state instead. Its Create the first roadmap button does the same thing.

Once you're building a roadmap, there's no scope control on the page at all — scope only ever filters the list.

The Swimlane Roadmaps breadcrumb is the only way back. It returns you to the list with your scope choice exactly as you left it.

7Choose how the roadmap displays

Switch between Timeline, Status, and Calendar from one control on the roadmap itself.

Each roadmap remembers your choice the next time you open it. That choice is yours alone.

Status needs a process workflow chosen first. Until then it shows a plain message instead of columns.

A team admin sees a path to pick one — the workflow cog if the team already has one, or a Create a process workflow button if it doesn't.

Anyone else just sees the same message, with no button.

On both Timeline and Status, the column headers stay pinned at the top as you scroll.

A long list of swimlanes never leaves you guessing which column you're looking at.

1Switch to Vertical

Click Vertical in the view toggle, alongside Timeline, Status, and Calendar. It's a plain fourth entry — no badge, no "new" marker.

The board reshapes at once. The lane-rows grid becomes stage columns side by side, in your process workflow's own order.

Every item stays exactly where it was — same stage, same lane. Switching views only rearranges the work; it never changes it.

Your choice is personal. Reopening the roadmap later puts you back on Vertical, but it changes nothing about the view anyone else sees.

A direct link to the roadmap opens on Vertical only if that's the view you last chose there. Anyone who has never chosen a view lands on the roadmap's own saved default instead.

2Read the board

Stages run left to right in your workflow's own order. There's no lane row anywhere — lanes live inside each stage column instead.

Inside a column, a lane's card stacks in your team's label order. A lane with nothing in that stage simply has no card there — not an empty one.

Each lane card's header shows the label's colour dot, its name, and a count. That count is only for this one stage, never the lane's total across the board.

Stage headers show just a name — no count, on a full column or an empty one. They stay pinned at the top as you scroll.

A long column never leaves you guessing which stage you're in.

Work with no stage yet gets its own column, first, before the others — exactly like it does on Status. If nothing is unplaced, that column simply isn't there.

3Read a row

Every row shows an item's name as a link, its status words, and its one-line description right on the row's face. You never have to open anything just to read it.

An assigned item shows its owner's initials avatar next to their name. An unassigned one shows neither.

An item with no status words reads "No defined next steps" instead, drawn as an outline so it reads as an absence, not a state.

Click an item's link and it opens in a new tab, leaving the board exactly where you left it.

Click the item's name instead, and its standard detail sheet opens over the board.

4Collapse a lane card

Click a lane card's header to fold it shut. Its rows disappear and the header alone remains, still showing its count.

Click the header again to bring the rows back.

Collapsing is per card, not per lane — the same label's card in another stage column stays exactly as you left it.

5Filter by label

Above the board, a rail of pills carries each label's total count across the whole roadmap. Click one to filter the entire board down to that lane.

Filtering to a label expands any of its cards you'd collapsed. A stage with nothing in the chosen label still keeps its column and header, empty.

Click the same pill again to clear the filter.

This filter is the roadmap's own — the same one Timeline, Status, and Calendar use. Choosing a label here changes what those views show too, and it's remembered the next time anyone opens the roadmap.

6Search the board

Type into "Search this roadmap…" and rows that don't match disappear as you type — by name, description, link, or status words.

Matching ignores letter case and stray spaces around what you type.

A lane card left with nothing to show disappears along with its rows, though its stage column and header stay put.

Clear the field and every row and card comes back, each in whatever expanded or collapsed state it held before.

Search and the label filter work together — narrowing by label first, then searching, only ever narrows further.

7Hide done work or narrow by owner

Turn on Hide done and every finished row leaves the board at once, along with any lane card left holding nothing else.

That choice survives a reload, exactly as it does on the roadmap's other views.

Pick a name in the owner filter and the board narrows to their rows only, clearing any lane card that has none left.

Unlike the label filter, the owner filter isn't saved — it resets the next time you open the roadmap.

1Drag a card to reschedule it on the Timeline

Drag a card to a new quarter on the Timeline. A confirmation dialog opens before anything saves.

Confirm it, and the card moves to that quarter. The item's own due date changes with it.

2Retime work on the Calendar's Day grid

On the Day grid, drag a chip to another day and drop it.

If the drop is unambiguous, it writes immediately. No dialog appears at all.

{{shot:02-day-grid-drag|Dropping a chip on an ordinary day writes the new due date at once, with no confirmation.|annotate:day cell=Drop here}}

Dropping on a day at or before the item's own start works differently. Nothing saves yet.

A small chooser opens instead, asking whether to shift the whole run or keep the start where it is.

{{shot:03-day-grid-chooser|Dropping before an item's start opens a chooser instead of writing immediately.|annotate:Shift the whole run=Pre-selected choice}}

Drop a chip back on the day it started from and nothing changes. No write happens either way.

3Retime work on the Agenda

The Agenda groups work into week bands. A drag here only tells the app which week, never which day.

Drop a row on a week band and a chooser opens, asking which day that week. Nothing saves until you pick one.

{{shot:04-agenda-day-chooser|Every Agenda drop opens a day chooser, even a drop back on the item's own week.|annotate:Which day that week?=Pick a day to finish}}

Pick a day and the row moves there, in that band's date order.

Cancel instead, and the row returns to where it started. Nothing is written.

4Retime work on the Spans lane

On Spans, dragging the middle of a bar moves its whole run — start and due date together.

The bar's length stays exactly the same.

{{shot:05-spans-whole-bar-drag|Dragging a bar's body moves start and due together, keeping the run's length.|no-annotation:the shot is a before/after comparison of one bar's position, not a single control to box}}

Dragging one end of the bar changes only that end. The other end never moves.

An end can never cross past the opposite one.

{{shot:06-spans-edge-drag|Dragging a bar's cap changes only that one date; the opposite end stays fixed.|annotate:cap=Drag to change one end}}

5Retime work on the Deadlines lane

On Deadlines, drag a flag to a new day and it writes immediately — the same single-write rule as the Day grid.

A flag landing on a Friday renders in flip mode. Its name moves to the left of the dot, so it still fits inside the week row.

{{shot:07-deadlines-friday-flip|A flag dropped on a Friday flips its name to the left so it still reads inside the row.|annotate:Friday flag=Flips here}}

6Give an undated item its first date from the Unscheduled tray

Every item with no date sits in the Unscheduled tray. It's a pill in the Calendar toolbar showing how many are waiting.

Click the pill and a panel docks on the left, showing those items as chips.

Drag one out onto a day and a chooser asks whether that day should be its due date or its start date.

{{shot:08-unscheduled-tray|Dragging a chip out of the Unscheduled tray onto a day opens a chooser for the item's first date.|annotate:Unscheduled=Click to open the tray}}

The tray stays docked as you scroll. It never accepts a dated item dragged back into it — it only gives dates out.

7Add work with + Add

Every cell an admin can edit shows a small + Add button on hover. Without admin rights, no cell shows it anywhere.

Click it and a form opens, asking only what the cell couldn't already tell it.

If rows are labels, it asks which project. If rows are projects, the project is already fixed — it never asks.

The choices offered are always limited to what's actually on this page. A project or column that isn't part of the roadmap never appears, however you search.

8See what your addition writes back

On the Timeline, the quarter column you clicked becomes the card's due date — its last day, specifically.

The trailing Later column leaves the card undated instead.

On Status, the workflow stage you clicked is written in the same request that creates the card. It opens already sitting in that stage.

On the Calendar's Day grid and Deadlines lanes, the day you clicked becomes the due date directly.

On the Agenda, a short "which day that week" question comes first, since a week band alone isn't a date.

{{shot:10-calendar-add-writes-date|Adding from a Calendar cell writes the clicked day as the due date immediately.|no-annotation:the shot confirms a written date on the grid, not a control to press}}

Whatever you add appears in its cell right away, before the server confirms.

If the save fails, it quietly disappears again. No error banner, no toast.

9Add more than one item at a time

Open the form's multi-add mode from any cell and type more than one line.

Each line becomes its own card, carrying that cell's project, column, and date.

These cards don't paint immediately the way a single add does. They show up the next time the page loads.

10Reach + Add on a touch device

On a laptop or tablet with no hover, every cell's + Add is visible at rest. You can see it before touching anything.

{{shot:11-touch-add-visible|On a no-hover device, "+ Add" shows at rest instead of waiting for a hover that can't happen.|annotate:+ Add=Visible without hovering}}

On a mouse, nothing changes. The button still only appears when you hover the cell.

1Open the Calendar

Choose Calendar in the view toggle, next to Timeline and Status.

The quarter board is replaced by month sections, each a stack of full-width week rows.

A sub-view toggle appears beside it, reading Day grid · Agenda · Spans · Deadlines. Day grid is active first.

Viewing the Calendar isn't limited to admins. Anyone on the team sees the same months, week rows, and cards.

Which view and sub-view you land on is remembered for you alone. It never changes what a teammate sees opening the same roadmap.

2Read the month scaffold

Each month's header names how many cards are targeted inside it — "0 targeted" for an empty month, or a real count for a busy one.

A month with trouble in it flags that too: a red count for anything overdue, an amber count for anything off track.

Each week gets its own full-width row, labeled by its starting date. Its day columns run Saturday through Friday.

The current week carries a "This week" chip. Today's own date is filled in the brand color and marked "Today" — no other day is marked that way.

A week with nothing targeted in it still gets its full row. Empty weeks are visible gaps, not collapsed away.

Days that spill into a neighboring month render dimmed. A card targeted on one of those days shows there too, without counting toward that neighboring month's total.

A card sits on its target date, full stop.

Even once it's overdue, the Calendar never slides it forward the way Timeline rolls overdue work into the current quarter.

A done card moves to the day it actually shipped, marked with a green checkmark and dimmed styling.

3Change the date range

Click the range pill in the toolbar to open a menu of six ranges: This month, Rolling 3 months, This quarter, Rest of year, All scheduled, and Custom range….

Each of the first five rows shows its own concrete months and how many cards fall inside it — the same counting rule the month headers use.

A checkmark marks whichever range you're currently on.

Stepping the window with the toolbar's arrows leaves no row checked — the pill's own months are now the only truth.

All scheduled fits the window to the work itself — from the month of the earliest targeted card through the month of the latest, empty months included.

Your range choice is yours alone. A teammate who's never touched it still opens the roadmap on its saved default, whatever range you last picked for yourself.

4Filter to a label or an owner

Choose a label from the labels filter to see only that label's cards. Every week's count updates to match what's actually visible.

The label filter and the sub-view you're on are saved with the roadmap.

The owner filter is not — it resets to All owners each time you come back.

Switching between Day grid, Agenda, Spans, and Deadlines never drops a filter you've set. The same cards, range, and label stay in place across every one.

5Work the Day grid

A card renders as a one-line chip in its label's color, truncated with an ellipsis if the day column is too narrow.

Overdue work carries a red dot on its chip. Off-track work carries an amber one.

Hover an empty day and a team admin sees a dashed "+ Add" affordance appear inside it. A team member without admin rights sees no such affordance there.

Clicking + Add opens the same Add From Anywhere modal the swimlane board uses, locked to this roadmap's projects. The new card lands on the day you clicked.

Click any chip to open its item detail sheet, with the Calendar still visible behind it.

Changing its target date there moves the chip at once, with no page reload.

6Work the Agenda

Each week lists its cards as one-line rows, in date order, led by a day-and-date badge.

A row carries its label chip and its owner's avatar and name.

Today's row is highlighted in the brand color with a "Today" chip. An overdue row carries a red "Overdue" chip.

A shipped card shows a green checkmark, its name struck through, and a "Shipped" chip naming the date.

Every date badge carries its true weekday, even across a month boundary. No two sub-views ever print a different weekday for the same date.

Click a row to open its item detail sheet, exactly as a Day grid chip does.

7Work the Spans lane

A card with both a start and a target date renders as a bar in its label's color, ending in a solid target tick.

A card with no start date renders as a single-day pin instead of a bar.

A bar that crosses a week boundary appears in both rows, capped and continued with a small arrow where it crosses.

An overdue bar turns red in every week it touches. A done bar turns green with a checkmark before its name.

A dashed line marks today, running through only the current week's row.

Click a bar to open its item detail sheet, from either week it appears in.

8Work the Deadlines lane

A card appears exactly once here, as a flag dot on its target date.

Even a card that runs for over a week shows nothing on the days leading up to it.

The flag wears its label's color.

A deadline landing on a Friday keeps its name to the left of the dot, so the whole entry stays inside its week.

Overdue and off-track flags carry the same red "Overdue" and amber "Off track" chips the other sub-views use.

Click a flag to open its item detail sheet.

9Collapse a month

Click a month's headline to collapse it. Its week rows disappear, but the headline stays — name, count, and any overdue or off-track flags included.

Expanding it again shows exactly the cards it held before.

A collapsed month stays collapsed the next time you open that roadmap, across all four sub-views.

It's yours alone, and it doesn't follow you to a different roadmap.

Anyone can collapse a month, admin or not. Doing so only changes what that one person sees.

The Unscheduled tray is never affected by collapsing — it keeps showing every card in it regardless.

10Hide weekends

Turn on Hide weekends in the Calendar toolbar and Saturday and Sunday drop out of every week row, on every sub-view.

A card dated on a hidden day isn't lost. Its week carries a marker naming how many items fall on hidden days, and activating it reveals them.

{{shot:14-hidden-day-marker|A week with weekend-dated items carries a marker naming how many fall on hidden days.|annotate:marker=Reveals hidden items}}

A bar that crosses a hidden weekend still draws as one continuous bar, with no gap where the weekend used to be.

You can't drop a card onto a hidden day either — dragging one over the gap where Saturday and Sunday used to be shows no drop target.

The setting is per person and per roadmap. It survives you leaving and coming back.

It doesn't reach a teammate, and it doesn't follow you to a different roadmap.

On a fresh visit to any roadmap, weekends start hidden by default. The toolbar control reads "Hiding weekends" in deep purple to say so.

11Schedule an unscheduled card

A card with no target date at all doesn't disappear. It lives in the collapsed Unscheduled pill in the toolbar, showing a count.

Expand the pill and a tray docks along the calendar's left edge, listing each undated card as a chip in its label's color.

The tray holds its place across Day grid, Agenda, Spans, and Deadlines. It stays on screen while you scroll the dated grid underneath it.

Undated cards are never counted in any month or week. Changing the date range never touches the tray — undated work is range-independent.

1Open your Scorecard

Your Scorecard is the team's Data view. Rows are your Measurables, columns are weeks, and the left of the grid stays pinned as you scroll sideways — the Measurable, Owner and Target columns never slide out of sight.

The bar above the grid controls what you are looking at. Three pills switch the period between Weekly, Monthly and Quarterly. A Year picker sits beside them. An owner picker reading All owners narrows the grid to one person's rows, and the Active only pill hides Measurables that have been archived.

Three more controls sit on the right of that bar if you are a team admin: Set Targets, a settings menu that switches the grid between expanded and compact and turns the notes column on, and a button that downloads the Scorecard as a CSV.

When the page loads, the grid scrolls itself so the current period's column is on screen — whichever way round your weeks are ordered. You should not have to hunt for this week.

Switch to Monthly or Quarterly and read the cells carefully, because this is the part people get wrong. A month cell is not the month's weeks added together — it shows one representative week from that month. A Measurable whose May weeks read 55, 45, 47 and 30 shows 55 for May, not 177. Quarterly works the same way.

There is a second thing happening in those views. The on-track and off-track colouring is judged against your weekly target scaled up to the period — roughly four and a third weeks for a month, thirteen for a quarter — while the Target column goes on displaying the weekly figure. So the same number can show green in Weekly and red in Monthly against what looks like the same target. The colour is comparing against more than the column says.

Once any Measurable on the card is connected to a source, a legend appears beneath the grid explaining the marks: On track, Off track, N/C for "no value delivered this week", a dot for "Edited after sync", and the reminder that "All cells editable — click a week to type over a synced value". A card with nothing connected shows no legend, because it has no marks to explain.

2Record this week's number

Click the current week's cell on your row, type the number, and press Enter — or just click somewhere else, which commits it the same way. The number paints in the cell immediately, before the server has confirmed anything, and the save finishes in the background. Refresh the page and it is still there.

Here is the behavior worth knowing about: a number stays in the week you entered it into. If you record Sunday afternoon and come back Monday morning, after the Scorecard's current week has rolled over, your number is still sitting in last week's column — unchanged, not zeroed, not carried forward. The new current week's cell is simply empty, which means "not entered yet" and reads differently from the number you recorded.

An empty week reads as a dash once the Measurable has a target. Before a target is set, the same empty cells render a question mark instead — so a row full of question marks usually means nobody has set the target, not that nobody has recorded anything.

Screenshot not captured this run: no Measurable in the current Examp.ly fixture has an unset target, and this pass did not create one (see findings.md). The behavior described above is unchanged from the last verified capture.

Past weeks work exactly like the current one. Click any earlier week's cell, type, commit, and it persists — no week behaves differently from its neighbours.

A cell you are not allowed to edit simply does not respond. Clicking it does nothing: no message, no error, no explanation. If a cell will not open for typing, you are not the owner, not the assignee and not a team admin on that row.

You do not have to refresh to see other people's work. When a teammate records a value in their own session, the number appears in your grid on its own, and nothing else on the page flickers or reloads.

3Add a Measurable and set it up

Team admins get a + Add Measurable button above the grid. It opens the same sheet you get when you open an existing Measurable — one edit surface, in create mode. Name it in the header, where the field prompts "Give it a name…".

The sheet's Settings tab is where the definition lives. Target is the number to hit. Unit takes a symbol like "$, %, #". Direction is Higher is better or Lower is better, which decides which side of the target counts as on track. Target Period offers Weekly, Monthly, Quarterly and Yearly. Aggregation — Sum, Last or Average — decides how weeks combine when the grid is read by a longer period. Owner searches your team members.

Display is the small one that changes how the row reads all year. Leave it on Show Full Numbers and 1,500,000 shows as $1,500,000. Switch it to Abbreviate Numbers and the same value shows as $1.5M. It is set per Measurable, so a revenue row can abbreviate while a defect count does not.

The Description tab holds one box for context — the prompt reads "Optional description". There is no per-tab save: one Save in the sheet's footer commits everything you changed on every tab, and Cancel sits beside it.

Back on the grid you can change a target without opening the sheet at all. Click the Target cell, type, and press Enter or click away. A Measurable with no target yet shows + Set target to anyone who can edit it, and a plain dash to everyone else.

Each row carries a ⋮ menu that appears when you hover it. A team admin gets Edit and Archive, plus Move up and Move down for reordering.

The two reorder items are fussier than the rest: they appear only in Weekly view with no owner filter applied. Narrow the grid to one person, or switch to Monthly, and Move up and Move down quietly disappear from the menu, leaving Edit and Archive. Clear the filter and go back to Weekly to get them back.

Archiving asks first, and the confirmation tells you the row is only hidden: "will be hidden from the scorecard. You can view it again using 'Show Archived'." Turn the Active only pill off to bring archived rows back into view — their menu swaps Archive for Restore.

A member who is not a team admin — even the Measurable's own owner — opens that menu to find nothing in it, which is worth knowing before you go looking for a control that is not there for you.

4Let a number fill itself in

If a system somewhere already knows this number, stop retyping it. Open the Measurable and go to the Data Source tab. A card at the top of the tab says "This Measurable can fill itself in" and explains the deal: each week's value lands in the matching week on the Scorecard, cells stay editable, and every change — synced or typed — is logged.

The Data Source picker offers four choices: Manual, Google Sheets, Other API and Roll-up.

Choose Other API and the connected configuration appears beneath. If your account already has saved connections, they are listed — pick one and you are asked for no credential at all, because the saved connection carries its own.

If there is nothing saved, or you would rather not wait on an admin, type the endpoint and an API key straight into the fields on this tab and press Connect — Enter in the key field does the same thing. The key masks itself as you type. You do not need to be an account admin, you are never told to go somewhere else, and this works from wherever you opened the sheet, including from inside a running Level 10 or a 1-on-1.

Next, tell the Scorecard which part of the response is the number. Under Turn the response into a value the tab lists the fields it found and you click the one that holds the value. Note the field tagged Sets the week — that is the date the Scorecard reads to decide which week each value lands in, which is why a connected Measurable fills the right column rather than always the current one. If a week gets more than one value settles the tie, with Latest (keep the most recent), Sum (add them up), Count (how many entries) and Average (the mean of them).

Press ▸ Test data source before you commit to anything. The button paints its own feedback first, then shows the number it actually fetched and the week it would land in. Nothing has touched your Scorecard yet — the hint beside the button says so plainly: "Runs the request with the saved credential. Nothing is written to the Scorecard until you save."

Set How often it syncs — Weekly, aligned to the Scorecard week (Mondays, 6:00 AM), Every weekday morning, or Only when refreshed by hand — and press Save. Two things happen. The row grows a chip naming the connection with its last-synced time beside it, and every past week keeps exactly the value it already held. Connecting a Measurable changes nothing retroactively.

From then on the number arrives on its own. The week's cell fills with the fetched value and nobody typed it.

When a pull fails and its retries are exhausted, the Scorecard says so instead of inventing a number. The week reads N/C — not last week's figure, not a substitute — and the row's chip turns amber with needs attention and a Reconnect link ready to click. Every past week keeps the value it already had.

A synced number is not the last word. Click the cell and type over it: the cell takes the edit, a small dot appears in its corner marking it as edited after the sync, and hovering it names who changed it. The change is filed as an Override, so nobody has to guess later whether the number came from the source or from a person.

To go back to typing, set Data Source to Manual. The connected configuration disappears, the row's chip goes with it, and every value you ever synced or typed is still sitting in its own week. As the tab puts it: "Manual entry: Each week, the owner (or anyone who can edit this Scorecard row) types the number straight into the week's cell. You can switch back to a connected source anytime; nothing is lost."

Google Sheets works a little differently. You pick the Google account the sheet is read with from the connections an admin has already authorized — the helper text is explicit that admins connect one once on the Integrations page and no credential is entered here. Then you paste the sheet's link into Spreadsheet and name the exact Tab and Cell the number lives in.

It is one cell, not a range: "One cell, not a range. B2 works; B2:B10 does not." There is no test control until you have saved, because the preview reads the saved binding rather than what is still in the fields. And as everywhere on this tab, "Nothing syncs until you save. Past weeks stay as they are."

5Roll several numbers into one

A Measurable can be the sum or the average of other Measurables instead of a number anyone types. On the Data Source tab, set the source to Roll-up. Roll-up Type offers Sum and Average.

Then pick the parts under Measures to Roll Up. A Team picker lets you browse any team you have access to, and the list you build can mix them — a component that lives on a different team is shown back to you with that team's name beside it, so you can tell where each piece came from without going to look.

Press Save and the sheet closes onto a row that has already changed: it carries a Roll-up badge beside its name and its current-week cell shows the total, with no refresh. After that it keeps itself current — record a value on any component, on any team, and the roll-up recalculates the moment the component commits.

Open a roll-up's Settings tab and you get a Component Measures block at the foot of the tab listing every part by name with its current-week value, and a Make changes link that takes you straight back to Data Source to edit the composition. A Measurable that is not a roll-up shows no such block at all.

One consequence to expect: a roll-up's cells do not take typing. Clicking a week on a roll-up row does not open it for editing, because its values are calculated from its parts. Connected and manual rows stay editable; roll-up rows do not.

6Check a number's history

Every Measurable keeps its own record of what happened to it. Open the Measurable and choose the History tab — its label carries a badge with the number of entries waiting inside.

The feed is grouped by day, newest first, and it logs more than values. A sync shows as the source itself doing it, named and timestamped, with the week it filled. A hand edit over a synced value carries an Override tag and shows the old and new numbers as a pair. A change to the target shows the same way, with the person's avatar. Connecting a source and disconnecting one are both logged. And a failed pull sits in the feed highlighted amber, saying the week was left N/C and carrying a Reconnect action right on the entry, so you can fix it from where you found out about it.

Four filter pills narrow the feed: All, Values, Settings and Connection, each showing its own count. Pick one and the entries that do not belong disappear, along with any day that has nothing left in it.

You do not need to reload to keep up. If someone else overrides a value while you have the feed open, the new row arrives in it on its own.

7Manage the account's Connections

Credentials that more than one Measurable should share are created once, on the Integrations page, in the Connections section. The section is marked Admins only and carries a count of how many connections the account holds.

Press New connection and a panel asks for three things: a Name, a Base address and an API key. Save it and the key is shown to you in full exactly once, under a warning you should take literally — "Shown once — save it now. It won't be shown again." From then on the card shows it masked, and there is no way to read it back.

Each card carries what you need to trust it: Connected or Needs attention, when it last synced, who added it and when, and Used by a count of Measurables. Test paints its own feedback first and then flashes "✓ 200 OK" when the connection answers.

A connection whose authorization has lapsed says so instead of failing quietly. The card turns amber, reads Needs attention, and states the consequence in plain terms — the token expired, and Measurables on this connection show N/C until it is reconnected — with Reconnect as the card's main action.

Disconnect asks before it does anything, and it names every Measurable it would break: "These Measurables will stop syncing and show N/C until you reconnect:" followed by the list. Nothing is disconnected until you confirm.

A member who is not an admin sees the same list read-only — names, types, statuses and used-by counts, without New connection, Test, Disconnect or Reconnect. That gate belongs to this page alone. On a Measurable they can edit, they can still enter an endpoint and key inline and connect it themselves, exactly as Step 4 describes.

Beneath the connections sits Available integrations, a tile per named system — "Named systems can connect with one authorization." A tile whose system you have already connected says so, so you are not left wondering whether you did it twice.

8Review the Scorecard in your Level 10

The weekly meeting does not get its own copy of the numbers. The Level 10's Agenda has a Scorecard section showing the same rows you just left — the same values, the same source chips, the same last-synced times. If a number is missing, record it right there in the meeting; the cells behave exactly as they do on the Data view, Enter and click-away both.

The control that matters here is a filter by person. Pick someone and the grid narrows to their rows immediately — no reload, no spinner, no skeleton — and the picker shows who you chose. Choose All owners to bring everyone back. It works from the keyboard too: open it, arrow to a name, press Enter. Pick someone who owns nothing on this Scorecard and you get an empty section with the picker still sitting there, so you can undo the choice from where you made it.

What the meeting's Scorecard deliberately leaves out is the rest of the filter bar: there is no year picker, no period toggle and no archived switch. The grid stays on the current year's weeks so everyone in the room is reading the same thing.

The Measure edit sheet opens from here too, with everything it has anywhere else — including the Data Source tab, so a Measurable can be connected mid-meeting without anybody leaving the meeting.

9Prep before the meeting

The weekly 3-Step Prep is where you fill in your numbers before the room needs them. It opens by asking "How do you want to prep?" — Step by step walks you through one section at a time, and All on one page puts everything on one scroll. Whichever you pick you get the same sections, and you can switch between them.

The Measurables step shows only your own rows — the help text says so: "Enter this week's number for the Measurables you own. Only your own Scorecard rows show here." Each row gives you three columns: Target and Last week to read, and This week to type into.

Two small buttons sit on each row. + headline attaches a headline to that number, and + issue raises an issue about it — the tooltip nudges you when the number is short, asking whether you are missing the target or worried about the period ahead.

This is the one place where typing a number does not save it. Enter does nothing here and neither does clicking away — nothing is written until you press Submit prep at the end, which sends the whole prep at once. The footer says as much while you work: "Nothing saves until you submit".

If you own no Measurables, the section is not there at all — it is skipped, not shown empty. And what you do type lands where it is needed: the prep's Measurables feed the Scorecard review in that week's Level 10.

10Track personal Measurables in a 1-on-1

A 1-on-1 has its own Measurables section, for the numbers that belong to one person rather than the team's card.

The + button in the section header creates one, using the same sheet you already know. Watch the Owner field: it defaults to you, so creating a Measurable for the person you are meeting with means switching Owner to them. Do that and it appears in their Measurables — on their screen as well as yours — with them as owner, and they can record into it and edit it themselves.

Recording is quicker here than on the grid. Click the card's big number, the value opens ready to overwrite, and Enter commits it. Type something that is not a number and the card tells you so: "Enter a number". Clicking the card's name opens the full edit sheet.

To pull existing team Measurables onto the 1-on-1, use the gear menu's Choose Measurables. The dialog is titled Select Team Measurables:, lists a team's Measurables with their owners as checkboxes — the ones already on this 1-on-1 come up pre-checked — and commits with Save.

Each card carries a 13 WKS graph with Last wk beneath it. Read that chart as a shape, not a calendar. It plots the last thirteen values that were actually recorded, spaced evenly across the card, so the line runs the full width whether those thirteen readings came from thirteen consecutive weeks or from eight months of patchy recording. Nothing is invented to fill a week nobody recorded — but nothing marks the gap either, so the horizontal distance between two points is a position in the sequence, not elapsed time.

11Point a team at another team's Scorecard

A team that should read another team's numbers rather than keep its own is pointed at them from the team's page. Open the team, go to its More tab, and press the pencil on the Inheritance card. Team admins get the pencil; everyone else reads the card as it stands.

Set Inherit scorecard from to the team whose Scorecard this one should show, then press Save. Nothing is written at the moment you change the picker — Save commits it and nothing else does. Cancel puts the card back to the values it had, and the team's Scorecard source is untouched.

After that, the inheriting team's Data view opens with a banner naming the team it reads from, and the parent's rows show read-only. The + Add Measurable button is not offered on an inheriting Scorecard, because the Measurables belong to the other team.

Ownership travels with the Measurable, not with the screen. If you own a Measurable, you can record into it from whichever team's Scorecard you are looking at it on, and its edit sheet opens editable for you there — the same rights you have on the team that owns it.

12Ask the AI

If you would rather ask than look, the sidebar's Chat tab opens the assistant — Cmd+J opens and closes it too. Ask what a Measurable reads this week and you get the number the cell shows. It makes no distinction between a value that synced in and a value someone typed: both are just this week's number.

1Open your team's Level 10

Go to Meetings. The Level 10 is the first of three tiles, marked with a green Included pill and an EOS Pure pill beside it.

Quarterlies sits second and 1:1 (One-on-One) Meetings last. Only the first two are marked EOS Pure.

2Prepare before the meeting

The day before your meeting and the day of it, a banner appears on your main pages.

It reads "Tomorrow = [your team] update day." or "Today = [your team] update day." with a green Update measurables + progress button.

The day-of banner shows all day. There is no cutoff hour, and each person's "today" is their own time zone's date.

3Work the agenda in order

The Agenda tab runs top to bottom: Segue, Scorecard, Rocks, Headlines, Done, Issues, To-Do, then Conclude.

The page header names the week you are in, like Week 35 · Aug 24, 2026.

4Post your headlines

A headline is a piece of team news that lives seven days, from one meeting to the next.

Type it into the compose row at the bottom of the Headlines section and press Enter, or click Add headline beside it.

New headlines are added at the bottom of the list, next to the form, and the form stays where it is.

Your own photo shows on the headline straight away — not initials, and not after a refresh.

5Read the scorecard

The Scorecard section shows the team's measurables for the week, exactly as they read on the Data screen.

A measurable fed by an integration carries its source chip and its last-synced line here too. A roll-up carries its Roll-up badge.

Every row shows its owner's avatar and name — their photo, or their initials if they have none.

6Review the rocks

The Rock Review section opens on this quarter's rocks.

Its header carries two pills: This quarter and Last quarter. Click Last quarter and the list repaints immediately.

The subtitle then reads that last quarter is showing and names it, and this quarter's rocks are gone from the list.

Your choice is remembered — when you leave and come back, and in a fresh session too. Switching back is remembered the same way.

7Work the to-dos and issues

The Agenda's To-Do, Issues and Done sections are the meeting's working list.

Add a to-do by typing into the section's Add to-do… field and pressing Enter. The card appears before the save finishes.

That inline field has no due date control on it.

Mark something done from its completion circle and it moves into Done in the same paint, with no reload.

Done keeps a range control of its own, set to last 7 days.

An issue keeps its Issues marker even while it sits in the Issues section — the marker says what it is, not where it is.

8Turn an issue into a to-do

This is how an issue gets solved rather than re-discussed. Open the issue from the Issues list.

Above its details sits a tip card: "Issues get solved when they turn into To-Dos — create one to resolve this Issue."

It carries one button, Create To-Do to resolve this issue.

9Rate the meeting

The agenda ends at Conclude, and Conclude is a roll call.

A Rate the meeting block asks "How effective was today's Level 10? 1–10, gut check."

It lists every attendee with their avatar and an empty – placeholder. A YOU badge marks your own row.

Beside it a Meeting score block reads the average and how many have rated, against a goal of 8.

1Open the team's Issues list and read it

Go to EOS Components and pick the Issues tab. The heading reads Issues with a count of the rows in view.

You land on the long-term list, showing open issues. The filter at the left of the bar is set to Long-term (V/TO), and the status beside it is set to Open.

That filter has three settings: Long-term (V/TO), Short-term (L10) and Both.

So the two lists a team keeps are two settings of one control, not two places on the page.

Each issue is its own card on the list's gray surface, with a gap between one card and the next.

There are no column headings above them, and nothing to sort by.

A row carries a lot in one line.

Reading across: its position number, the issue's name, a V/TO or L10 chip saying which of the two lists it is on, and the date it was opened.

Then its comment and attachment counts, if it has any, and any labels the team has put on it.

Below those sit context chips saying where it came from, and out at the right the avatar of whoever raised it and a status dot.

A team admin's row also carries a drag grip and an archive control.

2Add an issue to the list

Team admins get an Add Issue button.

It opens the same add box you get anywhere else in the product, in its usual place on the screen — not a popover, not anchored to the list.

You are not asked to choose where the issue goes.

With the long-term list in view, the box opens with its destination already set to Long Term Issues for the team whose list you are on.

Type the name and save. @mention a teammate in the name and the issue is created assigned to them.

The new issue appears at the top of the list straight away, looking exactly like every other row: no spinner, no greyed-out state, no pending badge.

The save finishes in the background. If the server refuses the create, the row is taken back out of the list.

There is no second way in. This screen has no inline add box, visible or click-to-reveal.

The button is the only way to create one here, and a member who is not a team admin has no way to add on this screen at all.

3Raise issues while you prep for the meeting

Most of a team's weekly issues are not typed into the Issues list.

They are typed into the prep that runs before the meeting, on the screen titled 3-Step Prep, at its Issues To Address step.

You reach it from Customize, where a 3-Step Prep tile opens it. That tile is the only link to prep in the product.

Nothing on the Level 10 itself points at it, so it is worth pinning if your team preps every week.

You do not need to be an admin. Anyone prepping for the meeting can put issues on the team's list this way.

The step tells you what it wants. The help reads "👈 Add any issues your team needs to address", and the field prompts "Separate your issues by hitting the 'enter' key".

Beside the field, a Current Issues: list shows what the team already has open. You are adding to a list you can see, not typing blind.

Every line you type becomes one new team issue, on the weekly list the meeting works through.

Nothing is saved until you submit the prep, which the footer says as you type.

4Raise an issue during the meeting

The other place issues get raised is the meeting itself, when a to-do turns out to be stuck.

You do not retype it. You move it.

On the Level 10's Agenda tab, pick up the to-do from the To-Do section and drag it into the Issues section.

While you are dragging, the Issues section rings and tints, with a floating tag reading "DROP INTO ISSUES".

Back where the to-do came from, the To-Do section holds a dashed placeholder reading "MOVING…".

Let go and it is in Issues immediately, before the server has confirmed anything.

The move finishes in the background, and the Agenda does not reload.

5Send something to the long-term list from wherever you are

Anything you are looking at, anywhere in the product, can go on the team's long-term issues list without navigating to it.

The compass dock has a Long-term Issues tab. It sits behind the … at the end of the dock's tab strip.

Open it beside whatever you are working on and drag the card onto it.

It works from the Level 10's board and from its agenda, from a 1-on-1's Issues list and its Next Steps list, and from a project's board, table and Gantt.

The dock's list belongs to a team, and the tab shows which one at the top.

On a good drop the item appears on the list at once, before the server confirms.

The tab then refreshes behind it, so the fetched row replaces the painted one. That refresh is the only feedback there is: no success message appears.

Drop something that is already on that list and no second copy is added. A brief message tells you it is already a long-term issue.

Screenshot not captured this run: reproducing the duplicate-drop refusal needs a first drop to actually land, and this run's browser automation could not commit that drop via synthetic input events (the drag-hover states painted correctly — see the two shots above — but releasing over the target never registered). See findings.md. The behavior described above is unchanged from the last verified capture.

Here is the part worth trusting. The drop moves the item and leaves the rest of it alone.

Nobody is assigned, re-assigned or notified, the due date does not move, and it is added to nobody's day plan or work session.

What does change is where it lives. A to-do you drop this way becomes an issue on the long-term list, so it leaves the team's weekly one.

On a project's Gantt it keeps its scheduled dates too.

There you must pick the item up from its row in the left-hand list, because dragging its bar on the timeline reschedules it instead.

Screenshot not captured this run: this shot depends on the same completed-drop mechanic as the one above, which this run's automation could not commit (see findings.md). The behavior described above is unchanged from the last verified capture.

6Turn a discussed issue into a to-do

This is the step the whole feature is built around.

An issue that has been talked through is worth nothing until somebody owns a piece of work on it. So the issue asks for that work itself.

Open the issue from any list it appears on. Its sheet opens over the page.

An issue with nothing recorded against it shows a tip card, reading word for word: "Issues get solved when they turn into To-Dos — create one to resolve this Issue."

The card carries one control, a button labelled Create To-Do to resolve this issue.

You get the same prompt whichever list you opened the issue from. It is one shared sheet.

Press the button and the form opens in place, in the slot the tip card was in.

The sheet does not navigate, nothing opens over it, and the issue's own details stay where they are.

The form is labelled New To-Do — Resolves this Issue, and it already knows almost everything.

The title is filled in with the issue's own name, and you can type over it.

The description is empty and prompts "What will we do to resolve this?" The issue's description is deliberately not copied into it.

Three pills beneath carry the owner, a due date, and the destination: the team's Level 10 to-do list.

The only controls are Cancel and Create To-Do.

There is no status to choose, because a new to-do is always Not started.

The due date is worth a second look, because it is not the issue's.

It is the to-do's own creation date plus seven days — the weekly rule — shown as a readable date rather than an empty "set a due date" prompt.

The issue's own due date, up in its details, is untouched.

Press Create To-Do — or just press Enter in the title field, which is the same path.

The button paints its working state first, in that frame, before the server has answered anything.

It goes pressed and busy, and its label reads "Creating To-Do…". Pressing it again does nothing.

The Steps count on the tab strip ticks up by one in that same frame, before the server has answered.

Then the form is replaced, in the same slot, by what you now have.

First a confirmation line with a green check. It names the Level 10 the to-do landed on and finishes "— also shown under Steps on this Issue."

An Undo control sits at the right of that line.

Under the line is a compact card for the to-do, carrying its completion circle, its title, and four pills: Not started, the due date, the owner, and the destination.

The prompt is gone, because the issue is not asking any more. No toast appears at any point in this.

One to-do now exists in two places at once.

It is on the meeting's To-Do section, where it appeared immediately without a reload, and on the issue's own Steps tab.

It does not show up twice on the meeting. The Issues section still holds the one issue it came from.

On the Steps tab it is an ordinary step row with exactly one chip on it, reading Resolves this Issue.

No heading, no divider, no separate section — a step row plus one chip.

That chip follows the recorded link and nothing else.

A step somebody typed by hand with word-for-word the issue's own title carries no chip. An issue like that still shows the tip-card prompt, whatever its steps happen to be called.

A step added afterwards does not take the chip either. It stays on the to-do's row.

The card is permanent, and that is the point of it.

Close the sheet and reopen the issue minutes or days later, and the card is still in the same place, with the to-do's current owner, status and due date.

The prompt does not come back.

Anyone who can see the issue sees the same card. It names the to-do's owner, not whoever is looking at it.

The green confirmation line and Undo, though, belong to the moment you created it. Days later they are gone, and the card is all that is left.

If you created it by mistake, Undo takes back all of it in one action.

The confirmation and the card disappear before the server confirms, the tip card returns with its button at its resting label, and the Steps count drops back.

The to-do is gone from the meeting's To-Do section and from Steps. Again, no toast.

7Move an issue between this week and the long term

There is no control for this on the Issues list.

The move lives on the issue, on its Alignment/Spaces tab, which lists every place the issue appears.

The row titles tell you which list you are on.

A weekly issue's row is titled with the team's Level 10 and carries the sub-line "Weekly L10 · "Issues" section".

A long-term issue's row is titled with the team's long-term issues list, and nothing on that row says Level 10.

To send a weekly issue to the long-term list, press Move on that row, choose the team's long-term issues list, and press Move here.

The row retitles the moment you confirm — before the save completes, with nothing to reopen and no refresh.

Everything asserting the old membership updates at once.

The issue leaves the Level 10's Issues section immediately while your sheet stays open, and the heading above the issue's name changes to name its new list.

One thing to read carefully. While you are still on the Level 10, that meeting keeps a row of its own under Appears on, marked Current view.

It is naming the screen you are on, not a list the issue is still on. Open the same issue from anywhere else and only the long-term list is named.

The trip back uses a different control, and this catches people out. A long-term row carries no Move and no remove.

To put the issue back on the weekly list, use Add to a surface… and pick Level 10 · Issues for that team.

It reappears in the meeting's Issues section immediately.

The move takes edit access on the issue. Without it, Add to a surface… is not offered to you.

The row's Move button is still shown, though, and a move you start that way is refused when it tries to save.

8Complete an issue from its row

When an issue is done with, you close it from the list without opening anything.

Click the completion circle at the left of its row, or move keyboard focus to that circle and press Space.

Nothing asks you to confirm.

The issue is marked complete and its row leaves the list immediately, before the server confirms. The save finishes behind you.

Reload the page and it is still complete. One click is always enough, including on an issue you added a moment ago.

The row leaving is not the issue vanishing.

This list is the team's open issues, so a completed one is not shown on it at all. You un-complete it where done items are shown, on the issue itself.

On the meeting screens it behaves the same way, with somewhere visible to land.

Mark an issue done in the Level 10's or a 1-on-1's Issues section and it moves straight out of Issues and into Done, with both counts changing.

It is still under Done after a reload, checked off and struck through there.

It does not bounce back, and it is never left struck through in the Issues section it came from.

9Ask the assistant what is being done

If you would rather ask than open the issue, the assistant answers from what is recorded rather than from the names of things.

Ask what is being done about an issue and it reports the to-do that carries the link, naming its owner and its due date.

Those are current values, not the ones they had when the link was made. It reads the issue's other steps out too, with their status.

If the to-do has since been deleted or archived, it reports nothing working the issue.

Ask about an issue nobody has started and you get told that plainly: nothing is working it yet.

That is an answer, not a gap.

It will not guess.

A step named word for word like the issue is described as an ordinary step, not as the thing resolving it.

Asked which step resolves an issue where none carries the link, it answers that none does.

Ask it to create a to-do for an issue that already has one and it tells you one exists and names it before making a second.

Ask it to unlink a to-do but keep it, and it will tell you what that costs.

The only reversal is removing the to-do itself, and it asks before doing it.

Afterwards it reports the to-do gone from the Level 10's to-do list and from the issue's Steps.

1Open the prep from the top bar

The day before your meeting, the top bar reads "🚀 Tomorrow = [your team] update day." Beside it sits a green button, Update measurables + progress.

The notice takes the middle of the bar, between Switch team and the icons on the right. Every other control keeps its place, and the bar does not get taller.

Press the button. The prep opens under the page heading 3-Step Prep, for the team the bar is showing.

The keyboard works too. Tab to the button and press Enter.

On meeting day

On the day itself the message reads "🚀 Today = [your team] update day.", with the same button beside it.

It stays until the meeting ends — its start time plus the minutes in its agenda. After that, the bar is back to normal until next week.

On any other day there is no notice at all. Who sees it, and when it stops, is covered at the end of this article.

2Pick how you want to prep

The first time you open the prep, it asks. A line reads "Prep for [day]'s Level 10 · [your team]", and under it, "How do you want to prep?"

Two cards are yours to pick: Step by step, "One section at a time.", and All on one page, "Everything on one scroll."

A third card, Chat, is greyed out and cannot be picked. It is not available yet.

Under the cards it says "You can switch anytime — we'll remember your choice." Both halves are true.

Next week it remembers

Open the prep the following week and it goes straight into the approach you picked. The chooser does not come back.

A toggle at the top of the prep, beside the context line, reads Step by step and One page. Use it to change your mind at any time.

Switching mid-prep keeps everything

The two approaches are two views of one prep in progress. A win typed in one is already there in the other.

Progress carries across as well. A section you finished in one shows as finished in the other.

What Step by step looks like

A rail on the left, titled Weekly L10 Meeting Prep, lists the six sections and then Review & submit. You see one section at a time.

Above the section a line counts you along: Step 1 of 6, then Step 2 of 6, and so on. Each section you finish earns a checkmark on the rail.

← Back and Next → sit above the hint "Nothing saves until you submit".

Back is disabled on the first section. On the sixth, the button reads Review →.

What All on one page looks like

All six sections sit on one scroll, under a header that stays put while you scroll.

The header reads "📅 For [day]'s Level 10 · [your team]" and counts "0 of 6 sections updated" over a progress bar.

Each section carries a pill that reads Not updated. Touch the section and it flips to Updated, moving the count up by one.

The submit button lives in a bar pinned to the bottom. Step 4 covers it.

3Fill in your six sections

Whichever approach you picked, the sections are the same six, in the same order: Wins, Measurables, Milestones, Headlines, To-Dos and Issues To Address.

Only your own things are in them — the measurables you own, your milestone, your to-dos. Nobody else's appear.

If you own no measurable, there is no Measurables section for you. Your prep has five.

No screenshot this run — every available demo identity currently owns at least one Measurable, so the five-section state couldn't be captured live.

Wins

Two fields: Enter a personal win: and Enter a professional win:.

If you already entered wins this week, they are filled in for you.

Measurables

Each scorecard row you own is listed with its Target, Last week and a This week field. Only the row's owner can fill in This week.

Each row also carries + headline and + issue.

Hover + issue and a tip reads "Not hitting the target of [target] …? Or concerned about hitting next period? Log issues with this button".

No screenshot this run — this is a native browser tooltip and doesn't render in an automated capture.

Milestones

Your milestone sits under its rock. The rock sits under the goal for the year it serves, labelled This year.

The tile reads "Milestone · due end of quarter". Pick On track or Off track — there is no third choice — and add a note in Comments? if you want.

One thing to know about that comment box. A word with # in front of it becomes a new action, linked to the milestone and due at the end of the week.

The section says so itself: "A #hashtag in your comment creates a linked action due end of week."

Headlines

Type each headline on its own line. The help reads "👈 Add more headlines for your Weekly L10", and the field itself says "Separate your headlines by hitting the 'enter' key".

Each line becomes one headline. Headlines expire at the next Level 10 Meeting.

To-Dos

Each of your 7-day to-dos takes a status: Done, Blocked/stuck, Extra steps needed or Not started. A comment is optional.

What each status does happens when you submit. Step 4 covers it.

Issues To Address

The help reads "👈 Add any issues your team needs to address". A Current Issues: list shows what the team already has open.

Type new ones one per line — the field says "Separate your issues by hitting the 'enter' key". Each line becomes one new issue for the team.

A light week

Nothing to update in a section? It shows an empty state, and you move on.

A week with no milestone and no to-dos still has wins, headlines and issues to fill in.

4Submit once

Nothing is saved until you submit. There is no per-section save, so if you leave the prep before submitting, nothing is kept.

Switching between the two approaches is not leaving. Your entries stay.

In Step by step

The last stop on the rail is Review & submit. Its help reads "Nothing has saved yet. Give it a look, then submit — everything posts to [day]'s Level 10 at once."

Each section is summarised with an Edit link, so you can go back and change anything.

The button reads Submit prep, with the hint "This submits everything at once".

After you submit, a success screen reads "You're ready for [day]'s Level 10." and lists where each section went.

In All on one page

The bar pinned to the bottom reads "Nothing is shared until you submit." beside a single Submit prep button.

Press it and the bar confirms: "You're ready for [day]'s Level 10."

No screenshot this run — the week's one real submission went through Step by step; a second live submission wasn't available to capture the One-page confirmation.

What one submit does

The button shows it is working the moment you press it, before anything has come back.

Everything posts at once: your wins, this week's number into the scorecard's history, your milestone's status and comment, each to-do's status, your headlines, your new issues, and a record that you did your prep.

You do not have to touch every section. Wins and one milestone status, with the rest left alone, is a complete prep.

A hashtag in a milestone comment becomes its linked action now, due at the end of the week.

No screenshot this run — the created action wasn't located on the planner in time; the behavior is confirmed by BDD scenario 3.2.5 against the code.

What each to-do status does

Done completes the to-do. Blocked/stuck turns it into an issue for the team to solve at the meeting.

Extra steps needed and Not started both leave the to-do open. Each adds a comment for you: "Status marked 'more work needed'" or "Status marked 'not yet started'".

No screenshot this run — this week's fixture had only one 7-day To-Do, already used for the Blocked/stuck example, so Extra steps needed had nothing to demonstrate on.

If part of it does not save

Sometimes one update fails while the rest go through. The prep tells you which one — the section, and the item by name — with a reason in plain words.

It never gives you a count of nameless failures.

What saved stays saved, and what you typed stays put. Come back and your wins are filled in, with the status you chose still selected.

Retry sends only the part that failed, so nothing that already saved is written twice.

When the retry lands, you see "You're ready for [day]'s Level 10."

No screenshot this run — the deliberate network failure didn't intercept before the real submission completed, and the week's one submission is now used.

1Read the closing quarter's plan

In Review V/TO™, the quarter's business plan renders below the Vision and Accountability Chart buttons.

A long plan clamps and scrolls inside its own panel, so the rest of the agenda never moves — the Expand button releases the clamp. This wasn't directly confirmed this pass: the demo fixture's plan was short enough that it never needed to clamp.

2Fix a number in place

Click any chip or box on the plan you're reviewing. A team admin can edit; everyone else only reads.

Type the new value and click Save, or press ⌘+Enter — both do the same thing.

Cancel or Escape discards whatever you typed instead.

A save that changes nothing writes no history entry — the history is a list of real edits, not a list of visits.

3Draft next quarter's plan

In Establish New Quarterly Rocks, a second panel carries next quarter's plan, marked Required output.

An empty Revenue or Profit field shows nothing to a non-admin. An admin sees a dashed doorway chip instead, inviting them to fill it in.

Write here the same way you edit the closing quarter's plan — click a box, type, and save.

What you write belongs to next quarter's own plan. It never touches the quarter you just reviewed.

4Use Suggest updates

Click Suggest updates on the draft panel to have the app propose next quarter's plan from this quarter's own numbers.

It settles into a summary bar naming how many suggestions it found, each anchored to the field it would write.

Click What I read to see exactly which sources fed the suggestions.

Accept a suggestion and it writes that one field. Dismiss it and nothing is written.

Accept all resolves every open suggestion at once. A field with an open suggestion can't be hand-edited until you accept or dismiss it.

5Read a plan's history

Click History on either plan panel to see every saved edit and accepted suggestion, newest first.

The closing quarter and next quarter keep entirely separate histories. Writing one never moves the other's count.

An admin can click Restore on an older entry to bring the plan back to that state, after confirming.

Restoring doesn't erase the writes that came after it — they stay in the list.

Reading history never writes anything. A non-admin can read the same list but has no Restore button on it.

1Open the Quarterly screen

The agenda lays out in sections — Issues, Next Steps, Check In, and the quarter's Rocks review. Each is its own gray-bordered block.

Every row inside a section is its own card. It carries a name, any context chips it holds, and an avatar for who owns it.

2Open an item

Click an issue's or next step's name to open its item sheet. The page behind it doesn't move — no scroll jump, no reload.

Closing the sheet puts you right back where you were.

A Rock's milestone row works a little differently. The whole row opens it, not just the name.

Clicking it never opens the Rock's own drawer underneath.

3Add an issue or a next step

Open a section's create form and type what you want to add. Press Enter, or click Add issue or Add next step instead.

Either way, the row appears at the top of its list before the server confirms anything.

The form stays open, empty, and ready for the next one.

If a save fails, the row it painted disappears. The form stays open and empty — your typed text is never silently lost or put back for you to notice missing.

Type @ inside the form to mention a teammate. A dropdown lists the team and narrows as you keep typing.

Selecting someone completes their login right into your text. Nothing is created or assigned yet.

Only once you submit does the mention turn into a real assignment, and the row picks up their avatar.

4Mark something done

Click a row's completion checkbox, or open its item sheet and complete it there. Either way the row leaves its section at once, before the server confirms.

It stays gone after you reload the page.

You can complete an item the moment you add it. Click its checkbox once, right after typing it, and it's marked done and the form closes with it.

5Reorder the list

Drag a row by its handle to move it within a section, or across sections entirely. It lands exactly where you dropped it.

Not captured this pass — reliably simulating a mid-drag frame wasn't feasible with scripted input this pass. This claim stands on the BDD, unphotographed.

The order you set is still there after you reload.

From the keyboard, focus a row and press Alt+Arrow Down or Alt+Arrow Up to move it — no mouse needed.

Dragging never opens the row underneath it, and only a team admin sees drag handles at all.

6Move to Vision, the Accountability Chart, or Rocks

The Review V/TO section carries buttons for Vision and the Accountability Chart. Each opens in a new tab.

Your meeting stays open behind it, exactly where you left it.

Click Define Rocks to set the quarter's Rocks. It opens Traction already showing the quarter you're planning for — one quarter ahead of the meeting you're running.

You can add Rocks there without touching a single selector.

On a team that doesn't run EOS, this same button reads Define Goals instead.

If the team has no framework assigned yet, it renders disabled rather than a link to nowhere.

Not captured this pass — Examp.ly is an EOS-framework team, and no non-EOS team fixture exists in the demo org to show this state. This claim stands on the BDD, unphotographed.

7Write the Check In

Click the Check In card to open its editor. Write what the quarter needs to hear.

Save it with the Save button or ⌘+Enter. The card paints your new text immediately, before the server confirms.

Only a team admin can write it. Everyone else reads it.

A filled-in Check In stays visible to them. An empty one reads N/A rather than showing an empty box.

1Rate the meeting

In the Conclude section's Rate the meeting roll call, click your own empty score placeholder.

Pick a score from 1 to 10. Your row paints it immediately, before the save even finishes.

A score of 8 or higher paints with the on-goal treatment. Anything below 8 paints differently.

The Meeting score block updates at the same moment. It shows the average and how many attendees have rated so far.

Only your team's admin can open and change anyone else's row. Everyone else can open only their own.

2Read the score over time

Scroll down from the roll call to Score over time.

Three tiles summarize it: Last meeting, the 4-quarter average, and Quarters at 8+.

Not captured this pass — the demo org has no rated Quarterlies in its history, so this screen shows "No Quarterlies have been rated yet" instead of the three summary tiles. This claim stands on the BDD, unphotographed.

Below the tiles, a trend line plots each quarter's average, with a dashed line marking the goal of 8.

A grid beneath that shows every attendee's score for every quarter in range, colored the same way as the roll call.

Not captured this pass — it only renders once a Quarterly has been rated at least once, and the demo org has no rated history. This claim stands on the BDD, unphotographed.

Change the range control to look further back. Anyone on the team can do this, not just the admin.

Before your team has ever rated a Quarterly, this section says so plainly instead of showing an empty chart.

3Write the quarter's check-in

The Check In tab holds three fields for the quarter: Check In, Learnings, and Focus.

Only your team's admin can write or edit them. Everyone else can read what's there.

Edit just one field and the other two stay exactly as they were. A partial save never touches the fields you leave alone.

4Attach a file to the quarter

Open the Attachments tab. It lists only what's attached to the quarter you're currently viewing.

Change the quarter and the list changes with it. A quarter with nothing attached reads "No attachments yet."

As the admin, click Upload File to add one. Everyone else can open what's already there, but sees no Upload File control.

To remove one, click its Delete attachment control and confirm in the Delete Attachment dialog.

1Capture a next step

Type a next step into the Next Steps section and press Enter, or click Add next step.

Either way, it appears as the first row at once, before the save even finishes.

The rows already there move down and keep their own order beneath it.

Reload the page and the new row is still first — the order painted is the order that was saved.

Adding a next step never touches the Issues section beside it. Only the Next Steps list changes.

2Carry a Rock into the new quarter

Carrying a Rock forward makes a copy for the new quarter.

The original stays exactly where it was, in the quarter that closed.

Only the Rock's unfinished milestones come across.

Whatever was already complete stays on the record of the quarter that finished it.

The copy starts clean — no on-track or off-track history, no judgement carried over from last quarter.

It keeps the original's owner, not whoever ran the carry-forward.

Carry a Q4 Rock forward and it lands in Q1 of the following year, not back in Q1 of the same one.

Try to carry the same Rock into the same quarter twice and the meeting names why, right on the agenda.

It names the Rock and the quarter pair already carried. Nothing new gets created.

Only a team admin can carry Rocks forward, and only on a team running EOS.

3Tick off your team's EOS Tools

The Quarterly agenda carries twenty EOS Tools tiles — the practices a team running EOS checks off as it adopts them.

A team admin ticks and unticks them. Everyone else on the team can only read the state.

A tile ticked here shows the same way in the legacy app, and the reverse.

Both apps write the one record, not two records kept in sync by hand.

4Print the quarter

Click Print on the Quarterly agenda and it opens the Team Business Review — the report itself, not a second print pipeline.

It opens already set to the meeting's own year and quarter.

The meeting stays open behind it. Printing isn't limited to team admins — any member sees the same doorway.

From the report, Print in its own toolbar builds the deck in your browser.

It downloads a PDF named for the team and the quarter on screen — no server round-trip.

The deck matches the screen exactly. Every slide shown prints, in the same order.

A section with nothing to show — no Marketing Strategy recorded, say — is left out of both.

5Read the report before you print it

The Scorecard section lists every measurable with its owner, its goal, and its weekly values for the quarter.

A week nobody recorded shows blank, never a guessed number.

The quarter and year selectors always read the actual quarter, spelled out — "Q2", "2026" — never a bare digit.

The cover slide shows your team's own logo if it has one.

It falls back to the ResultMaps logo if the team has none, or if the stored one fails to load.

Vision fields — Purpose, the values beneath it — show as plain text, however they were formatted when someone typed them.

Under EOS terminology, the card holding Purpose is headed "Core Focus", not "Focus."

6Find Quarterly Meetings from the Meetings hub

Open Meeting Pulse and three tiles are waiting: Level 10 first, Quarterlies second, 1:1 (One-on-One) Meetings last.

Level 10 and Quarterlies both carry an EOS Pure pill beside their green Included pill.

The 1:1 tile carries neither — it isn't an EOS practice the way the other two are.

Every team member sees the same order and the same marking, whether or not they administer the team.

1Open Publish to web

Open the page and press the ⋯ menu at the top right, then choose Publish to web….

If you don't see the entry, that's the permission telling you where you stand: publishing belongs to the page's author and to team admins. Being able to edit a page is not enough to publish it — putting something in front of the world is a bigger decision than fixing a typo, and the product treats it that way.

2Choose who can view

The dialog opens with a warning banner you're meant to actually read: Public even to people outside my organization. That's the honest description of both choices below it.

Anyone with the link is the default. The page becomes readable by any person or company you hand the link to — a customer, a candidate, a partner — with no account and no sign-in. The link itself is the only protection: it's long and random enough that nobody will guess it, search engines are told not to index it, and it isn't listed anywhere public. But once you send it, you can't control where it gets forwarded. Publish this way when the content is genuinely fine for the open internet.

Anyone with a ResultKit login is the gated case. The link works the same way, but a visitor must be signed in to ResultKit before the content appears — any live ResultKit account will do, including accounts from other organizations. What this buys you is accountability, not secrecy: nobody anonymous ever reads the page, but it is not limited to your own company. Publish this way for content meant for the ResultKit community rather than the whole internet.

If what you actually want is "only my team" or "only certain people," don't publish at all — that's what the page's regular sharing controls are for.

3Say it out loud, then publish

Below the choices sits a field labeled Type I understand to continue, and the Publish button stays disabled until you've typed exactly that — I understand, capital I. It's deliberately not a checkbox. You're making a page public; the product wants one unambiguous moment where you meant it.

The instant you publish, the dialog shows the live link — it looks like resultkit.ai/p/ followed by a long random code — with a Copy link button beside it, the visibility you chose, and a line recording who published it and when. That record is permanent: even after the page comes back down, your team's history of who made what public survives.

From this moment the link is live, and it stays current. There's no snapshot and no re-publish step — every edit you save shows up at the public link immediately. If the page is a work in progress, remember the world is reading your latest save.

4What your visitor actually sees

A visitor to an Anyone with the link page gets the page and only the page: the title, the content, images and all, on a clean reading column with a small Made with ResultKit badge at the bottom. No sidebar, no page tree, no comments, no author name, nothing to click into your workspace. Links inside the page that point at your other, unpublished pages appear as plain text — the public copy never leaks a path into private material.

A visitor to an Anyone with a ResultKit login page who isn't signed in sees a gate instead: This page is for ResultKit users — Sign in to view this page — and a Sign in button. None of the content shows until they're through. Once signed in, they get the same clean reading view described above.

One small exception, and it's a convenience: a teammate who opens the public link while signed in — someone who could already see the page inside the app — gets an Open in app button at the top right, so they can jump from the public copy to the real page.

And if a link has been taken down, every visitor sees the same plain "page not found" — a dead link never advertises that something used to be there.

5Spot what's published at a glance

Anywhere you can see a page, you can see whether it's public. A published page wears a small globe after its name in the page tree — visible to anyone who can see the page, no admin rights required. Open the page yourself with edit rights, as its author or a team admin, and the same globe appears again under the title, next to your save status.

Team admins get one more view. At the top of the page tree sits an Internal | Published switch, with a count of what's currently live. Internal is the tree you know. Published filters that same panel down to only the pages that are public — each with its live /p/ link, who published it, and a green Live dot — the quickest honest answer to "what are we exposing right now?". To grab a page's link or take it back down from here, open the page and return to ⋯ → Publish to web….

6Changing your mind

Everything about publishing is reversible, and the reversals behave the way you'd hope.

Switching the audience — from link-only to login-required or back — happens in the same dialog and keeps the same link. Tighten or loosen the door without re-sending the URL to anyone.

Unpublish — the button waiting in the same Publish to web… dialog once a page is live — kills the link the moment you click. Anyone holding it gets "page not found," and images that were on the page stop loading too. The page itself is untouched — still in your tree, still editable, just private again.

Publishing again creates a brand-new link. The old one is gone for good — intentionally. If a link escaped to somewhere it shouldn't have, unpublish and republish, and the escaped copy is permanently dead while you carry on with a fresh one.

Archiving a published page unpublishes it automatically, and a page restored from the archive comes back private. Nothing quietly stays public after you've put it away.

1Find a page in the tree

Open Pages. The tree lists your team's whole library down the left.

Each level is indented one step further than its parent.

The page you have open is the only highlighted row. Click any other row's title to open it.

The highlight moves and the title changes. The tree itself doesn't move or reload.

A long title is cut off with an ellipsis rather than widening the tree.

Rest the pointer on a cut-off row and the full title shows in a tooltip.

Not captured this pass: A page title too long for the column truncates; hovering it shows the whole name.

Click a row's chevron to expand or collapse its children. Clicking the title opens the page instead — only the chevron folds the branch.

2Resize or hide the tree

Drag the handle on the tree's right edge to widen or narrow it, anywhere between 200 and 520 pixels.

Double-click the handle to snap it back to its resting width.

Whatever width you choose is remembered for you. It's there again the next time you open Pages, in the browser you set it in.

Click Hide page list — in the tree's header, or in the page action row — to collapse the tree entirely.

The open page widens to take its place.

A small Pages chip appears above the page title while the tree is hidden. Click it, or the same toggle in the page action row, to bring the tree back.

3Create a new page

Click ＋ Page in the top bar to start a new top-level page.

It appears at once, titled Untitled and already open, before the save even completes.

Hover any row in the tree and click its New sub-page control to nest a page beneath it instead.

The new page lands first among that page's children, above whatever was already there.

A page you drag somewhere else afterward keeps that placement. Being newest only decides where it starts, not where it stays.

4Reorder or nest a page by dragging

Pick up a page by its drag handle and move it.

The tree shows you which outcome you're about to get before you let go.

Not captured this pass: Dragging a page straight down shows a reorder among its siblings.

Drag straight down and it reorders among its siblings.

Drag to the right and it nests under the page above instead — the tree names which page it will fold under, before you release.

Not captured this pass: Dragging a page to the right shows it will nest under the page named in the indicator.

The page lands exactly where the indicator promised, the moment you release it.

5Reach a page by its own link

Every page has its own link. Copy it from the open page.

It identifies that page specifically, not just the Pages screen in general.

Open a page's link and it takes you straight there. If the page belongs to a different team than the one you're in, it switches your active team first.

If you're signed out when you open the link, you land on that same page once you sign in — not on a default screen.

A link to a page you can't view refuses the content plainly. It never shows a blank or broken screen.

Not captured this pass: Opening a link to a page you can't view shows an explicit unavailable message, never a blank screen.

6Archive a page — and bring it back

If you authored a page, or you're an admin of its team, the page action row carries an Archive page control next to Delete page.

Click it and a dialog names the exact page. It states that the page will leave the tree but stay readable, and can come back later.

Nothing archives until you confirm.

Archiving a page with sub-pages takes them with it. The dialog says how many, and the whole branch leaves the tree together.

An archived page is gone from the tree, but never gone for good.

Click Show archived at the bottom of the tree to reveal it again.

Opening an archived page shows a banner naming who archived it and when, and its body turns read-only.

A page archived before that detail was tracked shows only the date.

An admin or the page's author sees an unarchive control in that banner. Anyone else can still read the page, just not bring it back.

7Download a page

Every page carries a download control, open to anyone who can read the page — not only its editors.

Click it and choose a format. Markdown (.md) keeps headings, bold, links, and lists.

Plain text (.txt) strips all of that down to words. Word (.docx) opens as a formatted document in Word or Google Docs.

A Preparing… indicator appears the moment you choose. It flips to Downloaded once the file saves.

The file is named after the page's title. It only ever holds that one page's own content — a page with sub-pages downloads without them.

A picture in the body travels inside the Word file and scales to fit the column.

Markdown links to it instead, and plain text marks where it sat with a bracketed line.

Not captured this pass: A Word download with an embedded picture, scaled to fit the page's text column.

8Pin a page — and file it in a folder

Click the pin control in the top bar and the page pins immediately, with nothing else to choose.

A small menu opens alongside it, offering an optional name and a way to file the page into a folder.

Type an existing folder's name, or a new one — or walk away and leave the page loose.

Pinned pages and folders live in the sidebar's Pinned section.

Click a closed folder to open it, or drag a page onto one to move it in.

Drag a page below the folders to take it out, or pick Remove from folder from its overflow menu instead.

Deleting a folder never unpins the pages inside it. They drop back to the loose list underneath.

1Start editing a page

Click into the title, or anywhere in the body. You're editing at once.

You can also click the pencil in the page's action row. It only appears if you have edit rights, and it disappears entirely on a locked page.

Clicking in and typing nothing, then clicking away, leaves the page untouched. Entering edit mode by itself isn't a change.

Nothing on screen ever announces a save — no "Saving," no "Saved," no spinner. Autosave runs quietly in the background the whole time you're typing.

2Format text with the selection bubble

Select any run of text and a bubble appears right above it — or below, if above would cover the action row.

It carries Bold, Italic, Underline, Strikethrough, inline code, a link tool, four text-style buttons — paragraph and three heading levels — and three list buttons.

Click a control and the change paints at once. Click the same control again to undo it.

Keyboard shortcuts work too — ⌘B for Bold, for instance — without ever opening the bubble.

3Turn lines into a list or checklist

Select more than one line and click Bulleted list, Numbered list, or Checklist on the bubble.

Switching a selected list from one kind to another converts it in place — it never nests one list inside another.

A checklist's checkboxes toggle on their own, independent of the bubble.

4Write in markdown

Click Markdown at the left of the controls row below the title, and the page's own content appears as literal markdown — headings as ##, list items as -.

Edit it as text and click Rich to switch back — your changes render formatted immediately.

The shortcuts work in Rich mode too, without switching anything: type # then a space to start a heading, or - then a space to start a bulleted list.

5Build a table

In Markdown mode, type a header row and a delimiter row, ResultKit-style — a line of dashes under the headers — then switch back to Rich.

Lining up the dashes with colons controls alignment — a colon on the left, both sides, or the right sets that column's alignment when it renders.

6Add a picture

Drag an image file from your desktop into the body, or paste one from your clipboard. It appears right where you dropped or pasted it, immediately.

Paste more than one image at once and both land, in the order they were on your clipboard.

An image the page can't keep — too large, or one that fails to upload — is refused with a reason on screen. It never quietly disappears after you reload.

7Drop in an emoji

Hover the title, or put your cursor in it, and an Emoji chip appears just above it.

Hover any heading and its own smiley shows in the margin beside it. Select body text and the bubble carries the same smiley.

Every path opens the same picker: a fixed grid of thirty emoji, no search box and no categories.

Picking one puts it at the very front of the title or heading, replacing one already there. In the body, it replaces whatever text you had highlighted.

The emoji is ordinary text once it lands — backspace deletes it like any other character.

1Set who can create pages on your team

Open your team's detail page and find the Who can create pages setting.

It offers exactly two choices: All members and Admins only. All members is the default until someone changes it.

Click Admins only and it takes effect at once, saving behind you.

Only a team admin sees this setting at all. Anyone else's team detail page simply has no such control — not a disabled one.

Changing it never touches any existing page. It governs who may create a new one, not who can see the pages already there.

2Choose who can see a page

Open Manage permissions from the page's action row to reach the Who can see this page panel.

Every new page starts visible to Whole team, whether or not you name anyone else.

The panel offers three rows: Whole team, Specific people, and Just you. None of them has anything to do with publishing a page to the public web — that's a separate control entirely.

3Add or remove specific people

Turn on Specific people and name someone. Their chip appears at once, and the save follows behind it.

Whole team and Specific people are independent grants, not alternatives. Naming someone under Specific people never turns Whole team off — the two simply add together.

Removing a person's chip takes away only that person's access. Everyone else you named keeps theirs.

The page's own author has no remove control on their own access. Even a direct attempt to revoke it is refused.

4Clear a page down to Just you

Click Just you and both grants clear in the same instant. Whole team turns off and every chip under Specific people disappears.

It's a single action, not a sequence of separate clearings.

Turn Specific people back on afterward and it starts empty. Nothing remembers who was named before — you name people again from scratch.

5Know what a sub-page inherits

A new sub-page starts with its parent's audience, copied at the moment you create it.

After that, the two are independent. Restricting the parent later leaves an existing child exactly where it was, and widening the parent doesn't widen it either.

Changing a child's own audience never reaches back up. A page owns its own audience, and neither its parent nor a sibling follows it.

1Open the Comments panel

Every page loads with the panel closed.

A badge on the toolbar's Comments button and a row at the end of the document are the only signals a conversation exists.

Click the toolbar's Comments button, or the end-of-document row, to open it.

Either one works the same way. Escape, or the panel's own close button, collapses it again.

On a page with no comments at all, the end-of-document row reads "Add a comment" instead of a count.

That's the only thing on screen saying commenting is possible here.

2Leave a comment on the whole page

Open the panel and type into its composer at the top — the one that reads "Add a comment to this page…".

The Comment button stays disabled until you type something.

Click Comment, or press Cmd/Ctrl+Enter — either one posts it.

The new thread appears at the top of the panel immediately.

The page's save indicator settles from "Saving…" to "Saved" right after.

A comment over roughly 65,000 characters is refused with a clear error, not silently trimmed.

Nothing you typed is lost — you just have to shorten it.

3Comment on a specific passage

Select a run of text in the document, by mouse or by keyboard.

A small toolbar appears above it with Bold, Italic, Link, and Comment.

Click Comment and the passage gets a dashed, pending highlight right away.

The panel opens with a composer pinned to the top, already quoting your selection.

Submit it and the dashed highlight turns solid.

Cancel, or press Escape, and the highlight disappears — nothing is created.

Editing the wording around a commented passage leaves its highlight alone.

If the exact passage gets rewritten or removed, its thread isn't deleted.

It stays in the panel, tagged "original text changed", with no highlight left to click.

4Reply in a thread

Click a thread's replies control to expand it, or click straight into an already-expanded reply field.

Type your reply and click Reply, or press Cmd/Ctrl+Enter.

It appears under the thread at once, carrying your own name and avatar — never the name of whoever started the thread.

Replying to a resolved thread doesn't reopen it.

It just adds your reply, and the thread stays resolved until someone clicks Reopen on purpose.

5Resolve a thread, or reopen one

Anyone who can see the page can resolve any thread — including one they didn't start.

Click Resolve and it leaves the panel's Open view right away.

Resolving is silent — there's no "Saving…" indicator, unlike posting or editing a comment.

A resolved passage's highlight switches to a green, resolved style in the document.

Reopen brings a resolved thread back, and shows who resolved it and when.

Reopening it also increments the toolbar badge again.

6Travel between a comment and its passage

Click a highlighted passage in the document and its thread opens selected in the panel, scrolled into view.

Click a thread's card in the panel instead, and the document scrolls to its passage and flashes once.

Only one pairing holds at a time — one selected card, one active passage.

Clicking elsewhere in the document, or selecting a different thread, clears the old pairing first.

A page-level thread has no passage to travel to.

Selecting it in the panel leaves the document exactly where it was.

7Filter the panel

The panel opens on Open by default.

Switch to Resolved or All with the filter controls at its top.

Your filter choice is remembered for you, per page, the next time you open that page's panel.

It doesn't change what you see on any other page.