AzAd Smart Verifier is designed to stay manageable after launch. The main setup work is connecting a source, validating the sync, creating the public form, and publishing it. After that, most teams only need to keep their Google Sheet or CSV source updated as new results, certificates, or records are issued.
Following the correct sequence avoids the usual problems of mismatched headers, empty result templates, or publishing a form before the source is actually reliable.
Use Google Sheets or CSV depending on how your institution already manages records. Keep the source simple and consistent before syncing.
The public site should search local synced records, not request the spreadsheet on every visitor lookup. This is better for speed and reliability.
Choose the label, placeholder, button text, layout, and captcha behavior that fit the verification experience you want to publish.
Use default result rendering or create a custom result card or certificate template that maps your record fields clearly.
Place the saved form with shortcode or Elementor, then test it with known sample records before announcing the page publicly.
After launch, the ongoing job is mostly record maintenance in the sheet and periodic sync review, not rebuilding the page experience.
Do not publish the form before the synced dataset is verified, and do not keep changing source headers after the mapping is already working. Both issues cause most first-time rollout problems.
If you need rollout support, licensing help, or a check on your student result or certificate workflow, use the contact page for direct assistance.