Personal & Life
Application Documents Board: One Master Resume, Many Versions
Intermediate | 1 whiteboard page · Task board: 5 columns (5 parent tasks, 10 subtasks)
Intermediate: Method names appear, but the whiteboard explains the key points. Use the examples as a guide and fill it in, thinking it through for your own situation.
A resume and cover letter lab built around one master set plus three swap points per employer, opened when you are applying to several places and about to write the first document. The whiteboard holds that goal, six steps from raw material to updated master, a grid of prompts against employers, a matrix for what to fix before the deadline, and the patterns that get documents rejected. Five task columns run from To write to Submitted - one card per employer, moved to Drafting once the three swap points are rewritten, to In review while readers have it, and to Submitted after the checks.
Once you have a free account, you can copy this template from the marketplace
Whiteboard preview
Read the whiteboard text as plain text
Application Documents Board
How to use: (1) Answer the four prompts with no employer named → (2) Fill the swap grid and move each card through to Submitted
1. The Goal (one master set, three swap points per employer)
- What this board is for Build one master set and change only three things per employer. Never start from a blank page again.
- The three swap points 1. The opening of the why-us 2. The names of the company and its business 3. What you want to do there. Everything else ships as-is.
- The promise before sending Always read it aloud first. Check that no previous employer's name survived and that the text fits the stated length limit.
- Where the master lives Overwrite the master with whatever you actually submitted, so only the newest set exists. The next employer starts as a copy of it.
2. Six Steps from Blank Page to Sent (run them in this order from the first document)
- Add material Bring the moments and numbers from your self-review into the material column as cards.
- Write master Answer all four prompts — why us, strengths, what you did, where next — with no employer named.
- Tailor it Read the posting and the business, then rewrite only the three agreed spots in their words.
- Get review Have one reader inside your field and one outside it mark every sentence that did not land.
- Submit Confirm length and typos, move the card to submitted, and note the date you sent it.
- Save version Fold the fixes back into the master, and copy that version for the next employer.
3. Prompts Against Employers (what changes from the master)
| Company A | Company B | Company C | |
|---|---|---|---|
| Why us | Link my work to their problem | Quote what their staff said | Lead with the field I follow |
| Strengths | Show scale in headcount and time | Back it with how long I kept at it | Show how fast I picked it up |
| What you did | Team project, my own role first | The fix I proposed at work | How I shipped my own build |
| Where next | The work I want in a few years | One skill to grow on the job | A path deeper into the craft |
4. What to Fix Before the Deadline (impact against effort)
Vertical axis: Impact on the outcome (small to large) / Horizontal axis: Effort to fix (low to high)
- Fix it right now Real impact, quick to change. Start every pre-deadline session here and clear it before moving on.
- Book time for it Worth a lot but slow to rewrite. Decide how much you can finish before the cut-off, then start.
- Fix it in passing Typos and an inconsistent tone. Clear them in a single read-aloud pass, never as their own work session.
- Leave it this time Costly to fix and barely moves the result. Log it against the master and handle it in the next round.
5. Patterns That Get Rejected
- A why-us that could be sent to anyone
- Describing the work but never what you learned
- Ignoring the prompt to say your own thing
6. Habits You Get Called Out For
- Long sentences where the subject quietly changes
- Ending on effort with no action described
- Conclusion buried at the end, nothing up front
7. Pre-Submission Checklist
- No company or team name left over from the last application
- The text sits inside the stated length limit
- Submission method and cut-off time re-checked against the posting
Task board contents
To write 15 items
Gather raw material
Collect the ingredients before you write. Without concrete moments and numbers at hand, every sentence stays abstract.
List 10 experiences
Pull ten moments from classes, clubs, part-time work, and personal builds, and add them as cards in the material column.
Add one number each
Attach a headcount, a duration, or a change figure to every item. Look up anything you cannot recall precisely.
Draft the master
Answer all four prompts without naming any employer. Once this exists, every later application is only a swap.
Draft the why-us
Lead with the conclusion, follow with the experience that backs it, and close with one line about the work ahead.
State your strength
Say the strength in a single sentence, then immediately give the moment and the number behind it.
Tailor per company
Copy the master and rewrite only the three agreed spots in the employer's own words. Never redo the whole text.
Read the job posting
Take three phrases from the role description and the work itself, and copy them into that employer's column in the grid.
Swap three sections
Rewrite the opening of the why-us, the names of the company and its business, and what you want to do there, then move the card to drafting.
Get a review
You cannot see what fails to land in your own writing. Pick your readers and keep the exchange on the board.
Pick two readers
Ask one person inside your field and one outside it, then move the card to the review column.
Apply the feedback
Write down verbatim the sentence that did not land, and be able to explain in one line how the new version differs.
Submit and archive
Nothing goes out before the checklist. After sending, keep the master current so the next employer starts from it.
Run the final check
Check for leftover company names, the length limit, and the submission method and cut-off time, then read it aloud before sending.
Update the master
Fold every review fix back into the master so the next application starts from the newest version.
