↓ Skip to main content
Rillsoft AI
Connect Rillsoft

Prompts

Show the cost trend baseline and current plan per week

Weekly columns and cumulative lines for baseline and current costs in the chosen period – on one weekly axis, checked against the program.

All people, companies and projects shown are synthetic Rillsoft sample data – from the shipped industry packages or, where stated, from a test project.

The prompt

Show me the cost trend from Rillsoft Project per week: on top two columns per week, baseline and current plan, below both cumulative as lines, on the same weekly axis. First ask me for project or portfolio and the period. Spread the costs of each task evenly over its working time by the calendar and sum them per week; check the calculation on the current effort against the role usage per week and name the largest deviation. Save nothing.

Changes the project (one undo step)

Show the detailed prompt
Create the cost trend of baseline and current plan per week from Rillsoft Project. First ask me for: - Scope: project or portfolio (name the open one and let me confirm), - Period: start and end; suggest whole weeks, at most about 30 – otherwise months. If the open portfolio has unsaved changes, ask whether I want to save or discard them. Baseline means the costs in the baseline, current plan the costs of today's plan; there are no booked actual costs. The program's cost chart cannot be read through the interface; you calculate the trend from the tasks. Data: - Read the calendars in the portfolio. Set the role usage by project and role, absolute, time filter on the period, time scale week, and read the report: the sum per project and week is the current effort (for the check). - Open the project files one after another. Read the project tree (calendar per task) and, without a time filter, cost, time and effort variance; match the tasks by UUID. - Per task and week: share = working time in the week divided by working time from start to finish, both from the task's calendar; tasks on their people's calendar with the project calendar. Baseline with the baseline dates, current plan with today's dates. Costs per week = costs × share, cumulative from the start of the period. - Check on the current effort with the same share: the total per project equals the role usage in the period; per week the portfolio deviates by at most 5 %; projects without a cost variance have baseline equal to current plan in every week. If not, report that instead of the chart. Presentation: - Two panels one above the other on the same weekly axis, no second y-axis. - On top two columns per week, baseline in light grey-blue, current plan in strong blue; label only the strongest week. - Below the baseline cumulative dashed, the current plan cumulative solid; at the right edge the end values and, with extra costs, a red ▲ with the gap. - x-axis calendar weeks, months below; y-axes from 0. - Title "Cost trend baseline and current plan per week – <start>–<end>", subtitle with scope, baseline, calculation and "amounts without a currency". - Footer: totals in the period, variance, strongest week, week with the largest variance, one sentence on the check with the largest deviation, source with date. Save nothing, reopen the portfolio at the end and reset view and time scale.

In your words

  • Half-year: How do the costs of our portfolio develop per week until the end of March, baseline against current plan, also cumulative?
  • Single project: Show me the weekly cost trend with the cumulative line for the Press R-12 retrofit.
  • Coarser: Cost trend of the portfolio for the whole of 2027, per month instead of per week, please.

What you need

  • A portfolio or project in which every project has a baseline.
  • Answers to the AI’s questions: scope and period.
  • An AI client that can draw charts (as an image, HTML or a file). Rillsoft Project supplies the figures per task; the AI spreads them over the weeks and draws.
  • Read-only mode is not enough: opening files and switching view, time filter and time scale count as writing in the interface. The AI changes nothing in the plan; at the end it resets the view.

What you get

Two panels on the same weekly axis: baseline and current plan per week on top, both cumulative below, plus totals, the strongest week and the check. In the test portfolio Machinery and plant engineering (five projects, one baseline each and extra effort in three projects set for the check), CW 40/2026 to CW 12/2027 hold 2,018,488 in the baseline against 2,063,040 in the current plan, +44,552 or 2.2 %. The strongest week is CW 50/2026 with 127,854; the extra costs arise between CW 43 and CW 50, most of all in CW 48 (+10,024).

In the single project R-12 the extra costs fall in CW 47 to 50; the cumulative current line ends 14,400 above the baseline. The AI checks the calculation on the current effort against the role usage per week: the totals per project match, per week the portfolio is at most 4.7 % off, R-12 exactly in every week.

Cost trend baseline and current plan per week, portfolio Machinery and plant engineering, 2026-09-28 to 2027-03-28: on top a light baseline and a blue current plan column per calendar week between about 25,000 and 127,854 (strongest week CW 50), a dip over Christmas; below the cumulative lines, baseline dashed up to 2,018,488, current plan solid up to 2,063,040, gap ▲ +44,552
Result of the prompt: baseline and current plan per week and cumulative – the extra costs arise between CW 43 and CW 50
Cost trend baseline and current plan per week for the Press R-12 retrofit: columns from CW 45/2026 to CW 5/2027, current plan above the baseline in CW 47 to 50 (strongest week CW 48 with 20,808); cumulative lines end at 116,056 baseline and 130,456 current, ▲ +14,400
The same in a single project: the extra costs of R-12 fall in CW 47 to 50

Why it is useful

Whether extra costs arise early or late in a project, and when the money is needed, only shows in the trend. Rillsoft Project has a cost chart for this, but it cannot be read through the interface. The prompt recalculates the trend from the tasks and backs it with the role usage per week.

How the answer is produced

The AI reads calendars and the role usage per week in the portfolio, opens the project files one after another and reads costs, dates and effort per task in the baseline and the current plan. It spreads the costs of each task evenly over its working time, sums them per week and accumulates them. It compares the same calculation on the current effort with the role usage. The total per project for a period comes from Draw baseline and current plan costs for a period.

rillsoft_portfolio_file_open rillsoft_calendar_list rillsoft_view_state_get rillsoft_view_state_apply rillsoft_timescale_apply rillsoft_analysis_report_get rillsoft_project_file_open rillsoft_project_tree_get rillsoft_variance_report_get

Limits

The trend is a calculation by the AI: costs spread evenly over the working time of each task. Rillsoft Project spreads tasks that follow their people’s calendar differently around absences; so the totals match exactly, single weeks up to about 5 % do not – the AI names the largest deviation. Accumulation starts at the beginning of the period, not at the project start. Invoicing and payment terms are not included. “Current plan” means planned costs, not booked actual costs; amounts without a currency. The question belongs to the catalogue of management questions, topic costs. The product page of Rillsoft Project describes planned/actual comparison. Related prompts:

Try it

Get started
Industry package
Machinery and plant engineering.rpp
Product version
Rillsoft Project 10 (Build 10.0.625)
Last verified
2026-10-16
Verification
Figures and statements verified on the named sample package against the named product build – MCP session, view and report; German and English package with identical figures.