Software & apps · Practice guide

Help suppliers complete missing submission details

Illustrative situation

A portal accepts an incomplete submission and the receiving team discovers the gap only when work begins. Receipt and acceptance are different steps. A portal that treats them as identical may hide missing documents until work begins. Explain the information needed for the next decision and make incomplete submissions understandable.

Healthcare scheduling software, planning board and organised folders in a blue, white and orange office.
Choose software around the work your team needs to do.

What this means for your practice

Define the information needed for the next administrative decision. Show missing items clearly and distinguish receipt from acceptance of the submission.

An example to discuss with your team

Submit a fictional record missing an essential attachment; the next action should be clear.

Healthcare software workflow connecting task cards, a checklist and a database.
Map the work and the information it depends on.
Healthcare software testing with normal paths and a separate exception route.
Test the exceptions as well as the normal workflow.

What to ask before you choose

Submit a fictional record missing an essential attachment. Inspect what the sender sees and what the reviewer receives. Can the missing item be added against the same reference? A specific correction request is more useful than a vague rejected label that starts another email exchange.

Make a correction possible without starting again

Describe required information before the supplier begins, including any document formats or limits that affect submission. Explain which details are necessary for the next decision and label optional material clearly. This helps the supplier prepare the right files instead of discovering an unexpected requirement at the final step.

Use a fictional submission with one missing attachment and follow the review from both sides. The receiving team should identify the gap, and the supplier should receive a specific request connected to the original reference. Check whether a replacement can be added without losing the material already accepted or creating a second unrelated submission. Keep 'received', 'awaiting information' and 'accepted' understandable if those stages are used. Agree who returns incomplete material and who covers that task during absence. Repeated missing items are worth reviewing with the team: they may show that the original instructions are unclear, rather than a need for a more complicated portal or another reminder email.

How to check the result

Count submissions returned for avoidable missing information.

Turn reading into a next step

Your action checklist

Work through these checks with your team or supplier. Tick the ones you have resolved and leave unknowns open.

Checks to discuss

Record what you know, what is still missing and the answer you need from your team or supplier.

Use project decisions only, without personal, patient or confidential details. Entries stay in this page and are not submitted to Kay & Co. Copy or download before leaving; this page does not save your notes.

Further reading

These sources provide background for the topic. The practice examples and checklist are illustrative planning suggestions from Kay & Co.

Related guides

Need help with this?

Tell us what is getting in the way. Kay & Co. can help you understand the options and turn the next step into something that works for your practice.

Explore software & apps services or discuss your project.

Try the free Healthcare Digital Planner to find your starting priority.