Quick answer: Windows folders provide a home for each client project. Use New++ to create a repeatable starter structure, Tag+ to label supported files by project and status, and Comment+ to keep feedback with the relevant file. Commands+ can launch your usual tools from Explorer, while Context Menu+ arranges the commands you use most.
Use a client website project as your example
A fictional client, Northwind Studio, needs a small website. Your files include a brief, reference images, copy drafts and delivery notes. Start with a template containing Brief, Working and Deliverables folders, plus a Project notes.txt starter.
Keep the template free of another client's files or credentials. Its purpose is to repeat your useful structure, not to duplicate a past project's private content.
1. Create the project from your starter
Place the starter folder in the templates location configured under Settings > New++. In the destination folder, clear any file selection, then choose the starter from New++. Rename the created copy Northwind website and fill in the brief.
Starting with nothing selected avoids moving existing selected files into the new folder when New++'s selected-item option is enabled. Once the basic template works for you, add date variables or prompted values where they save repeated typing.
2. Label work by project and next action
Apply the Northwind tag to supported project files. Add a small status set: Working, Awaiting feedback and Ready to send. Keep one current status per file and update it when your work moves forward.
Folders keep the project together. Tags let you later find Awaiting feedback files across several projects without collecting duplicate copies in a separate folder.
3. Keep feedback attached to the right version
On a copy draft, use Comment+ to record: Client wants a shorter introduction and the updated contact details. Check the email from 14 September before sending. Include the source or date of the feedback so the note remains understandable later.
Comments provide context; they are not automatic version history. Keep clear version names and use your normal backup or version-control process.
4. Bring your frequent tools into the menu
Use Commands+ to add your editor or another frequently used program, with the appropriate selected-file arguments. Test the command with a sample file. Use Context Menu+ to group project commands together and place them where you want them.
Start with opening an application. Only add scripts that move or modify files after you have tested their behavior on copies.
The result: less setup and clearer handoffs
Your next project starts with the same useful folders. The current draft has its feedback beside it, and an indexed filter for Northwind and Ready to send helps you gather candidates for delivery.
Tools used: New++ · Tag+ · Comment+ · Commands+ · Context Menu+