Route investment requests by their purpose
Give capacity, risk and other investment proposals the appropriate review path.
How this works
Give capacity, risk and other investment proposals the appropriate review path.
Route an investment proposal according to the decision it asks the business to make. Capacity expansion, risk reduction and mandatory replacement need different supporting evidence; a project label should not substitute for the applicable approval policy.
Before you start
Defined operating scope
Capital requests have different purposes and require distinct supporting evidence and approval paths.
Required source material
Obtain Investment request; Expected effect; Approval policy. If connectors are unavailable, use authorized files with the same fields.
Decision and exception rules
A capacity request has no evidence of the claimed bottleneck. Request the relevant operating analysis before presenting expansion as justified.
Prepare the inputs
- request_id
- Required
Proposal, amount and sponsor
Specify currency and requested decision.
- purpose
- Required
Capacity, risk, replacement or other stated goal
Allow mixed purposes with separate evidence.
- supporting_analysis
- Required
Expected effect and assumptions
Distinguish measured constraint from asserted need.
- approval_policy
- Required
Thresholds, roles and required evidence
Use the current applicable version.
Implementation, step by step
Establish the working record
- Confirm the selected records, effective versions and responsible owner.
- Check request_id, purpose, supporting_analysis, approval_policy before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.
Checkpoint: The input record identifies the selected request_id and any missing required fields.
Classify the request’s purpose
- Classify the proposal’s purpose from the actual requested effect and identify mixed-purpose components.
- Check routing against the exact policy version, amount and purpose.
Checkpoint: A saved intermediate result for: Classify the request’s purpose.
Collect the relevant supporting analysis
- Collect the evidence relevant to that purpose, such as constraint data, risk assessment or replacement condition, retaining gaps.
- Verify every claimed effect is supported or explicitly marked as an assumption.
Checkpoint: A saved intermediate result for: Collect the relevant supporting analysis.
Route it to authorized reviewers
- Determine authorized reviewers from policy and amount, then route a review-ready packet or a targeted request for missing analysis.
- Check routing against the exact policy version, amount and purpose.
Checkpoint: A saved intermediate result for: Route it to authorized reviewers.
Reconcile the proposed result
- Check routing against the exact policy version, amount and purpose.
- Verify every claimed effect is supported or explicitly marked as an assumption.
Checkpoint: The listed discrepancies have a named reviewer or an explicit unresolved status.
Package the result and unresolved work
- Validate constraint assumptions and applicable approval authority.
- Routing prepares a decision; it does not approve spending or financing.
Checkpoint: A review-ready investment request. Unresolved items remain visible in the review record.
Decisions along the way
A capacity request has no evidence of the claimed bottleneck.
Request the relevant operating analysis before presenting expansion as justified.
The amount crosses a policy threshold.
Use the corresponding approval route and do not split the request to evade it.
The proposal combines purposes with different reviewers.
Include the required reviewers and preserve separate rationale for each component.
What you will produce
capital-request-routing-result.json
JSONA review-ready investment request. Label proposed and completed states separately.
Include: request_id · purpose_classification · amount · evidence_checklist · analysis_gaps · required_reviewers · routing_status · status · evidence_reference · review_note
capital-request-routing-review.md
MarkdownKeep the evidence and unresolved decisions needed to apply this result, including exceptions involving approval_policy.
Include: source_reference · question · owner · next_action
Check the result
- Check routing against the exact policy version, amount and purpose.
- Verify every claimed effect is supported or explicitly marked as an assumption.
- Inspect request_id and purpose in both the original and output; confirm that record identity and interpretation survived the transformation.
- Validate constraint assumptions and applicable approval authority.
When something goes wrong
A capacity request has no evidence of the claimed bottleneck.
Request the relevant operating analysis before presenting expansion as justified. Retain the affected evidence and recovery status.
The amount crosses a policy threshold.
Use the corresponding approval route and do not split the request to evade it. Retain the affected evidence and recovery status.
The proposal combines purposes with different reviewers.
Include the required reviewers and preserve separate rationale for each component. Retain the affected evidence and recovery status.
A worked example
SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT
Request
Route investment requests by their purpose for the following bounded example; prepare the result for review.
Inputs
Synthetic example: Request R-5 proposes equipment costing 50,000 units for capacity expansion. Policy requires operations and finance review above 40,000; no bottleneck data is attached.
Expected result
Synthetic expected result: Route to operations and finance with status evidence incomplete and a request for constraint analysis. Do not mark the investment approved or infer expected return.
Run a small pilot
Start small
Trial a representative batch containing the ordinary case and the exception demonstrated above.
Record the baseline
Record current preparation time, review effort and correction types for the same records.
Agree success criteria
Agree acceptable review and error limits; measure correct reviewer routing; requests returned for missing or mismatched analysis.
Stop or revise
The proposal combines purposes with different reviewers. Pause affected records and apply this recovery: Include the required reviewers and preserve separate rationale for each component.
Keep the scope clear
- Routing prepares a decision; it does not approve spending or financing.
- Qualified owners assess investment assumptions and authority.
Check before using
Validate constraint assumptions and applicable approval authority.
Business activities
- Raise capital or evaluate investments
FROM A RECIPE TO YOUR WORKFLOW
Bring the company context together.
This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.
For this recipe: Investment request · Expected effect · Approval policy
Start with one recurring task, agree which sources to use, and review the first result with your team.
Discuss this workflow