EIR describe the managerial, commercial and technical sides of producing project information; the technical side specifies the detailed information that answers the PIR. They are written so they can be built into project appointments and usually line up with trigger events such as the end of a project stage. EIR should be set wherever appointments are made; they can be split and passed down the supply chain, and appointed parties can add to them. Across a project they should form a single consistent set that answers every PIR.
This control maps to 1 controls across 1 other frameworks. If you already hold one of them, the evidence you collected for it is the starting point here rather than new work.
Every mapping shown was judged rather than inferred from wording similarity, and the ones that failed review are published too. See the coverage reports and what was rejected.
The graph holds this control, the 1 it maps to, and the evidence behind each claim, over MCP and REST.