The project's work, stage by stage, with the time it took
Activities move through the project's stages, and a stage only advances once its targets are met. Hours are logged against that work and come back as a schedule, reports, and a better estimate for the next project.
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.
The project advances stage by stage, and a stage only opens once its targets are met
The office picks the track and the product minds the gate: every stage has targets measured inside the project, and each advance is recorded.
Example: on a project following the NBR 13531 track, the developed design stage meets its three mandatory targets (no pending activities, at least one accepted, requirements checked) and the desirable one (a sheet). The gate opens, the project advances to the next stage, and the advance is recorded with its author and the state of the targets.
Ready-made tracks, or the office's own
NBR 13531, RIBA and Lei 14.133 come configured with their stages. Whoever administers the licence can build a track of their own.
An activity is born in a stage
With no stage given, an activity joins the project's current stage, and it is that stage's work that counts towards the gate.
Targets, not a manual tick
No pending work, at least one activity accepted, the stage's requirements checked and, desirably, a sheet in the project.
The exception is recorded
Advancing with a mandatory target still open is a manager's decision, with a reason, saved alongside the state of the targets at that moment.
Every activity with a state, an owner and a history
- 01
The one who accepts is a manager
On the board, accepting, rejecting and reopening are manager decisions, recorded with author and time. Everyone else gets a clear refusal.
- 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 history that only grows
Every creation, transition and check becomes a record, 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
Time is logged by period, against the activity
Each person has their own timesheet, and the project's Hours tab logs straight onto the project. There is no timer to leave running: you say when it started and when it ended.
Example: on the timesheet, someone logs 08:00 to 12:00 on the Aurora Building project, linked to the activity Check V3 deflection, with a description of the work. The entry goes in, the service is suggested from the description, and the day adds up to 8 hours, meeting the contracted working day.
A period, not a timer
Day, project, start and end, with a description of the work. Duration is computed on the server, and a shift that runs past midnight counts too.
The hour lands on the activity
An entry can point at an activity of the same project. That link is what lets the schedule compare planned with actual.
The service comes from the description
The category is suggested from what was written, out of the licence's own service catalogue. Picking it by hand locks the choice.
The day has a ceiling, the rest is a warning
Going past 24 h on the same day is refused, saying how much is already logged. Overlaps and gaps show as warnings, without blocking.
Each person's working day
The day's balance is measured against the contracted working day. Changing it applies from today on, and earlier days stay as they were.
Logged time comes back as a schedule, reports and an estimate
A logged hour does not sit idle in a timesheet. It shows an overrun while there is still time to act, closes the month for whoever administers, and teaches the office to estimate the next project.
- Logged periodday, project, start and end
- Linked activitythe hour lands on the right work
- Servicesuggested from the description
- Contracted dayeach person's balance
- Scheduleplanned against actual, with overruns in view
- Reports and CSVby project, by person and by service
- Next estimateactual hours from finished projects recalibrate the service type
Schedule
Each item shows actual hours against planned and flags the overrun. Actuals show for whoever manages the project and whoever administers the licence.
Reports and CSV
By project, by person and by service, month by month, with a CSV ready for Excel, for whoever administers the licence.
The next estimate
Once five projects of a service type are finished, the product proposes replacing its estimate with the median of what they actually took. And the assistant answers whether the office has done something similar, with the estimate next to the actual.
See the project's work and time in one place
Tell us how your office tracks work and hours today. We reply by e-mail.
Talk to usRather try it first?