Explain the changes and their effect on the applicant’s knowledge and proposed duties. Have material differences assessed before relying on the earlier analysis. A revision creates a duty for someone. The company must decide whether the procedure the applicant knows is still the procedure the assignment will use; the applicant must be candid about which version they actually worked in. Neither question waits politely for a filing date, and both cost less to answer before the file is assembled than after a request for evidence arrives.
Keep the version history understandable
Identify what remains relevant and what the applicant still needs to learn. Preserve dates and authentic records. A revised manual should not be presented as evidence of experience with procedures the applicant has not yet used.
Sequence this so no step wastes the next. Establish the version history first, meaning which release the applicant worked under, when it changed and what changed, because that determines whether the earlier examples still describe the knowledge being claimed. Then ask whether the proposed duties use the old practice, the new one, or a transition between them.
A petition describing experience with procedures the applicant has not yet used invites the very challenge it should avoid. Where a revision is substantial, an honest file says which parts carry forward and which will be learned on assignment, and lets the employer explain why the remainder still needs this person.