Documentation

Everything you need to grow your first plan

Guides for getting from an empty project — or a five-thousand-task MS Project file — to a simulated, defensible schedule.

Start here

Onboarding

Your company on Foreweave

From the signup form to a working workspace: email verification, your organization's isolation boundary, the two role layers, and the first plan.

7 min Quickstart

Your first 20-task plan

Create a project, add tasks on the Gantt by dragging, link them, and watch the critical path appear. If you know Microsoft Project, you already know this.

10 min Migration

Import from MS Project

Bring an XML export across — tasks, links, calendars, assignments and all. What round-trips cleanly, what to check after import, and why we don't read .mpp files.

8 min First simulation

From one date to a distribution

Attach three-point estimates to your riskiest tasks, run 5,000 iterations, and read your P50 and P80 off the S-curve. Includes how to explain the chart to your boss.

15 min

Guides

Gantt

Editing at full speed

Drag-to-create, bar move, edge resize, in-grid date edits, freeze panes, undo — the complete interaction reference.

Scenarios

What-ifs and comparisons

Create overlays, compare finish dates and critical-path changes side by side, and promote a scenario to baseline.

Risk

Reading simulation output

S-curves, finish histograms, the criticality Gantt, and tornado sensitivity — what each one tells you, and what it doesn't.

Tracking

Baselines and variance

Capture a baseline, track percent complete, and read schedule variance without spreadsheet gymnastics.

Teams

Resources and levelling

Assignments, the work formula, over-allocation flags, and when (not) to let the leveller move your tasks.

AI agent

Drafting with the agent

How to describe a program so the agent drafts well, reviewing diffs, and what the agent will refuse to invent.

Profiling

Before the agent writes a task

The project profile, the kickoff interview, the planning guideline you accept first, and what the agent remembers between sessions.

Programs

Program master schedules

Read-only mirrors, publishing changes upward, and the critical-path impact gate that decides what applies and what waits for you.

Spreadsheets

The schedule in a spreadsheet

Import CSV or XLSX — even when the plan is drawn as coloured or merged cells — and confirm the reading, with provenance, before it lands.

Documents

Documents from the schedule

Document Studio: decks and reports built from a scoped slice of plan, and the consent model behind its different data path.

Scheduling concepts

The vocabulary Foreweave uses, in one place — word for word the definitions the application's own help gives. Open the glossary in the app.

Critical path — The chain of tasks with no slack, where any slip moves the project finish date.
Total float — The slack a task has before it delays the project finish date.
Dependency — A link stating that one task's start or finish governs another's, in one of four types: finish-to-start, start-to-start, finish-to-finish, or start-to-finish.
Lag — Working time added to a dependency, delaying the successor; a negative lag is a lead, which pulls it earlier.
Constraint — A rule pinning a task to a date, such as start-no-earlier-than, which the engine obeys even when the logic would place the task elsewhere.
Deadline — A date a task is expected to finish by, which is reported as missed but never moves the task.
Calendar — The definition of working time — which days and hours count — that every duration in the project is measured against.
Working minutes — The unit the engine schedules in, counting only time the calendar says is workable, so a weekend costs a task nothing.
Baseline — A saved copy of the schedule's dates, kept to compare the plan you committed to against the plan you have now.
Criticality index — The share of simulated runs in which a task landed on the critical path.
Percentile date (P50, P80, P90) — A finish date the simulation reached or beat in that percentage of its runs.
Scenario — A named set of overrides explored alongside the plan, which never changes the plan until you promote it.
Planning guideline — How the AI agent intends to plan a project — its phases, gates and structure — agreed with you before it creates any task.
Provenance — Where a value came from — typed by a person, extracted from a file, or inferred by the agent — recorded alongside the value and never supplied by the caller.
Review gate — The check on a program master that queues a member project's change when it moves the critical path, and applies it automatically when it does not.
Drift — A difference between a mirrored task in a master schedule and the member project it came from.

API reference

Everything in the UI is on the REST API — authenticated bearer tokens, optimistic concurrency via schedule version tokens. A taste:

POST	/projects/{id}/tasks	Add a task; the schedule recomputes on commit.
PATCH	/tasks/{id}	Edit dates, duration, constraints, mode — conflicts are reported, never clamped.
POST	/projects/{id}/dependencies	Link two tasks; cycles are rejected with a 422.
GET	/projects/{id}/schedule	The full computed schedule, with critical path and slack.
POST	/scenarios/{id}/simulate	Launch a Monte Carlo run; results are reproducible from the recorded seed.
POST	/projects/{id}/program/publish	Publish a member's net changes to every program master it belongs to.
GET	/uploads/{id}/extraction	What was read out of an uploaded spreadsheet, with per-item provenance, before you accept it.
GET	/projects/{id}/export?format=mspxml	Your whole plan back out, any time.

Full reference with schemas and auth flows ships with your workspace. Can't find something? Ask us directly.