Logical artifact
Use one logical document for a continuing résumé, cover letter, portfolio, or other supporting material. It provides a stable home for a sequence of versions.
Résumé version tracker
Know which résumé version you actually sent.
When you tailor materials for several opportunities, a filename is not durable provenance. HiredBase keeps a logical document separate from its immutable versions, then associates the exact submitted version to the application it belonged to.
Provenance for application materials
Treat the document you sent as history, not a mutable file name.
HiredBase distinguishes the logical document—for example, a software-engineering résumé—from an uploaded immutable version. The application record can then point to the exact submitted résumé, cover letter, or supporting document version.
- Store original filename, file size, MIME type, upload time, and SHA-256 digest for each uploaded version.
- Reuse an exact matching user-owned file digest instead of creating unnecessary duplicate storage.
- Keep submitted associations separate from the application’s mutable current intended documents.
- Archive a logical document without corrupting historical application provenance.
The distinction that prevents version drift
Submitted and intended are different records for a reason.
Immutable version
A new upload creates another version. The original file metadata and content digest remain associated with that historical version rather than being overwritten.
Submitted association
Attach an exact version as the résumé, cover letter, or supporting document submitted for one application. That provenance stays stable even when your current preference changes.
Private access
Documents are kept in private storage and preview or download uses authorized access. The public site does not expose a document directory.
A practical document trail
Review the package that went out, then choose the next one intentionally.
- 1. Upload a version
Add a résumé, cover letter, portfolio/supporting document, or other allowed file. A new version never silently overwrites a prior one.
- 2. Associate what was submitted
Connect the exact version to the application’s submitted package, alongside the rest of that opportunity’s context.
- 3. Keep future intent separate
Change the current intended résumé for later applications without changing the historical version that went to an earlier role.
Common questions
Version history without pretending it proves causality.
- Can I replace the résumé I plan to use next?
- Yes. You can update an application’s current intended résumé. That does not alter an earlier submitted association, which continues to identify the exact historical version.
- What happens if I upload the same file twice?
- HiredBase computes a SHA-256 digest and can offer reuse when the same user already has the exact file, rather than creating avoidable duplicate storage.
- Can version outcomes tell me that a résumé caused an interview?
- No. HiredBase can show recorded outcomes by submitted version when there is enough data, but those records describe associations and do not establish causality.
Explore HiredBase workflows
Start with the Job Application TrackerCreate the application record that stores a submitted package.Save the job descriptionKeep the original requirements alongside the materials tailored for them.Track interviewsReview the submitted package while preparing for later conversations.Use the job search CRMKeep the people and follow-ups tied to the same application record.