ForkTex NetWork — Workspace and Work Analytics
Romania
A collaboration platform whose work-journal model is the mechanism behind a commitment we make on every engagement: a client can see what was done in every hour they paid for.
- Client
- ForkTex
- Industry
- Cloud Infrastructure
- Period
- Sep 2024 — Ongoing
Outcomes
- Granularity
- Hourly, each entry carrying its activities
- Periods
- Weekly through yearly, aggregated at read time
The situation
NetWork is our collaboration platform: organisations and teams, projects with boards, communications, and the work analytics behind a commitment made on every engagement.
What we built
The work journal
An entry pairs hours with a description of the work. The system does not accept a duration with no activity, because an optional description stops being written within two months and a column of bare numbers is unauditable.
Aggregation
Weekly through yearly figures are computed at read time, never stored. A stored total stops matching its entries the first time one is corrected, and the client is then shown two numbers with nothing to say which is right.
Reporting
Given a payload and a config, produce a document — no database, no session. The same path serves an API call, a scheduled monthly report, or an export from a file.
What mattered
This was called "work logs" and became "work journal" deliberately. A journal is chronological, append-only and audit-shaped, which settles the design arguments the old name kept reopening: corrections are entries rather than overwrites.
Outcome
In production, and the mechanism behind the work analytics included in every ForkTex engagement.