A project overview has to hold an entire launch on one page without flattening it into a single line that hides which part is actually behind.
Harbour Street relocation — overview
The move runs in three phases. Phase one is complete; phase two starts once the lease is countersigned.
The lease signature is the single dependency for phase two; a two-week slip moves the move-in past the quarter close.
A project touches more than one team, and each of them wants to see its own part without wading through the other two. A date only earns its keep once it is fixed to the place a delay would actually show up, rather than restated in a paragraph that goes stale the moment the plan changes. Whoever is asking how the whole thing is going matters here, not the person deciding whether to fund it.
Every stream of one project, on one page
Design, engineering and marketing each get their own named space inside the same document, so nobody has to stitch together three separate updates to see how one launch is actually going.
The timeline for this project, not a slice of one
Every task for this launch sits on the same timeline, grouped by the stream that owns it, so a delay in one shows up next to the work it is holding up rather than in a status update from another team.
Key dates fixed to a place, not a sentence
Launch day, review dates and deadlines sit on their own calendar next to the timeline, so a date lives as a fact on the page rather than a line buried in the text around it.
Which part of the overview they kept returning to
You see which heading kept them longest — the timeline, the calendar, or the section on who has to be ready — and whether it pulled them back once they had moved on. That is measured heading by heading, not by which stream’s space inside a shared section they were looking at.
An example — not your document. Sections are the document’s own headings.
Most of their attention went to “Cover” — 2m 42s of 4m 00s. They came back to “Timeline”.
Time each section spent on screen, counted only while the tab was in front and the reader was active. It shows what was in front of them, not what they read.
This page is about what a project overview has to do. For the blocks the editor is built from — see the editor.
The template is a filled-in example of one. This page is about what a project overview needs whether you start from that or a blank page: streams that stay separate, dates fixed to a calendar, and a timeline for the whole project rather than one team’s slice of it.
No — Quixli has no per-section permissions. Everyone with the link can edit any part of the document; keeping a stream someone else’s to touch is a convention the team keeps, not something the document enforces.
No — they are two separate blocks on the page. Move a date in one and update the other by hand, the same as you would any other fact stated twice in a document.