Appendix: operational control worksheets

A practitioner record should connect evidence, model and action. A dependency register without acceptance evidence is incomplete. An acceptance record without the successor it releases is difficult to use. A change form without a decision owner can remain unresolved while its options expire. The completed fictional records in this appendix show how the pieces join. They are not templates filled with generic advice alone; each has an explicit boundary, condition and disposition that a reader can inspect and adapt.

These fictional installation records contain no private agreements or client data. The numerical input supplies tasks, ranges and predecessors; the practitioner layer supplies meaning, evidence, ownership and authority outside the small app. Connect the layers without treating a displayed date as completed governance or supported operational credibility. The records demonstrate that control logic rather than claim the scheduling tool has performed it.

The integration manager should maintain stable links between package, interface, task and decision identifiers. A changed label should not break those links. A scope revision should record which links remain valid and which need a new boundary. In a small project, a controlled document may be enough; in a larger one, a structured system may be appropriate. The principle is inspectability. A reviewer should be able to follow the obligation from its definition to the evidence and the decision that permits reliance.

Record completion should be judged by use. A filled form is not complete if its evidence reference is inaccessible or its authority undefined. A signed acceptance is not sufficient if the conditions are omitted from the successor release. A resolved change is not fully integrated if the supplier and operator still use different configurations. The closure check asks whether the authorised decision has reached every material affected record and recipient. Administrative appearance should not substitute for executable continuity.

Carry the records' qualifications into the summary: partial release stays bounded, recovery depends on capacity evidence, risk response retains residual exposure, and governance does not prove physical readiness. Those conditions tell the recipient what may proceed. Removing them creates a broad ready label that must be reinterpreted during mobilisation, delaying action rather than simplifying it.

The dependency record joins receiving works to assembly. Its causal type is physical interface plus acceptance information. Its release evidence is a compatibility and readiness record under the selected configuration. The producing owner is the works manager and the receiving owner is the assembly manager. The open challenge asks whether a bounded unaffected area can be released before the whole receiving package is accepted. The disposition permits only separately defined unaffected preparation while the affected interface remains held.

This disposition should travel into the schedule. The full assembly task remains dependent on accepted receiving readiness. A separate preparation activity can be added only if its scope and prerequisites are credible. The app can calculate such a scenario once explicitly entered, but this appendix does not invent its duration. The record demonstrates how qualified release can be represented without falsely completing the entire predecessor. It also preserves who accepted the exposure and why.

The acceptance record identifies configuration, criteria, evidence and authority. Its fictional disposition holds the affected equipment-to-receiving interface pending compatibility resolution. Production evidence is accepted as evidence of production, while assembly release remains open. This is a useful distinction because it recognises genuine progress without overstating its consequence. The recipient can see what must happen next, and the producer can challenge the requirement or supply the missing evidence through the controlled process.

State the residual item's permitted and prohibited activities. An open document may block one release alone; a physical discrepancy may permit inspection but prevent operation. A generic minor label cannot express those consequences. Classify against actual technical and statutory requirements, then record the permission and basis. The illustrative record demonstrates where that decision belongs and grants no universal permission.

When compatibility is resolved, the acceptance record should identify the accepted version and close the relevant hold. Earlier evidence remains in history, with its former scope. The schedule’s actual date should correspond to the newly defined acceptance event. This prevents a retrospective correction from implying that the interface was ready earlier than it was. History remains useful for learning and responsibility while current readiness becomes clear.

Screen the fictional supply-acceleration offer with the duration-switch study: receiving works becomes binding, while price and executable capacity remain unestablished. Request supplier method and capacity evidence, inspection and logistics confirmation, and receiving-branch review. The authority can then compare the complete intervention with current forecast and target. The filled assessment remains conditional and establishes no real-project acceleration approval.

The risk response concerns a configuration change that could invalidate receiving work. The action is a compatibility review before irreversible release, with a notification rule for later changes. The trigger is an unresolved material interface at the release review. The fallback holds affected irreversible work while permitting only agreed unaffected preparation. Residual exposure includes later changes and communication failure. This record distinguishes completing the review action from eliminating the risk mechanism.

The escalation record concerns an expiring test-resource reservation. It names the unresolved readiness question, required evidence, actual decision authority and consequence of delay. The requested decision is whether the defined test scope may proceed under specified conditions. The fallback is to preserve permitted preparation and release unused resources according to the actual arrangement. The record avoids a generic urgent label by connecting urgency to an operational option that may disappear.

The baseline record preserves the authorised reference, current forecast and target separately. Discovery of the readiness decision changes the forecast immediately once its basis is credible, while the authority disposes of baseline treatment. The earlier reference remains available. This preserves both timely information and historical comparability. A change can improve the control model without erasing the earlier commitment or deciding contractual responsibility through a planner’s edit.

At review closure, the manager reconciles these records. The configuration, task meanings, acceptance conditions, supplier instruction and resource reservations must describe the same selected plan. Any outstanding condition remains visible with an owner. This reconciliation is the practical test of integration. A collection of individually well-written forms can still fail if they refer to incompatible versions or if their decisions never reach the execution team.

A release rehearsal asks a recipient to use the records as if the successor were about to begin. Can the assembly manager identify the accepted configuration, find the evidence, understand exceptions and know who authorised the release? Can the operator distinguish test readiness from service acceptance? Can the sponsor see the forecast’s conditions and the action needed if one fails? The rehearsal exposes ambiguity before mobilisation turns it into delay or irreversible work.

The rehearsal should include a challenge. Suppose the supplier changes a document, the accepting authority is unavailable or a residual defect affects the proposed test. Follow the record through the consequence. Does the release hold automatically where required? Is the escalation owner clear? Does the schedule remain truthful? This is a qualitative control exercise, not a stochastic simulation. Its purpose is to test whether the record’s wording and links support an actual decision under a plausible change.

A failed rehearsal should produce a specific correction. Clarify the scope, repair an evidence link, identify the authority or reconcile a configuration. Do not close it with a generic statement that teams should communicate better. The correction should be small enough to inspect and concrete enough to verify. Once repaired, repeat the relevant part of the rehearsal. This mirrors the discipline used for model reproduction: a claim is supported by an executed check of the property it asserts.

The records should remain proportionate. A routine local task may need only a simple accepted-outcome note. A material interface crossing suppliers, technical authorities and operators needs more explicit evidence. The control system should scale with consequence and uncertainty. Excess paperwork can obscure important releases just as insufficient records can hide them. The rehearsal helps identify which information a real user needs at the point of action.

Release the stated scope under its recorded conditions, evidence and authority, identifying what can be relied upon now and what needs monitoring. Future uncertainty remains. The record's practical value is an inspectable commitment chain: computational precision supports the forecast, while administrative completion and accepted delivery retain their distinct meanings.