Define what counts as done before you quote the automation.
Turn a workflow you understand into a scope your client can review: included work, exclusions, dependencies and observable acceptance conditions. When the request changes, record whether it is an included defect, an addition to estimate or a question to clarify.
US buyers · One payment · Applicable tax and final terms shown at checkout.
“Route new leads” still leaves a lot to agree.
Which form? Which fields? What happens to duplicates or a missing email? A proposal can name the integration while leaving its working boundaries open. This pack helps you record those boundaries and give later requests a clear route to a decision.
- An operational scope attachment for your own proposal or agreement.
- Acceptance conditions with an exact input, observable result, timing limit and named reviewer.
- An intake and dependency register that keeps missing facts and owners visible.
- A change request and impact estimate using your own hours, rates, direct costs and scheduling capacity.
Compare a vague request with a scope someone can test.
The free two-page fictional example turns a lead-routing request into a bounded scope, three acceptance conditions and a change request. It also shows why correcting an agreed routing failure differs from adding a second form and enrichment.
The full pack adds editable scope, intake, acceptance and change files; three completed fictional scopes; ten request-classification exercises; and a field mapping to your closeout records.
In the fictional scope, one approved form sends leads to one CRM. A GB lead sent to the wrong agreed queue is an included defect. Adding a second form and an enrichment service crosses the baseline and needs a separate estimate. An unclear request stays pending until it can be compared.
Fictional teaching example. Your agency supplies discovery, estimates and its own agreement; an estimate does not authorize work.
Build the baseline. Keep the change decision with it.
Use the intake workbook to record what is known, then complete the scope and acceptance conditions. The change files give you a separate place to explain a request, its impact and the client decision.
Tested in WPS Writer and Spreadsheets 11.8.2.8498 on Windows. Microsoft Word and Excel themselves have not been tested. Files are provided as DOCX, XLSX and PDF.
- PDFSTART-HERE.pdf
- XLSXacceptance-conditions.xlsx
- XLSXchange-impact-workbook.xlsx
- DOCXchange-request.docx
- PDFchange-request.pdf
- XLSXintake-and-dependencies.xlsx
- DOCXscope-attachment.docx
- PDFscope-attachment.pdf
- PDFthree-fictional-scopes.pdf
- TXTLICENSE.txt
- TXTVERSION.txt
A good fit if…
- You understand the basic workflow and have a proposal or change request to prepare.
- You can gather client inputs, account dependencies and observable acceptance conditions.
- You want reusable scope and change records for up to five distinct client projects.
Choose another route if…
- You need a legal contract drafted or reviewed.
- You need someone to discover the client requirements or build the automation.
- You want a project price or delivery date without assessing effort, dependencies and capacity.
Agree the baseline. Record the next request against it.
The pack is an operational attachment to your own agreement. It helps you describe the work and compare requests; you conduct discovery, agree commercial terms and decide when work may start.
- Compare the lead-routing, invoice-extraction and internal-support-assistant fictional scopes.
- Gather the real input, output, volume, timing, dependency owners and unresolved questions.
- Complete the scope attachment and acceptance conditions; record the baseline and client decision under your own agreement.
- For a later request, clarify missing facts, classify it, estimate where needed and record agreement before changing the baseline.
Questions before you choose.
Is this a legal agreement?
No. It is an operational scope attachment for your own proposal or agreement. It does not replace discovery interviews, legal terms or legal advice.
How does it separate a defect from an addition?
Compare the request with the recorded baseline. A failure of an agreed acceptance condition on an in-scope input is an included defect. A known addition beyond a boundary needs a change estimate. Missing detail must be clarified before committing.
Will the workbook tell me what to charge?
It calculates from the hours and rates you enter and shows one-time costs and recurring monthly fees separately. It does not insert a rate, margin, tax or contingency, or prescribe your project price.
Does an estimate mean the change can start?
No. Record the client decision using your own agreement, update the scope and acceptance conditions, then schedule after dependencies are ready. Estimated workdays do not promise a calendar completion date.
How many estimate lines are available?
The change-impact workbook has eight labor lines. Use separate numbered estimates for more lines; the workbook does not combine them.
Do I need the Closeout Pack too?
No. Each pack works independently. The optional field mapping lets you carry acceptance IDs, owners and other shared fields into your own closeout records or the separate Closeout Pack.
What does the license include?
One purchasing agency may use the files for five distinct client projects. Completed client-specific outputs may be shared with that client. Revisions inside the same separately scoped delivery do not consume another project. Unfilled source templates may not be redistributed or resold. Your purchase includes access to updates published for this product in the twelve months after purchase. No update schedule, new feature or future compatibility is promised. You may continue using the files received under the product license after that period. Read the full product license.
Which applications were tested?
Tested in WPS Writer and Spreadsheets 11.8.2.8498 on Windows. Microsoft Word and Excel themselves have not been tested. Files are provided as DOCX, XLSX and PDF.
What are the refund terms?
14-day full refund, including after download. Email lattice@shirasusystems.com with your order reference within 14 calendar days of successful payment. No reason required.
Two practical field notes.
Automation Scope and Change Pack
$199 USD
One agency · Five client projects
US buyers · One payment · Applicable tax and final terms shown at checkout.
Preparing to hand over the completed automation? See the separate Automation Project Closeout Pack for closeout, test and ownership records. Each pack works independently.