How to Collect and Verify Documents Online

Chasing admission documents is one of the most thankless jobs in a counselling team. Photos arrive on WhatsApp, PDFs land in three different inboxes, and nobody is quite sure whether the marksheet on file is the final one or a placeholder. ASH moves the whole exchange onto the applicant's own status page, so documents come in against the right record and your team verifies them in one place. Here is how the workflow runs end to end.

Build the document checklist

Start by deciding what each applicant must submit: a class 10 and 12 marksheet, a photo ID, a passport photograph, a category certificate where relevant, and so on. Request these against the application record. Each requested item becomes a line on the student's checklist with its own status, so the requirement is explicit rather than buried in an email thread.

How the applicant submits

Instead of accepting raw file uploads from strangers, ASH asks the applicant to paste an https link a Google Drive file, a photo link, or any hosted document. On their applicant portal, each pending item shows an "add document link" button; they submit the URL and the item flips to uploaded. This keeps large files off your CRM, gives you a durable reference, and lets students update a link if they sent the wrong one.

The verification workflow

Every submission lands as uploaded, never verified, because approval is always a human decision by your team. From the record, a staff member opens the link, checks it, and sets the outcome:

• Verified the document is correct and accepted; the student sees a green badge and can no longer edit it.
• Needs correction something is off; add a short remark such as "marksheet is blurred, please re-share" and the student sees it and can submit a new link.
• Rejected the document is not acceptable in its current form.

Because the remark shows on the student's own page, you are not drafting a separate email to explain what went wrong.

Keep a clean trail

Each document carries its status and remark on the record, so anyone picking up the file later can see what was asked for, what was submitted, and what was accepted. That matters at audit time and when a query gets handed between counsellors mid-season.

Practical tips

• Ask students to share links with view access, so your team is not blocked by a permission prompt.
• Use the remark field generously; a specific reason gets a correct re-submission faster than a bare "rejected".
• Verify in batches; the checklist makes it easy to see who is complete and who is still short a document.

The result is a document trail your team controls, tied to the right applicant, without a single attachment lost in an inbox. Pair it with the Education CRM pipeline and each application moves from enquiry to enrolment with its paperwork attached.