Overview
Construction scheduling and project planning — what Sequence is, the output templates that turn a schedule into a deliverable, what it is built on, and what is not built yet.
Sequence is a scheduling and project-planning application for construction work. It holds the schedule itself — activities, logic, baselines, resources and cost — and it is built to make that schedule read well on the page it ends up on.
Those are two jobs, and Sequence keeps them apart. The grid, the critical path and the resource pool are one half. The other is output templates: named, reusable definitions of how a schedule renders, so the same activities become a tiled A3 working schedule and a one-page board slide without either being rebuilt by hand. How a schedule looks is data — bar shape, fill, colour, labels and timescale, as rules over your own columns — rather than a setting somebody re-applies every month.
It is a Tauri desktop application, the same shell as Draft and Redline, and it shares their interface conventions: an activity rail, dockable panels, a settings tree, and a command surface that an agent can drive as well as a person.
What is built#
| Schedule | The grid: activities, durations, logic, the critical path |
| Baselines | Snapshots to compare the live schedule against |
| Quality check | Checks against the schedule's own rules before anybody else finds them |
| Resources | A resource pool, assignments, capacity profiles, levelling |
| Cost | Three cost sources, accruals, and earned value |
| Look-ahead | The construction working window, grouped for a foreman |
| Scenarios | Fork the schedule, change it, diff it, merge it back |
| Impact and recovery | Compression, fragnet insertion, and a record of what each change did |
| Views and filters | Saved ways of looking at the same schedule |
| Conditional formatting | Rules that colour the grid by what matters today |
| Output & templates | Page setup and tiling, bar and milestone styles, palettes, the annotation layer |
| Comments | Threaded, per row and per sheet |
| Notifications | A centre, with subscriptions, and seven ready-made schedule alerts |
| History | The activity log, filterable and exportable |
| Permissions | Authored here; enforced when a server is present |
| Files | The .ammg schedule file, delimited-text import, plot output |
What is not built#
Documents and Automation appear in the specification and are not built.
Specified, not built.
Specified, not built.
Schedule export is partial. The grid leaves as CSV or .xlsx and dated rows leave as a calendar file, alongside the drawn plot — PDF, PNG or SVG. What is short is the calendar, which is a file rather than a subscribable feed; interchange with other scheduling tools does not exist yet. See Files, import & output.
CSV, iCalendar and .xlsx all ship. The workbook carries the hierarchy as a real outline level and a frozen bold header. ⚠ The one shortfall against the specification is the calendar: §12.11 asks for a subscribable FEED — a URL the calendar re-fetches — and what ships is a FILE, saved once, which goes stale silently while continuing to look current. That is a difference of kind rather than a missing wire: published links exist, but they serve a FROZEN artifact that does not change when the schedule does, so there is no live-artifact path in the product for a feed to be built on. ⚠ Separately and by decision, the workbook carries NO FORMULAS: durations, dates and rollups are computed by the scheduling engine from logic and calendars, and no Excel expression reproduces them, so a formula would recalculate into disagreeing with the schedule. That is a refusal on the merits, not an omission.
In a beta build the unbuilt panels are hidden rather than shown greyed out — see the roadmap.
Beta#
Sequence is in beta. It is incomplete, it will have defects, and it is not licensed for production work. See installing the beta.