Each move keeps its reason, the risk behind it and who decided. "Why is this late?" takes ten seconds, and everybody gets the same answer.
Project and portfolio memory
The dates moved. Nobody wrote down why.
For PMOs and programme leads who answer to executives for several projects at once.
Every organization keeps its plans - in spreadsheets, slide decks, and a project tool nobody updates. Almost none of them keep the reasoning: why a date moved, which risk caused it, who decided. Theruka keeps both, so strategic work stops disappearing into meetings, files, and chat history.
Every Max feature for 14 days. No card, nothing to install - start with the spreadsheet you already have.
Decision memory
A plan tells you what you agreed to. It rarely tells you why it changed.
Six months in, the dates are different, three assumptions have quietly moved, and the file that explains any of it was never written. So the same question gets re-argued every quarter, and a slipped date looks exactly like a bad decision.
Decision memory is the missing half: the record of why the plan is what it is, kept next to the plan itself. It turns "this is late" into "this is late because we chose the pilot over the full rollout in March, and here is what we did about it."
- Why, not just what Every change carries the reason it happened, next to the change itself.
- Settled stays settled The argument you finished in March does not come back in June.
- A slip has a cause You can tell a date that moved for a reason from a decision that went wrong.
What you get
Everything around a plan, in one place.
Open risks ranked by the milestone they threaten and when, each with an owner - and the ones nobody has answered at the top.
Next to every committed date, the date it is likely to finish - learned from how your own team's milestones have finished before.
theruKO is the AI assistant built into Theruka. Drop in Excel, MS Project, Word, PowerPoint or PDF and it becomes milestones, owners and risks; then theruKO drafts the weekly update and answers "why did this move?" It runs on your plan's monthly AI credits.
On Max: connect Theruka to Claude or Cursor, sign in, and ask "what needs my attention?" or "why did this slip?" It can read your plans, never change them.
One page a week. Owners answer from their phone, the report is ready to print, and Slack or a weekly email reaches whoever never opens a dashboard.
One version of the truth
The plan, the report and the answer are three copies of the same thing.
That is where the friction comes from. The plan lives in one tool, the report is rebuilt by hand in another, and the answer to "why did this move?" is reconstructed from memory in the meeting itself. Three artefacts, maintained separately, disagreeing quietly - and the executive is the one who finds out they disagree.
The plan
Kept onceDates, owners, dependencies and risks in one place - imported from the plan file you already have, or pulled from Jira or Monday with the history of every date, so it stays in step with where the work actually happens.
The report
Not rebuilt - readThe executive view is the plan, arranged for somebody who has ten minutes: what moved, what caused it, what is still unanswered and how long it has been open. Nobody assembles it, so it cannot be out of date or quietly flattering.
The question
Answered from the same record"Why is this three weeks later than March?" is answered by the plan itself, in front of everybody, with the risk that moved it and what was decided. Not from a memory that flatters whoever is speaking.
When those three stop being separate documents, the arguments they used to cause stop happening. The meeting is about what to do next, rather than about whose version of last quarter is right.
By the second month, "why is this late?" is a ten-second answer instead of a two-day search through files and chat history - and the answer is the same one everybody sees.
How it works
This is your plan, minutes after you upload it.
Bring the spreadsheet your team already argues over, or paste the plan as text. Theruka reads the milestones, dates, owners and risks out of it and builds the executive view for you - then keeps the reason attached to everything that changes afterwards.
Start your 14-day free trial
Where it fits
It works with the plans you already have.
You do not migrate anything or ask anyone's permission to start. Upload one plan, keep using the spreadsheet next to it if you want, and see whether the second month is calmer than the first.
- Your files, not a new formatExcel, CSV, MS Project, Word, PowerPoint, PDF or pasted text in - reports out as PDF
- Your data stays yoursNothing is shared until you share it, and there is no lock-in
Before you try it
The three questions everyone asks first.
- Do I have to give up my spreadsheet, or Jira, or MS Project?
- No. Theruka sits above whatever you already run rather than replacing it - your team keeps working where they work. Bring a plan in from Excel, CSV, MS Project (saved as XML), Word, PowerPoint, PDF or pasted text, or connect Jira or Monday: the work comes in with the history of every date, and stays in step when you pull. The connection only reads - Theruka never writes back to Jira or Monday.
- Who else has to approve this before I can try it?
- Nobody. Free is two people, one portfolio and one project, sign in with Google - no card, no install, nothing for IT to deploy. You can load your own plan this afternoon and decide on your own evidence. Bring the PMO in later, once you have something worth showing them.
- Where does my data live, and can I get it back out?
- In your own workspace, private by default: nothing is visible to anyone else until you deliberately share it, and every share is a link you control and can revoke. Reports print to PDF from inside the product, and if you ever want a full copy of your data, ask us and we will send it. Enterprise adds a security review for organizations that need one before they can say yes.
- Your data stays in your workspace
- No sharing without your permission
- Your data back whenever you ask - no lock-in
Company