TOOLS & GUIDES / AI & AUTOMATION
Map the process before the software.
A practical checklist and reusable brief for a clearer conversation.
PRANERAO planning guide · updated 1 October 2026 · examples and checklists, not professional or platform-specific advice.
01 / CHECKLIST
Choose one repeatable task
Write down the trigger, input, action and expected output. Describe the process as it works today, including manual steps and recurring problems.
02 / CHECKLIST
Check the source information
Identify which system holds the correct customer record and who can update it. Avoid moving unnecessary personal information into another tool.
03 / CHECKLIST
Define exceptions and handoff
What happens when a required field is missing, two records conflict or a customer asks for a person? Name the person or role responsible for taking over.
04 / CHECKLIST
Agree permissions and costs
Confirm access roles, customer permissions where needed, provider charges and allowed message types. The proposal should identify configuration, usage and support separately.
05 / CHECKLIST
Test safely before rollout
Use test records and representative failure cases. Check duplicate triggers, incorrect routing, missing permissions and interrupted integrations. Agree a rollback or manual fallback.
06 / CHECKLIST
Make the operation visible
Document alerts, logs and who checks them. Agree useful signals such as failed handoffs or unresolved enquiries. A workflow needs an operating owner after setup.
Your working template.
Copy these prompts into your project notes and fill in what you know.
Task and business goal: Trigger and source system: Inputs actually required: Expected action and output: Human owner and escalation: Exceptions to test: Permissions and provider costs: Manual fallback or rollback: Monitoring owner: Success measures and review date:Download the working template (.txt) ↗
