Example brief
A fictional organisation wants to assess an established Umbraco platform before selecting an upgrade scope. Its solution contains an external subscription integration, a custom editor extension and a repeatable deployment pipeline. The entries below illustrate the shape of a review.
Example compatibility register
Record the current evidence and the next decision separately. A review item stays unresolved until the relevant evidence is available.
| Option | When to consider it | Evidence to collect |
|---|---|---|
| CMS and runtime | Confirm the supported path for the actual source and target versions. | Record exact versions and official upgrade notes before estimating. |
| Editor extension | The extension depends on APIs that may differ in the target version. | Inventory its behaviour; prototype the uncertain part and compare editor workflows. |
| Subscription integration | The current integration depends on a package whose support needs checking. | Review compatibility and error handling; agree update, replacement or custom implementation. |
| Release pipeline | The pipeline must build and host the target runtime. | Verify build tooling, environment settings and deployment steps in a test environment. |
Example risk entry
Risk: the editor extension may require new implementation work. Evidence needed: target-version API compatibility and a walkthrough of the existing workflow. Proposed next step: a focused investigation with its own review point. Scope impact: update the estimate once the approach is agreed. Owner: assign the decision to the relevant client or delivery lead.
Example acceptance and handover outline
Acceptance criteria are agreed with the people who own the workflows. The following are prompts for scoping; they are not claims of tests executed on a client site.
- Editors can perform the agreed editing, preview and publishing journeys
- Migration checks reconcile the relevant content, media and records
- Integration success and failure scenarios are reviewed against the agreed behaviour
- Environment configuration and deployment steps are repeatable
- Open defects, recovery steps and operating responsibilities are recorded
What a real assessment would add
A scoped assessment replaces these example entries with actual evidence, owners and decisions from your platform. Estimates, implementation choices, timing and recovery constraints depend on that review. Use the example to discuss the level of detail your team needs.
Useful next steps
Continue exploring
Discuss your platform
Share your current platform, the change you need and your delivery constraints. Scope and engagement can be discussed around your team.
Discuss an Umbraco Project