The NGX Evidence Standard
Know what supports the decision. See what still needs checking.
Technology decisions depend on more than a number. NGX keeps supporting documents, assumptions and gaps visible so your team and advisor can understand the basis for a recommendation.
Understand what the information can support.
Each label describes one specific claim, such as a price, a term-end date or where a service is installed. Evidence supports the claim it speaks to: an invoice can establish what was billed without proving the charge was correct.
- Verified
- Evidence directly supports the record.
- For exampleAn agreement on file states the term-end date.
- Supported
- Several signals make the record credible, but it has not reached Verified.
- For exampleSeveral invoices show the same recurring charge, but the agreement is not on file.
- Assumed
- Believed to be true, without evidence sufficient to support it.
- For exampleA cost model uses an implementation date that has not been confirmed.
- Missing
- Information the record needs is absent.
- For exampleA service is billed, but no agreement on file states its notice period.
- Conflicting
- The available evidence disagrees with itself.
- For exampleAn invoice charge differs from the rate stated in the agreement.
The examples are illustrative.
In the platform, these labels are worked out from the documents on file for key facts, such as a service’s monthly cost or an agreement’s term. Your advisor uses them to see what still needs checking. See what the platform records.
A label describes the evidence behind a fact. Whether a finding is awaiting review, or a record has been signed off, is tracked separately.
The same number can mean different things.
A monthly figure can describe what was billed, what a proposal expects or what later billing confirmed.
Billed
What an invoice records.
It shows what a provider charged for a period. It does not show that the charge matches the agreement.
Projected
What a proposal or cost model estimates, under stated assumptions.
It depends on prices, dates and scope that are still to happen.
Verified result
What later evidence confirms against the agreed comparison.
For example, billing after a change, set against the starting point both sides agreed on.
A lower proposed monthly price is not automatically a realized saving. Upfront costs, overlapping services, timing and scope can all change the result, so cost savings stay projected until billing confirms them.
See how a transition is costedKeep the question connected to its source.
When a detail is missing or two sources disagree, the question stays with the records it came from until the right person answers it.
Connect the relevant records and supporting documents.
Your team and the platform
Your team sends invoices and agreements through a secure upload link. The platform reads them, links them to the services and locations they cover and holds uncertain details for review.
Identify the missing detail or disagreement.
The platform and your advisor
Checks flag differences such as billing at a closed location or an invoice above the agreement’s monthly commitment. Your advisor reviews what is flagged and what is missing.
Have the appropriate person confirm or resolve it.
Your team, the provider or your advisor
The answer comes from whoever holds it: your team for a site change, the provider for its billing, your advisor for an agreement’s terms.
Update the record with the supported conclusion.
Your advisor
Your advisor updates the record, and its label reflects the evidence now on file. Until then, the question stays open.
Missing information does not prove a service is absent, and a flagged difference does not by itself prove an error.
Start with your Technology Baseline.
Bring the invoices and agreements you already have. We’ll confirm the scope, organize the information and review the findings with your team.
