A week of applying, arranged so the hard part happens once

Applying is a batching problem. Here is an arrangement of a week that puts the expensive work at the front and keeps it there.

ConxfolioPublished 2026-09-13

— batch the similar work; it is all the same work.

Applying badly is usually a sequencing problem rather than an effort problem. The arrangement below puts the expensive work at the front and batches the rest, which is the only reliable way to make the fifth application cheaper than the first.

Day one: the document, and nothing else

Import an old document or start from a design, correct the review, and then write the achievement lines properly. That last part is the evening, and it is the thing that pays for the rest of the week. How to write experience bullets is the page to have open while you do it.

Day one, late: one check, read properly

Run the ATS checker once and work the findings in the order it prices them. Structural faults found now stay fixed for the whole week, and the difference a single fix makes is visible because previous reports are kept, which is shown in what changed after one fix.

Day two: read adverts, and only read them

Collect the week's postings without writing anything. Four passes each, and a decision on each: apply or skip. How to read a job posting is the method, and requirements that are really preferences is what stops you skipping jobs you can do.

Day three: batch the letters

Write them in one sitting. The cover letter builder takes the posting and selects evidence out of the résumé, so what you supply each time is the motivation sentence and your judgement about which paragraphs to keep. Doing four in a row reuses the same frame of mind, which is the whole argument for batching.

Day three, also: keep the gaps

Each letter's review names the requirements your evidence cannot support. Copy those into your record beside the application. They are the most likely interview questions and the most reliable list of what to learn, which is the case made in reading your own gaps list.

Day four: send, and record

Export, attach, send. Then write four columns down: role and employer, date, which documents went, outcome. There is no tracker here and there is not going to be one, for the reasons in tracking your own applications.

Day five: one improvement, not five

Take the single fix the report priced highest and do only that, then re-run the check. One measurable improvement a week compounds; a general resolution to improve the résumé does not. The pair of measurements in taking a résumé from 40 to 97 is what that looks like at the extreme.

What to do on a week with no replies

Nothing to the document, for at least a fortnight. Replies arrive on employers' schedules, so a week of silence carries no information about your résumé and a strong urge to act on it anyway. The useful work in that week is the record: which roles, which requirements kept appearing in the gaps lists, and whether the applications were all to the same kind of employer. That is a diagnosis you can act on. Rewriting a document that measured well because nobody has written back is how people arrive at a fourth version that is worse than the first.

What this page does not claim

That this arrangement produces interviews, or that any number of applications a week is correct. Nothing here measures outcomes and nothing here knows your market. What the shape does is reduce the cost of each application after the first and stop you rewriting a document you have already written, which is the only part of a job search a tool can honestly help with.

One last thing, and it is about the weeks when this does not work. A search that is going badly produces a strong urge to rewrite the résumé from scratch every Sunday, and that urge destroys the one asset the arrangement depends on. If the outcomes are poor, look at the record rather than the document: the same missing requirement appearing five times is a different problem from a document that does not extract, and only the second one is fixed in a builder. The honest limits of every résumé tool is the page about where that line falls.

One closing thought about pace. The arrangement above is a week because a week is long enough to contain a bad day and short enough to keep a record accurate. The specific days matter less than the separation: writing, reading, letters and sending are four different kinds of work, and doing them in the same session is what makes an evening feel long and produce two applications. Batching them is the entire trick, and it works whatever the calendar looks like.