How GovIntel Works
What happens after you connect
Once your connection is verified the assessment dispatches, resolves and delivers without an operator driving any part of it.
Reaching CONNECTED used to be the end of the automated path. A customer could complete every onboarding step and then wait indefinitely, because starting an assessment required a human. That is no longer the case.
What runs without anyone
A background sweep, on an interval, does four things:
- Dispatches an assessment for engagements that have connected and are cleared to run
- Reconciles runs in flight, resolving each to its real outcome
- Retrieves and stores the board pack when a run succeeds
- Emails you that your pack is ready, with retry and backoff if mail is failing
Why the email is sent by a sweep
A notification sent at the moment of transition has nowhere to put a failure. That is exactly how an earlier defect worked: a send was awaited inline, the mail provider started rejecting, and a saved record was reported to the customer as a failure.
Driving the send from a sweep makes it a fact to be reconciled rather than a step that can fail a transition. The state is already durable before anyone tries to email about it.
What still needs a person
Pricing and payment for a paid engagement, and issuing your onboarding link in the first place. Neither is something a system should decide on its own.
If a run does not report
An assessment that never produces a result is settled rather than left running forever. A dispatch that produced no run at all is reported as a failed dispatch after a grace period, rather than as an engagement that claims to be running something that does not exist.