> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dev.sylvera.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Rating Process
> A step-by-step walkthrough of Sylvera's Ratings process
The Ratings process typically lasts 3-5 weeks from kick-off to publication
Sylvera requests further documentation from the developer with a data request sheet, under a signed Engagement Agreement. This may include clarifying a variable used in a credit calculation, providing a shapefile of the project area, or commenting on external reports relevant to the project.
Sylvera's Core Pillars are assessed independently, based on the evidence gathered, then combined to form the letter grade (AAA–D). This grade reflects the project's overall quality across every pillar.
The developer reviews the draft during a 5-business-day feedback window. This gives them an opportunity to flag factual errors or provide additional context before the Rating is finalized.
Sylvera incorporates feedback and publishes the Rating to the Sylvera platform
## Governance principles
* Commercial conversations are always decoupled from Rating production. Commercial team members are not privy to scoring discussions
* Even when the developer is the paying customer, engagement with Sylvera's Ratings team remains separate. Analysts are not included in client-facing calls; our Client Delivery team acts as the intermediary between the Analyst team and clients
* Purchasing a Rating can secure prioritization of the Rating's timeline, but never influences its outcome
* Every Rating within a given project type follows the same deterministic framework, so no project or developer is assessed on different terms
## Developer Engagement
Sylvera engages with project proponents as part of the Rating process for every project.
To improve the quality and accuracy of our Ratings, and to ensure a fair process, we often seek clarification from proponents or request additional information. This could include asking a proponent to justify a variable used to calculate permitted credit issuance, requesting a shapefile (map) of an area of interest, or asking for comment on a press article about the project.
Despite this engagement, Sylvera always maintains editorial control over its published materials.
Sylvera shares a project type-specific Data Request Sheet as the first step. The developer will then provide Sylvera with all relevant project information, on an agreed timeline
Sylvera reviews the information and asks material questions while producing the Rating. Documentation commonly requested includes carbon accounting data, project and reference area boundaries, financial models, land tenure records, benefit-sharing details, and explanations for any registry status flags
Sylvera shares the draft Rating with the developer for feedback, opening a 5-day feedback window
Sylvera incorporates the feedback it receives and publishes the finalized Rating
#### **Status labels**
**Pending developer engagement**
This project is undergoing developer engagement.
**Finalized by developer**
Sylvera has engaged with the developer. Any questions have been addressed and incorporated into the Rating, where relevant, as of the last update.
**No response from developer**
The project developer has not responded, or has chosen not to engage with Sylvera.
For more information, see our [Project Developer Relationship Policy](https://www.sylvera.com/governance).
# Post Rating Care
## On Watch
After we publish Ratings, if we become aware of circumstances that could lead to a material change to a project's Rating, including its withdrawal, we place the project On Watch until the review is complete. This status signals to market participants that a project's Rating is more likely than not to change, positively or negatively, as a result of new information.
We remove the On Watch status once a review and the Rating is updated. If the review results in a change to the project's Rating, we explain that change. If the Rating doesn't change, we explain why.
Potential triggers for On Watch status include:
* A recent policy change, at the national or project level, that could significantly affect the project's ability to issue credits.
* Recent extreme weather events or human activity that have caused a significant loss of carbon stock in or near the project area.
* Recent reports or information suggesting the project will stop operating as a voluntary carbon project (e.g. project withdrawal or early termination).
* Recent reports or allegations about the project that, once investigated and corroborated, suggest the Rating needs to be revised.
* Planned framework or machine learning model updates that may affect the Sylvera Rating, positively or negatively.
Read more about the On Watch status in our [Monitoring and Amendments to Ratings Policy](https://www.sylvera.com/governance). If you'd like to discuss further, reach out to your usual Sylvera contact or email [governance@sylvera.io](mailto:governance@sylvera.io).
## Grievance
Sylvera commits to engaging Project Developers throughout the Rating process, keeping requests minimal and consolidated, providing a consistent point of contact, and honoring the developer's right to flag factual errors or raise a Grievance.
After publication, developers can still ask questions, submit new information, or appeal a Rating Decision, and any engagement meeting Sylvera's definition of a Grievance is resolved within a timely manner, with app disclosure if a Rating changes following an appeal.
This process doesn't apply to Pre-Issuance Deliverables and isn't required for Estimated Ratings, though Sylvera still commits to good-faith engagement in those cases, and Sylvera Parties are expected to stay mindful of independence and conflict-of-interest obligations throughout.
Read more about this in our [Project Developer Relationship and Grievance Policy](https://cdn.prod.website-files.com/673b5918a90b730875736def/68526bd0cd6870af028331e3_1.6%20Project%20Developer%20Relationship%20and%20Grievance%20Policy%20-%20%5BJune%202025%5D.pdf).