[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-338836-105":53,"doc-detail-338836-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","scope-contracts-project-agreements-workbook","Scope, Contracts & Project Agreements - Workbook","","STRETCH LEARN · WORKBOOK provides a practical document kit for scoping and contracting client projects. It guides teams to convert a vague brief into a deliverables matrix with acceptance criteria, explicit exclusions, and MoSCoW priorities, then assemble an eight-section statement of work linked to a master agreement. The workbook also helps define a clause-based service agreement, establish payment terms tied to ownership transfer, and set IP and licensing positions, including protective checklists to remove ambiguity and control change.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":11,"@type":70,"position":76},"https://docshare.wps.com/template/presentations/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/scope-contracts-project-agreements-workbook/338836/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/scope-contracts-project-agreements-workbook/338836.png","ImageObject",442,249,{"name":88,"@type":89},"Liam","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-09-27","2026-09-21",true,{"@type":98,"interactionType":99,"userInteractionCount":79},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"How does the workbook help define project scope clearly?","Question",{"text":108,"@type":109},"It turns briefs into a counted deliverables matrix with acceptance criteria, explicit exclusions, and MoSCoW priorities, plus exercises to find ambiguities and assumptions that commonly trigger disputes.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What documents does the workbook help you assemble and how are they connected?",{"text":113,"@type":109},"It guides an eight-section statement of work assembled from standard sections and wired to a master agreement, with instructions for referencing which document controls if conflicts arise.",{"name":115,"@type":106,"acceptedAnswer":116},"How does the workbook address payment, ownership, and risk in the service agreement?",{"text":117,"@type":109},"It provides payment term guidance using a payment schedule tied to full payment for ownership transfer, and protective clauses designed to cap risk and decide disputes through clear contractual language.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},338836,1790313372,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":8,"category_name":11,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":79,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":79},8796095461564,"https://ap-avatar.wpscdn.com/davatar_155a257f0dc6eb9ab79c44ca47cae57d","STRETCH LEARN · WORKBOOK  \nScope, Contracts & Project Agreements—Workbook  \nThis workbook turns the course into a working set of documents you can send to a real client. Complete each section as you finish the matching module, and by the end you will have adeliverables matrix with acceptance criteria, a reusable statement of work, a service agreement with the clauses that decide disputes, and a change-order process that converts scope creep into billable revenue. Use the templates to scope your next project, build your contract, and log every change.  \nScope: Defining the Work Before You Commit  \nConvert a fuzzy brief into a counted deliverables matrix with acceptance criteria, explicit exclusions, and MoSCoW priorities.  \nWorksheet: Deliverables Matrix Builder  \nFor your next project, list every deliverable as its own row and define done for each. Use the SOW Builder template to fill the matrix. If you cannot count it or test whether it is finished, it is not scoped yet. Deliverable name (plain, specific)  \n__________________________________________________________________________  \n__________________________________________________________________________  \nExercise: Find the Ambiguity in Your Last Brief  \nTake a recent or current project brief and hunt for every place a difficult-but-honest client could interpret it differently than you intend. This is the single pass that removes most future conflict.  \n• Which deliverable is named so vaguely that the client and you might picture different things (like the logo example)?  \n• Where did you write soon, a few, reasonable, or as needed instead of a date, count, or named limit?  \n• What adjacent work might the client assume is included that you never intended to do?  \n• Which inputs are you silently assuming the client will provide, and what happens if they do not?  \nWorksheet: Exclusions, Assumptions, and MoSCoW Sheet  \nMake the boundary of the project explicit and rank every deliverable so trade-offs are easy under pressure. A client who marks everything a Must have has not prioritised; resolve that before you sign.  \nExclusions (printing, hosting, copy, stock licenses, maintenance, extra formats)  \n__________________________________________________________________________  \n__________________________________________________________________________  \nChecklist: Scope Readiness Checklist  \n[ ] Every deliverable is named, counted, and has a format  \n[ ] Each deliverable has 2-3 testable acceptance criteria that define done [ ] An exclusions list names the adjacent work that is not included [ ] An assumptions list states the inputs and rights I am relying on [ ] Deliverables are ranked with MoSCoW so trade-offs are pre-agreed [ ] The scope passes the stranger test: someone new could build exactly this  \nStatements of Work and the Agreement Stack  \nAssemble the eight-section statement of work, wire it to a master agreement, and strip out the ambiguity traps.  \nWorksheet: Statement of Work Assembler  \nBuild your reusable SOW by completing all eight standard sections. Keep a master template with bracketed placeholders so you can produce a tailored SOW for a new project in under an hour.  \nBackground and objectives (the client goal in 2-3 sentences)  \n__________________________________________________________________________  \n__________________________________________________________________________  \nExercise: Decide Your Document Stack  \nChoose how you will structure your paperwork for repeat versus one-off clients, and wire the documents sonone contradicts the others.  \n• For a repeat client, will you sign one master service agreement and attach short SOWs per project?  \n• For a one-off client, which clauses are legal (belong in the MSA) and which are operational (belong in the SOW)?  \n• How will your SOW reference the governing agreement, and which document controls if they conflict?  \n• Which content currently lives in the wrong document and should move (legal terms out of the","cbCaivoSiRjTp4Wq","https://ap.wps.com/l/cbCaivoSiRjTp4Wq","pdf",15703,10,"English","# Scope, Contracts & Project Agreements - Workbook\n## Scope: Defining the Work Before You Commit\n## Statements of Work and the Agreement Stack\n## The Service Agreement: Clauses That Protect Both Parties","[{\"question\":\"How does the workbook help define project scope clearly?\",\"answer\":\"It turns briefs into a counted deliverables matrix with acceptance criteria, explicit exclusions, and MoSCoW priorities, plus exercises to find ambiguities and assumptions that commonly trigger disputes.\"},{\"question\":\"What documents does the workbook help you assemble and how are they connected?\",\"answer\":\"It guides an eight-section statement of work assembled from standard sections and wired to a master agreement, with instructions for referencing which document controls if conflicts arise.\"},{\"question\":\"How does the workbook address payment, ownership, and risk in the service agreement?\",\"answer\":\"It provides payment term guidance using a payment schedule tied to full payment for ownership transfer, and protective clauses designed to cap risk and decide disputes through clear contractual language.\"}]","Scope, Contracts & Project Agreements - Workbook | PDF",1790026068]