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
Which projects are behind their planned progress? First ask me for project or portfolio; the reference date is the status date. Read actual progress in Rillsoft Project, let the planned progress at the status date be calculated, read it and undo that at once. Show planned, actual and the gap per project in percentage points and hours, weighted by effort, as a ranking with a traffic light (amber above 5, red above 15 percentage points), and the tasks the gap sits in. Save nothing.Changes the project (one undo step)
Show the detailed prompt
Create a ranking of the projects by progress gap from Rillsoft Project.
First ask me for:
- Scope: project or portfolio (name the open one and let me confirm),
- Thresholds: name the default and ask whether it applies – amber above 5, red above 15 percentage points behind.
The reference date is the status date; name it.
Tell me first: planned progress is written to the plan briefly and undone at once.
Data:
- Read actual progress and effort per task.
- Let planned progress at the status date be calculated, read it, undo and check that actual progress is back for every task; if not, report that instead of the ranking.
- Delayed tasks from the conflict list, only with a delay above 0.
- Per project, planned and actual weighted by effort, gap in percentage points and in hours; per task with a gap, planned, actual, percentage points, hours and delay.
- Do not recalculate anything from the plan.
Report:
1. Header with scope, reference date and source.
2. Three to five key findings with figures: how many projects are behind, the project with the largest gap, the largest task, projects not started yet.
3. Dumbbell per project: planned light, actual dark, one colour, one axis in percent, gap in percentage points and hours at the end.
4. Ranking of the projects with traffic light and table of the tasks with a gap.
5. Data basis and rules.
Save nothing.In your words
- Monthly review: Which projects are behind plan at the status date, and by how many hours?
- Single project: Is MX-200 behind on progress? Show me the tasks with the largest gap.
- Stricter: Rank by progress gap, but red from 10 percentage points.
What you need
- An open project or portfolio with maintained actual progress and a set status date.
- Answers to the AI’s questions: scope and whether the default thresholds apply.
- Read-only mode is not enough: the AI has planned progress calculated, reads it and undoes the step at once; then it checks that actual progress is unchanged.
What you get
A ranking with key findings, a dumbbell per project and the tasks with a gap. In the test portfolio Machinery and plant engineering (five projects, status date 16 Nov 2026 and a backlog in two projects set for the test) two of five projects are behind plan, none by more than 5 percentage points – all progress lights green. Furthest behind is Assembly line MX-200: planned 21.4 %, actual 17.1 %, 4.3 percentage points or 244 hours of work.
The gap sits in four tasks; the largest is “Program the station sequence control” with planned 40 % and actual 10 %, 108 hours and delayed by 4.5 working days. E-Drive 400 test bench has not started yet at the status date. After undoing, the AI checks that every actual value is back.
Why it is useful
Progress shows earlier than any date whether a project is drifting from the plan. Rillsoft Project calculates where each task should stand at the status date; the ranking sets that against the reported state – comparable in percentage points and tangible in hours, with the tasks it hinges on.How the answer is produced
The AI reads actual progress and effort per task, has Rillsoft Project calculate planned progress at the status date, reads it and undoes the step at once. Per project it weights by effort, calculates the gap in percentage points and hours and rates like the progress light in the overall status. The delay per task comes from the conflict list.rillsoft_project_tree_get rillsoft_task_progress_recalculate rillsoft_history_undo rillsoft_project_conflict_list
Limits
The ranking is only as good as the reported actual progress. A progress gap is not a schedule delay: a task can be behind and still within its float – whether committed dates are at risk is shown by Which committed delivery dates are at risk?. The status of a single project in words comes from the project status summary; all 22 questions are in the catalogue. The product page of Rillsoft Project describes progress tracking. 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.