Esc

↑↓ move↵ openIndex · Pagefind
Scheduling / Reports, print Gantt, scheduled emails and the schedule assistant

Reports, print Gantt, scheduled emails and the schedule assistant

Run twelve P6-style schedule reports to CSV, XLSX or PDF, print a tiled Gantt PDF on tabloid or A3, email any of them on a daily, weekly or monthly schedule, and, where your company has turned it on, ask the schedule assistant questions answered only from cited, saved schedule facts.

On this page

The Reports page (Schedule › Analyze › Reports) turns the saved schedule into the documents a project team actually circulates: a critical path list for the OAC meeting, a three-week look-ahead for the superintendents, a baseline variance for the owner, and a Gantt to pin on the trailer wall. Reports need Schedule admin.

The twelve reports

Report What it lists
Critical path (the default) The engine’s longest path in driving order, then other activities with zero or negative float.
Total float Unfinished activities in total float bands, in working days.
Look-ahead Unfinished work starting or running in the next 2, 3 or 6 weeks from the data date, by week.
Baseline variance Start and finish variance against a named baseline’s original calculation, in calendar days. Negative means later than the baseline.
Milestones Start and finish milestones with forecast or actual dates, baseline dates and variance.
Period progress Activities actually started or finished this period, and baseline starts or finishes that didn’t happen.
Out of sequence Successors started or finished before their predecessors allow.
Constraints Activities with primary or secondary constraints, hard or soft, and whether the engine met them.
Open ends and logic Missing predecessors or successors, dangling starts and finishes, leads and start-to-finish links.
Resource usage Resource demand by period against recorded capacity, from the latest saved resource histogram.
Cost and earned value BAC, PV, EV, AC, CPI, SPI and EAC, with per-activity values. It also needs Budget view, with the Budget tool on.
DCMA 14-point health The latest saved DCMA 14-point assessment for the version.

Reports read stored data only: the current saved version, its calculation, the chosen baseline, the latest health check and the latest histogram. A Sources line names each one. When an input is missing, the report says it’s unavailable and why, rather than showing a zero.

Formats

  • CSV: formula-safe, with an Activity IDs column.
  • XLSX: three sheets, the report, a Summary and Notes.
  • PDF: letter, legal, tabloid, A4 or A3, landscape or portrait (default letter, landscape). Every page carries the project, version, data date, period and baseline, and a Page X of Y footer.

Files are named schedule-<report>-v<version>-<data date>, so you can always tell which version a printout came from. Through the API, every report is also available as JSON.

The Print Gantt panel on the Reports page produces a vector PDF of the saved schedule.

  1. Choose the paper. Letter, legal, tabloid (the default), A4 or A3, landscape or portrait.
  2. Choose the timescale and fit. Day, week (the default), month or quarter. Actual scale (tile pages) keeps the timescale and tiles across pages. Fit timeline to page width and Fit to one page shrink it.
  3. Choose a Planner layout (optional) to print with its timescale, Bar Chart Options and bar list, including baseline bars. If the layout’s progress line is on, the PDF draws it on every page, with a legend entry, using your primary baseline or the project baseline as the layout says.
  4. Choose what prints. All activities, Not complete or Critical only; an optional date range; a title up to 120 characters; columns from Activity ID, Activity name, Start, Finish, Dur, TF and %; baseline bars with a baseline picker; and the legend.
  5. Download Gantt PDF.

Tiled pages run rows down and time across, up to 400 pages, and each footer says where the page sits (Page X of Y (rows r/R, time c/C)). Every page carries the project, version, data date and baseline. WBS and level-of-effort summary rows aren’t printed. If you ask for more columns than fit on the paper, or the plan has no calculated dates, the print is refused with the reason.

Scheduled email delivery

Use the Scheduled email delivery panel on the Reports page to send any of the twelve reports, or the print Gantt, by email on a schedule.

  1. Open the report you want to send, with the options you want, such as look-ahead weeks or a baseline.
  2. Choose the frequency: daily, weekly (the default) or monthly.
  3. Choose the format. Reports go as PDF, XLSX or CSV. The print Gantt goes as PDF, with its paper, timescale, fit, filter, columns, baseline and legend options.
  4. Choose recipients from the project’s members. You’re ticked by default.
  5. Schedule email. The first delivery goes out on the next job run.
  • Fresh at every send. Each run builds the report from the saved data at that time. Dates follow each run’s data date. Leave the baseline as Latest baseline at each run to always compare with the newest named baseline.
  • Recipients are re-checked every time. Each recipient must still have Schedule admin, and for Cost and earned value also Budget view, when the email goes out. Anyone who has lost access gets nothing. Each report is built with the recipient’s own access.
  • Attachment or link. When the mail provider supports attachments and the file is 10 MB or less, the report is attached. Every email also carries a sign-in link to the current report, which checks access again when opened.
  • Track and stop. The panel lists your scheduled emails, how often each runs, its format and recipients, and the last run’s status and how many people it reached. Stop cancels a schedule.
  • Told when it fails. If a delivery stops for good, because you lost access or the saved report options are no longer valid, or fails on its last retry, the person who scheduled it gets a notification, in the app and by email per their preferences, with the reason. Earlier attempts that may still succeed don’t notify, and the same failure isn’t repeated while an identical alert is unread. The alert disappears if the schedule is deleted.

Schedule assistant

The schedule assistant answers questions about one project’s saved schedule, such as Why did the finish move since last update? or Summarize the critical path. It can also draft an update narrative. It’s off by default.

How it stays grounded

  • It answers from saved data: the current and previous versions and their calculations, compare runs, up to 50 date traces, health, risk, up to 10 open scenarios, and costs if you have Budget access.
  • When no saved result covers the question, it calculates one. For why did the finish move? without a saved compare of the two versions, it runs an engine comparison of the current and previous versions. For a question about what drives an activity without a saved date trace, it runs a date trace. These are read-only calculations on saved versions, at most three per question (two of them traces). They aren’t kept, and the facts they produce are labelled computed for this question. If one can’t run, the answer says so.
  • That data is turned into numbered facts. Each answer must cite them, or say the data isn’t enough. Citations to facts that don’t exist are dropped. An answer that still cites nothing is flagged: This answer cites no schedule facts. Treat it as unverified.
  • It never edits the schedule. If it suggests a change, you get a Proposed scenario with a Save as scenario button, and you adopt it in Scenarios like any other.

Turning it on

An administrator enables the assistant for the deployment and connects a language model provider. The company’s Ask uses AI setting, shared with Analytics Ask, must also be on. When it’s off, the Assistant item doesn’t appear in the schedule navigation.

The cited facts, including activity names, dates and float, are sent to the language model provider to write the answer. Each person can ask 30 questions an hour by default. You need Schedule admin and a saved version.

  • Mistake: Printing a report from an unsaved draft

    In the app: Reports and prints read the saved version. Save and calculate first, then check the version in the file name.

  • Mistake: Sending the cost report to a reviewer without Budget access

    In the app: Cost and earned value needs Budget view. Export it to PDF for people outside the Budget tool.

  • Mistake: Pasting an assistant answer into a narrative unchecked

    In the app: Follow its citations back to the facts, and treat any flagged answer as unverified.

Keep exploring

Related across os.construction

Run it on your own project.

Start a 14-day free trial. Want a say in what ships next? Join the founding program.

Your role (optional)

14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →

Ask the OS

Reading this page

Ask anything about this page. Answers use what you're reading as context.

Suggested

    AI · may be imperfect · sample data where shown

    Open file