Propellus agency workspace example, with identifying values obscured.
Propellus agency workspace example, with identifying values obscured.

A file can contain several uploads and still be incomplete. A required document may be absent, an image may be unreadable, or two documents may contain information that needs checking. Treating all of those cases as “documents received” leaves the difficult work for later.

A useful preparation process distinguishes collection from checking and checking from readiness for review.

Start with the right application context

Requirements depend on the application being prepared. Propellus’s configurable workflow considers destination, nationality and residency when defining the relevant journey. The aim is to ask for information in context rather than send every traveller the same generic checklist.

The operational team still needs to confirm the configured requirements for its supported workflow. This article describes how to organise the work; it does not provide destination-specific visa requirements.

Describe the issue precisely

“Something is wrong with your documents” is difficult to act on. A request should explain which item needs attention and what the traveller can do next.

  • Missing: a required item has not been provided.
  • Unreadable: the file is present but the relevant detail cannot be checked.
  • Mismatch: information differs between the application and a supporting document.
  • Needs review: the team must resolve an exception before proceeding.

These are useful operational distinctions, not a claim that every product screen uses these exact status labels.

Keep follow-up connected to the file

When the team asks for a replacement document, record the reason in the application’s working context. When it arrives, check whether it resolves the original issue. A new upload should not automatically mean that the file is ready.

Propellus brings intake, document extraction, checks and the team workspace into the preparation journey. That provides a place to identify the information that still needs attention before human review.

Make the next action visible

For each incomplete file, the team should be able to answer three questions: what is missing or inconsistent, who needs to act, and what happens after they do?

A short review of waiting applications can reveal whether work is held up by traveller responses, an internal check or an unclear request. Those causes need different interventions.

Use “ready” for a specific stage

Ready for a team review is different from ready for final submission. Keep those stages distinct, especially when the prepared application is transferred into a supported portal.

A practical pilot can track follow-up rounds and how often an application returns for correction after it was marked ready. Use the findings to improve the requirements, instructions and review process rather than simply sending more reminders.

See the workflow

Bring your team’s process to the conversation.

Explore the product and discuss the destinations and application stages that matter to your business.