Artefacts in
The documents your team already produces.
- Schedule extracts and programme updates
- RAID logs and action trackers
- Meeting minutes and notes
- Contractor and supplier reports
- Key project correspondence

Product
Board packs, delivery reports and risk registers that draft themselves from the project artefacts your team already produces, with a citation trail back to every source document and a human reviewing every output.
Artefacts in
Outputs out
Principles
The copilot is being built as a productised service first, with a secure software core underneath. The direction is deliberately narrow: reporting for renewables and net-zero infrastructure programmes, done properly, before anything else.
Nothing goes out without human review. AI accelerates the draft; a named person stays responsible for what is sent, filed or presented.
Every generated statement traces back to a source document and location, so senior people can trust and challenge the draft.
Model endpoints are configured not to store client content, and each client's data stays isolated.
Client data is processed and held in the United Kingdom as a design constraint, not an afterthought.
A private, local-model deployment path is in active development for sensitive project environments.
Getting involved
The first workflows are being shaped with the people who own the reporting cycle today, against real programmes and real artefacts, before any public launch.
PMO leads and delivery directors shape the first workflows around real reporting cycles.
The copilot runs against a live programme's artefacts under NDA, reviewed side by side with the existing process.
The product opens more widely only when pilots prove the drafts are trustworthy.
Product interest
Early-testing requests go straight to the Attenta inbox for personal follow-up. Launch-only interest stays quieter.
Talk to us
Ask about the copilot, or start with the operations service while the product takes shape.