Product

Everything your portfolio needs to stay standardized — and stay true to its own work breakdown.

Nine areas, all grounded in the same principle: nothing important is entered in isolation at the top. It's derived from the WBS itself.

Portfolio structure

Environment → Portfolio → Sub-portfolio → Project, with real server-side multi-tenant isolation.

Standardized WBS

A portfolio-owned catalog of workpackages and deliverables, individually activated per project.

Reusable templates

Pre-select catalog items and pre-schedule the Gantt so a new project starts already sequenced.

Planning & critical path

4 dependency types, business-day lag, and a genuine forward/backward-pass CPM calculation.

RACI everywhere

Accountable / Responsible / Consulted / Informed at workpackage, iteration, and deliverable level.

Two-tier budget

OPEX/CAPEX budget lines broken into individually-payable commitments, annualized view.

Workload visibility

Planned vs. actual time kept strictly separate; a manager board across every project at once.

Consolidation & reporting

Portfolio-wide matrix of progress and risk, plus a journal-style status report per project.

Customization

Six custom field types and a drag-and-drop intake form builder, per portfolio.

Standardization

A catalog once, then templates do the rest

Each portfolio owns its own curated catalog of standard workpackages and deliverables. Project templates, scoped per sub-portfolio, pre-select which catalog items apply and pre-schedule their Gantt — offsets, durations, dependencies — anchored to real dates the moment a project is created.

  • A catalog item added later can be reintegrated into an already-running project
  • Cycle detection runs before any template dependency is saved
Reusable project template with a pre-scheduled Gantt — Klonn.it screenshot
Planning & critical path

Four dependency types. A real critical path — not a cosmetic badge.

Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish — each with lag in business days. A forward pass, then a backward pass computes slack per task; anything at zero slack is flagged critical.

Discovery Design Legal review Sign-off Build Test Launch
Critical path — zero slack Has float — not blocking the end date
FS SS FF SF Lag in business days Cycle detection on save
Accountability

RACI that actually governs who can edit what

Accountable, Responsible, Consulted, Informed — assignable at workpackage, iteration, and deliverable level, multiple people per role. It's not a separate document: write access to budget lines, schedule and progress cascades down the WBS from whoever holds Accountable or Responsible on that entity or an ancestor.

  • Server-validated — an assignee must be an active member of the same environment
  • Feeds directly into "My tasks" and "My team" workload boards
RACI matrix at deliverable level — Klonn.it screenshot
Budget

Budgeted, committed and paid — reconciled, not guessed

A budget line (OPEX or CAPEX) breaks down into individually-payable commitments. A line with any commitment, or a commitment already marked paid, can't be silently deleted — enforced server-side as defense in depth, not just hidden in the interface. An annualized view breaks totals down by year, with an explicit "unplanned" bucket.

  • Attachable at workpackage, iteration, or deliverable level
  • Write access scoped by the same RACI cascade as everything else
Two-tier OPEX/CAPEX budget with committed and paid amounts — Klonn.it screenshot
Workload

Planned time and actual time never get mixed up

Planned time is entered by the project manager; actual time only ever by the person themselves — enforced server-side, not a convention. A dedicated "My team" board gives a service or team manager direct visibility into their people's load across every project they're involved in.

  • Granularity (day/week/month/…) locks once entries exist, to prevent mixed data
  • Real visibility across projects — not a spreadsheet per project manager
'My team' workload board grouped by project — Klonn.it screenshot
And the rest

Reporting, customization, and the security to back it all up.

Reporting & consolidation

A journal-style status report compiling every tracking note across the WBS, plus a portfolio-wide consolidation matrix. Printable via your browser's own print-to-PDF.

Customization

Six custom field types, including long-form formatted text, markable required and/or filterable — placed via a drag-and-drop project intake form builder, per portfolio.

Security & administration

Invitation-only onboarding, brute-force lockout, CSRF everywhere, hardened sessions, immediate-effect deactivation.

AI project assistant

And an AI assistant that ties it all together — without ever deciding for you.