Work with sign-off, and time measured where it happens
Every activity has a state, an owner and a trail. Only a manager accepts, and accepting publishes that version of the calculation report. Hours are logged by period and compared against each person's contracted working day.
Example: the activity “Check V3 deflection” is in review, the requirement check runs, and a manager accepts it. The record keeps who accepted and when, and that version of the calculation report becomes published.
What the board guarantees
- 01
The one who accepts is a manager
Accepting, rejecting and reopening are manager decisions. Everyone else gets a clear refusal, and the decision is recorded with author and time.
- 02
Review checks the requirements
On the way into review, the applicable requirements are checked. If something diverges it comes back with the report, and going ahead anyway takes an explicit gesture.
- 03
Sign-off publishes the report
That moment's version of the calculation report becomes published. Reopening the activity puts the document back to draft.
- 04
A trail of what happened
Every creation and every transition becomes a record that only grows, and the activity's history shows all of it in plain words.
An activity is born from what the project already knows
A finding on the project, the sheet that failed the overnight sweep, the assistant when it cannot do what was asked, or the divergence that arrived as BCF.
- Finding on the projectthe button on the project overview
- Nightly watcha failed sheet becomes work at 05:17
- Assistantwhen it cannot do it, it hands the work over
- Divergence in BCFthe import brings the target with it
- Board, with a trailevery transition is recorded, with author and time
- Scheduleactual against planned, in hours
- Manager sign-offpublishes that version of the calculation report
How time goes in, and what it becomes
- 08:00 → 12:00
Logged by period, with no timer
Day, project, start and end, with a description of what was done. Duration is computed on the server, never sent by the browser.
- hour → activity
An hour can belong to an activity
The entry links to an activity of the chosen project, and that is how the schedule compares actual against planned.
- description → service
The service comes out of the description
The category is suggested from what you wrote, and picking it by hand locks the choice. Services are defined by whoever administers the licence.
- 24 h cap
The day has a limit, the rest is a warning
Going past 24 h on the same day is refused, with how much is already logged. Overlaps and gaps show as warnings, without blocking the entry.
- 8 h/day contracted
A working day per person
Each person has their own, the day copies it when it is created, and a change applies from today on: a closed month is not rewritten.
- CSV
Reports for whoever administers
By project, by service and by person, with a CSV ready for Excel. On the project tab, the manager sees the team and each person sees their own hours.
The same work, over time
Work breakdown, with bars
The breakdown on the left, months across the top, one bar per item and today's line. Each leaf shows actual and planned, and flags the overrun.
Progress weighted by duration
The indicator says how far it has come, how many activities are on the schedule, and how many are late.
No dependencies between activities
Order comes from the tree and from the dates. Predecessor and successor do not exist yet, and this page would rather say so.
See your work and your hours in one place
Tell us how your office tracks work today. We reply by e-mail.
Request access