Fictional case: v3 approved, v4 pending

Everything here is fictional, not a client response or legal evidence. These short snapshots are for practicing the record. Preserve the entire actual reviewed file and original reply in real work.

Preserved v3 snapshot

P-042 / homepage / v3 / October 8, 2026. Heading: “A website for your studio”. Button: “Book a consultation”. Layout: heading, short introduction, services, contact. Photos will follow; this request does not approve pricing or additional scope.

Martina asks Jane: “Do you approve the text and layout of this v3 for implementation? Photos excluded. Please reply by October 12.” Fictional Jane reply October 10: “Yes, I approve the text and layout of v3.” V3 status: approved within that scope. Actual export __; original reply __.

New v4 snapshot

At the client’s request the button changes to “Send an inquiry”. Label: P-042 / homepage / v4 / October 12. Do not overwrite v3 or transfer its approval. The new request identifies the button change and asks about v4.

Fictional reply: “Yes, provided the button links directly to the form.” V4 status: awaiting clarification and another review. Martina confirms the destination form by October 13 and sends the corresponding version. This is not unconditional approval of v4. With no reply at all, the status remains pending and Martina owns a dated next contact.

Record check: open the preserved v3 and find the old button; open v4 and find the new one. The v3 reply must still lead to v3. Add exact file links, authorized reviewer and recipient-access evidence to the real record. Actual check result __; this example does not perform it for you.