Preparation guide
Prepare the evidence your application needs.
Map every requirement to reliable proof, find the gaps early, and assemble material you can use with confidence.
Strong applications are easier to produce when the evidence exists before the form asks for it. Preparation is the work of connecting requirements to credible proof.
Map each requirement to proof
Use the provider's current instructions as the list of things to prove. For each requirement, name the best document, record, link, or example and where it lives. If you cannot name evidence, mark the gap rather than drafting around it.
Give evidence a clear state
| State | Meaning | Next action |
|---|---|---|
| Ready | Current, relevant, and usable in the requested format. | Keep it with the requirement it supports. |
| Needs revision | The evidence exists but is stale or unclear. | Update and review it. |
| Missing | No reliable evidence is available yet. | Name an owner and an internal due date. |
| Not applicable | The provider's instruction does not apply here. | Record the reason instead of silently omitting it. |
Scroll to see all columns
Check quality before reusing material
Review dates, names, numbers, links, permissions, and your role in each example. Reuse saves time only when the material still answers this provider's question. Remove a broad claim if the underlying record supports a narrower one.
Turn a vague gap into a task
“Need proof of experience” is hard to finish. “Find the dated project record that shows my role and result, confirm it can be shared, and link it to the experience question” has a checkable end point.
Protect sensitive material
Application evidence may contain personal or project information. Share only what the provider requests, check filenames and document metadata, and keep private working copies in an appropriate location.
Check whether the provider asks for a specific document, file type, date range, or method of submission before collecting a broader set of material. If a requirement is unclear, ask for clarification rather than sending unnecessary sensitive details.
Assemble a reviewable set
Before submission, check that every required item is present and that names, dates, links, and versions agree. A reviewer should be able to see which requirement each item supports. Remove duplicates and unrelated material that make the answer harder to verify.