In this article
A useful startwork register tells you which document you saved, the project it belongs to, where the copy came from and when you obtained it. Keep that information beside the file rather than relying on names such as “final” or “new.” The goal is to locate the right copy and notice uncertainty, not to certify an agreement.
Build the register only for documents you are entitled to keep. Use the production’s approved instructions for questions about document access, required forms or changes. This publication does not review personal forms or decide whether a document meets employment, tax or legal requirements.
Official context
Wrapbook’s worker guide distinguishes documents uploaded during onboarding from completed forms listed under Startwork. It describes viewing a completed form and saving a PDF copy. The guide was checked on October 25, 2026; interface labels may change. The register below is independent advice for identifying your own copies, not a statement that any form is complete or legally sufficient.
Describe the copy before describing its status
Start by recording what you can observe: the document title, the project shown, the source location and the date you saved the file. If a date or version appears inside the document, record it separately from the download date. Saving an older document today does not make it a newly issued document.
Keep your interpretation in another field. For example, “appears to match the form viewed today” is a personal observation, while “approved by production” requires an actual source for that statement. This separation makes the register useful even when you do not yet understand every label in the document.
A compact register that answers real questions
Use one row for each distinct document copy you need to track. A private note or simple table is enough. The register should help you find files; it should not reproduce sensitive identifiers or become a substitute for reading the document itself.
- Project reference: your consistent name for the production.
- Document title: the title visible in the source, with a short personal description only if needed.
- Source and saved date: where the copy was obtained and when you saved it.
- Document date or version: only what actually appears, leaving the field blank when none is shown.
- Private file location: a filename or folder reference that you can open.
- Relationship to other copies: duplicate, different-looking copy, or unresolved comparison.
A link from your project record index is sufficient to connect this register to the rest of the job. You do not need to scatter copies across every project note. Keeping fewer working locations can make it easier to recognize which file you actually inspected.
Check the file you saved
Open the downloaded file before assuming the task is finished. Confirm that it is readable, belongs to the intended project and contains the pages you expected. A successful download indicator says little about whether you selected the intended form. If a file is password-protected or fails to open, use the authorized source for assistance rather than uploading it to an unknown conversion website.
Record a problem in plain language: “Only the first page is visible in this copy” is more useful than “document broken.” Do not repair apparent missing content by pasting material from another production’s form. Preserve the original copy and ask the responsible source to explain or provide the appropriate file.
Fictional example: the two “final” files
A worker has two files from the fictional project Orchard, both named “startwork-final.pdf” by different downloads. One was saved before a conversation with the production, and one afterward. The worker renames the local copies with saved dates, records their original filenames and compares the visible document title and page count.
The files appear different, but the worker does not label the later download “replacement agreement” without confirmation. Their register says “difference observed; asked which copy should be used for future reference.” That wording preserves the actual question. A newer filename alone cannot explain whether the underlying terms changed or whether one file simply contains additional pages.
Keep a change trail without creating a verdict
When a later copy arrives, record its relationship to the earlier copy as carefully as the evidence allows. If the authorized source explicitly identifies it as a replacement, retain that explanation with the record. If you only know that the files differ, describe the difference and leave the conclusion open.
Avoid overwriting an older file while a question remains unresolved. At the same time, do not treat this article as a universal retention schedule. Applicable obligations, production instructions and your circumstances can affect what should be retained. The practical point is to avoid accidental loss while you determine the appropriate handling.
Ask about one uncertainty at a time
A question about access differs from a question about a document’s meaning. Identify which you need answered. For access, explain the project and document you are trying to locate. For content, use the appropriate authorized or qualified person rather than assuming a technical help channel can interpret an agreement.
The focused-question method helps you state what you observed and what clarification you need without attaching a complete personal archive. Do not send identifying documents to this publication. Use a verified, appropriate channel and provide only the information necessary for that specific request.
Make the register usable after the job
Before moving a project out of your active working folders, test whether the register still leads to the intended files. Note unresolved comparisons so they do not disappear into an archive. The wrapped-project archive guide can help you separate current questions from settled reference material. A reliable register remains modest: it explains where a copy came from and what you know about it, without claiming more authority than the evidence supports.
Source & scope
Official documentation checked October 25, 2026. The organizational methods and fictional examples are independent editorial analysis, not an official procedure or a private-account test. This article does not determine pay, benefits, tax treatment, contractual rights or record-retention obligations.