Projects are not static. They evolve as the work evolves, and managing them well is part of building a structured practice.
A client project has a natural lifecycle. It begins when the enquiry arrives and you create the project. It grows as you upload documents, have consultations, and develop the proposal. It peaks during the active booking and pre-departure phase. And once the trip is complete and the post-trip follow-up is done, it moves into a dormant state. You do not need to delete it: keep it as a reference for when the client returns or refers someone to you. The history is valuable.
A destination project is ongoing. It grows as you add supplier updates, post-trip observations, and new product information. Review it periodically to remove documents that are out of date or no longer relevant. A destination project that contains a lodge brief from three years ago alongside this season’s updated version creates confusion rather than clarity. Keep it current.
A task-specific project evolves as your practice matures. Your social content standards will sharpen. Your proposal structure will refine. Update the project instructions as your standards develop. The project should always reflect your current best practice, not the standard you had when you set it up.
The practical habit is a brief review at the start of each month: which projects are active, which need updating, which can be archived. Five minutes of housekeeping keeps the whole system working efficiently
