You meant to work on the dossier this week. Then a student needed help, a meeting ran long, and the paper revision came back. By Friday, the dossier is still waiting, now with one less week between you and the deadline.
The problem isn't always motivation. “Work on dossier” is too large and vague to compete with a task that has an obvious next step. The book recommends starting early, learning the submission system, gathering materials, and leaving time for feedback. A useful schedule turns those intentions into smaller jobs.
Work backward from the real deadline.
Confirm the submission date and any earlier internal deadlines. Then identify the steps that depend on someone else: obtaining an official report, getting a question answered, or asking a colleague to read a section. Those tasks need lead time even if your own writing is moving quickly.
Don't assume every part of the package is yours to collect. External evaluations and other confidential materials may be handled through a separate institutional process. Clarify your responsibilities rather than putting someone else's task on your checklist.
Choose a personal target that leaves room before the official deadline, where possible. That space isn't an invitation to keep rewriting forever. It's room for the missing file or technical problem you couldn't predict.
Give each work session a visible result.
Instead of booking an afternoon to “prepare portfolio,” define a result you can recognize: confirm the review window, assemble the required teaching reports, draft the service overview, or check evidence references in the research section.
Some tasks will take longer than expected. That's fine. A defined task helps you notice what is blocking progress. Maybe the paragraph is difficult because you don't yet have evidence for the claim, not because you need another hour of staring at the screen.
Keep a short list of unresolved questions separate from the writing. Otherwise, one missing answer can stall an entire section that you could mostly complete now.
Separate drafting from checking.
An early draft needs the right claims, context, and evidence. It doesn't need every sentence polished. Once the argument is sound, revise for clarity, consistency, and length. Save the technical check for an assembled version so you can test what the reviewer will actually encounter.
This doesn't mean ignoring the format until the end. Know the limits and structure from the start. It means you don't have to perfect every label while you're still deciding which contribution the section should explain.
Book feedback before you need it.
Ask a trusted colleague whether they can review a specific section by an agreed date. Send the relevant criteria and a focused question. Leave yourself time to consider the response, ask for clarification, and revise thoughtfully.
If you finish the draft the night before submission, even excellent feedback arrives too late to help much. Protecting a revision window is part of preparing the case, not a luxury after the real work is done.
Today, choose three short sessions over the next week. Give each one a concrete result and identify anything you need to request first. You don't need an elaborate project plan. You need a next step small enough to begin and a schedule that makes room for the parts you can't rush.
Adapted from The New Faculty Handbook by Zafer Unal, chapter 14, pp. 233–236.
