📖 How to use Control — field-by-field instructions
▼
Control generates a complete meeting briefing: a timed agenda, structured talking points, a stakeholder map, tough-question Q&A prep, and a risk radar. The example below is pre-filled for the ING Bank ERP Migration Steering Committee — scroll right to see the generated output.
1 · Your role
Determines your perspective in the briefing. A Project Manager gets operational talking points; a Sales Executive gets commercial framing. Select the role you hold in this meeting.
2 · Meeting type
Controls the tone and structure. A Steering Committee gets an executive, decision-oriented briefing. A Technical Review gets detail-heavy content with fewer political considerations.
Project / client
Used throughout to make the briefing specific. Include both the client name and project name — e.g. ING Bank — ERP Migration. Never leave this blank.
Key stakeholders
List names and titles separated by commas. Each person gets their own stakeholder card with influence score, interests, and suggested approach strategy. The more names you add, the richer the briefing.
Main goal / agenda topics
List the topics or decisions needed in this meeting. These become the timed agenda items. Be specific — “Q4 go-live review, budget CR-007 approval” is better than “project update”.
Your concerns
The most important field for Q&A prep and Risk Radar. Add what you expect to be challenged on, risks you are worried about, or political sensitivities. This is fed directly into the toughest prep sections.
Project status
At risk or Off track will trigger more defensive talking points and harder Q&A questions, which prepares you better for a difficult meeting.
Meeting duration
Controls the number of agenda items and depth per topic. A 30-minute meeting gets a focused 3-item agenda; a 2-hour meeting gets a full structured programme.
💡 Best results tip: Specificity = quality. Real stakeholder names, real concerns, and concrete agenda items will produce a briefing that reads like it was written by someone who knows your project. Vague inputs produce generic output.
Understanding your output tabs
📋 AgendaTimed agenda with goals and owners per item.
💬 Talking PointsStructured arguments per topic — ready to use in the meeting.
👥 StakeholdersPer-person interest, influence score and approach advice.
❓ Q&A PrepAnticipated tough questions with suggested answers.
⚠️ Risk RadarWhat to avoid saying, what to watch out for, and power tips.
ProQuenta Control
Walk into every meeting fully prepared.
Full briefing: agenda, talking points, stakeholder map, Q&A prep, and risk radar.
✦ Example — ING Bank ERP Migration
1. Your role
2. Meeting type
3. Context
4. Supporting documents (optional)
📌 Example output — this is what a generated briefing looks like.
0:00–0:05
Welcome & agenda confirmation
0:05–0:20
Q4 go-live readiness review
0:20–0:38
Budget CR-007 — approval request
0:38–0:52
Regulatory compliance status update
0:52–1:00
Decisions, actions & next steps
📊 Project Status
Current status: At risk — actively managed
The project is at risk due to data migration complexity discovered in the build phase. Two legacy data streams have structural integrity issues. A mitigation plan is in place and will be shared today.
Q4 go-live remains the target date
The revised schedule includes a 3-week buffer. No further slippage is expected if CR-007 is approved today. The path to go-live is clear — this meeting needs to unblock it.
💰 Budget — CR-007
CR-007 is a risk mitigation measure, not an overrun
CR-007 covers €85K in additional data cleansing work. This scope was not visible during pre-sales — it was discovered during build. Without this approval, go-live cannot be maintained.
ROI framing: €85K prevents a €200K delay cost
Each month of delay costs ING an estimated €200K in parallel-run operations. CR-007 is therefore the lower-cost path. This is a straightforward financial decision.
🔒 Regulatory Compliance
DNB pre-audit passed — AFM on track
DNB pre-audit passed on 14 March with zero critical findings. AFM sign-off expected end of November, two weeks before go-live. Regulatory compliance is the one green line on this project.
S
Sandra van der Berg
Programme Director — Influence: 85%
On-time delivery, regulatory compliance, steering committee accountability and visibility over risk.
Lead with the mitigation plan and evidence of control. Frame CR-007 as risk management. She needs to be confident before Pieter commits.
P
Pieter Hendriks
CFO — Influence: 90%
Budget control, ROI, no surprises. Will scrutinise every euro of CR-007 and needs written justification before signing.
Open with the cost-benefit numbers immediately. Have the written scope justification ready. Never say “small increase” — always frame in ROI terms.
Why has the budget increased again — wasn’t this in scope?
CR-007 covers data cleansing work that was not in the original contract. During the build phase, three legacy data streams were found with structural integrity issues that were not visible during pre-sales assessment. This is a well-documented industry risk in ERP migrations of this complexity and scale.
High difficulty
Can you guarantee the Q4 go-live date?
We cannot give guarantees, but our confidence level is high. The revised schedule incorporates a 3-week buffer and accounts for all known risks. If CR-007 is approved today, the path to go-live is clear. We recommend confirming this date formally after today’s decision.
High difficulty
What is the regulatory status — are we covered before go-live?
Yes. The DNB pre-audit passed on 14 March with zero critical findings. AFM sign-off is expected by end of November — two weeks ahead of go-live. Regulatory compliance is currently the strongest line on this project.
Medium difficulty
🔴 Avoid saying
“We’ll figure it out” — never say this about the data migration timeline without a written plan in hand.
“It’s just a small budget increase” — Pieter will push back hard. Always frame CR-007 in ROI terms, not minimisation language.
“The regulatory team has it under control” — only assert this if you have written confirmation from your compliance lead.
🟡 Watch for
Sandra may request a formal risk register update — have one ready to share after the meeting or within 24 hours.
Pieter may ask for written scope justification before signing CR-007 — have the document available on screen or printed.
🟢 Tips
Open by framing this as a decision meeting, not a status update. This lifts accountability and attention in the room immediately.
Bring a printed CR-007 one-pager for Pieter. Financial decision-makers appreciate something they can physically sign or annotate.