Three fictional examples for choosing a useful first phase

These examples illustrate planning decisions. They do not describe client outcomes or promise a particular commercial result.

A service changes in one language first

A training provider revises the prerequisites of a course. Its German page is updated, while the French guide still describes the previous requirement. The first question is not how quickly the remaining words can be translated. It is which pages and documents depend on the changed fact and who can approve their meaning.

A first phase could establish page families, review states and a preview of one complete course journey. Acceptance asks the editor to identify every affected version and the reviewer to follow the actual enquiry process. See multilingual publishing.

A revised offer reaches billing incorrectly

An equipment service customer accepts a revised quotation, but the invoice draft is prepared from the original. Staff need to relate the customer's decision to a particular offer and identify the approved record for billing.

The first phase might establish version-specific decisions without changing the accounting application. The next phase can connect the approved reference through a supported interface. Review includes an old link opened after revision. See quote workflows.

A document contact changes

A customer employee leaves the organisation. Their files still belong to legitimate customer work, but their account should no longer provide access. Simply deleting the contact could erase context; keeping the account active could expose private material.

A portal scope should address membership, removal, reassignment and document ownership separately. Acceptance uses a copied download link and an unrelated customer account. See document portals, then bring your own redacted example.