Skip to main content

How to force complete an Engage request

Force complete an Engage request to review partial client data and run available checks when a client cannot finish the process.

Written by Ula Moyse-White

Overview

You may need to force complete an Engage request if a client encounters issues completing it, or if they no longer need to finish all required steps. Force completing allows you to review the information provided so far and run the necessary checks.

ℹ️ Important

Force completing is different to the Close Link option: force completing still processes the data the client has provided, whereas closing a link does not capture any information.


Before you start

Before force completing a request, make sure that:

  • The request has a status of In Progress — the client has started but not yet completed it

  • You have access to the Engage dashboard


How to force complete an Engage request

  1. Go to the Engage dashboard and locate the In Progress request.

  2. Click the ⋯ (three dots) icon next to the request and select Force Complete.

  3. A preview will appear showing the client's progress and which information will be available on force completion.

  4. Add a comment explaining the reason. This will be visible to all colleagues on Legl.

  5. Click the red Force Complete button to confirm.


What happens next

  • The request may briefly enter a Processing stage while checks are completed.

  • Once processing is complete, a summary of available information will appear in your dashboard. Both completed and incomplete checks will be shown.

  • You can still assign a reviewer to the request or send a new Engage request to capture any missing information.


Important information

  • Once force completed, the client cannot continue completing the request.

  • Force completing is not the same as closing a link. Force completing still runs checks on the data provided; closing a link captures no information.

  • If the request remains in Processing for more than a few hours, contact our Support team.

Did this answer your question?