Turn a rough idea into a project brief you can actually use.
Use this free builder before you request a quote, brief a specialist, prepare a procurement conversation, or start an internal initiative. Work through what you know and leave unknown items blank rather than guessing.
No email is required. You can print or save this page as a PDF from your browser. Nothing is sent to Pathfinder unless you separately choose to start a project.
Build the brief
01 / Desired outcome
What should be different when this project succeeds? Describe the operating result rather than the tool you think you need.
Your notes: ________________________________________________
02 / Current condition
What is happening today? Where are delays, inconsistency, manual effort, quality issues, service gaps, learning gaps, or missed opportunities showing up?
Your notes: ________________________________________________
03 / People affected
Who uses, manages, approves, receives, learns from, or is affected by the process or service?
Your notes: ________________________________________________
04 / Current process
In plain language, what happens today from start to finish? Include important handoffs and decision points.
Your notes: ________________________________________________
05 / Scope boundary
What appears to be included in this phase? What is definitely not included?
Your notes: ________________________________________________
06 / Dependencies
What systems, vendors, data sources, approvals, teams, policies, contracts, or external deadlines could affect delivery?
Your notes: ________________________________________________
07 / Decision owner
Who can approve scope, budget, access, policy, final acceptance, or procurement? Who needs to be consulted?
Your notes: ________________________________________________
08 / Constraints
What accessibility, data/privacy, security, legal, policy, procurement, budget, brand, staffing, location, or technology constraints are already known?
Your notes: ________________________________________________
09 / Timing
Is there a real deadline? What drives it? Which review or procurement dates matter?
Your notes: ________________________________________________
10 / Success evidence
How will you know the work is complete and useful? What measurable or observable evidence should exist?
Your notes: ________________________________________________
Readiness check
Before requesting firm implementation quotes, confirm that you can answer most of these:
□ Desired outcome is clear without naming a tool.
□ At least one concrete example of the current problem exists.
□ Users and people affected are known.
□ A first-pass in-scope / out-of-scope boundary exists.
□ Important systems, vendors, data and approvals are known.
□ A decision owner is identified.
□ Accessibility, privacy/data, security, procurement and policy have been considered.
□ Timing is defined as fixed or preferred.
□ Success/acceptance evidence can be described.
7-9 checked: ready for a focused scoping conversation.
4-6 checked: clarify missing items before firm implementation pricing.
0-3 checked: discovery should come before selecting a solution or vendor.
When the requirement is ready, bring the brief - not a guess.
Use a Pathfinder conversation when the project spans several practices, the requirement is public-sector or institutional, or accessibility, data, security, procurement, multiple stakeholders, or specialist capacity materially affect the scope.