Unmasking Freelance Scope Creep: Real Examples & How to Fight Back

Unmasking Freelance Scope Creep: Real Examples & How to Fight Back

• Expansion of Existing Deliverables: What was supposed to be a simple social media campaign becomes a full-blown multi-channel marketing strategy.
• Gold Plating: The client (or sometimes even the freelancer, trying to impress) adds unnecessary features or perfectionist touches that go beyond the project's functional needs.
• Misinterpretation of Requirements: The client's understanding of a deliverable differs significantly from the freelancer's.
• Evolving Business Needs: Genuine changes in the client's market or strategic direction that necessitate changes to the project. While sometimes justifiable, these still need proper management. The consequences of unmitigated scope creep are severe for freelancers. They include: * Budget Overruns: Performing more work for the same pay effectively means working for less than your agreed-upon rate, impacting your profitability.
• Missed Deadlines: The addition of new tasks inevitably pushes back completion dates, leading to frustration for both parties and potentially damaging your reputation for reliability.
• Burnout and Stress: Constantly completing "extra" work can lead to exhaustion, reduced motivation, and a diminished enjoyment of your craft. This is particularly critical for independent professionals often managing multiple client projects simultaneously. Find tips on avoiding burnout in our guide to digital nomad well-being.
• Decreased Quality of Work: When rushed and overworked due to expanded scope, the quality of your output can suffer, undermining the value you provide.
• Strained Client Relationships: While clients may initiate the creep, their patience can wear thin if deadlines are constantly missed or if you consistently push back on their requests without a clear process. Conversely, you might resent the client for the extra work, leading to a breakdown in communication.
• Opportunity Cost: Time spent on underpaid or unpaid scope creep is time that could have been dedicated to new, profitable projects or marketing your services. Understanding these foundational elements is the first step in recognizing and resisting the creeping tendrils of project expansion. It's important to remember that scope creep isn't always malicious; often, it arises from a lack of clarity or a client's evolving understanding of their own needs. Regardless of its origin, the responsibility to manage it effectively ultimately falls on the freelancer. ## Real-World Examples: When Too Much Became Too Much To truly grasp the gravity and varied forms of scope creep, it's helpful to examine specific instances. These examples highlight how seemingly small requests can snowball into significant problems across different freelance disciplines. ### Web Development & Design: The "Just One More Page" Syndrome Scenario: A freelance web developer is hired to build a 5-page informational website for a local small business, including a home page, about us, services, contact, and a simple blog. The agreed-upon price is $3,000, with a 3-week timeline for completion. Creep:
• Week 2: The client asks, "Can we add a testimonials page? It's just quotes, so it should be quick." (Adding a new page, even if simple, requires design, development, content population, and testing time.)
• Week 3: "We've decided we also need an online store for two products. It doesn't have to be fancy!" (A major addition requiring e-commerce integration, payment gateway setup, product management, and security considerations.)
• Week 4: After the site is largely built, the client says, "I really love the animations on that competitor's site. Can you add those to our main sections? And perhaps integrate our Instagram feed scrolling on the homepage?" (Significant new feature requests, design changes, and API integrations.)
• Week 5: "My nephew said the site doesn't look modern enough on his iPhone XS Max. Can we completely re-do the mobile layout?" (Major redesign and development work, post-coding review.) Impact: The developer ends up building a 10-page website with e-commerce functionality, complex animations, and a full Instagram integration, requiring 8 weeks of work instead of 3. The original $3,000 fee now translates to a drastically lower hourly rate, and other projects are delayed. This often happens if the initial client communication isn't clear enough about mobile design, which is a core expectation in modern web development. For resources on clear project communication, explore our Project Management Essentials articles. ### Content Creation & Marketing: The "While You're At It" Request Scenario: A freelance content writer is hired to produce 10 blog posts (800 words each) for a client's niche industry, priced at $100 per post, with a 2-month delivery schedule. Creep:
• Month 1: The client starts asking for extra research on each topic. "Can you deep-dive into these 5 studies for the next post? And also create 3 social media snippets for each blog?" (Extra research time and additional deliverable creation.)
• Month 2: "Our CEO just launched a new initiative. Can you write a 2,000-word whitepaper on it instead of the next two blog posts, and then draft an email campaign to promote it?" (Significant change in deliverable type, word count, and addition of new marketing collateral.)
• Post-Delivery: "The posts are great, but can you go back through posts 1-5 and add internal links to these 15 new product pages we just launched? And optimize all of them for 'keyword X' which we just decided is our primary focus?" (Retroactive work, SEO optimization, and significant editing beyond initial scope.) Impact: The writer spends roughly double the time they initially budgeted for the 10 blog posts, adding whitepaper writing, email campaigns, in-depth research, and extensive retroactive editing, all without additional compensation. This directly affects their freelance income. ### Graphic Design: The "Just A Few More Revisions" Trap Scenario: A freelance graphic designer is commissioned to create a new logo and brand identity guide for a startup, including 3 initial concepts with 2 rounds of revisions on the chosen concept. The fee is $1,500. Creep:
• Round 1 Revisions: The client requests significant changes that essentially combine elements from all 3 initial concepts into a fourth, new concept, rather than revising one.
• Round 2 Revisions: Instead of final tweaks, the client says, "It's close, but my business partner wants to see it in a different color palette, and with a completely different font family." (A major overhaul, outside the spirit of "revisions.")
• Post-Approval: "Can you also design business cards and letterheads with the new logo? And maybe a quick social media banner? We just figured you'd do that as part of the brand package." (Addition of entirely new deliverables.)
• Months Later: "We're launching a new product. Can you just tweak the logo slightly for that, add a sub-tagline, and send us the files in 10 different variations for print and web applications?" (Ongoing design work for which no retainer or project was established.) Impact: The designer performs work equivalent to 5-6 rounds of revisions and creates multiple additional branding assets, far exceeding the initial agreement. The initial $1,500 payment becomes a fraction of what such extensive work should command. These examples underscore a crucial point: scope creep isn't always a single, large request. Often, it's a series of small, seemingly innocent additions that cumulatively decimate your project's profitability and your sanity. Recognizing these patterns across different fields is the first step in formulating a strong defense. ## The Psychology Behind Scope Creep: Why Clients Ask for More Understanding why clients engage in scope creep, even unconsciously, can be as important as knowing how to react. It’s rarely malicious intent; more often, it’s a confluence of factors related to communication, clarity, and evolving needs. ### 1. Lack of Clarity and Ambiguity This is perhaps the most common culprit. Many clients, especially those new to hiring freelancers, don't fully understand their own needs until they see progress. They might have a vague idea but lack the technical vocabulary or project management experience to articulate it precisely. "We Need a 'Stylish' Website": What "stylish" means to one person can be vastly different for another. Without concrete examples, benchmarks, or specific design elements, this can lead to endless revisions as the client tries to articulate their taste during* the design process.
• "Increase Our Social Media Presence": This broad goal can encompass anything from posting daily to launching paid ad campaigns, influencer collaborations, and community management. If the specific tactics and deliverables aren't agreed upon, anything the freelancer doesn't do can be perceived as incomplete. Freelancer's Role: It's your responsibility to translate their vague ideas into concrete, measurable deliverables. Asking probing questions during the discovery phase is crucial. ### 2. The "If We're Going to Do It, Let's Do It Right" Mentality Once a project is underway, clients often start thinking about ideal outcomes rather than essential ones. They might see an opportunity to add a feature or improve something "while you're already in there." They genuinely believe these additions are minor or logically fit within the existing work. * "Since you're redesigning the logo, can you just give me a stationery set design too? It's basically using the same elements." While the elements might be similar, stationery design is a distinct deliverable with its own set of requirements, file formats, and design considerations.
• "You're already coding the contact form, can you just add a dropdown for subscription preferences? It's just a few more lines of code, right?" Even "a few lines of code" can involve backend logic, database updates, UI/UX considerations, and testing, expanding the original task significantly. Freelancer's Role: Explain the distinct effort involved for each sub-task, even if they appear related. Educate them on the dependencies and implications of each "small ask." ### 3. Fear of Missing Out (FOMO) and Competitive Pressure Clients often operate in competitive markets. They see what competitors are doing, or what new technologies are emerging, and suddenly feel their project needs to incorporate these new elements to stay relevant. * "Our competitor just launched a new feature...": This can lead to urgent, reactive requests to add similar (or even superior) features to their own project, regardless of the original scope.
• *"My friend said we have to have a chatbot on our site...": External influences and trendy additions can quickly derail a focused project. Freelancer's Role: Help clients prioritize. Remind them of the original project goals and how new requests align (or don't align) with those objectives. Often, these "must-have" features can be phased into a future project. ### 4. Project Evolution and Genuine Business Needs Sometimes, scope creep isn't a problem; it's a necessary evolution. A client's business might genuinely pivot, or market conditions might change significantly, requiring adjustments to the project. A startup changes its core offering mid-development: This isn't scope creep in the negative sense, but a genuine shift.
• A new regulatory compliance requirement emerges: This could necessitate changes to a website or software. Freelancer's Role: While these are legitimate reasons for change, they must be managed with a formal "change request" process. They are not spontaneous additions to the existing agreement. This is an opportunity to strengthen the client relationship, not let it erode your profitability. By understanding these underlying motivations, freelancers can approach scope creep not just as a problem to be shut down, but as an opportunity for clear communication, client education, and the implementation of project management strategies. This understanding can help you respond with empathy and professionalism, rather than just frustration. Check out our Client Communication Strategies Guide for more on this. ## Proactive Prevention: Setting Up for Success From Day One The best way to deal with scope creep is to prevent it from happening in the first place. Proactive measures, taken right from the initial contact with a potential client, can save you immense headaches down the line. This foundational work is critical for any independent professional, whether you're a seasoned freelancer or just starting your remote work career. ### 1. The Power of a Detailed Project Brief/Statement of Work (SOW) Before any work begins, a meticulously crafted project brief or Statement of Work (SOW) is your strongest defense. This document should leave no room for ambiguity. Specific Deliverables: Clearly list everything* you will provide. If it’s a website, specify the number of pages, custom functionalities, third-party integrations (if any), content responsibilities (who provides text/images), and revision rounds. For content writing, state article count, word count per article, topic areas, research depth, and number of edits.
• Out-of-Scope Items: Explicitly state what is not included. This is just as important as what is included. For example, "SEO optimization beyond basic keyword placement is not included" or "Ongoing website maintenance post-launch is not part of this agreement."
• Project Timeline: Outline key milestones, deadlines for freelancer deliverables, and deadlines for client feedback/approvals.
• Payment Schedule: Detail when payments are due (e.g., 50% upfront, 25% at milestone X, 25% upon completion).
• Revision Policy: Define the number of revision rounds included and what constitutes a "revision." Be specific (e.g., "2 rounds of revisions on design concept; subsequent revisions will be billed hourly").
• Review and Approval Process: How will deliverables be reviewed? Who is the key decision-maker on the client's side? How long do they have for feedback?
• Change Request Process: Crucially, outline the procedure for requesting changes outside the agreed scope (more on this below). Actionable Tip: Use a template for your SOWs that you can customize for each project. Have the client sign off on this document before any creative or developmental work commences. For larger projects, consider exploring our guide to B2B contracts. ### 2. Thorough Discovery Phase and Requirements Gathering Don't rush the initial conversations. The "discovery phase" is where you deeply understand the client's needs, goals, and expectations. * Ask Open-Ended Questions: Go beyond "what do you want?" to "why do you want it?" and "what problem are we trying to solve?" This helps uncover underlying motivations and unstated assumptions.
• "Why" Questions: For every desired feature, ask "why is this important?" and "what impact will this have?" This helps prioritize and identify truly essential elements versus "nice-to-haves."
• User Stories (for developers/designers): "As a [type of user], I want to [action], so that I can [benefit]." This provides clear, user-centric definitions of functionality.
• Visual References: For design projects, ask for examples of what they like and dislike. "Show me websites/logos that you admire, and tell me why." Actionable Tip: Document all conversations and decisions during this phase. Send meeting recaps with action items and confirmed requirements to the client for their review and approval. This creates a paper trail for future reference. ### 3. Educating Your Client About the Process Many clients simply don't understand the intricacies of freelance work or project development. It's your job to educate them. Explain Your Process: Walk them through the typical stages of your project, from discovery to delivery. Explain why* certain steps are necessary.
• Define "Deliverable": Ensure they understand that what you produce at each stage is a specific, agreed-upon item.
• Manage Expectations: Be upfront about what's possible within the budget and timeline. If their vision is grand but their budget is small, address it early. Explain the cost implications of changes.
• The "Iron Triangle": Introduce the concept that you can have any two of Fast, Cheap, or Good, but not all three. If they want to add scope (More Good), something else—cost (Cheap) or time (Fast)—must give. Actionable Tip: Create a simple "Client Onboarding Guide" or FAQ that outlines your typical process, revision policies, and how changes are managed. Share this upfront. This can be listed as a resource on your About Us page or within your service offerings. ### 4. Phased Approaches and Milestones Breaking larger projects into smaller, manageable phases with clear deliverables and acceptance criteria for each phase can help. * Incremental Delivery: Instead of delivering one huge project at the end, deliver in stages. This allows clients to see progress, provide feedback, and catch potential scope creep early.
• Milestone Payments: Tie payments to the completion and approval of specific milestones. This provides incentive for both parties to adhere to the agreed-upon scope for that phase. Actionable Tip: For complex projects, propose a "Phase 1" that tackles the core functionality. Once that's complete and approved, additional features can be discussed for "Phase 2," effectively making them new projects. This is particularly useful for longer engagements, common for digital marketing freelancers. By investing time in these proactive prevention strategies, you lay a solid foundation for a successful project and minimize the chances of scope creep eroding your margins and peace of mind. This isn't being rigid; it's being professional and setting clear boundaries, which ultimately fosters mutual respect. ## Responsive Strategies: Handling Creep When It Happens Despite your best proactive efforts, scope creep will inevitably appear. The key is how you respond. Effective management of scope creep is about maintaining control, clear communication, and protecting your project's integrity without alienating your client. ### 1. Recognize It Immediately & Document Everything The moment you suspect a request is outside the agreed-upon scope, hit the pause button. Don't simply proceed, assuming it's a minor addition. * Listen Actively: Pay close attention to keywords like "can we just add," "it would be great if," "while you're in there," or any request that deviates from your SOW.
• Internal Assessment: Quickly check the request against your signed SOW. Is it truly new, or is it a clarification of something already included?
• Document the Request: Keep a clear log of all client communication, especially those related to new requests. This includes emails, meeting notes, IM conversations, or any other medium where the request was made. Actionable Tip: Create a simple "Project Changes Log" spreadsheet for each project. Note the date of the request, the request itself, your assessment against scope, and the proposed resolution. ### 2. Refer Back to the Original Scope Your Statement of Work (SOW) is your contract and your compass. When a new request comes in, gently but firmly guide the conversation back to this document. * "That's a great idea, [Client Name]! Looking back at our Statement of Work for this project, page X, section Y, we outlined these specific deliverables. This new request falls outside of that original agreement."
• "I understand you'd like to add [new feature], and that's definitely something we can explore. As per our initial agreement, this project includes [original deliverables]. Would you like to proceed with the original plan, or would you like to discuss how this new feature would impact our timeline and budget?" Actionable Tip: Have your SOW readily accessible during client calls. Referencing exact sections and bullet points lends authority and shows you're prepared. This professionalism builds trust, a cornerstone of successful remote team collaboration. ### 3. Implement a Formal Change Request Process This is perhaps the most critical responsive strategy. Every request that falls outside the SOW must go through a formal change request. * Acknowledge and Validate: "Thanks for bringing this to my attention! This sounds like a valuable addition." (Acknowledge and affirm the client's idea, avoiding immediate negativity.)
• Explain the Impact: "Given our current timeline and budget, adding this would require X additional hours and push our completion date to Y. It would also increase the project cost by Z." Be specific with hours, dates, and costs.
• Provide Options: Offer choices: Option A: Add to current project. "We can incorporate this, but it will require a formal change order, adjusting the timeline and budget." Option B: Defer to a future phase. "We can complete the original scope first, and then address this as a separate mini-project or Phase 2." * Option C: Swap a feature. "To keep within our original budget/timeline, we could swap out [less critical original feature] for this new one."
• Require Written Approval: Never proceed with out-of-scope work based on a verbal agreement. Send a "Change Order" document that details the new request, its impact on scope, timeline, and cost, and requires the client's signature or explicit email approval. Actionable Tip: Prepare a simple "Change Order" template. It should outline: Original Project, Change Requested, Impact on Deliverables, Impact on Timeline, Impact on Budget, and require client signature/approval. ### 4. Price It Appropriately (and Don't Undercut Yourself) When providing a quote for out-of-scope work, ensure you price it fairly based on your standard hourly rates or a new project fee. * Value Your Time: Don't discount new work just because the client "has already paid for big things." Each task stands on its own.
• Factor in Communication Overhead: Remember that changes often require more meetings, more emails, and more coordination, which are all part of your time.
• Consider Impact on Other Projects: If taking on new scope means delaying another client's project, factor that opportunity cost into the new pricing. Actionable Tip: If the client pushes back on the price for a change order, gently remind them of the value you provide and the time investment required. "My rates reflect the quality and expertise I bring to your project. This new feature requires X hours of specialized work." Explore our guide to pricing your freelance services. ### 5. Know When to Say No (and How to Do It Gracefully) Sometimes, a request is genuinely unreasonable, beyond your capabilities, or would fundamentally derail the project. Knowing when and how to decline is a vital skill. * Be Polite and Professional: "I appreciate you thinking of me for this, but unfortunately, [this request] falls outside my area of expertise/current project capacity/the agreed-upon scope and would significantly impact our current deliverables."
• Offer Alternatives (if possible): "While I can't incorporate that into this project, I can recommend a colleague who specializes in that area." Or, "Let's revisit this after the main project is complete."
• Focus on the Main Goal: "My priority right now is to deliver the core functionality we agreed upon by our deadline. Adding this would jeopardize that." Actionable Tip: Practice saying "no" in a way that protects your boundaries without damaging the relationship. It's often about stating what you can do, rather than what you can't. This is part of maintaining work-life balance for nomads. By adopting these responsive strategies, you transition from being a passive recipient of endless requests to an active manager of the project, guiding your client towards the best outcomes while protecting your own interests. This builds respect and leads to more successful project completions. ## Technologies and Tools to Aid in Scope Management In the age of remote work, a variety of digital tools can be instrumental in preventing and managing scope creep. These tools facilitate clarity, documentation, and streamlined communication, acting as virtual assistants in your battle against expanding project boundaries. ### 1. Project Management Software Platforms like Asana, Trello, ClickUp, Monday.com, or Jira provide a centralized hub for all project-related activities. * What they do: Allow you to define tasks, assign responsibilities, set deadlines, and track progress. You can break down the project into granular steps, making it clear what is (and isn't) part of the work.
• How they help with scope creep: Visual Scope: The agreed-upon tasks and deliverables are visually represented. Any new task added by a client immediately stands out as an "extra." Activity Logs: Most platforms log all changes, comments, and task additions, creating an auditable trail of project evolution. Client Collaboration (controlled): You can invite clients to view progress, but often limit their ability to add or modify tasks without your approval, forcing discussion before execution. Budget & Time Tracking Integrations: Some tools integrate with time tracking and invoicing software, making the cost of new tasks immediately apparent. Actionable Tip: Choose a tool that fits your workflow and client's comfort level. Ensure tasks are written clearly and linked directly to the SOW. Regular reviews of the project board with the client can highlight scope changes proactively. For small teams, consider our guide to remote team collaboration. ### 2. Version Control for Documents & Files For creative freelancers (designers, writers, developers), tools that track changes to documents and code are indispensable. * What they do: Services like Google Drive, Dropbox (with version history), GitHub (for code), or design tools like Figma and Adobe XD (with built-in versioning) save every iteration of a file.
• How they help with scope creep: No "Lost" Changes: You can always revert to a previous version if a client decides to undo a revision, minimizing wasted effort. Accountability: It clearly shows who made which changes and when, removing ambiguity about revision counts. Proof of Original Design/Content: If a client claims "that's not what I approved," you have undeniable proof of the original submission and subsequent revisions. Actionable Tip: Implement a strict versioning protocol. Name files clearly (e.g., `ProjectName_Logo_v1.ai`, `ProjectName_Logo_v2_ClientFeedback1.ai`). For written content, use "track changes" in Word or Google Docs for collaborative editing. ### 3. Dedicated Communication Platforms While email is fundamental, dedicated platforms can structure communication better. What they do: Slack, Microsoft Teams, or specific client portals offer channels for different topics, making conversations more organized than sprawling email threads.
• How they help with scope creep: Channel-Specific Discussions: Create channels for "General Discussions," "Feedback on Deliverable X," and crucially, a "Change Requests" channel. Searchable History: Easy to trace back specific conversations where new ideas or requests were first mentioned. Reduced Informal Requests: Clients might be less likely to casually drop a significant new request in a structured chat channel than in a quick, informal message. Actionable Tip: Set clear expectations with clients about how and where all official project communication and change requests should occur. Discourage project-critical discussions over personal messaging apps. ### 4. Time Tracking Software Tools like Toggl, Clockify, Harvest, or RescueTime are crucial for understanding where your time actually goes. What they do: Allow you to track the exact amount of time you spend on each task, client, and project.
• How they help with scope creep: Evidence of Overtime: If you find yourself consistently going over estimated hours for tasks, it’s an early warning sign of creep. Justification for Change Orders: When quoting for new scope, you can back up your pricing with data on how long similar tasks actually take. Hourly Billing for Changes: If you've agreed to an hourly rate for approved out-of-scope work, these tools provide undeniable proof of hours worked. Improved Estimates: Over time, tracking helps you become much better at estimating future project scopes, which helps prevent creep from inaccurate initial quotes. Actionable Tip: Make time tracking a habit for every single task, even small ones. Review your time logs regularly to identify trends and potential scope issues. This is essential for freelance efficiency. By integrating these technologies into your freelance workflow, you create a system that not only helps you manage projects more effectively but also provides the necessary documentation and data to confidently address and control scope creep. These tools transform fuzzy requests into trackable data, making the invisible impact of creep visible and manageable. ## Client Buy-In: Getting Them On Board with Scope Control Successfully combating scope creep isn't just about your internal processes; it also heavily relies on fostering a collaborative relationship with your client where they understand and respect project boundaries. Getting their buy-in on scope control is paramount. ### 1. Transparency From the Outset Openness about your process and boundaries builds trust and avoids surprises later. Explain the "Why": Don't just say "no additions allowed." Explain why* a detailed SOW, a change request process, and defined deliverables are important for their project's success. "By clearly defining our scope upfront, we ensure the project stays on track, on budget, and delivers exactly what you need without delays or unexpected costs."
• Show the Value: Frame scope control as a benefit to the client. It ensures focus, avoids feature bloat, and guarantees timely delivery of critical functionalities. Actionable Tip: During the onboarding call or when discussing the SOW, dedicate a few minutes to walk them through your "rules of engagement" regarding changes, emphasizing how it leads to a smoother project for them. Link them to resources on project management best practices if they are interested, perhaps even a brief mention of our guide to client onboarding. ### 2. Continuous Communication, Not Just Reactive Don't wait for creep to happen. Maintain regular, scheduled check-ins. Regular Progress Updates: Send weekly or bi-weekly reports summarizing progress against the SOW. This reinforces what is* being worked on and highlights where the project currently stands.
• Milestone Reviews: At the completion of each major milestone, hold a formal review. Confirm that deliverables meet the agreed-upon standards for that phase. This prevents retroactive changes to already approved work.
• Pre-emptive Discussions: If you foresee potential areas where a client might want to add something, address it proactively. "Once we complete the core website design, we can discuss Phase 2 features like the advanced search function you mentioned." Actionable Tip: Schedule recurring meetings in your calendar and share them with the client. Use a shared agenda and send meeting minutes summarizing decisions and next steps. For more on communication styles, consult our guide on digital communication etiquette. ### 3. Frame Changes as Opportunities, Not Problems When a change request does come in, your framing can significantly impact the client's reception of your response. * Positive Language: Instead of "That's not in scope," try "That's a fantastic idea, and a very valuable addition. Let's explore how we can integrate that into a future iteration or as an add-on to this current project."
• Solution-Oriented: Offer options (add to current project with cost/timeline adjustment, defer, swap features). You're not saying "no" to their idea; you're managing its integration.
• Focus on Value: Explain the value of the new feature and why it therefore warrants a separate fee or adjustment. "This advanced reporting feature will provide deep insights, and to ensure we build it robustly, it will require X additional hours including data integration and custom UI development." Actionable Tip: Practice scripting these responses so they come across as professional and helpful, not confrontational. Your goal is to be a project partner, not an adversary. ### 4. Create a "Parking Lot" for Future Ideas Clients often have many great ideas that aren't essential for the current project. Create a space for these. * Maintain a List: During calls or throughout the project, keep a "Future Ideas" or "Parking Lot" list for the client.

*