19 business analysis documents, blank and filled in on one case

• Analysts who need to show their work: in an interview, in a portfolio, or on a first rules-heavy project. The filled set shows what finished work looks like; the blanks and the review exercise are how you produce and defend your own.
• Analysts who have seen templates but never a finished, consistent set: one case, one set of IDs, every document pointing at the others.
• Working analysts who want blanks they can use at work tomorrow, with the reviewer's questions already written on the first page.
• Analysts moving into public-sector or regulated work, where every rule has an owner and a clause number.

Every document opens with a page addressed to you (in the Excel files, the "How to use" sheet). It says what the document is for, when to use it and how to fill it in, then lists what a reviewer will ask and the common mistakes. In the filled version, each reviewer's question points to where the document answers it, and a final section explains why the document is built the way it is.

02-INDEX.pdf lists every file and every ID, and shows where each ID appears. Online, the same index is a page: every ID opens a card with its definition and the places it is used. The review exercise is twelve requirements with ten planted faults. The answer key is a separate file.

A council in England handles requests for information from a shared mailbox and a spreadsheet. Two laws apply to the same inbox: the Freedom of Information Act 2000 for most information, and the Environmental Information Regulations 2004 for anything about the environment. At a council that means planning, waste, noise and much else. The two regimes count the same 20 working days. They differ on nearly everything around them: who may ask, how, what can be refused, what can be charged and how the answer can be challenged.

The files hold the analysis for one process and one request log that serve both regimes. It runs from the brief to a change request, raised once the regulator's new name had a date: 30 September 2026.

The council, its starting point and most of its roles are my choices, tagged [MINE]. Every rule carries a tag: [LAW], [GUIDE] or, for a local choice, [MINE] with the decision that made it. Each is traced to the clause, the page or the decision it came from.

Why English law?

Because every source behind the rules is published. The Acts and regulations are on legislation.gov.uk, the Code of Practice is on GOV.UK, and the regulator's guidance is on the regulator's own website. So every rule taken from them can be checked, by you or by anyone who reviews your work. The rules I chose are marked as choices and point to the decision that made them. The blanks carry no case content: they fit any process that runs on published rules.

Why these documents

Three things you might expect are left out on purpose.

• No use-case specifications. The user stories carry the behaviour, and the state model carries the clock. A third description of the same flow would be the one that drifts.
• No business case with money in it. A council handles requests because the law says so, not because it pays for itself. Any cost or benefit figure would be invented.
• No interview notes, workshop minutes or recordings. No interview took place. The starting point of the fictional council is my choice, and it is tagged [MINE].

Four tags

• LAWStated in an Act or a statutory instrument, with the section or regulation named.
• GUIDEPublished by a government body or a regulator, but not law: a statutory code of practice, a regulator's guidance, or official data such as bank holidays.
• MINEA choice I made for this case: a role, a date, a starting point, a threshold. Kept visible so it can be argued with.
• OPENA question nobody outside the organisation could answer, logged with an owner, a due date and a fallback.

[GUIDE] is used only in these files. The tags used elsewhere on this site are explained on the method page.

• Not legal advice. It shows analysis on rules you can check, as they were read on 29 September 2026.
• Not a course, and not preparation for any certification.
• Not a library of 150 templates. It is 19 documents that fit together.
• Not a real council's documents. The council is fictional and unnamed.
• Not about Scotland. Scotland has its own law and its own regulator.
• Not updated and not supported. They are a snapshot, and the date is printed in every document.
• No AI prompts. No interview transcripts or meeting notes either: no interview or meeting took place, and none is invented.

The licence is for one person. Use the files in your own work, including paid work for a client or an employer. Change them, copy parts into your own documents and keep copies for yourself.

Do not share, upload or publish the files, whole or in large part, in their original or an edited form. Do not sell or give them away as templates, and do not let anyone else use your copy. A team buys one copy per person. Documents you produce with the templates for your own work are yours.

Quotations from legislation and official guidance are public sector information under the Open Government Licence v3.0. This licence does not restrict what the Open Government Licence allows. The terms in full.

If the files are not what you expected, email hello@analify.com within 14 days of your order. Write from the address you used to buy, or add the order number from Polar's receipt. You get a full refund, no questions asked.

If you cannot read the files on analify.com or download the ZIP, there or from Polar's customer portal, email me and I will refund you in full, also after the 14 days.

Polar issues the refund to your original payment method, and your access to the library and the download ends when the refund is issued. The refund policy in full.