The programme said week 14.
Who agreed to week 17?
On every job that slips, the dates are the easy part to reconstruct. The hard part is who accepted the change, on what basis, and whether anyone could have edited the record afterwards. Axgenta is built so that question always has an answer.
A programme that becomes real work
Milestone, task, sub-task — on a Gantt planner, a drag-and-drop card board, or a spreadsheet-style table, all editing the same plan. Then you publish, and every line lands on a named person's list instead of staying a picture of an intention.
Dependencies that cascade
Link bars with finish-to-start, start-to-start, finish-to-finish or start-to-finish relationships. Move one and every must-follow successor shifts with it, as a single undoable change.
Working-day maths, not calendar days
The planner respects your company work calendar, so a five-day activity doesn't quietly land on a weekend or a public holiday.
You cannot publish an incomplete programme
Every milestone must hold at least one task, and every task and sub-task must carry a description and a named responsible person. Publishing is blocked until it does, with the gaps named.
The plan stays a draft until you publish it, and a published programme keeps syncing both ways: changes proposed from the work side come back as an explicit accept or reject rather than silently rewriting the baseline.
The part inspectors care about
Work under inspection cannot be altered. By anyone.
When a task moves to Review Needed, the structure locks: sub-tasks cannot be edited or deleted and progress cannot be updated — not by the assignee, not by the site manager, not by the project owner. Only the named reviewer can act, and only to approve or reject.
Once complete, the structure freezes again. Reopening is not an edit: the performer submits a reopen request, the owner approves it, and the task is stamped Restarted with its progress reset and a fresh start timestamp. The record shows that it was reopened, permanently.
Completion notes
Every finished task carries a written account of how it was done — the evidence a reviewer scores
Task history
The sequence: when it slipped, what was approved, what was rejected and on what feedback
File access logging
Reads are logged, so “who opened the revised drawing?” has an answer
Twelve trades on site. Zero seats to buy.
Assign work to a subcontractor by email, from the task itself. They get a branded task page — the invitation email deliberately carries no description and no internal identifiers. Their status, progress and completion time sync back onto your programme and show up on your dashboard like any other update.
Your internal notes never cross. Their attachments stay theirs. Neither side can browse the other. When the package closes, you revoke the link: new posts stop, the history stays readable.
How the boundary is enforcedCommercial & risk fields, native
- Contract reference
- Risk level — Low to Critical
- Client name
- Budget
- Location
- Sponsor and reviewers
- Project type — Client, Infrastructure, Maintenance
- In-scope, out-of-scope, dependencies
Save the set your team always uses as a reusable template, and put site standards in the project note — its text is appended to the description of every task the programme generates, so the method statement reaches every trade automatically.
Inspections, permits and plant checks that run themselves
A scheduled task is a rule that creates real work on a date. Until that date fires it stays in a queue rather than cluttering anyone's list pretending to be work — which is exactly the failure mode of creating a year of recurring inspections up front.
Set the rule once
- Daily, weekly, monthly, yearly, or up to 60 hand-picked dates
- Sub-tasks carry their own responsible person and their own due offset
- Reviewer, priority, reminders and method notes copy onto every occurrence
Then it survives real conditions
- Auto-tags stamp month, year and occurrence number, so “every permit check in FY26” is a filter
- If the system was unreachable when a date passed, only the most recent occurrence publishes — no flood of stale work
- If the owner's account goes inactive the schedule pauses rather than failing silently
The client and the consultant see the programme. Neither gets a licence.
Toggle a public link on the project and any stakeholder opens a read-only view with no sign-in. Toggle it off and the URL stops working that moment. For the formal record, export to Excel or PDF and pick exactly which columns travel — a lean set for the weekly progress note, the full set including contract reference and risk level for the archive.
White-label branding on exports is available on Apex and above. See plans →
Where Axgenta stops, stated up front
This is a delivery and accountability layer, not a construction suite. There is no BIM or model viewer, no drawing register, no formal RFI or submittal workflow, no quantity take-off, and no earned-value cost control. Teams generally keep the tools that do those things.
What Axgenta replaces is the layer nobody has a tool for: the programme that has drifted from the spreadsheet, the trade whose progress lives in a WhatsApp thread, and the sign-off that nobody can produce six months later.
Put one package through it
Fifteen days, full access, up to five seats, no card. Build one milestone programme, invite one subcontractor, and share the view with the client.