8 min read · Educational overview
Step 2: Correct and Approve Energy Data Without Losing the Original
When an input needs attention, the client should submit a clear correction—not overwrite history. The system keeps the complicated versioning, review routing, and audit trail in the background.
PDR Delta handles an exception as a new version that can be reviewed and approved. The original remains available as evidence, the corrected value has its own history, and calculations or exports are limited to the approved version that passed the required checks.
1. A correction becomes a new version
A client or authorized reviewer does not need to edit history out of existence. They provide the corrected value or document through the workspace. The system connects that submission to the original record and preserves the sequence for later review.
2. Review ownership stays visible
Different actions can require different roles. A client can provide information and respond to a request. A reviewer can examine evidence. A Founder can approve controlled provider drafts, factor registrations, calculations, or batch decisions. The workspace keeps those responsibilities separate.
3. Automation removes repetitive work
Behind the scenes, the system can route exceptions, check coverage, prevent duplicate decisions, record retries, maintain operational health, and preserve an append-only audit trail. Automation supports the review process; it does not turn an unresolved exception into an approved conclusion.
4. Only approved inputs move forward
After the required review is complete and coverage is acceptable, the approved version can support a calculation and a private handoff. This gives the client a simple result while keeping evidence, version history, and decision ownership available to the internal team.
Sources and reading context
Primary source links are provided for context. They do not establish PDR service eligibility, tax or accounting treatment, a reporting obligation, a client metric, or an external assurance conclusion.
Frequently asked questions
What happens when a value is wrong or incomplete?
The workspace opens a correction path. The corrected information is stored as a new version with its source context, while the earlier record remains available rather than being silently overwritten.
Who approves a controlled correction?
Approval follows the configured role boundary. In the Package 1 workflow, provider drafts, material factors, and controlled calculations can require Founder or reviewer approval before they enter the approved reporting path.
Can an unapproved correction be exported?
No. Report and handoff gates are designed to block incomplete coverage, pending review, or unapproved calculations. The client sees the next action rather than an unsafe export option.
These answers provide general workflow context only. They do not replace tax, accounting, legal, or procurement advice.