PROJECT BRIEF
Cleargrain Docs · Operations & Research Support

Copy this template and complete only the sections you need.
Describe the work first. Do not include passwords, access tokens, full payment
information, or unnecessary personal records. Use fictional or redacted examples
until the scope, transfer method, and permitted tools are agreed.

THE ESSENTIALS
Project name: [short name]
What is getting in the way? [one or two sentences]
What should the finished work help someone do? [specific result]
Who will use it? [role]
What inputs already exist? [file types, notes, quotes, or recordings]
Approximate size: [files and rows / recording length / number of options]
Requested output: [workbook / procedure / comparison brief / other]
Deadline to consider and reason: [date and dependency, or flexible]
Who can answer questions and review the result? [role]
What would make the handoff acceptable? [two or three observable checks]
What must stay outside the scope? [systems, actions, data, or other limits]

OPTIONAL: SPREADSHEET CLEANUP
What does one row represent? [order line, receipt, contact, etc.]
Authoritative reference and version: [approved list or source]
Important field rules: [IDs, leading zeros, dates, currencies, units, blanks]
Known problems or open decisions: [examples and decision owner]
One-time result or recurring need? [describe]

OPTIONAL: SOP / WRITTEN PROCEDURE
Process trigger and finish: [what starts it; evidence that it is complete]
Walkthrough available: [format and total minutes]
Process owner and intended reader: [roles]
Approved policies, decision points, and exceptions: [references or description]

OPTIONAL: RESEARCH / COMPARISON
Decision to support: [specific question]
Must-have requirements and preferences: [separate the two]
Existing quotes, options, and sources: [titles or public links]
Source boundaries and date sensitivity: [what to include; when facts may change]

OPTIONAL: RECURRING WORKFLOW
Trigger and frequency: [event and approximate frequency]
Example input and expected output: [nonconfidential description]
Exceptions and actions requiring a person's approval: [describe]
Maintenance owner and manual fallback: [role and current method]

BEFORE WORK BEGINS
Agree the scope, output format, fee, timing, acceptance checks, revisions,
permitted tools, data handling, and any support or maintenance expectations.
This completed brief is a starting point for scoping, not an order or contract.