
Decision governance for IT change · Works with Jira and Confluence
¹ Flyvbjerg, Budzier, Aaen, Keil and Zottoli, Project Management Journal 57(1), 2026: 11,011 projects across 23 project types; IT cost overrun measured from the estimate at the final investment decision. 18.26% of IT projects overran by more than 50%; the mean overrun among them was 5.53 times the estimate.
Works with Jira and Confluence
The plan goes to Jira.
Stages become epics and activities become tasks, in the Jira project you choose. Exporting again updates the same issues instead of duplicating them.
The documents go to Confluence.
The initiation pack and the plan are published as pages under one parent page, in the space you choose. Exporting again updates the same pages.
The evidence comes back.
FORGE Logic® reads Jira and shows what the evidence says beside the project manager’s own report, area by area. The project manager confirms the position and explains only where they disagree.
FORGE Logic® is the record of what was decided and planned. Jira stays the record of the work. Nobody moves tool.
A report better than the evidence raises a flag that needs a named answer, or goes to the sponsor.
FORGE Logic® ecosystem
01
BILLET drafts the initiation pack from reviewed inputs and lists the gaps and weak assumptions it finds. ASSAY shows, point by point, what is demonstrated, only asserted, or missing.
02
SEAL records who approved which version, in which role, and why. The person who asked cannot approve their own request.
03
Every assumption, gap and approval is kept with the evidence behind it, so the next sponsor can see what was decided and why. On the roadmap: your own base rate from the initiatives you have already closed, and what your record says about the next one, put in front of the sponsor at the decision.
Get early access