Skip to content

Following an application from draft to decision

Know what has happened, what remains unconfirmed and who needs to act next. A status is useful only when you understand the event behind it.

5 min read

An application can move between preparation, official processing and actions required from your team. Not every procedure follows the same sequence. Use the request’s details and official responses to understand its progress rather than assuming that every status means the same thing across authorities.

Who does what

  • Your team

    Prepares information, checks documents and completes authorised actions.

  • Motaded Platform

    Organises supported requests and displays available information about their progress.

  • Relevant authority

    Receives and processes official requests and determines their outcomes.

  • Other required participants

    Complete any procedure-specific actions such as signing, providing information or making a payment.

In what order

  1. Identify the request

    Confirm the company, procedure and available reference. Check whether an official request already exists before starting another application.

  2. Review what is still being prepared

    A workspace draft may contain incomplete or unreviewed information. Check what remains before taking an official action.

  3. Review the information to be sent

    Confirm the applicant, company details, attachments and intended action. Prepared information is not proof of submission.

  4. Confirm whether the authority received it

    Look for the available receipt, reference or verified status. If receipt is unclear, check the existing attempt before submitting again.

  5. Follow the next required action

    Read any request for changes, payment, signature or additional information. Identify who must act and through which service.

  6. Review the official outcome

    Check whether the request was approved, rejected, returned, cancelled or otherwise concluded. Interpret the result within that procedure.

  7. Keep the result and continue

    Retain the relevant document or response and identify any remaining steps. A completed request may be one part of a longer company journey.

Prepared vs received

Prepared in the workspace

  • Information has been collected or reviewed
  • An official request may not yet exist
  • Details may still need correction
  • No authority decision has been established

Received by the authority

  • There is evidence of an official request
  • The authority’s process determines its progress
  • Further action may still be required
  • Receipt does not mean approval or final issuance

Read these stages as meanings, not universal status labels

  • Draft

    Preparation is still in progress. Check missing information and documents.

    Your team

  • Ready for review

    The preparation needs an authorised review before proceeding.

    Authorised reviewer

  • Receipt unconfirmed

    It is not yet clear whether the authority received the action. Verify before retrying.

    Status check / relevant authority

  • Under processing

    The request is in the official process; check whether any action is required.

    Relevant authority

  • Action required

    Someone must provide information or complete another step. Read the specific instruction.

    Named participant

  • Outcome available

    Review the official response and any resulting document or conditions.

    Relevant authority

Mistakes to avoid

  • Treating “ready” as “submitted”.
  • Treating a request reference as proof of approval.
  • Repeating an action because the result is not immediately visible.
  • Assuming “returned” and “rejected” always mean the same thing.
  • Treating a successful payment as proof that the entire procedure is complete.
  • Closing the work without reviewing the actual result.

FAQ

Check its details and status before creating another one. Where supported, use the existing-request workflow rather than duplicating the application.

Follow the request, not just the status

Use Platform to keep application information, available responses and next actions in context.

Explore Platform