
Internal Project Proposal
Docs + Word9 pages
Free
Requirements go wrong when they describe a design instead of a need, or when every line is marked as essential. This template gives business analysts a clear order: purpose and owner, stakeholders with a RACI matrix, the current process, numbered requirements with priority and tests, then scope, assumptions and sign-off.
The sample follows Sandpiper Works as it replaces phone and spreadsheet bookings with a service booking portal: 64 requirements, 37 of them must-haves, a £480,000 budget and a 99.9% availability target. Replace the sample with your own project, keep each requirement to one testable sentence, and add a measurable acceptance test to every line.
Click Make a copy in Google Docs, then confirm on the Google page. The copy is saved to your own Google Drive.
Write the purpose in two sentences on page 1 and name the business owner, version and status in the title block.
Replace the sample requirements with your own, one must or should sentence each, and give every line an owner and a measurable test.
Assign MoSCoW priorities, keep must items to 60% of the list or fewer, and update the stakeholder and RACI pages.
Delete the guide page at the end, then share the document with your business owner and delivery lead for sign-off.
Most projects land between 30 and 120 numbered requirements. The sample shows 64. Quantity matters less than each line being a single sentence a tester can pass or fail.
Yes. Rename the groups to your product areas, keep the priority, owner, status and test columns, and use the stakeholder pages for product, design and engineering leads.
No. Sandpiper Works, its people, email addresses and every figure are fictional sample data. Replace them with your own details before sharing the document.

Docs + Word9 pages
Free
Docs + Word5 pages
Free
Slides + PowerPoint11 slides
Free
Docs + Word7 pages
Free
Docs + Word3 pages
Free