Documents

The Documents view turns your project’s own data into written deliverables — a project charter, a status report, a risk register write-up, and so on. Each one is drafted from the registers, stakeholders, and project details already in the project, not written from scratch.

The document catalog

Which documents a project offers comes from its methodology — the way of working you picked during onboarding (PMBOK, ISO 19650, or Agile). See Create a project.

The available documents are listed under Documents in the sidebar, grouped by type. For example, a PMBOK project offers a Plans group (project charter, project management plan, communications management plan, stakeholder engagement plan, lessons learned) plus a Reports & summaries group; an ISO 19650 project offers information-management deliverables (EIR, BIM execution plan, MIDP, TIDP, and others); an Agile project offers backlog, release, and sprint documents. Every methodology shares the same Reports & summaries group — the register narratives (status report, risk register, issue log, decision log, action item log, stakeholder register).

Note

A document in the list may show “Generator not yet available”. That means the deliverable belongs to your methodology but the app can’t draft it yet — pick another, or check back later.

Generating a document

Open a document from the sidebar, then use the button at the top right:

• Generate — drafts the first version.
• Regenerate — drafts a fresh version from the current project data.

Generation is an LLM pass (an AI model reads your project data and writes the document). It pulls the relevant registers and project details and composes the text from them, so the result reflects what’s actually recorded. The generators are instructed not to invent detail that isn’t in the data — where a section has no source data, the draft says so or leaves a brief placeholder instead.

A draft can take a little while. When it finishes, the document appears below, showing its version number, when it was generated, and the model used (when recorded).

Versions

Every Generate or Regenerate creates a new version — earlier versions are kept, not overwritten. The view shows the latest version by default; when more than one exists, a version dropdown at the top right lets you open any earlier one (read-only). Each entry shows its version number, when it was generated, and — for scheduled runs — that it was produced automatically.

Finalize & file

A generated document lives in this view until you decide it’s the record copy. Finalize & file renders the version you’re looking at to a PDF (built on the server — no printing to PDF from the browser) and files it as an issued document in the project’s Files tree, in the folder the filing standard allocates for that kind of plan (a PMBOK management plan files under 10_Management, for example).

Finalizing the same document again replaces it with a new version of the same filed record — you never end up with duplicates. Filed copies are treated as outputs: the platform doesn’t re-ingest its own generated documents back into project intelligence.

Scheduling

The Status Report can regenerate itself on a weekly schedule, so a fresh one is always waiting without anyone clicking Generate.

Go to Settings → General → Scheduled status report and:

• Turn on Generate automatically.
• Pick the day and time. These are in the project’s own timezone — set the timezone under Settings → General first; without one, the schedule uses UTC.
• Set the look-back — how many days of activity each report covers (7 by default).

Each scheduled run saves a new version, exactly like a manual one. It does not email anyone or post anywhere — open it from the Documents view, where scheduled runs are tagged as automatic in the version dropdown. A schedule runs at most once a day, and only while the project is active. Changing the schedule needs document write access.

Note

Only the Status Report can be scheduled today. Other documents are still generated on demand.

Permissions

You need read access to a project’s documents to open this view, and write access to generate or regenerate. Document access is governed by your role’s permissions.