The Monday-morning rebuild
Recurring tasks have recurring ingredients: the spreadsheet, the template, the boilerplate paragraph, the two reference files. Each time the task comes around, you gather the same items from the same places — a few minutes of hunting that never gets faster, because nothing remembers the set.
Saving a set in DropK
- Build the shelf once. Gather everything the task needs — files, folders, text snippets — onto the shelf, the way you would for a normal run.
- Save it as a layout. Give it a name that matches the task: “Weekly report”, “Client onboarding”, “Invoice run”.
- Restore it next time. Open saved layouts, pick the set, and the shelf repopulates. Do the work, then clear the shelf — the saved set is untouched.
Sets can mix files and text
A saved set is not limited to files. The status-update boilerplate, the email opener you always adapt, the standard reply — text snippets sit in the set beside the files, so the whole kit arrives together. Text mode lets you adapt a snippet on the shelf before pasting, as covered in tips and tricks.
Keep sets where the work lives
In settings, you decide which folders hold your saved drop and text layouts. Point them at the project directory, or at a synced folder, and the sets travel with the project instead of hiding in an app library. A set that stops being useful is just a file — delete it like one.
Good candidates for a first set
- A weekly or monthly report: data file, template, distribution note
- A design handoff: brand assets, spec document, standard handoff message
- An invoice run: template, rate sheet, payment-details snippet
Pick whichever one you rebuilt most recently — that is the set that pays for itself first. New to DropK? Start with the basics, or download it free from the Mac App Store.
