A plan you can question. A next move you can make.
The Trail Map is the reviewed output of an Edge assessment. It brings the workflow, sources, opportunities and action plan together so you can decide what to change and why.
Seven parts of one practical decision.
The scope stays focused on one workflow. The deliverables connect the evidence to the first move and to how you will judge its result.
- Operating scorecard
- A concise view of cash, capacity, friction, risk and readiness, grounded in the evidence reviewed.
- One current-state workflow
- The people, systems, decisions, handoffs, delays and rework behind the chosen process.
- Three prioritized opportunities
- The problem, evidence, value range, effort, confidence, dependencies and measurement method for each opportunity.
- Baseline register
- The starting measure, target, source, period, owner and review date needed to judge a future result.
- Sequenced 90-day plan
- What to do first, what to defer, who needs to act, indicative cost and when a change could be measured.
- One starter asset
- A supported SOP, control checklist, requirements specification or automation blueprint. A blueprint is a design; production implementation is a separate engagement.
- Decision menu
- A clear choice between acting with your team, using an advisor or scoping implementation help, with the next decision made explicit.
Follow one finding through the sample.
Our fictional invoice-handoff example connects source evidence to a proposed change, acceptance checks and a measurement plan. It is an illustrative assessment, not a customer result or a recorded software run.
- Inspect the reasoning
- Follow the source, finding, review record and proposed change. Missing owners and unanswered questions remain visible.
- Check the measurement boundary
- The sample defines what would be measured after implementation. Its outcome is labelled “Not measured” because no result has been observed.
What the review record tells you.
The report version and analyst sign-off travel with the recommendations.
- Who reviewed the judgment
- A named analyst reviews evidence sufficiency, assumptions, priorities and the measurement design. Their sign-off identifies the version they reviewed.
- How certain the conclusion is
- Sources, confidence, value assumptions and gaps help you challenge the recommendation. An estimated benefit remains a planning input until it is measured.
- Where the scope ends
- An automation blueprint or starter asset does not imply that an automation has been deployed. Build, target validation and production release need their own scope and approvals.
Choose what happens next.
Two included check-ins, at 30 and 90 days after delivery, review progress against the baseline. Continuous monitoring is separately scoped.
- Act with your team
- Use the plan and starter asset to assign an owner, agree the first change and start collecting the evidence needed for the follow-up.
- Bring your advisor
- Share the findings and assumptions with an existing advisor or implementation partner. The Trail Map stands on its own.
- Scope ProcessScout implementation
- The full $1,500 fee can be credited toward a ProcessScout-delivered implementation of $7,500 or more signed within 30 days of Trail Map delivery. This engagement is called Ridge in the assessment terms. Unused credit expires; the credit cannot be transferred to fees charged by your own implementation partner.
Start with one workflow.
The assessment is $1,500 USD, paid upfront. In the application, this offer is called Foothill Cash & Capacity Assessment. You can review your brief and the assessment terms before payment.