How GovIntel Works
The engagement lifecycle
The stages an engagement moves through from first enquiry to a delivered board pack, and what each one means from your side of it.
Currentengine 9.0.0Verified 2026-08-30
An engagement moves through a defined set of stages. Two facts drive it: the state of the AWS connection, and the state of the assessment.
| Stage | What it means |
|---|---|
| New lead | Your enquiry has been received |
| Onboarding link sent | A single-use link to connect your AWS account has been emailed to you |
| Onboarding opened | You have opened the link and started the connection |
| Deploying AWS access | You are creating the CloudFormation stack in your account |
| Verifying access | GovIntel is running a real verification against the role you created |
| Connected, starting assessment | The boundary check passed and the assessment is being dispatched |
| Assessment running | Collectors and control checks are running against your account |
| Board pack ready | The pack has been produced and you have been emailed a link to your portal |
| Delivered | You have retrieved the pack |
| Closed | The engagement is complete |
The outcomes that are not the happy path
| Stage | What it means |
|---|---|
| AWS connection failed | Verification did not pass. The reason is reported, and it is usually a stack that did not finish or an option chosen the other way |
| Assessment failed | The pipeline broke. That is ours to fix, not yours |
| Insufficient evidence | The run worked, and refused to issue a rating because too little of the environment could be evidenced. A different fact, deliberately kept separate |
| Access expired or revoked | The engagement expiry passed, or the stack was deleted. Both are normal ends to an engagement |
What moves it
Most transitions are automatic. Once your connection is verified, dispatch, status resolution, pack retrieval and notification all happen without an operator. See What happens after you connect.