PREPARE A TRUTHFUL JOB APPLICATION

Use these files to draft and check a CV and, if the vacancy requests one, a cover letter. Nothing here sends an application or contacts an employer. The worked applicant, organisations, vacancy, dates and history are entirely fictional. Replace or remove every example fact. Use only your own supported experience. Never invent qualifications, dates, metrics or commitments.

1. Check the real vacancy first
Read its authentic instructions: role, required materials and file format, length, deadline and time zone, reference and submission destination. A one-page CV or a cover letter is not universally required. This pack is preparation help, not professional career advice or a promise of interviews, employment or ATS compatibility.

2. Gather facts privately
Use blank/role-and-facts.txt as a private worksheet. List two or three important requirements and one supported example for each. Paid work, volunteering, study or other relevant activity may supply evidence, but label it accurately. Leave unknown facts blank until checked. Avoid collecting identity documents, medical history or other unnecessary sensitive information. Read fictional-role-and-facts.txt and evidence-map.txt to see the distinction between evidence, interest and a gap.

3. Start with a blank document
The blank folder contains a CV and cover letter as native .document.json plus ordinary .docx and .html copies. Bracketed prompts are instructions, not claims. Replace every prompt, remove unused sections and remove the template instruction line only after checking the result. Do not simply rename the fictional example as your own.

Hub route: open the Document workbench at https://free4allhub.com/tools/documents/. Choose the .document.json file, read the incoming review, and explicitly choose “Open this document and replace current work”. Save current work first if you need it. Cancel leaves it in place. Opening a file replaces the document; it does not merge. Edit the text, title and language as needed.

Ordinary document route: open the blank DOCX in your preferred document app and save your own copy. Check its appearance there. HTML is a readable standard export. DOCX and HTML cannot be imported back into the Hub editor. Changes made to a DOCX do not update its JSON or HTML siblings. Choose one editing route and manage each version deliberately.

4. Make a useful revision
Compare worked/cv-v1 with worked/cv-v2. “Helped with attendance records” becomes a concrete description already supported by F04. Compare the cover letters: version 2 uses F05 to answer the revised handover requirement, rather than inventing a new skill. Read revision-guide.txt. The example files are learning material and must not be submitted as real applications.

5. Save, close, reopen and check
In the Hub, choose “Download editable project (JSON)” to keep an editable source, then “Export Word document (.docx)” and/or “Export readable HTML” as required. A download request is not proof of a saved file: locate the actual file and check its name and contents. Browser-generated names are neutral and may acquire a numbered suffix. Rename your copies clearly, for example your-name-role-cv-v2.document.json and your-name-role-cv-v2.docx. Renaming does not convert formats.

Open a fresh Document workbench, choose the actual saved JSON, review it and explicitly replace the current document. Check all text, make a substantive revision, download a second version and reopen that actual second file. Keep the first version until the second is checked. Export the new DOCX/HTML again; older exports are not updated automatically. Closing or refreshing the editor loses tab-only work. There is no autosave, sync or permanent backup. Do not overwrite your only copy.

6. Optional private tracker
blank/application-tracker.csv-table.json contains one completely blank row. Its status and next-action fields are empty. Open the CSV workbench at https://free4allhub.com/tools/csv/, choose the file with “Reopen editable table JSON”, review it and explicitly choose “Open this table”. The separate “Import comma-separated CSV” picker is for ordinary .csv files. Every cell remains text; dates do not schedule reminders. Use one row per application if useful. The worked tracker instead demonstrates three preparation checkpoints for ONE fictional vacancy, not three applications or a submission history.

Download editable JSON and protected CSV, locate the actual files, then reopen the JSON in a fresh CSV workbench, review, explicitly open, revise and save again. Native JSON preserves exact text. Protected CSV may add a leading apostrophe to formula-like text, and reimport retains it. Protection is not encryption or a universal formula-security guarantee. Other spreadsheet apps may infer dates or numbers and lose leading zeros. Recheck imported data. All stored rows are exported, including filtered-out rows, in stored order. The initial preview shows only the first three rows. Check every row before sharing; a filter is not redaction.

7. Final review before you choose to share
Use truth-and-sharing-checklist.txt. Open the actual DOCX/HTML in the app you and the recipient will use. Check names, dates, spelling, contact details, headings, page breaks and completeness. Search for brackets, “FICTIONAL”, “BLANK TEMPLATE”, Jordan Vale, example.invalid and the example organisations. This helps find leftovers; it cannot guarantee accuracy or submission safety. Check every sentence and metadata too. Keep your fact worksheet and tracker private unless you deliberately choose otherwise. Preparing files grants no permission to send them.

FILES AND LIMITS
Native JSON is the Hub editing source. DOCX and HTML are separate standard exports. All are unencrypted and unredacted, including titles, links, notes and all tracker rows. No real personal data is needed to try this pack. There are no macros, attachments, images, forms, automatic submissions, reminders or external AI processing in these artifacts.

These actual files were validated and reopened through the unchanged native parsers in a file-based Node harness. See verification/RESULTS.txt for the exact tests and actual Writer render results. A harness is not a fresh browser test. Word desktop, Excel/Calc, physical phones and screen readers have not been tested for this pack. Check exported files in your own app. Page count can change after any revision or in a different app.

Free online Word and its resume/cover-letter templates, and the free LibreOffice desktop suite, are alternatives. This pack establishes no subscription savings or formatting advantage. Its purpose is a coherent example, truthful revision and editable local source. See references.txt for general preparation guidance and official product links.

source/ and verification/ contain reproducibility code and technical evidence, not material to submit to an employer. The license applies only to original pack material, not to Hub dependencies or third-party products. No site or application runtime is bundled.
