Skip to content
EmargenEmargenDocs

InitiativesHow to

Follow delivery

Follow an initiative’s delivery when you need to know where its build stands, say because a customer is asking when. Delivery explains the idea.

Before you start

Section titled “Before you start”
Who can
Anyone who can open the initiative follows its build.
You need
An approved initiative being built. Before approval, its Slices tab shows the plan instead.
The pictures
ACM-293, Single sign-on for every depot at once, at ACME, the company in the docs’ pictures. It’s shown being built, as the product manager who approved it sees it, with their chat hidden.

Steps

Section titled “Steps”

  1. Open an initiative being built from the initiatives list, where it’s under Delivery. It opens on its Slices tab. To give the build the whole width, click Hide the chat at the chat’s edge.

    Open the initiatives list (opens Emargen in a new tab)
    ACM-293 as Lena sees it, her chat hidden: the Slices tab with Completion 0 of 100, Slices done 0 of 2, Tasks closed 0 of 11, Time blocked None, Scope updates 1 since approval; the two slices as lanes up to Now; Slices 2 picked in the bar on the right.ACM-293 as Lena sees it, her chat hidden: the Slices tab with Completion 0 of 100, Slices done 0 of 2, Tasks closed 0 of 11, Time blocked None, Scope updates 1 since approval; the two slices as lanes up to Now; Slices 2 picked in the bar on the right.
    1. Slices, in the initiative’s bar. Click it to come back here from anywhere in the initiative.
    2. The build in numbers.
    3. The slices, each a lane on one timeline, with its tasks as small cells at the end.

  2. Read the numbers across the top. Completion says how far the requirements are built, out of 100. Slices done and Tasks closed count out of all of them. Time blocked says how long slices have been blocked in all, and which are blocked now. Scope updates counts the change requests decided with an option since approval. New tasks counts the tasks added while the build went on. In the pictures, none of eleven tasks is closed yet.

  3. Then the lanes. Each slice runs from when its build started to Now. A lane is solid while the slice is in progress, hatched while it’s blocked, and carries a mark where it was done. The key under the lanes says what each colour means.

  4. Click the arrow before a slice to see its tasks. Each shows who has it, with which coding agent, and where it stands. Click the arrow again to fold them.

    The lanes with ACM-295 open: under it, ACM-366 Switch every tested depot on in one request, Marek Nowak · Codex, in progress; ACM-367, ACM-368 and ACM-370 in progress with Jonas Berg's Codex and Claude Code; ACM-369 and ACM-371, blocked; ACM-372 in progress; ACM-373, unclaimed.The lanes with ACM-295 open: under it, ACM-366 Switch every tested depot on in one request, Marek Nowak · Codex, in progress; ACM-367, ACM-368 and ACM-370 in progress with Jonas Berg's Codex and Claude Code; ACM-369 and ACM-371, blocked; ACM-372 in progress; ACM-373, unclaimed.
    1. The arrow, now folding the tasks away.
    2. A task in progress, with who has it and their coding agent.
    3. A task that’s blocked. It can’t start until the tasks it names are closed.

  5. Click a slice’s title to open its page. It shows the slice’s demo, its tasks with their repositories, the history of its build, and what was shaped for it.

    The slice ACM-295 Switch every depot on, and one back as Lena sees it, in a tab beside Slices: In progress · 22 Oct 2026, Comment; the demo; its eight tasks with a Table and Timeline switch, each with its repository and who has it; History, Started when Codex took ACM-367; and Shaping.The slice ACM-295 Switch every depot on, and one back as Lena sees it, in a tab beside Slices: In progress · 22 Oct 2026, Comment; the demo; its eight tasks with a Table and Timeline switch, each with its repository and who has it; History, Started when Codex took ACM-367; and Shaping.
    1. The slice’s tab. Click Slices beside it to go back.
    2. Table and Timeline. Show the tasks as a table, or each on a timeline from when the task was claimed.
    3. A task. Click it to open its page.
    4. History. When the slice started, and any block, unblock or done since.

  6. Click a task to open its page. It says what to do, its repository, who claimed it and when, and the tasks it’s blocked by or blocks. Once it’s closed, the page says when, and links its merge request when the agent gave one.

  7. Click Slices to go back, and scroll down. Requirements takes each requirement in turn. Shown working tells you whether someone has seen it work, and marked every slice that serves it done. Done says how far it’s built, out of 100. In the pictures, every requirement is at 0 and Building.

  8. Read Blockers. Blocked by is the tasks that wait on other work, and what each waits on. Blocks is the tasks here that hold work up. Click Map to see who blocks whom.

    Blockers as Lena sees it, with List and Map: Blocked by 3, among them ACM-369 Switch every tested depot from the single sign-on settings, 10 days, Waiting on ACM-366 and ACM-367; Blocks 5, among them ACM-366 Switch every tested depot on in one request, Blocks 1 task, Needed by ACM-369.Blockers as Lena sees it, with List and Map: Blocked by 3, among them ACM-369 Switch every tested depot from the single sign-on settings, 10 days, Waiting on ACM-366 and ACM-367; Blocks 5, among them ACM-366 Switch every tested depot on in one request, Blocks 1 task, Needed by ACM-369.
    1. A task that can’t start, and how long it has waited.
    2. What it’s waiting on.
    3. A task that holds work up.

  9. Read To reply and to do. It shows what waits on a person, how long each has waited, and what is held up meanwhile. Click By requirement to group the rows under the requirement each touches, or Settled to see what was answered or decided before. In the picture, a colleague’s question waits on the initiative’s owner.

    To reply and to do as Lena sees it: By kind and Open picked; To reply 1, Answer “Once the one setup per customer ships, whose depots switch first: Kelderby's next 18 or Halden's 14 sites?”, 2 days, Asked by Ana Ruiz · Tom Weber's to answer.To reply and to do as Lena sees it: By kind and Open picked; To reply 1, Answer “Once the one setup per customer ships, whose depots switch first: Kelderby's next 18 or Halden's 14 sites?”, 2 days, Asked by Ana Ruiz · Tom Weber's to answer.
    1. By kind and By requirement. How the rows are grouped.
    2. Open and Settled. What’s still open, or what was decided.
    3. A question waiting for an answer, and how long it has waited.
    4. Who asked, and whose it is to answer.

What you get

Section titled “What you get”
  • You can see what’s done, and what’s holding up the build.
  • Nothing you did changed anything. The numbers follow from the work.
  • To find the initiative again quickly, star it at the top. It then appears under Starred in the menu.

Next

Section titled “Next”

How to

Page by page