The prompt
Score 10 of 10, Excellent
Use it when Several teams want projects started and you need to score them against agreed criteria so leadership can decide what to fund first.
- {{decision_makers}}
- {{decision_meeting}}
- {{requests}}
- {{criteria}}
- {{capacity}}
- {{priorities}}
- {{close_call_margin}}
Full prompt and why it works
Prompt
Score and rank the project requests below against our criteria, for {{decision_makers}} to use at {{decision_meeting}}, so they can see why each request lands where it does before deciding what to fund. The ranking is an input to their decision, not the decision. Project requests (one per entry, with whatever each includes: sponsor, goal, cost, effort, dates, benefits): """ {{requests}} """ Our scoring criteria and weights: """ {{criteria}} """ Capacity and budget available this period: {{capacity}} Strategic priorities for the period: {{priorities}} Produce: 1. A scoring table with one row per request and the columns Request, a score from 1 to 5 for each criterion, Weighted total, Evidence (the fact from the request behind each score, in a few words). 2. The ranking, highest weighted total first, with a line showing where the available capacity or budget runs out, so the cut-off is visible. 3. Close calls: requests within {{close_call_margin}} of each other or of the cut-off line, and what would change their order. 4. Dependencies and conflicts: requests that need each other, or compete for the same people or systems. 5. Missing information: for each request, what is needed to score it with more confidence, and who to ask. Score only from what each request says, and where a criterion asks about strategic fit, judge it against the priorities above. A good scoring table lets a reader see the evidence for every number, so a sponsor who disagrees can point to the exact fact. Give the same score to the same evidence across requests, and do not reward a request for being longer or better written. For example, the form of one Evidence cell: "Cost 2: estimate is three times this period's spare budget". This example shows the form only. Do not invent costs, benefits or dates, and do not add criteria of your own. If a request gives nothing for a criterion, write ? instead of a score, show its weighted total as a range from the lowest to the highest possible score on that criterion, and list it under Missing information, so the gap stays visible instead of being averaged away. If the criteria or weights are unclear, such as weights that do not add up to 100 percent, say so at the top and show how the ranking changes under each reading.
Variables
- {{decision_makers}}
- Who decides, for example "the leadership team" or "the portfolio board".
- {{decision_meeting}}
- Where the decision is made, for example "the quarterly planning meeting".
- {{requests}}
- The project requests, each with whatever information it came with.
- {{criteria}}
- Your scoring criteria with their weights and, ideally, what a 1, 3 and 5 mean for each.
- {{capacity}}
- What you can take on this period, for example "about 6 people for 3 months and a budget of $200,000".
- {{priorities}}
- The goals for this period that projects should support. Write "none set" if there are none.
- {{close_call_margin}}
- How close two weighted totals must be to count as a close call, for example 0.3 points.
Why it works
- What good looks like. Every score cites the fact behind it and the same evidence gets the same score, so the ranking can be argued with on facts rather than impressions.
- If unsure. A request with no evidence on a criterion gets a ? and a range, which keeps a missing number from quietly helping or hurting it.
- What to avoid. No criteria of the model's own and no invented costs, and the ranking is framed as an input to the decision, which stays with leadership.