Inputs for developing the schedule should be identified and checked against the project's particular conditions. When fixing the critical path, activities that take a long time or need long lead times should be considered, the chain of dependent activities through the network from start to finish that sets the earliest possible completion date of the project or phase, which has to be explicitly identified. Standard schedule formats suited to different users should be adopted. The way duration estimates fit activity dependencies should be checked, with any inconsistencies settled before schedules are finalized and issued. Schedules should show critical and near-critical activities and the events that need particular inputs or decisions or at which major outputs are due (key events or milestones), and should include progress evaluation activities. The customer and the other stakeholders should be involved in, and informed about, schedule development when required; outside inputs, for instance those the customer is expected to supply while the project runs, should be analysed and allowed for; and suitable schedules should go to the customer and the other stakeholders for information or, where required, approval.
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.