Intrenion Ledger
A Service Decision Management System
Stop Assuming Agreement. Start Locking Decisions.
- Email records discussions.
- Excel tracks tasks.
- This records commitments.
The Difference
- Decisions require explicit approval from named stakeholders.
- Silence cannot be treated as agreement.
- Every change keeps visible history.
Vendor Projects Drift Because Decisions Are Not Clearly Locked
Most IT project problems do not start with big failures. They start with unclear agreement.
- Meetings end, but no one clearly approves the decision.
- Scope changes without written confirmation.
- Responsibilities shift without clear ownership.
- Old topics return because nothing was formally closed.
- Silence in an email is treated as agreement.
Small, unclear decisions later become expensive disputes.
What Vendor Tension Really Sounds Like
This is what people actually say in steering meetings.
- “That’s not what we agreed.”
- “We understood it differently.”
- “This was never formally approved.”
- “That was only a discussion, not a decision.”
- “We need to reopen this.”
These moments damage trust and increase cost.
What This System Does
This system turns discussions into explicit, approved Decisions.
- Every important meeting produces a clear Decision statement.
- Each Decision has one named owner.
- Stakeholders must approve, reject, or disagree and commit.
- Open Decisions stay visible until they are closed.
- Reopened Decisions keep full approval history.
Nothing moves forward on assumption.
The Real Risk
Unclear decisions create financial and political exposure.
- Scope increases without formal approval.
- Change orders turn into negotiation fights.
- Delivery delays trigger blame discussions.
- Contracts become hard to defend.
- Sponsors lose credibility with management.
When escalation starts, this is the record you bring into the room.
Traditional tools track activity but do not lock commitment.
- Email records messages but not formal approval.
- Excel tracks items but allows silent edits.
- Project tools track tasks but assume alignment exists.
- Shared documents store notes, but not binding Decisions.
- None provides a clean commitment history during disputes.
They work when things are calm and fail when pressure rises.
What Changes After a Few Meetings
The effect becomes visible quickly when used consistently.
- Fewer repeated discussions.
- Clearer ownership.
- Faster approvals.
- Cleaner steering meetings.
- Less confusion about scope.
Clear Decisions reduce later chaos.
What This Is and What It Is Not
This is a commitment control layer for vendor projects.
- It is not project management software.
- It does not replace task tracking.
- It is not a meeting transcription tool.
- It is not document storage.
- It locks Decisions that change scope, cost, timeline, or responsibility.
It governs what actually changes the project.
Pricing
Pricing reflects project-level exposure.
- 500 EUR per active project per month.
- Billed quarterly in advance.
- Up to 10 users included.
- 100 EUR per additional user per month.
- Onboarding and personal support included.
- Subscription renews each calendar quarter unless cancelled 30 days before quarter end.
For most projects, one avoided scope dispute covers multiple quarters of subscription.
Who This Is For
This is built for serious external IT projects.
- Project sponsors are responsible for delivery.
- Procurement and vendor management leads.
- Projects between 50,000 and 250,000 EUR.
- Teams facing repeated alignment problems.
- Engagements where scope and money matter.
If your vendor project carries real exposure, locked Decisions are not optional.
Core Capabilities
The system provides the essential controls needed to govern vendor Decisions.
- Structured Decision creation during or immediately after meetings.
- Explicit approval workflow with named stakeholders.
- Open the Decision dashboard with aging visibility.
- Full commitment history with controlled reopening.
- Role-based access for client and vendor users.
These capabilities ensure that important Decisions are clear, approved, and traceable throughout the project lifecycle.
Last updated: 2026-02-25