*Tip* If you have a hard time reading the screenshots in this article, click on the image to enlarge.
As you enter your historic records and current annual crop plans, you may see various warning messages throughout the process. These messages are meant to address any missing steps or data errors that may occur ahead of filing. We need to make sure your information is airtight ahead of sending it to the Carbon registries for certification. Having a high bar during this process is part of how we create the highest-value credits on the market and ensure the maximum credit potential for you.
Shortcuts
To get an overview of where your fields are in the submission process, you can click on the Programs tab at the top of the page to access your Carbon status dashboard.
Below the summary, you can view the progress details of each of your fields and any issues they may have. Click on "show details" to display more information. The link under "Next step" will take you to the earliest error that needs resolving.
Resolving Crop Plan Errors
You may see a "Needs review" message on one or more of your Crop Plans. This means there is an issue with the data that needs to be resolved before proceeding to the next section. To see more information, open the crop plan.
Here you will see a section called "Validation." This is where the error details are listed. The below crop plan has two different types of errors. These are "Attestation Required" and "Indigo Review Required." We'll explain how to resolve them below.
ATTESTATION REQUIRED
For this type of error, you should first review your data and field assignments carefully to ensure they are correct. If you are confident about what you entered, click "Confirm records." You will be asked to sign an attestation confirming that the data is accurate. Enter your legal name and click "Confirm attestation."
Below is a video walkthrough of this process. Note that despite the option to upload documentation pictured in the video, it is not necessary for errors marked "Attestation Required." Completing the attestation workflow will clear the error without document upload.
SUPPORTING DOCUMENTATION REQUIRED
For this type of error, there are two options:
Edit incorrect data. Review your data for accuracy. If you have spotted an error within an event, you can edit it individually in the Management Records section. Keep in mind that editing the data will change it for all fields assigned to this Crop Plan. If you only need to change the data for only one field, unassign that field from the Crop Plan and reassign it to another new or existing Crop Plan that has the appropriate data for that field.
Upload supporting documentation. See below section for guidance.
Adding Documentation
Click on "Add document" under the Validation section. This will reveal any documents that are already in your library, and a place where you can upload a new document. Select any relevant documents from your documentation library or upload a new one. Click on Attach Document.
Note: You can submit documents for all flagged events and from here. You do not need to specify which event the record is for, although naming your documents according to what they are is helpful for both the reviewer and for yourself when selecting documents.
Once you've selected all relevant documents, click on "Submit for review." While your documents are under review, you will see that noted at the top of the page.
Once the review is done, you will see "Completed reviews" appear in the same place (no need to refresh):
Click on the bar to expand the details of the review:
If your document was rejected, take a look at the reviewer notes to see what the issue was. From here, you can edit your records if they are incorrect, or upload a new document and then Submit for Review again.
Once you've made changes and submitted for review, any new reviews will appear in the same section, with the newest at the bottom.
When all of your error flags are resolved, the crop plan will show "Complete" with a green dot.
Warning Flags
You may see yellow warning flags while you are entering data. These will happen on unusual practices and prompt you to double-check your data. Please review your entry, and if you truly did perform the practice that was deemed unusual, you can still proceed, though you may be prompted for supporting documentation.
Below are some examples of this messaging.
This warning flag will also display on the summary page of the Crop Plan. Clicking on the warning symbol will display more detail about the issue. This type of warning will not always prompt you for evidence. Be sure to carefully review it for accuracy before proceeding. If you've realized that the data you entered is indeed incorrect, click on the Edit button to change it.
Practice Change Warnings
If something is considered standard practice in your region, such as no-till, that field will have to have an additional practice change in order to qualify. Below is an example of that messaging. You can still declare the practice change and it will generate credits in combination with a second, non-common practice change.
Maximum Inputs
To prevent typo errors, some data fields have maximum values that are allowed to be inputted. If your value exceeds the set maximum, you will have to correct it before you can save your entry. Below is an example of one of these errors.
Field Assignment Errors
During the field assignment segment, you will not see a field if it is ineligible for that crop plan. To display ineligible fields, you can select "Ineligible" or "Show all" from the filter list. Clicking on the message next to the field name will show more details about why that field is ineligible for assignment to that crop plan. This can happen during historical plan assignment as well.
FAQ's
Q: I see an error that I don't think should be an error. What should I do?
A: Send us a message through the chat icon at the bottom right of your account and we will look at it together to determine what needs to be done.
Q: What happens if I can't/don't resolve my errors?
A: Until all errors are resolved, a field will unfortunately not be eligible for filing (and is therefore also not eligible for payment). If you are having any trouble resolving an error, just send us a message through the chat and we will work it out together.
Q: Why do I have to provide documentation?
A: We validate the data you enter against various different resources. This includes regional norm data, USDA records, historical weather, and common practice data ranges. We ask for evidence because it helps us prove specific practices that our data validation checks may disagree with or determine is unusual. Before submitting evidence, our recommendation is that you first check what you entered to make sure it is correct.
Q: What do I do if my document is rejected?
A: Be sure to read the reviewer notes under "Completed Reviews." If there aren't any, and you are not sure why your document failed, feel free to reach out to us using the chat feature. Here are some things to keep in mind:
Crop plan data should reflect an average of all the fields attached to that plan. For example, if you submit a document with multiple planting dates and the majority of them are in late April, but you put down that your average planting date is April 1st, this document would fail.
You are not required to submit field-specific documentation for every field; however, if you do submit field- specific documents, they should represent the majority of the acreage on that crop plan. For example, if you have a 10-acre and a 100-acre field assigned to a plan, documentation that is specific to only the 10-acre field will not suffice. We encourage you to submit summary-style records instead if possible.
All documents must have been created around the time of the event. Documentation cannot be created for the purpose of submitting to Indigo. The exception to this is reports that are freshly generated, but contain historic data. For example, a seed retailer may generate a report today of all of your past purchases. This is acceptable because the purchases were documented in the seed retailer's system around the time of the original event.
Review your field assignments to make sure all of those fields truly followed the general practices associated with the crop plan.
The crop year that cover crops count toward are based on termination date. For example, a cover crop planted in the fall of 2024 and terminated right before a spring 2025 corn planting is considered part of the 2025 crop year. Keep that in mind when submitting documentation; documents for cover crops on a 2024 annual crop plan should be from the 2023 planting.