{"id":3997,"date":"2026-05-29T19:32:23","date_gmt":"2026-05-29T19:32:23","guid":{"rendered":"https:\/\/aaxonix.com\/resources\/?post_type=glossary&#038;p=3997"},"modified":"2026-05-29T19:36:43","modified_gmt":"2026-05-29T19:36:43","slug":"blueprint","status":"publish","type":"glossary","link":"https:\/\/aaxonix.com\/resources\/glossary\/blueprint\/","title":{"rendered":"Blueprint"},"content":{"rendered":"<style>\n.gt-body { font-family:'Poppins',sans-serif; color:#111; line-height:1.75; }\n.gt-def { border-left:4px solid #E8650A; padding:16px 20px; background:#fff8f4; border-radius:0 8px 8px 0; margin:0 0 32px; font-size:1.05rem; }\n.gt-section { margin:0 0 36px; }\n.gt-section h2 { font-family:'Fraunces',serif; color:#0A1628; font-size:1.5rem; margin:0 0 12px; }\n.gt-section p { margin:0 0 12px; }\n.gt-example-box { background:#f0f4ff; border-radius:10px; padding:20px 24px; margin:0 0 32px; }\n.gt-example-box strong { color:#2563EB; }\n.gt-related-pills { display:flex; flex-wrap:wrap; gap:10px; margin:0 0 32px; }\n.gt-related-pill { background:#f7f4ef; border:1px solid #ddd8cf; border-radius:20px; padding:6px 16px; font-size:0.875rem; color:#0A1628; text-decoration:none; transition:all .2s; }\n.gt-related-pill:hover { background:#0A1628; color:#fff; border-color:#0A1628; }\n.gt-see-also { margin:0 0 32px; }\n.gt-see-also-item { border-bottom:1px solid #ddd8cf; padding:12px 0; }\n.gt-see-also-item:last-child { border-bottom:none; }\n.gt-see-also-item a { font-weight:600; color:#2563EB; text-decoration:none; }\n.gt-see-also-item p { margin:4px 0 0; font-size:0.875rem; color:#68605a; }\n.gt-faq { margin:0 0 40px; }\n.gt-faq-item { border:1px solid #ddd8cf; border-radius:10px; padding:16px 20px; margin:0 0 12px; }\n.gt-faq-item h3 { font-size:1rem; color:#0A1628; margin:0 0 8px; }\n.gt-faq-item p { margin:0; font-size:0.9rem; color:#444; }\n<\/style>\n<div class=\"gt-body\">\n<div class=\"gt-def\">\nBlueprint in Zoho CRM is a process automation feature that enforces a structured, stage-by-stage workflow for moving records through a defined business process. Unlike Workflow Rules which run silently in the background, Blueprint requires users to actively transition records between stages and can mandate that specific fields are filled and conditions are met before a transition is allowed.\n<\/div>\n<div class=\"gt-section\">\n<h2>How Blueprint Works<\/h2>\n<p>A Blueprint is built on a canvas where you define <a href=\"https:\/\/aaxonix.com\/resources\/glossary\/blueprint-state\/\" class=\"sp-content-link\">States<\/a> (stages a record can be in) and <a href=\"https:\/\/aaxonix.com\/resources\/glossary\/blueprint-transition\/\" class=\"sp-content-link\">Transitions<\/a> (the actions that move a record from one state to the next). Each transition can have: <a href=\"https:\/\/aaxonix.com\/resources\/glossary\/blueprint-field-mandate\/\" class=\"sp-content-link\">Field Mandates<\/a> (required fields before transitioning), <a href=\"https:\/\/aaxonix.com\/resources\/glossary\/blueprint-before-action\/\" class=\"sp-content-link\">Before Actions<\/a> (actions that run before the transition saves), <a href=\"https:\/\/aaxonix.com\/resources\/glossary\/blueprint-after-action\/\" class=\"sp-content-link\">After Actions<\/a> (actions that run after the transition saves), and <a href=\"https:\/\/aaxonix.com\/resources\/glossary\/blueprint-sla\/\" class=\"sp-content-link\">SLAs<\/a> (time limits for completing the transition).<\/p>\n<p>When a Blueprint is active on a module, users see a visual progress bar showing the current state and available transitions. They click a transition button, fill any mandated fields, and then confirm  &#8211;  the record moves to the next state and all configured actions fire.<\/p>\n<\/div>\n<div class=\"gt-section\">\n<h2>Blueprint vs Workflow Rules<\/h2>\n<p><a href=\"https:\/\/aaxonix.com\/resources\/glossary\/workflow-rule\/\" class=\"sp-content-link\">Workflow Rules<\/a> automate background actions  &#8211;  they run invisibly. Blueprint automates and enforces a human-driven process  &#8211;  it controls what users can and cannot do at each stage. Blueprint is ideal for processes that need auditability, mandatory data collection, and user accountability at each step. Workflow Rules are better for background automation that does not require user interaction.<\/p>\n<\/div>\n<div class=\"gt-section\">\n<h2>Industry Example<\/h2>\n<div class=\"gt-example-box\"><strong>Insurance:<\/strong> An insurance company uses Blueprint on their Deals module to enforce a claims approval process. Each state represents a step in the process: &#8220;Submitted&#8221;, &#8220;Under Review&#8221;, &#8220;Document Verification&#8221;, &#8220;Approved&#8221;, &#8220;Disbursed&#8221;. A transition from &#8220;Document Verification&#8221; to &#8220;Approved&#8221; mandates that the assessor fills in the &#8220;Verified Amount&#8221; and &#8220;Risk Score&#8221; fields. An SLA ensures the assessor completes this within 24 hours or the manager is notified.<\/div>\n<\/div>\n<div class=\"gt-section\">\n<h2>Related Terms<\/h2>\n<div class=\"gt-related-pills\">\n<a href=\"https:\/\/aaxonix.com\/resources\/glossary\/blueprint-state\/\" class=\"sp-content-link gt-related-pill\">Blueprint State<\/a><br \/>\n<a href=\"https:\/\/aaxonix.com\/resources\/glossary\/blueprint-transition\/\" class=\"sp-content-link gt-related-pill\">Blueprint Transition<\/a><br \/>\n<a href=\"https:\/\/aaxonix.com\/resources\/glossary\/blueprint-field-mandate\/\" class=\"sp-content-link gt-related-pill\">Blueprint Field Mandate<\/a><br \/>\n<a href=\"https:\/\/aaxonix.com\/resources\/glossary\/blueprint-before-action\/\" class=\"sp-content-link gt-related-pill\">Blueprint Before Action<\/a><br \/>\n<a href=\"https:\/\/aaxonix.com\/resources\/glossary\/blueprint-after-action\/\" class=\"sp-content-link gt-related-pill\">Blueprint After Action<\/a><br \/>\n<a href=\"https:\/\/aaxonix.com\/resources\/glossary\/blueprint-sla\/\" class=\"sp-content-link gt-related-pill\">Blueprint SLA<\/a><br \/>\n<a href=\"https:\/\/aaxonix.com\/resources\/glossary\/workflow-rule\/\" class=\"sp-content-link gt-related-pill\">Workflow Rule<\/a><br \/>\n<a href=\"https:\/\/aaxonix.com\/resources\/glossary\/approval-process\/\" class=\"sp-content-link gt-related-pill\">Approval Process<\/a><br \/>\n<a href=\"https:\/\/aaxonix.com\/resources\/glossary\/commandcenter\/\" class=\"sp-content-link gt-related-pill\">CommandCenter<\/a><\/p>\n<\/div>\n<\/div>\n<div class=\"gt-section gt-faq\">\n<h2>Frequently Asked Questions<\/h2>\n<div class=\"gt-faq-item\">\n<h3>What is Blueprint in Zoho CRM?<\/h3>\n<p>Blueprint is a process automation feature in Zoho CRM that enforces a structured workflow for records. It defines states (stages) and transitions (actions to move between stages), and can mandate that specific fields are filled and conditions are met before a record can progress. It ensures process compliance and captures a complete audit trail.<\/p>\n<\/div>\n<div class=\"gt-faq-item\">\n<h3>What is the difference between Blueprint and Workflow Rules in Zoho CRM?<\/h3>\n<p>Workflow Rules run automatically in the background when trigger conditions are met. Blueprint requires active user participation  &#8211;  users see available transitions, fill mandatory fields, and confirm the move. Blueprint is for process control; Workflow Rules are for background automation.<\/p>\n<\/div>\n<div class=\"gt-faq-item\">\n<h3>Can Blueprint work on custom modules in Zoho CRM?<\/h3>\n<p>Yes. Blueprint can be applied to any standard or custom module in Zoho CRM, provided the module has a pick-list field designated as the Blueprint field to track states.<\/p>\n<\/div>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>Blueprint in Zoho CRM is a process automation feature that enforces a structured, stage-by-stage workflow for moving records through a defined business\u2026<\/p>\n","protected":false},"template":"","meta":{"seo_title":"Blueprint | Zoho Glossary","seo_description":"Blueprint in Zoho CRM is a process automation feature that enforces a structured, stage-by-stage workflow for moving records through a defined business pro","seo_keyword":"blueprint","seo_faqs":"[{\"q\": \"What is Blueprint in Zoho CRM?\", \"a\": \"Blueprint is a process automation feature in Zoho CRM that enforces a structured workflow for records. It defines states (stages) and transitions (actions to move between stages), and can mandate that specific fields are filled and conditions are met before a record can progress. It ensures process compliance and captures a complete audit trail.\"}, {\"q\": \"What is the difference between Blueprint and Workflow Rules in Zoho CRM?\", \"a\": \"Workflow Rules run automatically in the background when trigger conditions are met. Blueprint requires active user participation \u2014 users see available transitions, fill mandatory fields, and confirm the move. Blueprint is for process control; Workflow Rules are for background automation.\"}, {\"q\": \"Can Blueprint work on custom modules in Zoho CRM?\", \"a\": \"Yes. Blueprint can be applied to any standard or custom module in Zoho CRM, provided the module has a pick-list field designated as the Blueprint field to track states.\"}]","term_type":"Technical","glossary_related":"","glossary_links":""},"glossary_category":[1238],"class_list":["post-3997","glossary","type-glossary","status-publish","hentry","glossary_category-zoho-crm"],"_links":{"self":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/glossary\/3997","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/glossary"}],"about":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/types\/glossary"}],"wp:attachment":[{"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/media?parent=3997"}],"wp:term":[{"taxonomy":"glossary_category","embeddable":true,"href":"https:\/\/aaxonix.com\/resources\/wp-json\/wp\/v2\/glossary_category?post=3997"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}