Skip to content
SmartFACT HelpHandbooksWatch and practise
Handbooks: SmartFACT Automation

Coordinate complete policy releases across products

Review the exact member relationship, hold new work, activate each release and open each ready member explicitly.

Review edition · 25 October 2026 · For Author, Reviewer, Supervisor, Viewer

On this page

A coordinated policy set relates complete reviewed product releases to one requirement. It provides explicit member preparation and admission. It is not a promise that every product changes in one distributed transaction.

Compose the exact set

An Author opens Coordinated policy sets and prepares the complete set against its anchor requirement and revision. Select the intended member releases and exact native submissions. Inspect membership, scopes and dependencies before saving or importing a complete release-set bundle.

Do not use a partial member list to imply that every affected department is covered. Check which products and assignments support the intended coordination. An unsupported relationship remains a gap to resolve.

Review the relationship independently

An eligible Reviewer checks the exact saved set, contributor independence, complete release evidence and current member readiness. Record the review decision and reason against that version. A member release's own approval is not a review of the relationship between all members.

Keep each member's proof, native review and activation evidence distinct. A different set or changed member needs current review. Existing work retains its pinned release rather than having its interpretation silently replaced midway.

Prepare, activate and open explicitly

Prepare every member to hold new work. Activate each approved product release through its own reviewed native lifecycle. Open each member only after all products report the required ready state. Preparing or opening one member does not update the others.

Read retained delivery requests and exact member outcomes. If a reply is lost, use Check outcome. It reads the original result; it is not permission to send the change again. Recovery holds stay visible until the independent resolution they require.

Tell operational teams which admission step is complete and which remains pending. Avoid saying the whole set is live when one member is only prepared or another is still blocked. Use Activate and recover original requests and the source products' own readiness evidence for the final status.