Track post-launch value and outcomes

Determine keeps the selection useful after a winner is chosen. It links promised capability, implementation progress, user feedback and renewal planning so the business can see whether expected value was actually delivered.

In the app: /projects/…/reports

Before you start

• Select a winner. Determine becomes available at that point, although many outcome actions are most useful after implementation starts.

• Set the project target go-live date if you want the suggested 30, 90 and 180-day review cadence to land on meaningful dates.

Step by step

1. Build the promise-versus-delivered view

Review the rows derived from selected-vendor promises and project capabilities. Mark each Delivered, Partial, Not yet or Gap and add grounded notes. Agreed commercial terms remain visible as context rather than capability evidence.

2. Track implementation milestones

Add each milestone with a clear label, owner and due date. Move its status from pending to in progress to done as work advances, and delete only records that were created in error.

3. Schedule value reviews

Use the suggested 30, 90 and 180-day cadence as a starting point. Suggestions are based on the project target go-live, so update that project date if the review timetable is wrong.

4. Generate the post-launch survey

Create the survey from the original requirements and selected vendor, then review and publish it. Invite the intended users, monitor responses and open the full results for NPS and capability feedback.

5. Publish an eligible community outcome

When NPS results exist, the project is completed and the selected vendor is linked to the directory, use Publish outcome to share the supported anonymised result on the community vendor profile. Review the preview and your governance policy first.

6. Start the renewal loop

When reassessment is due, choose Start a renewal review. Disqovr opens the assessment-project flow with the current register asset prelinked as the incumbent, preserving context while letting the market be tested again.

Outcome publication is a separate, deliberate action. Draft survey results and internal implementation notes are not automatically posted to the community.

What happens next

• Use the workspace Reports value view to compare delivery signals across projects.

• Keep the software asset’s costs, contacts, contract dates and renewal notice current in the Register.

Troubleshooting

Determine or an outcome control is unavailable

Confirm a winner is selected. Community publication additionally requires a completed project, usable NPS results and a selected vendor linked to the shared directory.

Suggested review dates are wrong

Check the project target go-live date. The suggestions are not calculated from a later contract field unless the project target is updated to match.

The renewal project is missing incumbent context

Start it from the Register asset or the Determine renewal action rather than from a blank project. Confirm the asset is the one created or linked at delivery.