Control Attestations requirements

[David347]

We are currently looking at putting in some Control Attestations and I have been informed that all Control Attestations HAVE to start with a Yes/No Question on whether the control is compliant or not.

I thought that the whole point of weighting the questions was that you can generate a compliance score?

Q1. blah blah - weight 10

Q2. blah blah - weight 10

Q3. blah blah - weight 10

Q4. blah blah - weight 10

If weight = 30 then you are compliant?

My understanding could be wrong.

I appreciate your guidance.

[ybilge]

Hey Sandeep,
Thank you for your response. I have a confusion and I believe you can help me out here.
You said "Attestations has nothing to do with compliance score at the initial level at all." but when we create an attestation, the response of it (Yes/No) changes the compliance score.
After we execute an indicator, the compliance score may change (depending on the indicator result) but also if we create an attestation again, that also changes the compliance score.
For instance, let's say we create an attestation and the response of it is "No", then compliance score becomes 0% (we have one entity). Then we create an indicator with the result of "Passed", then our score becomes 100%. If we create an attestation with "No" again, the result becomes 0% again.  My point is, attestations have something to do with compliance score. 
Also, in the video you mentioned Compliance Scoring: a powerful feature that explains the importance of Entities, they literally used attestation to calculate compliance scoring, not indicators.
I would love to have your answer on this, I need to have a better understanding of this concept.
Thanks,
Ethan