How GovIntel Works
Who is waiting on whom
At every stage the next move belongs to you, to GovIntel, or to the system. Knowing which is what stops an engagement stalling unnoticed.
Every stage records whose move it is. This is the single most useful thing to know about an engagement in flight.
| Stage | Waiting on |
|---|---|
| New lead | GovIntel |
| Onboarding link sent | You |
| Onboarding opened | You |
| Deploying AWS access | You |
| Verifying access | The system |
| Connected, starting assessment | The system |
| Assessment running | The system |
| Board pack ready | You |
| Assessment failed | GovIntel |
| Insufficient evidence | GovIntel |
| AWS connection failed | GovIntel |
| Access expired or revoked | GovIntel |
| Delivered | Nobody |
| Closed | Nobody |
Why it is recorded rather than inferred
A stage waiting on the system that stops moving is a defect. A stage waiting on you that stops moving is not, it is a customer who has not got to it yet, and chasing that as though it were a fault is worse than leaving it alone.
The two need different responses, and telling them apart requires the distinction to be stored rather than guessed at from a timestamp.
Stalled engagements
GovIntel detects engagements that have stopped moving and raises it internally, once. The clock it measures is the time since the connection state last actually changed, not the time since the record was last written, which routine bookkeeping would otherwise reset.