Business preparation · Companion guide
Define project boundaries before adding more work
Explain what a business project includes, what it excludes and how proposed additions will be reviewed. Keep a useful improvement from becoming an unrecorded commitment.
Merchant Dash LLC · Includes a private checklist
Jump to the checklist ↓
What you’ll take away
- Describe a recognizable outcome and name the included work.
- Keep excluded ideas visible without treating them as commitments.
- Review additions before replacing the current scope.
A project boundary describes what the team intends to accomplish and what remains outside the current plan. Write it before comparing detailed tasks. A clear boundary helps people notice when a suggestion changes the job, rather than treating every reasonable idea as part of the original scope.
Describe an outcome someone can recognize
Use an observable result. “Refresh the property” can include almost anything. “Replace the seating in the reception area and return that space to ordinary use” gives the team a clearer subject. Then list the rooms, equipment or processes included. Use the same names in the scope note, supplier questions and internal checklist.
An outcome is not a promise about the business results that may follow. A completed reception project does not establish increased bookings, better reviews or any other future result. Keep hoped-for benefits in a separate assumptions section.
Name the excluded work without losing it
Create an “outside this project” list for related ideas. The list can include useful work that deserves a later decision. It is not a statement that the work is unnecessary. For each excluded item, say whether it is deferred, assigned to another project or still awaiting clarification.
A boundary may also separate internal work from supplier work. If a quote does not say who handles removal of old items, record that as a question. Do not label it excluded or included until the relevant scope is understood. This prevents the project file from turning silence into a commitment.
Review additions with a short change note
When somebody proposes more work, record the addition before editing the current scope. Ask what it changes: the outcome, location, sequence, required records or responsible roles. Identify which existing assumptions need another review. A change that appears small in a description may affect a dependency elsewhere in the plan.
Use a proposed-change status until the business follows its actual decision process. Keep the original scope and the revised version connected. The organizational note does not modify a supplier contract or grant anyone authority to make a commitment.
Ask the questions that reveal the boundary
Use these prompts during an internal review:
- What result is this project intended to produce?
- Which spaces, items and processes are included by name?
- What related work is explicitly outside the current plan?
- Which responsibility is unclear in the current records?
- What would the proposed addition change for the rest of the work?
If people answer differently, record the disagreement as an open question. Do not combine conflicting answers into a vague sentence that appears settled but cannot guide the work.
Illustrative example: a reception project expands during discussion
A fictional lodging business plans to replace reception seating. A colleague suggests changing the adjacent storage area at the same time. The coordinator records the suggestion separately. The storage change involves another area and new access questions, so the original seating scope remains current while the business reviews the proposal.
If the addition is later accepted internally, the revised scope names both areas and records which earlier assumptions need checking. If it is deferred, the seating project can still be described accurately. Neither outcome requires deleting the suggestion or rewriting the history.
Carry the boundary into the next document
Use the current scope when preparing supplier questions, a project checklist or an internal status update. If an existing business request was based on an earlier version, review whether a clear change note is needed through the established private route. Do not start a duplicate request simply to add an explanation.
The scope-boundary method above is an original Merchant Dash preparation framework. The SBA's planning guidance provides broader context for describing business activities and responsibilities. Keep private records in the business's approved system, and use the Business Planner when a blank outline would help organize the next review.
Your preparation checklist
- Write the intended outcome in one sentence.
- Name the spaces, items and processes included.
- List related work that is deferred or handled elsewhere.
- Separate unclear responsibilities from confirmed exclusions.
- Record each proposed addition and the assumptions it changes.
- Carry the current scope into the next project document.
Save your notes privately. This page does not collect your answers. Keep personal identifiers and confidential documents in your secure records.
One connected journey
Choose the next step you need.
Preparation is optional. You can use the request form when you are ready; these guides do not determine eligibility.
Choose a request
Start with the business activity and review the request service.
Prepare the details
Build a private records index and identify what still needs checking.
Understand the next step
Keep received, submitted and reviewed statuses distinct.
This hospitality operating-request service is unavailable in CT, FL, GA, MO, TX and VA.