Check document completeness against a named requirement set, not a fixed number of files. Each requirement should say when it applies, what counts as evidence and who can accept an exception. Software can then show which items are present, uncertain, missing or waived.
A single PDF may contain several required forms. Five PDFs may all be copies of the same form. Counting attachments is therefore a useful intake measure, but a weak readiness rule.
A fictional supplier-onboarding pack
North Pier Events is onboarding a furniture supplier for booking EV-63. Its internal checklist requires company details, an agreed price schedule and a delivery contact. For this fictional booking, an additional unloading plan is required because delivery is outside the venue’s normal hours.
The supplier sends “Company.pdf”, “Rates.pdf” and “Booking.pdf”. The last file contains the delivery contact but says nothing about unloading. A three-file rule would pass the folder. A case-specific checklist leaves one clear outstanding item.
| Requirement | Evidence found | Status |
|---|---|---|
| Company details | Company.pdf, page 1 | Present for review |
| Agreed price schedule | Rates.pdf, revision 2 | Approval reference needed |
| Delivery contact | Booking.pdf, page 2 | Present for review |
| Out-of-hours unloading plan | None linked | Missing |
The status of the price schedule matters. Its presence does not prove that the parties agreed it. Keep “document found” separate from “requirement accepted”, so the checklist does not accidentally make a commercial decision.
Write requirements people can maintain
Give every requirement a stable identifier, plain-language description and effective version. Avoid hiding the entire policy inside a long AI prompt. An operations owner should be able to explain why the unloading plan is requested and change that rule without reconstructing an undocumented conversation.
- Applicability: which case attributes make the item necessary?
- Evidence: which document or field can satisfy it?
- Freshness: does an earlier accepted version still apply?
- Reviewer: who can accept the item?
- Exception: who can waive it, and what reason must be recorded?
For EV-63, the trigger might be the confirmed delivery window “19:00–20:00”. If the time is unknown, mark applicability unresolved. Treating unknown as false would hide a potentially necessary task.
Check collection tools first
A collection portal may cover much of the work. Content Snare describes reusable requests and item-level review. Test your current product’s equivalent features before commissioning another portal. A custom component is more plausible where requirements depend on records held elsewhere or evidence must be compared across files.
Ask the vendor to demonstrate the awkward case: one file meeting two requirements, a replacement invalidating an acceptance, or a conditional requirement becoming necessary after a booking changes. Ordinary upload screens do not answer those questions.
Do not hide unresolved evidence
Files can be unreadable, password-protected or attached to the wrong supplier. Classify these as distinct exceptions rather than marking the requirement missing without explanation. A targeted request for an unlocked copy is different from asking the supplier to create a document.
Retain superseded material in the history where appropriate, but keep it out of the current accepted pack. When somebody waives an item, record the scope of that waiver. Approval for one evening delivery should not become a permanent exemption for every future booking.
A manageable first trial
Choose one onboarding category and write its checklist with the staff who currently review it. Assemble authorised examples covering ordinary, conditional and waived items. Have reviewers label the expected state before running the proposed workflow.
Compare missed requirements, unnecessary requests and time spent resolving uncertainty. The output should tell a colleague what to do next, with a link to the evidence. Clear Anvil’s workflow service can be scoped around this review step while existing storage and collection tools remain in place.
Sources and further reading
AI-assisted research and writing, checked against the linked sources. Worked examples are fictional. Product features can change; confirm the details in your own account.