[{"data":1,"prerenderedAt":1092},["ShallowReactive",2],{"use-case-en-pharma-field-force-operations-approvals":3,"use-case-starters-en-revo-approval-workflows":277},{"id":4,"title":5,"approvalWorkflowPattern":6,"body":9,"canonicalSlug":16,"critical":17,"cta":24,"description":33,"extension":34,"hero":35,"legacyRedirects":69,"locale":70,"meta":71,"navigation":7,"outcomes":72,"path":90,"phases":91,"platformFit":250,"primaryModule":263,"priority":264,"problem":265,"seo":273,"status":274,"stem":275,"__hash__":276},"useCases\u002Fen\u002Fuse-cases\u002Fpharma-field-force-operations-approvals.md","Field Force Operations Approvals for Pharma",{"enabled":7,"starterCategory":8},true,"field",{"type":10,"value":11,"toc":12},"minimark",[],{"title":13,"searchDepth":14,"depth":14,"links":15},"",2,[],"pharma-field-force-operations-approvals",{"title":18,"bullets":19},"When structured field workflows matter most",[20,21,22,23],"Your field force handles frequent operational requests such as samples, expenses, travel pre-approval, and PTO.","Managers need to approve quickly without sacrificing policy checks or operational visibility.","You want better control over budget utilization, operational load, and request quality across the field.","You need workflows that fit the speed of the field, not administrative processes that slow it down.",{"title":25,"description":26,"primaryCta":27,"secondaryCta":30},"See how REVO structures your field force operations","In just 30 minutes, you will see how REVO Approval Workflows can turn everyday field requests into structured, auditable workflows that move faster, reduce friction, and give management clearer operational control.",{"label":28,"href":29},"Schedule demo","https:\u002F\u002Frevosuite.com\u002Fschedule-demo",{"label":31,"href":32},"Explore Approval Workflows","https:\u002F\u002Frevosuite.com\u002Frevo-approval-workflows","Use REVO Approval Workflows to structure field force requests like samples, expenses, travel pre-approval, and PTO with faster approvals, cleaner data, and better operational visibility.","md",{"eyebrow":36,"title":37,"description":38,"primaryCta":39,"secondaryCta":40,"visual":41},"Field Force Operations","Structure field force operations without slowing the field down","REVO Approval Workflows turn everyday field force requests, samples, expenses, travel pre-approval, and PTO, into structured, auditable workflows that reduce back-and-forth, improve visibility, and help teams move faster with more control.",{"label":28,"href":29},{"label":31,"href":32},{"variant":42,"label":43,"title":44,"metric":45,"detail":46,"bars":47,"checkpoints":52,"partners":57,"allocationLabels":61},"field-ops-queue","Daily field ops queue","Samples, expenses, travel, and PTO in one queue","24 requests","Every request keeps its data, policy, budget, and decision state visible before work moves on.",[48,49,50,51],86,74,91,68,[53,54,55,56],"Samples","Expenses","Travel","PTO",[58,59,60],"Complete data","Policy check","Budget flag",[62,63,64,65,66,67,68],"Complete","Budget","Policy","Manager queue","Approved today","Finance review","Audit-ready",[],"en",{},{"title":73,"items":74},"What your teams gain from structured field force workflows",[75,78,81,84,87],{"title":76,"description":77},"Faster everyday requests","Samples, expenses, travel, and PTO requests move with less back-and-forth and clearer handoffs.",{"title":79,"description":80},"Cleaner request data","Managers receive complete operational context before approving, instead of chasing missing details.",{"title":82,"description":83},"Better operational visibility","Leaders can see request volume, budget utilization, and field operations activity across teams.",{"title":85,"description":86},"More auditable field workflows","Expenses, travel, samples, and leave decisions are captured with traceable data, comments, and outcomes.",{"title":88,"description":89},"Lower administrative friction","Field teams spend less time navigating administration, while management gains more control over daily operations.","\u002Fen\u002Fuse-cases\u002Fpharma-field-force-operations-approvals",[92,134,151,191],{"number":93,"title":94,"intro":95,"blocks":96},"01","Turn field force requests into structured forms","Capture the right operational details before requests reach approvers.",[97,112],{"title":98,"copy":99,"visual":100,"starterBrowser":109},"Customize REVO's pre-built forms","Start from REVO's starter forms for field force operations, then tailor fields, sections, and attachments to match your internal policies, without touching code.",{"variant":101,"label":102,"title":36,"metric":103,"detail":104,"bars":105,"checkpoints":106,"partners":107},"approval-flow","Starter category","4 ready-made starters","Samples, expenses, travel pre-approval, and PTO requests start with structured data.",[48,49,50,51],[53,54,55,56],[64,63,108],"Manager",{"source":110,"category":8,"showCategoryFilters":111},"revo-approval-workflows",false,{"title":113,"copy":114,"visual":115},"Or build your own from scratch","Design new field-force approval forms in minutes by defining what data to collect for each request type. Configure dynamic fields that appear only for specific selections or routes, so reps see exactly what they need to fill. Then configure closing forms to validate what actually happened and decide what should happen next, all through configuration, with no hardcoding or technical assistance required.",{"variant":116,"label":117,"title":118,"metric":119,"detail":120,"bars":121,"checkpoints":125,"partners":130},"form-builder","Dynamic form builder","Field request forms, routes, and closing checks","From blank form","Request-specific fields appear by type or route, then closing forms validate follow-up.",[122,50,123,124],82,67,76,[126,127,128,129],"Request type","Conditional fields","Route-specific checks","Closing form",[131,132,133],"Collect data","Route cleanly","Validate close",{"number":135,"title":136,"intro":137,"visual":138,"blocks":150},"02","Route to the right reviewers with complete context","Define approval sequences around the way your company works, without hardcoding every business process into custom software.",{"variant":101,"label":139,"title":140,"metric":141,"detail":142,"src":143,"alt":144,"width":145,"height":146,"bars":147},"Approval sequence builder","Flexible routing without hardcoding","Business rules","Conditional reviewers, parallel checks, and outcome paths stay configurable.","\u002Fplatform\u002Fapproval-sequence-screenshot-dark.png","Approval sequence configuration screenshot in REVO Approval Workflows",1612,980,[122,148,50,149],69,77,[],{"number":152,"title":153,"intro":154,"blocks":155},"03","Automate what happens after every decision","Standardize and accelerate how high-value approval requests move forward.",[156,172],{"title":157,"copy":158,"visual":159},"Outcome-based automation","Configure automations for any workflow and approval outcome. Approved, rejected, and changes-required decisions can each trigger different notifications, tasks, webhooks, and next steps.",{"label":160,"title":161,"metric":162,"detail":163,"src":164,"alt":165,"width":166,"height":167,"bars":168},"Decision automation","Approved, rejected, or changes required","Outcome triggers","Every decision starts the next action automatically","\u002Fplatform\u002Fpost-decision-automation-dark.png","Post-decision automation screenshot in REVO Approval Workflows",771,881,[51,169,170,171],84,59,92,{"title":173,"copy":174,"visual":175},"Downstream workflows and system updates","Approved requests can initiate updates in your ERP and CRM systems, dispatch email notifications to relevant stakeholders, and launch closing workflows to finalize logistics and documentation.",{"variant":101,"label":176,"title":177,"metric":178,"detail":179,"hideOutcome":7,"bars":180,"checkpoints":184,"partners":189},"Follow-up flow","Approval decisions move work forward","Automated next steps","ERP, CRM, email notifications, and closing workflows stay configurable.",[181,182,183,122],72,88,64,[185,186,187,188],"ERP","CRM","Email","Closing",[185,186,190],"Stakeholders",{"number":192,"title":193,"intro":194,"blocks":195},"04","Insights gained from adopting REVO Approval Workflows","Turn daily operational approvals into visibility on workload, spend, and recurring process friction.",[196,209,233],{"title":197,"copy":198,"visual":199},"Request volume and operational load by team member","See which reps, managers, or territories generate the highest volume of operational requests across samples, expenses, travel, and PTO. This helps management understand where operational load is concentrated and where approval activity may need better planning or support.",{"variant":200,"label":201,"title":202,"metric":203,"detail":204,"bars":205},"chart","Operational load","Request volume by team member","Workload view","Reps, managers, and territories ranked by approval activity.",[171,169,206,207,208],73,58,41,{"title":210,"copy":211,"visual":212},"Budget utilization across field operations","Track how budgets are being consumed across expense requests, travel approvals, and sample-related activity. This gives finance and managers a clearer picture of where operational spend is concentrated and how much budget remains available.",{"variant":213,"allocationOnly":7,"label":214,"title":215,"metric":216,"detail":217,"bars":218,"checkpoints":222,"partners":227,"allocationLabels":230},"event-investment","Budget discipline","Budget use across field operations","Spend view","Expense, travel, sample, and operational budgets stay visible for managers and finance.",[182,149,219,220,221],63,49,36,[223,224,225,226],"Used","Remaining","Concentrated","Follow-up",[108,228,229],"Finance","Operations",[54,55,53,231,232],"Meetings","Other ops",{"title":234,"copy":235,"visual":236},"Operational patterns and policy bottlenecks","Identify recurring friction points such as request types that are frequently delayed, routes that generate the most back-and-forth, or teams that repeatedly submit incomplete data. These insights help improve policy design, training, and workflow efficiency over time.",{"variant":101,"label":237,"title":238,"metric":239,"detail":240,"hideOutcome":7,"bars":241,"checkpoints":244,"partners":248},"Bottleneck signals","Delays and rework by workflow route","Friction map","Missing data, delayed routes, and policy exceptions become visible.",[242,183,48,243],78,52,[245,246,64,247],"Missing data","Rework","Delays",[108,228,249],"Ops",{"title":251,"description":252,"modules":253},"Where this use case fits in REVO","This Field Force Operations use case is powered by REVO Approval Workflows and can connect to CRM and Rx-Booster when operational activity needs more account or execution context.",[254,257,260],{"name":255,"description":256},"REVO Approval Workflows","Powers request intake, routing, automation, and audit trails for field force operations.",{"name":258,"description":259},"REVO CRM","Optional account, territory, or team context can be connected where field requests need customer or coverage visibility.",{"name":261,"description":262},"REVO Rx-Booster","Optional promotional workflows can link operational activity to commercial execution and rep performance.","Approval Workflows",0.8,{"title":266,"bullets":267,"summary":272},"Why field force operations create unnecessary friction",[268,269,270,271],"Field teams constantly submit operational requests, but many companies still manage them through email threads, chat messages, and disconnected files.","Missing details delay approvals for expenses, travel, samples, and leave, while managers spend too much time chasing context instead of making decisions.","Operational activity becomes difficult to audit, compare, and optimize when request data is inconsistent or buried across systems.","As request volume grows, the lack of structure affects both field productivity and management control.","Field operations should move quickly, but unmanaged request traffic turns daily work into scattered approvals, unclear budgets, and avoidable follow-up.",{"title":5,"description":33},"published","en\u002Fuse-cases\u002Fpharma-field-force-operations-approvals","aabYf0FzMOqdPZ0-FVTgQ7kfmhQlK-NAzW2IaxwGwVw",{"id":278,"title":255,"body":279,"canonicalSlug":110,"capabilities":283,"comparison":391,"cta":415,"description":422,"ecosystemFit":423,"extension":34,"faq":424,"hero":457,"legacyRedirects":617,"locale":70,"meta":618,"moduleName":255,"navigation":7,"path":619,"practice":620,"pricing":624,"priority":640,"productStory":423,"promptGuide":641,"roleValueStrip":423,"seo":654,"starters":655,"status":274,"stem":1090,"useCaseLinks":423,"__hash__":1091},"platformModules\u002Fen\u002Fplatform\u002Frevo-approval-workflows.md",{"type":10,"value":280,"toc":281},[],{"title":13,"searchDepth":14,"depth":14,"links":282},[],[284,299,316,335,351,374],{"id":285,"eyebrow":286,"title":287,"description":137,"bullets":288,"visual":289},"process-rules","Built for your processes, not ours.","Your process, your rules. Whatever rule you have, REVO Approval Workflows is designed to accommodate it.",[],{"variant":101,"label":139,"title":140,"metric":141,"detail":290,"src":143,"alt":144,"width":145,"height":146,"bars":291,"checkpoints":292,"partners":297},"Conditional reviewers, parallel checks, and outcome paths stay configurable",[122,148,50,149],[293,294,295,296],"Intake","Rules","Reviewers","Audit",[108,298,228],"Medical",{"id":300,"eyebrow":301,"title":302,"bullets":303,"visual":310},"decision-automation","Automate what happens next","Trigger emails, create tasks, update systems, launch follow-up workflows, or notify stakeholders automatically after every decision.",[304,305,306,307,308,309],"Configure automations for any workflow and approval outcome.","Trigger different actions for Approved, Rejected, Changes Required, and other outcomes.","Trigger another workflow automatically.","Notify users and stakeholders automatically through emails.","Connect REVO with third-party systems through webhooks.","Eliminate repetitive follow-up tasks and keep processes moving.",{"label":311,"title":312,"metric":162,"detail":313,"src":164,"alt":314,"width":166,"height":167,"bars":315},"Post-decision automation","Approved, rejected, changes required","Each decision launches the next action automatically","Post-decision automation configuration screenshot in REVO Approval Workflows",[51,169,170,171,124],{"id":317,"eyebrow":318,"title":319,"description":320,"bullets":321,"visual":322},"business-data","Complete the context","Approvals backed by real business data","Connect HCPs, HCOs, and products from your CRM to every request, reducing manual work while improving visibility into where time and budget are invested.",[],{"variant":200,"label":323,"title":324,"metric":325,"detail":326,"src":327,"alt":328,"width":329,"height":330,"bars":331},"Associated information","HCP, HCO, and product context attached","Live context","CRM-linked business data follows every request","\u002Fplatform\u002Fassociated-information-dark.png","Associated HCP, HCO, product, budget, and reference information screenshot in REVO Approval Workflows",843,301,[207,332,333,149,334],71,83,89,{"id":336,"eyebrow":337,"title":337,"description":338,"bullets":339,"visual":340},"organizational-knowledge","Turn every review into organizational knowledge","Enable reviewers to document observations, recommendations, and operational challenges alongside every decision. Over time, these insights help management identify recurring issues, improve processes, and make better operational decisions.",[],{"label":341,"title":342,"metric":343,"detail":344,"src":345,"alt":346,"width":347,"height":348,"bars":349},"Review notes","Recommendations and observations stay attached","Decision knowledge","Reviewer context becomes useful management insight over time","\u002Fplatform\u002Fnotes-dark.png","Reviewer notes and observations screenshot in REVO Approval Workflows",936,386,[49,122,183,50,350],79,{"id":352,"eyebrow":353,"title":353,"description":354,"bullets":355,"visual":356},"request-references","Connect every request to the bigger picture","Link approval requests together to create a complete business record - from the initial request to follow-up actions, supporting activities, and final outcomes. Preserve relationships between requests without losing context.",[],{"variant":101,"label":357,"title":358,"metric":359,"detail":360,"src":361,"alt":362,"width":363,"height":364,"bars":365,"checkpoints":366,"partners":370},"Request references","Linked approvals preserve business context","Connected record","Initial request, follow-up actions, and outcomes remain connected","\u002Fplatform\u002Freferencing-dark.png","Linked approval request references screenshot in REVO Approval Workflows",1762,302,[48,181,50,242],[367,368,226,369],"Initial","Support","Outcome",[371,372,373],"Request","Activity","Result",{"id":375,"eyebrow":376,"title":376,"description":377,"bullets":378,"visual":379},"financial-clarity","Approvals backed by financial clarity","Capture detailed cost items, calculate total investment automatically, and give approvers complete financial visibility before every decision. Validate budgets against configurable business rules on Enterprise plans.",[],{"variant":200,"label":380,"title":381,"metric":382,"detail":383,"src":384,"alt":385,"width":386,"height":387,"bars":388},"Cost calculation","Investment visibility before approval","Total cost view","Cost items, budget checks, and financial clarity before every decision","\u002Fplatform\u002Fcost-calculation-table-dark.png","Cost calculation table screenshot in REVO Approval Workflows",1864,694,[389,51,390,50,219],42,75,{"eyebrow":392,"title":393,"columns":394},"Where approvals get stuck, we create flow","Modern approvals, built for regulated businesses.",[395,405],{"title":396,"items":397},"The old way",[398,399,400,401,402,403,404],"Endless email chains","Missing information delays decisions","Rigid approval steps","Siloed approvals create compliance gaps","Manual follow-ups and reminders","Decisions are difficult to trace","Alien to life sciences",{"title":406,"items":407},"The REVO way",[408,409,410,411,412,413,414],"A focused personalized approval queue","Capture perfect data, every time","Flexible workflows tailored to your business","Connected workflows with complete business context","Automated routing and notifications","Complete audit trail for every approval","Built specifically for life sciences",{"eyebrow":416,"title":417,"description":418,"primaryCta":419,"secondaryCta":420},"Next step","See how REVO structures your approval workflows","In just 30 minutes, you will see how REVO Approval Workflows can replace email chains and spreadsheets with governed, auditable workflows for events, field force operations, commercial approvals, and medical review.",{"label":28,"href":29},{"label":421,"href":29},"Try before you buy","Build approval workflows without hardcoding business processes. Collect the right data, route requests to the right people, track every decision, and automate every next step.",null,{"title":425,"items":426},"Frequently Asked Questions",[427,433,437,441,445,449,453],{"question":428,"answer":429},"Why should I subscribe to REVO Approval Workflows?",[430,431,432],"Most organizations face the same trade-off: move approvals quickly with emails, chats, and spreadsheets while sacrificing control, or enforce strict processes that slow everyone down. REVO eliminates this compromise by combining speed with governance, allowing teams to move faster while ensuring every request follows the right process, captures the right information, and remains fully traceable.","Building and maintaining a custom approval system is another common approach, but it often requires significant development effort, ongoing maintenance, and costly changes whenever business processes evolve. REVO gives you the flexibility to design, modify, and automate approval workflows without hardcoding, helping your organization adapt in hours instead of development cycles.","Beyond managing approvals, REVO provides visibility into some of your organization's most important business activities and investments. Connect requests to HCPs, HCOs, products, budgets, events, and related business processes to gain a complete view of where resources are invested, how decisions are made, and how initiatives progress over time.",{"question":434,"answer":435},"Can REVO handle our approval process?",[436],"Yes. REVO is designed to support everything from simple single-step approvals to complex multi-stage workflows involving multiple departments, conditional routing, parallel approvals, business rules, and post-decision automation. You can start from scratch or customize our pharma-ready workflow starters.",{"question":438,"answer":439},"Can we customize forms and required information?",[440],"Absolutely. Every workflow can use fully customizable forms with dynamic fields, attachments, budget calculations, CRM-linked data, validation rules, and conditional visibility to capture exactly the information your reviewers need.",{"question":442,"answer":443},"Is REVO built specifically for life sciences?",[444],"Yes. REVO includes pharma-ready workflow starters and supports HCPs, HCOs, products, budgets, commercial approvals, medical reviews, compliance processes, congress approvals, sample requests, and many other life sciences use cases.",{"question":446,"answer":447},"How long does implementation take?",[448],"Most customers configure and deploy their first approval workflow within days - not months. More complex enterprise deployments are delivered collaboratively with our implementation team.",{"question":450,"answer":451},"Can we start small and expand later?",[452],"Absolutely. Many customers begin with a single approval process and gradually expand across departments using the same platform.",{"question":454,"answer":455},"Why is a 30-minute demo enough?",[456],"In just 30 minutes, you will see how REVO Approval Workflows solves what email chains cannot, improves approvals without adding friction, and puts your teams on the right track to move faster with control.",{"eyebrow":458,"title":459,"description":460,"primaryCta":461,"secondaryCta":464,"visual":467,"demo":478,"metrics":607},"Approval workflows for regulated teams","Build approval workflows without hardcoding your business processes.","Collect the right data - route requests to the right people - track every decision - and automate every next step.",{"label":462,"href":463},"Pricing plans","#pricing",{"label":465,"href":466},"Say goodbye to email chains","#comparison",{"variant":101,"label":468,"title":469,"metric":470,"detail":471,"bars":472,"checkpoints":473,"partners":476},"Approval command center","Request, review, approve, automate, audit","Structured request","Routed with context, policy checks, and traceable decisions",[171,49,169,123],[371,474,475,296],"Review","Approve",[298,477,228],"Compliance",{"eyebrow":479,"title":480,"description":481,"stages":482,"form":497,"review":528,"changes":557,"approvals":572,"automation":582,"closing":599},"Low-fidelity workflow demo","An event request moves from form to approval to automated closure.","The storyboard shows one structured request being submitted, reviewed with comments, approved, automated, and handed into a closing flow.",[483,486,488,491,494],{"id":484,"label":485},"form","Form",{"id":487,"label":474},"review",{"id":489,"label":490},"changes","Changes",{"id":492,"label":493},"approvals","Approvals",{"id":495,"label":496},"automation","Automation",{"title":498,"status":499,"submitLabel":500,"doctorDropdown":501,"fields":513},"Event sponsorship request","Ready to submit","Submit request",{"label":502,"placeholder":503,"selectedLabel":504,"options":505,"selected":510},"Add doctors","Select HCPs for the event","doctors selected",[506,507,508,509],"Dr. Lina Hassan - Cardiology","Dr. Karim Youssef - Internal medicine","Dr. Maya Nader - Endocrinology","Dr. Omar Adel - Hospital pharmacy",[511,512],"Dr. Lina Hassan","Dr. Karim Youssef",[514,517,520,522,525],{"label":515,"value":516},"Event","Regional cardiology roundtable",{"label":518,"value":519},"Organizer","Nile Medical Association",{"label":63,"value":521},"USD 18,500",{"label":523,"value":524},"Event date","12 Sep 2026",{"label":526,"value":527},"Attachments","Agenda + venue quote",{"title":529,"commentLabel":530,"changesRequiredLabel":531,"steps":532},"Inline review cycle","Reviewer comment","Changes required",[533,538,542,547,551,554],{"name":534,"role":535,"state":536,"detail":537},"Requester","Brand manager","Submitted","Event form completed with budget, HCO, agenda, and expected audience.",{"name":108,"role":539,"state":540,"detail":541},"Commercial lead","Approved","Budget and business rationale match the quarterly plan.",{"name":477,"role":543,"state":544,"detail":545,"comment":546},"Policy reviewer","Comment added","Needs more context before final approval.","Add the HCP audience split and invitation language.",{"name":534,"role":548,"state":549,"detail":550},"Form owner","Comment resolved","Audience split attached and invitation language updated.",{"name":298,"role":552,"state":540,"detail":553},"Medical reviewer","Scientific objective and agenda are aligned.",{"name":228,"role":555,"state":540,"detail":556},"Spend approver","PO threshold checked and spend owner confirmed.",{"title":558,"description":559,"resolveLabel":560,"resubmitLabel":561,"changedFields":562},"Requester resolves requested changes","The requester updates the event audience details, attaches the revised invitation language, resolves the reviewer comment, and resubmits the request.","Resolve comment","Resubmit request",[563,566,569],{"label":564,"value":565},"HCP audience split","42 cardiologists, 18 internal medicine, 10 hospital pharmacy",{"label":567,"value":568},"Invitation language","Updated with scientific objective and no promotional claims",{"label":570,"value":571},"Additional attachment","Revised invitation draft",{"title":573,"finalLabel":574,"steps":575},"Serial approvals","Final approved",[576,578,580,581],{"name":108,"role":539,"state":540,"detail":577},"Budget and business rationale approved.",{"name":477,"role":543,"state":540,"detail":579},"Comment resolved and invitation language accepted.",{"name":298,"role":552,"state":540,"detail":553},{"name":228,"role":555,"state":540,"detail":556},{"title":178,"events":583},[584,588,591,595],{"label":585,"detail":586,"status":587},"Email sent","Requester and reviewers receive the approved decision.","Done",{"label":589,"detail":590,"status":587},"Signal sent to ERP","Approval ID, budget, and vendor details are sent to ERP.",{"label":592,"detail":593,"status":594},"Vendor task created","Contract and payment checklist opens for operations.","Running",{"label":596,"detail":597,"status":598},"Closing flow started","Evidence collection and final reconciliation are queued.","Next",{"title":600,"description":601,"steps":602},"Closing flow","Approval completion becomes the starting point for post-event evidence, reconciliation, and audit readiness.",[603,604,605,606],"Confirmation email","Evidence checklist","Spend reconciliation","Audit trail locked",[608,611,614],{"label":609,"value":610},"Workflows","Flexible",{"label":612,"value":613},"Decisions","Auditable",{"label":615,"value":616},"Next steps","Automated",[],{},"\u002Fen\u002Fplatform\u002Frevo-approval-workflows",{"flow":621},[371,474,475,622,623],"Automate","Audit trail",{"eyebrow":625,"title":626,"userQuestion":627,"defaultUsers":628,"setupNote":629,"annualNote":630,"contactCta":631,"labels":633},"Seamless pricing that reflects value","Pricing","How many users do you intend to use this system from your end?",50,"Setup fees apply to all plans.","When paid annually",{"label":632,"href":29},"Contact us",{"workflows":634,"forms":635,"attachments":636,"perUserMonthly":637,"custom":632,"estimatedMonthly":638,"included":639},"Approval workflows","Customizable data forms","Attachments limit","\u002Fuser\u002Fmo","Estimated monthly total","Included capabilities",0.9,{"title":642,"description":643,"copyCta":644,"copiedLabel":645,"copyFailedLabel":646,"prompt":647,"questionsLabel":648,"questions":649},"Do you want to use ChatGPT or any similar tool to know more about REVO Approval Workflows?","We have prepared a ready-to-use prompt packed with key details about REVO Approval Workflows. Hit Copy Prompt, paste it into ChatGPT, and start asking questions to discover how the platform works and how it can help your business.","Copy ChatGPT prompt","Prompt copied. You can now paste it into ChatGPT.","Clipboard access was blocked. Try again after allowing clipboard access in your browser.","You are ChatGPT, and I want you to help me understand REVO Approval Workflows - a platform built specifically for Pharma and Life Sciences companies to manage compliant, audit-ready approval cycles.\n\nExplain how REVO's Approval Workflow Engine helps teams move away from the old way of endless email approvals, rigid processes, and compliance gaps, and towards a smarter, AI-assisted, fully configurable approval experience.\n\nHighlight how REVO:\n- Builds fluid, GxP-compliant approval workflows that adapt to any process (expenses, samples, events, vacations, orders, etc.)\n- Offers unmatched flexibility and customization without needing custom ERPs\n- Provides one unified system for all approvals - simple, smart, and ERP-free\n- Includes a dynamic form engine that captures perfect data every time\n- Connects related workflows and integrates with CRMs for full context\n- Assists approvers with AI and ensures every decision is tracked and compliant\n\nKeep the explanation clear, engaging, and easy for someone in pharma or life sciences to understand why REVO is the better, modern way to manage approvals.\n\nThen, answer the following FAQs:\n\n1. What makes REVO Approval Workflows different from generic workflow tools?\n\n2. What's meant by approval workflow?\nIt is the sequence of approval steps defined for a specific use case, task, or document within your company's approval process.\n\n3. What constitutes a form in the system?\nRepresents the data required by your company's process to approve a specific task.\n\n4. What are nested forms?\nIf your process requires collecting specific types of data - for example, a hotel reservation linked to a meeting request - you can nest multiple forms under one approval flow.\nThis allows approvers to review and act on related requests within the same approval instance - approving both, or approving one and rejecting another.\nThe result: a streamlined, trackable approval process that keeps every related decision connected and easy to manage.\n\n5. What should I do if I reach my document storage limit?\nYou can upgrade to the next plan or contact your dedicated customer service agent to request additional quota for a small fee. Please note that terms and conditions may apply.\n\n6. Can I delete\u002Fupdate current forms?\nForms can be edited or deleted only if they have no submissions.\nOnce a form has at least one submission linked to an approval, it can no longer be modified or deleted - ensuring data consistency and compliance.\nAny updates made after that point will create a new form version, which will count toward your form quota.\n\n7. Do you offer further customization if I need to?\nAbsolutely - we can tailor the platform to fit your company's specific processes. Please note that customizations may incur additional fees and are subject to terms and conditions.\n\n8. How does REVO help teams move faster without sacrificing control?\n\n9. Can approval processes be customized per department or region?\n\n10. What role does AI play in assisting approvers?\n\n11. How can companies get started with REVO Approval Workflows?\n","Questions examples",[650,651,652,653],"I don't know if my team needs this service, can you help me with this?","How is REVO Workflows different from other services like Veeva?","How is REVO Workflows better than emails?","Why is REVO Workflows good value for money?",{"title":255,"description":422},{"eyebrow":656,"title":657,"description":658,"categories":659,"labels":673,"items":686},"Build your own process","The flexibility to build. The speed to start.","Create completely from scratch or customize our pharma-ready starters to match your business processes.",[660,663,666,667,670],{"id":661,"label":662},"hcp","Events & HCP Engagements",{"id":664,"label":665},"grant","Grants and Sponsorships",{"id":8,"label":36},{"id":668,"label":669},"sales","Sales and Commercial",{"id":671,"label":672},"medical","Medical and Scientific Content",{"fields":674,"attachments":526,"standardData":675,"useCase":676,"complianceLens":677,"recommended":678,"all":679,"empty":680,"overview":681,"close":682,"viewDetails":683,"required":684,"none":685},"Fields","Suggested standard data","Use case","Compliance lens","Recommended","All","No starters match this view.","Overview","Close starter details","View starter details","Required","None specified",[687,729,763,791,821,849,881,909,935,965,996,1027,1055],{"id":688,"category":661,"recommended":7,"title":689,"description":690,"useCase":691,"complianceLens":692,"tags":693,"standardData":698,"attachments":701,"fields":706},"congress","Scientific Meeting \u002F Congress Sponsorship","Capture congress sponsorship scope, HCO organizer details, benefits, budget, and supporting documents.","Use when a team proposes sponsorship of a symposium, booth, satellite session, or similar HCO-led scientific engagement.","Surfaces sponsorship benefits, audience, budget, and documentation needed for medical, compliance, and finance review.",[694,695,696,697],"HCP","HCO","Congress","Sponsorship",[699,700,63],"Product","HCPs",[702,703,704,705],"Agenda","Invitation","Sponsorship contract","Benefit package",[707,710,712,714,718,721,724,726],{"name":708,"type":709,"required":7},"Event name","TEXT",{"name":523,"type":711,"required":7},"DATE",{"name":713,"type":709,"required":7},"Organizer \u002F HCO",{"name":715,"type":716,"required":7,"note":717},"Engagement type","DROPDOWN","Symposium, Booth, Satellite session, Congress sponsorship",{"name":719,"type":720,"required":7},"Sponsorship benefits","RICH_TEXT",{"name":722,"type":723,"required":7},"Sponsorship budget","COST_CALCULATOR",{"name":725,"type":720,"required":7},"Business and scientific rationale",{"name":727,"type":728,"required":111},"Supporting documents","MULTI_ATTACHMENT",{"id":730,"category":661,"recommended":7,"title":731,"description":732,"useCase":733,"complianceLens":734,"tags":735,"standardData":739,"attachments":740,"fields":744},"speaker","Speaker Program Request","Structure HCP speaker programs with topic, rationale, honoraria, audience, format, and required attachments.","Use when a brand, medical, or field team wants to run an educational speaker program for HCP audiences.","Highlights speaker rationale, honoraria, audience, materials, and repetition count for review.",[694,736,737,738],"Speaker","Honoraria","Program",[699,700,63],[741,742,743],"Draft slide deck","Speaker CV","Speaker contract",[745,747,749,751,753,756,759,761],{"name":746,"type":709,"required":7},"Program topic",{"name":748,"type":709,"required":7},"Disease area",{"name":750,"type":709,"required":7},"Proposed speaker name",{"name":752,"type":720,"required":7},"Speaker rationale",{"name":754,"type":755,"required":7},"Proposed honoraria","COST_ITEM",{"name":757,"type":716,"required":7,"note":758},"Program format","In-person, Virtual, Hybrid",{"name":760,"type":720,"required":7},"Educational objective",{"name":762,"type":728,"required":111},"Program materials and contracts",{"id":764,"category":661,"recommended":111,"title":765,"description":766,"useCase":767,"complianceLens":768,"tags":769,"standardData":772,"attachments":773,"fields":777},"advisory","Advisory Board \u002F Consultancy Meeting","Collect advisory objectives, advisor selection criteria, meeting logistics, and compensation details.","Use when feedback from selected HCP advisors is needed for medical, scientific, or strategic objectives.","Encourages documentation of legitimate need, advisor selection, compensation, and meeting logistics.",[770,771,694,298],"Advisory board","Consultancy",[699,700,63],[774,702,775,776],"Advisor list","Briefing materials","Consulting agreement",[778,780,782,784,786,788,790],{"name":779,"type":720,"required":7},"Advisory objective",{"name":781,"type":720,"required":7},"Advisor selection criteria",{"name":783,"type":716,"required":7,"note":758},"Meeting format",{"name":785,"type":711,"required":7},"Meeting date",{"name":787,"type":723,"required":7},"Compensation details",{"name":789,"type":720,"required":7},"Expected outputs",{"name":727,"type":728,"required":111},{"id":664,"category":664,"recommended":7,"title":792,"description":793,"useCase":794,"complianceLens":795,"tags":796,"standardData":799,"attachments":800,"fields":805},"Educational Grant to HCO","Review educational grants with HCO details, purpose, independence checks, amount, and documentation.","Use when an HCO requests funding or support for an independent medical education activity.","Separates educational purpose, independence confirmation, requested amount, and required evidence.",[797,695,798,697],"Grant","Education",[699,63],[801,802,803,804],"Grant request letter","Program agenda","Budget breakdown","HCO credentials",[806,808,810,812,814,816,820],{"name":807,"type":709,"required":7},"Requesting HCO",{"name":809,"type":720,"required":7},"Grant purpose",{"name":811,"type":709,"required":7},"Educational activity title",{"name":813,"type":755,"required":7},"Requested amount",{"name":815,"type":720,"required":7},"Expected outcomes",{"name":817,"type":818,"required":7,"note":819},"Independence confirmation","RADIO","Confirmed, Needs review",{"name":727,"type":728,"required":111},{"id":822,"category":8,"recommended":111,"title":823,"description":824,"useCase":825,"complianceLens":826,"tags":827,"standardData":829,"attachments":830,"fields":833},"samples","HCP Samples Request","Capture sample quantity, recipient details, medical justification, delivery need, and reconciliation checks.","Use when a field team requests product samples for legitimate HCP or HCO interactions.","Focuses on product, quantity, recipient, medical justification, and prior reconciliation status.",[53,694,828],"Field force",[699,700],[831,832],"Sample request support","Prior reconciliation evidence",[834,836,839,841,843,845,848],{"name":835,"type":709,"required":7},"Sample product",{"name":837,"type":838,"required":7},"Requested quantity","NUMBER",{"name":840,"type":709,"required":7},"Recipient HCP \u002F HCO",{"name":842,"type":720,"required":7},"Medical justification",{"name":844,"type":711,"required":7},"Requested delivery date",{"name":846,"type":818,"required":7,"note":847},"Prior samples reconciled?","Yes, No, Not applicable",{"name":727,"type":728,"required":111},{"id":850,"category":8,"recommended":7,"title":851,"description":852,"useCase":853,"complianceLens":854,"tags":855,"standardData":856,"attachments":857,"fields":861},"expense","Field Force Expense Request","Collect trip, meal, hotel, taxi, event fee, and HCP\u002FHCO-related expense details with policy confirmations.","Use for expenses that need manager, finance, or compliance visibility.","Includes HCP\u002FHCO involvement and hospitality policy confirmations to reduce back-and-forth.",[54,55,694,228],[700,63],[858,859,860],"Receipts","Invoices","Event confirmations",[862,865,867,869,871,874,876,879],{"name":863,"type":716,"required":7,"note":864},"Expense name","Trip, Travel, Hotel, Meal, Event fee",{"name":866,"type":711,"required":7},"Start date",{"name":868,"type":711,"required":7},"End date",{"name":870,"type":723,"required":7},"Expense line items",{"name":872,"type":818,"required":7,"note":873},"Payment method","Company card, Out-of-pocket",{"name":875,"type":720,"required":7},"Business purpose",{"name":877,"type":818,"required":7,"note":878},"HCP\u002FHCO involvement?","No, Yes",{"name":880,"type":728,"required":7},"Receipts and invoices",{"id":882,"category":8,"recommended":111,"title":883,"description":884,"useCase":885,"complianceLens":886,"tags":887,"standardData":889,"attachments":890,"fields":894},"travel","Travel Pre-Approval","Request travel approval with itinerary, estimated costs, linked events, and business justification.","Use before employees book travel for congresses, internal meetings, customer visits, or field activities.","Prompts for objective, itinerary, cost estimate, and event or HCP\u002FHCO linkage.",[55,888,828],"Pre-approval",[700,63],[891,892,893],"Itinerary","Event invitation","Estimated booking quote",[895,897,899,901,903,904,906,908],{"name":896,"type":709,"required":7},"Trip purpose",{"name":898,"type":711,"required":7},"Travel start date",{"name":900,"type":711,"required":7},"Travel end date",{"name":902,"type":709,"required":7},"Destination",{"name":891,"type":720,"required":7},{"name":905,"type":723,"required":7},"Estimated costs",{"name":907,"type":818,"required":7,"note":878},"Travel policy exception?",{"name":727,"type":728,"required":111},{"id":910,"category":8,"recommended":111,"title":911,"description":912,"useCase":913,"complianceLens":914,"tags":915,"standardData":917,"attachments":918,"fields":920},"pto","Field Force Vacation \u002F PTO Request","Collect leave dates, leave type, working days, coverage plan, and impact on visits or events.","Use when field employees request vacation, sick leave, personal leave, unpaid leave, or other PTO.","Operational starter focused on coverage and continuity of planned customer-facing activity.",[56,916,229],"Vacation",[],[919],"Medical certificate if required",[921,924,925,926,928,930,932],{"name":922,"type":716,"required":7,"note":923},"Leave type","Vacation, Sick leave, Personal leave, Unpaid leave",{"name":866,"type":711,"required":7},{"name":868,"type":711,"required":7},{"name":927,"type":838,"required":7},"Total working days",{"name":929,"type":709,"required":7},"Coverage owner",{"name":931,"type":720,"required":7},"Coverage plan",{"name":933,"type":934,"required":111},"Supporting document","SINGLE_ATTACHMENT",{"id":936,"category":668,"recommended":111,"title":937,"description":938,"useCase":939,"complianceLens":940,"tags":941,"standardData":945,"attachments":946,"fields":950},"order","Standard Sales Order","Capture customer, channel, product lines, volumes, payment terms, credit, and delivery requirements.","Use for standard orders from hospitals, wholesalers, pharmacies, or other commercial customers.","Structures commercial order data without adding workflow assumptions.",[942,943,944],"Sales order","Customer","Commercial",[699,63],[947,948,949],"Purchase order","Customer confirmation","Commercial terms",[951,953,956,958,960,962,964],{"name":952,"type":709,"required":7},"Customer name",{"name":954,"type":716,"required":7,"note":955},"Customer channel","Hospital, Wholesaler, Pharmacy, Distributor",{"name":957,"type":720,"required":7},"Product lines",{"name":959,"type":838,"required":7},"Indicative volumes",{"name":961,"type":716,"required":7},"Requested payment terms",{"name":963,"type":720,"required":7},"Delivery terms",{"name":727,"type":728,"required":111},{"id":966,"category":668,"recommended":7,"title":967,"description":968,"useCase":969,"complianceLens":970,"tags":971,"standardData":975,"attachments":976,"fields":980},"discount","Discount \u002F Rebate \u002F Free Goods Approval","Review price reductions with type, basis, structure, duration, volume, and rationale.","Use when a team proposes a discount, rebate, bundle, or free goods arrangement.","Prompts for commercial basis, duration, structure, and documentation to support pricing review.",[972,973,974,626],"Discount","Rebate","Free goods",[699,63],[977,978,979],"Pricing model","Customer request","Contract excerpt",[981,983,985,987,989,991,993,995],{"name":982,"type":716,"required":7},"Price reduction type",{"name":984,"type":716,"required":7},"Basis for request",{"name":986,"type":709,"required":7},"Customer \u002F account",{"name":988,"type":720,"required":7},"Covered products",{"name":990,"type":720,"required":7},"Discount structure",{"name":992,"type":711,"required":7},"Effective dates",{"name":994,"type":720,"required":7},"Commercial rationale",{"name":727,"type":728,"required":111},{"id":997,"category":668,"recommended":7,"title":998,"description":999,"useCase":1000,"complianceLens":1001,"tags":1002,"standardData":1006,"attachments":1007,"fields":1012},"tender","Tender \u002F Bid Approval","Prepare tender approvals with buyer, product lines, bid price, volumes, compliance checks, and documentation.","Use before submitting tenders to ministries, hospital systems, public buyers, or large accounts.","Makes eligibility, licenses, bid pricing, volumes, and documentation completeness visible before submission.",[1003,1004,626,1005],"Tender","Bid","Public sector",[699,63],[1008,1009,1010,1011],"Tender package","Pricing sheet","License documents","Submission checklist",[1013,1015,1017,1019,1020,1022,1025],{"name":1014,"type":709,"required":7},"Tender identifier",{"name":1016,"type":709,"required":7},"Buyer \u002F issuing authority",{"name":1018,"type":711,"required":7},"Submission deadline",{"name":957,"type":720,"required":7},{"name":1021,"type":723,"required":7},"Bid price details",{"name":1023,"type":818,"required":7,"note":1024},"Eligibility confirmed?","Yes, No, Needs review",{"name":1026,"type":728,"required":7},"Tender documents",{"id":1028,"category":668,"recommended":111,"title":1029,"description":1030,"useCase":1031,"complianceLens":1032,"tags":1033,"standardData":1037,"attachments":1038,"fields":1042},"contract","Commercial Contract \u002F Framework Agreement","Capture contract type, products, territory, financial model, term, reporting, and data obligations.","Use for frameworks, risk-sharing arrangements, capitation models, or other structured commercial agreements.","Separates scope, financial model, data requirements, reporting obligations, and termination details.",[1034,1035,944,1036],"Contract","Framework","Risk-sharing",[699,63],[1039,1040,1041],"Draft contract","Financial model","Legal comments",[1043,1045,1047,1048,1050,1051,1053],{"name":1044,"type":716,"required":7},"Contract type",{"name":1046,"type":709,"required":7},"Counterparty",{"name":988,"type":720,"required":7},{"name":1049,"type":720,"required":7},"Territories \u002F accounts",{"name":1040,"type":720,"required":7},{"name":1052,"type":711,"required":7},"Term dates",{"name":1054,"type":728,"required":7},"Contract documents",{"id":1056,"category":671,"recommended":7,"title":1057,"description":1058,"useCase":1059,"complianceLens":1060,"tags":1061,"standardData":1066,"attachments":1067,"fields":1071},"content","Promotional Content Review","Review promotional materials with claims, audience, channel, references, markets, and content files.","Use for campaign materials, digital content, field force aids, email, web, social, and similar promotional assets.","Prompts requesters to provide claims, references, audience, markets, channels, and source files upfront.",[1062,1063,1064,1065],"Promotional content","MLR","Digital","Campaign",[699],[1068,1069,1070],"Content files","Reference pack","Previous approval if applicable",[1072,1074,1076,1079,1081,1083,1085,1088],{"name":1073,"type":709,"required":7},"Content title",{"name":1075,"type":716,"required":7},"Material type",{"name":1077,"type":716,"required":7,"note":1078},"Intended audience","HCP, Patient, Public, Internal, Payer",{"name":1080,"type":716,"required":7},"Channel",{"name":1082,"type":720,"required":7},"Claims summary",{"name":1084,"type":720,"required":7},"Reference summary",{"name":1086,"type":1087,"required":111},"Previous approval reference","WORKFLOW_REFERENCE",{"name":1089,"type":728,"required":7},"Content files and references","en\u002Fplatform\u002Frevo-approval-workflows","vVYqTBF_u10EAzWWeTfxTxJzQ8DTYgTNUtzCVc7ZYKg",1784733015243]