Scheduling proposals

A scheduling proposal belongs to a work package and organization. It carries a revision, generation date, model version, predicted hours and a count of constraint violations. The coordinator can compare this result with task hours and the package budget before submission. Submitted proposals enter a review decision. Approval is tied to the current source revision; a changed package requires fresh consideration.

• Source. Link each proposal to the package and organization under review.
• Comparison. Examine predicted hours beside the task plan and package budget.
• Decision. Record the reviewer and revision before applying an approved plan.

Agree who supplies the proposed schedule and who can submit it. Decide how the team interprets constraint violations and what supporting evidence a reviewer needs. Name an independent reviewer. Before an approved plan changes task lines, the coordinator confirms that the package is still current and that the reviewed authority covers the change.

A coordinator receives a proposal for a package whose task plan totals fewer hours than the predicted schedule. The proposal also reports a constraint violation. The coordinator checks the dependency notes and budget, attaches supporting context and submits the current revision. The reviewer returns the proposal for correction or approves it with a reason. If the package revision changes while the decision is pending, the coordinator takes the revised plan back through review before applying it.

The reviewer needs more than a proposal status. Show the package subject, the task effort it would change, the predicted hours and any constraint findings together. A decision reason should explain what the reviewer saw at that revision. A Return decision asks the coordinator to revise the case; a Reject decision records a refusal. An Approve decision is authority for the reviewed scope only. Before the coordinator applies it, compare the current package revision and supporting files with the reviewed source. The operation receipt then gives the lead a place to inspect whether the intended task changes actually occurred. This sequence makes a schedule decision traceable after delivery starts.

• Schedule review inbox — Open submitted proposals with their predicted hours and constraints.
• Schedule proposal board — Follow draft, submitted and decided proposals.
• Approved schedules — Find reviewed plans awaiting application.

Follow scheduling proposals in the operating process. Review the data model when mapping project, package and evidence records.