Sample workflow assessment
Northstar Facilities Services — Quote-to-Cash
An illustrative consultant-led assessment showing how WorkflowMD supports the diagnosis of an operational workflow and helps structure the improvement journey — what is wrong, why, what should change and in what order.
Illustrative assessment · Fictional company · No customer results or performance claims
- Workflow assessed
- Quote-to-Cash
- Assessment type
- Initial workflow diagnosis
- Purpose
- Identify operational issues, structure recommendations and determine an appropriate improvement sequence
Attribution disclosure
Prepared using WorkflowMD. Sections identified as Consultant analysis are additions made by the consultant during review and are not presented as native WorkflowMD output.
01 — Executive assessment
Information and responsibility are not controlled across handoffs
Current situation
Northstar operates a multi-stage Quote-to-Cash workflow spanning customer enquiry, site assessment, quoting, scheduling, service delivery, invoicing and payment, using a combination of email, spreadsheets, technician notes, photographs, CRM records, scheduling software, accounting software, phone calls and messaging. The primary issue is not the presence of multiple systems. It is that information and responsibility are not consistently controlled as work moves between stages.
- Site-assessment information is captured inconsistently.
- Quote preparation can be delayed by missing information.
- Quote follow-up is not governed by a reliable trigger or ownership rule.
- Approved work requires information to be re-entered into scheduling.
- Job completion is not consistently communicated to finance.
- Invoicing may therefore be delayed.
- Management lacks a single workflow-level view.
- Staff maintain parallel spreadsheets and informal tracking mechanisms.
Needs Improvement
A qualitative characterisation of the workflow made by the consultant. WorkflowMD produces a Signature Score for each assessment; no score is reproduced here, and this wording should not be read as a product-generated rating.
Primary issue
Fragmented information and weak workflow control across departmental handoffs.
Immediate priority
Establish consistent information, ownership and stage-transition rules before expanding automation.
Business consequences
Slower handoffs
Work can wait between teams because the completion of one stage does not reliably trigger the next.
Administrative duplication
Information is entered, transferred or reconstructed across multiple systems.
Inconsistent execution
Different employees use different methods to capture, communicate and track information.
Delayed billing
Where job completion is not promptly communicated to finance, invoicing can be delayed even when the work is complete.
Weak management visibility
Management cannot easily identify which work is progressing normally and which items are stalled.
Increased operational risk
Quote follow-up, job scheduling and invoice initiation depend partly on individual memory or informal processes.
The financial impact of these issues cannot be quantified from the information currently available.
Immediate → Next → Future
WorkflowMD advises that an unstable or poorly defined workflow should not be automated, and phases its recommendations as Immediate, Next and Future. The full roadmap appears in section 08.
Stabilise → Standardise → Connect → Automate → Augment
The consultant's five-phase delivery structure. It is not a WorkflowMD-generated structure and sits alongside, rather than replacing, the product roadmap.
02 — Current workflow map
Enquiry to payment, in eleven stages
WorkflowMD output + consultant annotation- Enquiry
- Qualification
- Site Assessment
- Quote Preparation
- Quote Sent
- Customer Approval
- Scheduling
- Service Delivery
- Completion
- Invoice
- Payment
WorkflowMD reconstructs the workflow stages from assessment evidence. Stage-level owners, tools, handoffs and control notes shown here are consultant annotations for validation.
- 01Consultant annotation
Enquiry
- Likely owner
- Sales or administration
- Information
- Customer details, service request, location, contact information
- Tools
- Email, phone, CRM or messaging
- Manual activity
- Enquiry capture and initial data entry
- Primary handoff
- Enquiry to qualification
- Potential delay
- Information may need to be reconstructed from different channels
- Visibility issue
- It is unclear whether every enquiry is centrally recorded.
Consultant validation note
Confirm enquiry channels and whether CRM capture is mandatory. - 02Consultant annotation
Qualification
- Likely owner
- Sales
- Information
- Scope, customer requirements, site information, commercial suitability
- Manual activity
- Reviewing enquiry and determining next action
- Primary handoff
- Qualified opportunity to site assessment
- Potential delay
- Missing initial information may require further customer contact
- Visibility issue
- Qualification criteria have not been provided.
Consultant validation note
Confirm whether formal qualification rules exist. - 03Consultant annotation
Site Assessment
- Likely owner
- Technician or estimator
- Information
- Site conditions, scope, measurements, photographs, technical requirements and constraints
- Tools
- Technician notes, photographs, email, messaging
- Manual activity
- On-site inspection and information capture
- Primary handoff
- Technician to sales or estimating
- Potential delay
- Critical information may be incomplete
- Control issue
- Different technicians capture information differently.
A major workflow-control point: the quality of information collected here directly affects quote preparation.
- 04Consultant annotation
Quote Preparation
- Likely owner
- Sales or estimator
- Information
- Scope, site information, pricing inputs, materials, labour assumptions and customer details
- Tools
- CRM, email, spreadsheets or quoting system
- Manual activity
- Consolidating assessment information and preparing quote
- Primary handoff
- Completed quote to customer
- Potential delay
- Sales staff may need to return to technicians for missing information
- Control issue
- Quote readiness depends on the completeness of upstream data.
- 05Consultant annotation
Quote Sent
- Likely owner
- Sales
- Information
- Completed quote and customer contact details
- Tools
- Email and potentially CRM
- Manual activity
- Sending and tracking quote
- Primary handoff
- Quote to customer
- Potential delay
- Customer response
- Control issue
- Follow-up is inconsistent.
There is no confirmed workflow rule defining when follow-up should occur or who is accountable for it.
- 06Consultant annotation
Customer Approval
- Likely owner
- Sales
- Information
- Customer acceptance and approved scope
- Manual activity
- Recording approval and transferring job information
- Primary handoff
- Sales to operations
- Potential delay
- Approval may not immediately initiate scheduling
- Control issue
- Approved quote information is manually entered into another system.
- 07Consultant annotation
Scheduling
- Likely owner
- Operations
- Information
- Customer, location, scope, resources, timing and service requirements
- Tools
- Scheduling software
- Manual activity
- Re-entering approved quote information
- Primary handoff
- Operations to field team
- Potential delay
- Manual transfer and scheduling availability
- Control issue
- Duplicate data entry introduces avoidable administrative work and error potential.
- 08Consultant annotation
Service Delivery
- Likely owner
- Technician or field team
- Information
- Job scope, customer details, schedule, site requirements
- Tools
- Scheduling system, job records, messaging
- Manual activity
- Work execution and status updates
- Primary handoff
- Field team to completion stage
- Potential delay
- Exceptions or scope changes
- Control issue
- Exception-management procedures are unknown.
- 09Consultant annotation
Completion
- Likely owner
- Technician, field supervisor or operations
- Information
- Confirmation that work is complete, final job notes and any variations
- Manual activity
- Recording job completion
- Primary handoff
- Operations or field team to finance
- Potential delay
- Completion information does not always reach finance immediately
- Control issue
- Completion does not appear to create a reliable billing trigger.
- 10Consultant annotation
Invoice
- Likely owner
- Finance
- Information
- Completed work status, customer information, approved amount, variations and billing details
- Tools
- Accounting software
- Manual activity
- Confirming billability and creating invoice
- Primary handoff
- Invoice to customer
- Potential delay
- Finance may wait for confirmation that work is complete
- Control issue
- Billing readiness is dependent on upstream communication.
- 11Consultant annotation
Payment
- Likely owner
- Finance
- Information
- Invoice status and payment receipt
- Tools
- Accounting software
- Manual activity
- Payment monitoring and collections activity where required
- Primary handoff
- Financial reconciliation
- Potential delay
- Customer payment timing
- Visibility issue
- Invoice ageing exists as a recommended measurement, but current reporting capability has not been established.
03 — Primary findings
What WorkflowMD diagnosed
WorkflowMD outputWorkflowMD reports a maximum of three major diagnostic findings, each with evidence, an operational consequence and a severity rating drawn from Critical / High / Medium / Low.
- F01
Site-assessment information is not standardised
Evidence / observation
Technicians currently collect and communicate site information through different methods, including notes, photographs, email and verbal communication.
Operational consequence
Quote preparation depends on the quality and completeness of information received. Inconsistent capture can result in missing inputs, additional communication, delayed quote preparation and inconsistent quoting processes. Where information is incomplete, sales staff need to contact technicians again, which introduces avoidable rework and waiting time; the underlying cause sits in site assessment rather than in quote creation itself.
Severity: High
- F02
Quote follow-up lacks a dependable workflow control
Evidence / observation
There is no reliable trigger or clearly enforced ownership for following up unanswered quotes.
Operational consequence
Follow-up performance depends on individual behaviour rather than a controlled process. Quotes can remain unattended without management immediately knowing that an action is overdue.
Severity: High
- F03
Job completion does not reliably trigger invoicing
Evidence / observation
Finance does not always know immediately when work is complete and ready for invoicing.
Operational consequence
A completed job can remain unbilled while finance waits for confirmation. This creates an avoidable delay between operational completion and the beginning of the payment cycle.
Severity: High
04 — Consultant-expanded observations
Additional observations for the client discussion
Consultant analysisDeveloped by the consultant from the same evidence base. These are not additional WorkflowMD findings — the product caps primary findings at three.
- Observation A
Approved job information is entered more than once
Evidence / observation
Operations manually re-enters information from approved quotes into the scheduling system.
Operational consequence
Duplicate administrative work, additional handoff effort, risk of transcription errors, and potential delay between approval and scheduling.
Consultant severity assessment: Medium
Should be reassessed once transaction volumes and error frequency are known.
- Observation B
Management lacks end-to-end workflow visibility
Evidence / observation
Management cannot easily identify work sitting at critical points such as awaiting quote information, awaiting customer approval, awaiting scheduling, awaiting invoicing and awaiting payment.
Operational consequence
Management is more likely to discover stalled work through manual checking or escalation rather than through systematic workflow visibility.
Consultant severity assessment: High
- Observation C
Parallel tracking methods weaken the reliability of workflow information
Evidence / observation
Several employees maintain spreadsheets or informal tracking systems.
Operational consequence
Multiple versions of workflow status can exist simultaneously, weakening information consistency, reporting reliability, accountability and management confidence in workflow status.
Consultant severity assessment: High
Provisional: it depends on how widely the parallel records are used, and would reduce if their use proves narrow.
05 — Root-cause analysis
Observed problem → root cause → downstream consequence
WorkflowMD separates symptoms from root causes and reports up to three primary root causes with their contributing symptoms, an explanation and a consequence.
- Observed problem
- Quote preparation requires additional technician contact
- Root cause
- Unstructured site-assessment capture
- Downstream consequence
- Rework and delayed quote preparation
- Observed problem
- Quotes are inconsistently followed up
- Root cause
- Missing workflow trigger and unclear accountability
- Downstream consequence
- Opportunities may remain unattended
- Observed problem
- Finance does not always know work is complete
- Root cause
- Missing stage-completion rule and handoff trigger
- Downstream consequence
- Delayed invoice initiation
- Observed problem
- Approved work requires re-entry
- Likely root cause
- Fragmented systems and manual handoff
- Downstream consequence
- Duplicate administration and error risk
- Observed problem
- Managers cannot easily identify stalled work
- Likely root cause
- Fragmented workflow data and weak status visibility
- Downstream consequence
- Reactive management
- Observed problem
- Employees use separate spreadsheets
- Likely root cause
- Existing systems do not provide sufficient trusted workflow visibility, or users have developed workarounds
- Downstream consequence
- Conflicting information and inconsistent reporting
- Observed problem
- Process performance varies by employee
- Likely root cause
- Inconsistent process standards
- Downstream consequence
- Unpredictable execution
The dominant pattern is not simply “too much manual work”. The deeper issues appear to be:
- Information is insufficiently standardised.
- Ownership is not explicit at some critical stages.
- Stage completion does not consistently trigger the next action.
- Systems do not currently provide an effective end-to-end workflow view.
- Employees compensate through manual workarounds.
These issues should be addressed before Northstar attempts broad automation.
06 — Improvement opportunities
What should change
WorkflowMD produces evidence-linked recommendations across six capability areas: intake, ownership, automation, integration, reporting and communication. The groupings shown as consultant classifications are delivery labels — Standardisation and AI opportunity are not native WorkflowMD blueprint categories.
- 01
Standardise site-assessment capture
Create a defined site-assessment structure specifying the minimum information required before a quote can be prepared — customer and site, scope, measurements, photographs, access constraints, materials, specialist requirements, known exceptions and technician notes. The exact fields must be validated with Northstar.
WorkflowMD capability area: IntakeConsultant classification: Standardisation / Process improvement - 02
Define quote follow-up ownership and rules
Define who owns each open quote, when the first follow-up is due, subsequent follow-up rules, what constitutes closure, and escalation rules. This should happen before automating follow-up.
WorkflowMD capability area: OwnershipConsultant classification: Ownership / Governance - 03
Establish stage-completion criteria
Define what must be true before work progresses between major stages: Site Assessment Complete (all mandatory quote inputs captured), Quote Approved (acceptance recorded and scope confirmed), Job Complete (required operational completion information recorded), Ready to Invoice (all required billing information available).
WorkflowMD capability area: OwnershipConsultant classification: Process improvement / Governance - 04
Reduce approved quote-to-scheduling re-entry
Investigate whether approved quote information can move into scheduling without manual recreation. Conditional: Northstar's current applications and their integration capabilities have not yet been technically assessed.
WorkflowMD capability area: IntegrationConsultant classification: Integration - 05
Create a completion-to-invoice trigger
Once job-completion criteria are standardised, completion should reliably initiate the invoicing workflow. Options range from a notification to finance through to automated creation of a billing-ready record. Technical implementation should only be selected after the current system environment is assessed.
WorkflowMD capability area: AutomationConsultant classification: Process improvement / Automation - 06
Introduce controlled quote follow-up automation
Once ownership and follow-up rules are established, Northstar could automate reminders, task creation, notifications and overdue follow-up flags. Customer communication itself may remain human-controlled where appropriate.
WorkflowMD capability area: AutomationConsultant classification: Automation - 07
Create workflow-level status visibility
Provide management with a view showing work by workflow stage: awaiting site information, quote preparation, quotes awaiting customer response, approved awaiting scheduling, jobs in progress, completed awaiting invoice, and invoices outstanding.
WorkflowMD capability area: ReportingConsultant classification: Reporting / Visibility - 08
Evaluate AI-assisted quote preparation
Once site-assessment data is structured and sufficiently consistent, Northstar could evaluate whether AI assistance is useful for summarising technician notes, extracting structured information, drafting quote descriptions, identifying missing inputs and preparing an initial scope summary. AI should assist the process rather than compensate for uncontrolled source information.
Consultant classification: AI opportunity — a consultant category. WorkflowMD does not classify recommendations as AI opportunities.
07 — Consultant prioritisation
Consultant Prioritisation
Consultant analysisWorkflowMD provides priority labels and phased recommendations. The impact, effort, risk, readiness and final sequencing below are consultant analysis.
1. Standardise site-assessment capture
- Impact
- High
- Effort
- Low
- Risk
- Low
- Readiness
- High
2. Define quote follow-up ownership and rules
- Impact
- High
- Effort
- Low
- Risk
- Low
- Readiness
- High
3. Establish stage-completion criteria
- Impact
- High
- Effort
- Low
- Risk
- Low
- Readiness
- High
4. Create completion-to-invoice trigger
- Impact
- High
- Effort
- Medium
- Risk
- Low–Medium
- Readiness
- Medium
5. Create workflow-level visibility
- Impact
- High
- Effort
- Medium
- Risk
- Low–Medium
- Readiness
- Medium
6. Reduce quote-to-scheduling re-entry
- Impact
- High
- Effort
- Medium
- Risk
- Medium
- Readiness
- Unknown pending technical review
7. Automate quote follow-up controls
- Impact
- Medium–High
- Effort
- Medium
- Risk
- Low–Medium
- Readiness
- Medium
8. Evaluate AI-assisted quote preparation
- Impact
- Medium
- Effort
- Medium
- Risk
- Medium
- Readiness
- Low–Medium
What should Northstar improve first?
Standardise the information collected during the site assessment and establish clear workflow ownership and completion rules. These changes rank first because they address upstream causes rather than downstream symptoms. Automating quote creation, scheduling handoffs or invoicing before the required information and stage rules are reliable could make an inconsistent workflow move faster without making it more controlled.
- 01Structured information enables more reliable quoting.
- 02Clear ownership enables reliable follow-up.
- 03Defined stage completion enables reliable workflow triggers.
- 04Reliable triggers enable useful automation.
- 05Consistent workflow data enables trustworthy reporting and AI assistance.
08 — WorkflowMD roadmap
Immediate → Next → Future
WorkflowMD outputWorkflowMD phases its recommendations into three horizons. This is the roadmap the product produces.
- 01
Immediate
- Confirm ownership for each workflow stage.
- Define quote follow-up responsibility and escalation rules.
- Define the minimum site-assessment information required before a quote can be prepared.
- Define "approved", "complete" and "ready to invoice".
- 02
Next
- Establish a single reliable source of workflow status and a stage-level management view.
- Reduce duplicate entry between approved quotes and scheduling, subject to technical review.
- Introduce a completion-to-invoice trigger.
- 03
Future
- Automate quote follow-up reminders, overdue alerts and workflow exception alerts once rules are stable.
- Evaluate AI assistance for site-note summarisation, information extraction and scope drafting once source information is reliable.
09 — Consultant implementation sequence
Stabilise → Standardise → Connect → Automate → Augment
Consultant analysisThe consultant's delivery structure. Objectives, dependencies, expected benefits and suggested indicators are consultant additions; WorkflowMD roadmap items do not carry these fields.
- 01
Phase 1 — Stabilise
Consultant addition- Objective
- Remove ambiguity around ownership and workflow progression.
- Recommended actions
- Confirm ownership for each workflow stage; define quote follow-up responsibility; define escalation rules; identify current unofficial spreadsheets and workarounds; document major workflow exceptions.
- Dependencies
- Management and workflow-owner participation.
- Expected operational benefit
- Greater accountability and fewer activities dependent on individual memory.
- Suggested indicators
- Percentage of open quotes with an assigned owner; percentage of workflow stages with defined ownership; number of unresolved ownership exceptions.
- 02
Phase 2 — Standardise
Consultant addition- Objective
- Make workflow information and stage completion more consistent.
- Recommended actions
- Create standard site-assessment requirements; define mandatory information before quote preparation; define “approved”, “complete” and “ready to invoice”; establish consistent status terminology.
- Dependencies
- Phase 1 ownership decisions.
- Expected operational benefit
- Reduced rework, more reliable handoffs and improved workflow consistency.
- Suggested indicators
- Percentage of site assessments meeting required information standards; percentage of quotes requiring additional information; number of jobs with unclear completion status.
- 03
Phase 3 — Connect
Consultant addition- Objective
- Reduce unnecessary information transfer and fragmented workflow status.
- Recommended actions
- Map existing system capabilities; identify duplicate data entry; evaluate quote-to-scheduling integration; evaluate completion-to-finance information flow; define a reliable workflow-status source.
- Dependencies
- Standardised workflow information and stage definitions.
- Expected operational benefit
- Reduced administrative duplication and improved continuity between teams.
- Suggested indicators
- Number of fields manually re-entered; approval-to-scheduling time; number of handoff exceptions.
- 04
Phase 4 — Automate
Consultant addition- Objective
- Automate predictable workflow actions where rules are sufficiently stable.
- Recommended actions
- Evaluate automation for quote follow-up reminders; overdue-task alerts; approval-to-scheduling notifications; completion-to-invoice triggers; workflow exception alerts.
- Dependencies
- Clear ownership, stable status definitions and reliable system events.
- Expected operational benefit
- Reduced dependency on memory and manual monitoring.
- Suggested indicators
- Percentage of eligible actions triggered automatically; missed follow-up rate; completion-to-invoice time; number of overdue workflow actions.
- 05
Phase 5 — Augment
Consultant addition- Objective
- Use AI selectively where it can improve information handling or professional judgement.
- Recommended actions
- Evaluate AI assistance for site-note summarisation; structured information extraction; quote scope drafting; missing-information detection; workflow exception classification.
- Dependencies
- Reliable source information, suitable technical controls and acceptable output quality.
- Expected operational benefit
- Potential reduction in information-processing effort and improved consistency. These benefits must be tested rather than assumed.
- Suggested indicators
- Percentage of AI-generated outputs requiring substantial correction; time required for human review; information-extraction accuracy; user adoption; exception rate.
10 — Consultant AI and automation review
What is ready to automate, and what is not
WorkflowMD contributes the automation and integration recommendations, the process-before-automation sequencing, and the recorded exclusions with reasons. The grouping into candidate registers below — and the AI candidate list in particular — is consultant analysis.
Good automation candidates
Quote follow-up reminders
A quote status and elapsed-time rule can potentially create a predictable trigger. Prerequisite: ownership and follow-up rules must first be defined.
Job-completion notification
When a job satisfies agreed completion criteria, finance can be notified. Prerequisite: reliable definition of job completion.
Ready-to-invoice workflow
A completed job containing required billing information can potentially be flagged for finance.
Workflow exception alerts
Items remaining in a stage beyond an agreed threshold can be flagged.
Approved quote handoff
Approved quote information may be transferable into scheduling. Prerequisite: technical compatibility must be verified.
Potential AI candidates — consultant analysis
Site-assessment summarisation
AI could convert structured notes and supporting text into a concise summary.
Information extraction
AI could potentially extract relevant information from technician notes into defined fields.
Quote scope drafting
AI could assist with preparing an initial description of work from verified site-assessment information.
Missing-information detection
AI could assist in identifying potentially incomplete site-assessment records.
Workflow decision support
AI could potentially surface unusual cases for human review.
All AI outputs affecting commercial scope, pricing or commitments should retain appropriate human oversight.
Poor candidates for immediate automation
WorkflowMD records what it deliberately excluded and why. The heading below is the consultant’s grouping of those exclusions.
Entire site-assessment process
The current information capture method is inconsistent. Automation should not be used to conceal an undefined information standard.
Fully automated quote creation
The quality and completeness of source information have not yet been demonstrated. Pricing, scope and commercial judgement may also require human oversight.
Fully automated customer follow-up
Northstar has not yet defined the required follow-up policy, customer segmentation or exception handling.
Automated exception decisions
The nature and frequency of operational exceptions are currently unknown.
Broad end-to-end automation
The underlying workflow requires governance and standardisation first.
Do not automate a broken workflow. The objective is not to maximise automation; it is to improve the workflow and then determine where automation or AI provides justified value.
11 — Consultant validation agenda
Twelve questions for the workflow owners
Consultant analysisPrepared by the consultant from the WorkflowMD diagnosis for validation with Northstar's workflow owners. These questions are not produced or stored by WorkflowMD; the product's own clarifying questions are asked during intake, before the assessment is generated.
- 01
How many enquiries, quotes, approved jobs and invoices does Northstar process in a typical week or month?
Establishes workflow volume and helps quantify which problems materially affect operations.
- 02
What information must a technician provide before sales can prepare a quote without further clarification?
Defines the required site-assessment standard.
- 03
What percentage of site assessments currently require sales to contact the technician again?
Tests the scale of the observed rework.
- 04
Who owns a quote after it has been sent, and what follow-up behaviour is expected?
Validates the apparent ownership gap.
- 05
How many quotes currently receive no structured follow-up?
Determines whether the issue is occasional or systemic.
- 06
How is customer approval recorded, and what action formally tells operations that scheduling can begin?
Tests the sales-to-operations handoff.
- 07
Which information is manually entered into more than one system?
Establishes the real extent of duplicate administration.
- 08
What exactly makes a job "complete", and who records that status?
Required before designing a completion-to-invoice trigger.
- 09
How long typically passes between operational job completion and invoice creation?
Establishes a critical baseline.
- 10
What exceptions prevent jobs from following the standard process?
For example variations, partial completion, customer disputes, additional materials or return visits.
- 11
Which existing systems support APIs, webhooks, integrations, exports or workflow automation?
Determines technical feasibility.
- 12
Which workflow information does management currently trust, and which reports require manual reconciliation?
Tests the visibility problem and identifies existing reporting weaknesses.
12 — Measurement framework
Measure before claiming improvement
- Recommended measures
- Baseline recording (label, value and unit)
- Expected outcome
- Measured outcome
- Measurement method
- Outcome status
- Reassessment
- Before / after comparison
WorkflowMD does not claim improvement until a measured result is recorded.
This metric set was selected by the consultant for Northstar. Baselines should be established before major process or technology changes.
- Enquiry-to-quote time
- Elapsed time from qualified enquiry to quote issuance.
- Current baseline: unknown
- Site-assessment completeness
- Percentage of assessments containing all mandatory information required for quoting.
- Current baseline: unknown
- Quote rework rate
- Percentage of quotes requiring further technician information after the site assessment.
- Current baseline: unknown
- Quote follow-up compliance
- Percentage of eligible quotes receiving follow-up according to the agreed policy.
- Current baseline: unknown
- Quote response / conversion
- Customer outcomes for quotes where commercially appropriate. Interpret carefully: conversion depends on more than workflow quality.
- Current baseline: unknown
- Approval-to-scheduling time
- Elapsed time between customer approval and confirmed scheduling.
- Current baseline: unknown
- Duplicate entry rate
- Percentage of jobs requiring information to be manually re-entered into another system.
- Current baseline: unknown
- Completion-to-invoice time
- Elapsed time between confirmed job completion and invoice creation.
- Current baseline: unknown
- Workflow stage age
- Elapsed time individual work items remain in each workflow stage. Identifies bottlenecks and stalled work.
- Current baseline: unknown
- Invoice ageing
- Unpaid invoices by age and payment status.
- Current baseline: unknown
These are recommended measurements, not observed results. No performance improvement should be claimed until Northstar establishes baseline data and measures the workflow again after changes are implemented.
13 — Assumptions and evidence gaps
What is not yet known
WorkflowMD flags when an assessment is based on limited information, records the assumptions it has made, states its confidence and withholds conclusions the evidence does not support. The consolidated register below is consultant-prepared from those flags and the consultant's own review.
Workflow volumes
The number of enquiries, quotes, jobs and invoices processed has not been supplied. Without volume data, the total operational impact of each issue cannot be quantified.
Financial impact
No reliable financial impact has been calculated. It is therefore not possible to state revenue lost, administrative cost, labour savings, ROI or cash-flow improvement.
Processing times
Current cycle-time baselines are unknown and should be measured before implementation.
System architecture
The precise systems used by Northstar and their technical capabilities have not been documented. Integration and automation feasibility therefore require technical validation.
Duplicate entry
Manual re-entry is known to occur between quoting and scheduling, but its frequency and effort have not been measured.
Quote follow-up performance
The process is reported as inconsistent, but the proportion of quotes affected is unknown.
Exception frequency
The number and type of non-standard jobs have not been established. Exception-heavy workflows may require more human control.
Employee behaviour
The reasons employees use parallel spreadsheets have not been established. Removing them without understanding their purpose could create new problems.
Customer impact
No direct customer evidence has been supplied. The assessment should avoid claiming that current workflow issues are causing customer dissatisfaction until this is validated.
14 — Recommended next step
Decide what should change before implementing anything
Northstar should not proceed directly to a technology implementation. The next step is to validate the findings with Northstar’s workflow owners, establish baseline measurements, and convert the highest-priority opportunities into an implementation plan. This validation should involve representatives from sales, technicians or estimating, operations, finance and management.
- 01Validate findings with workflow owners
- 02Establish baseline measurements
- 03Convert high-priority opportunities into an implementation plan
Immediate questions to resolve
- What does the workflow actually look like in day-to-day operation?
- Which problems occur frequently enough to justify intervention?
- What information must be standardised?
- Where is ownership currently unclear?
- Which changes can be made without technology?
- Which system connections are technically feasible?
- Where will automation produce justified operational value?
- Where could AI assist after the workflow is stable?
- Which baseline metrics will demonstrate whether the changes worked?
How this assessment is delivered
A WorkflowMD assessment is viewed in the product, downloaded as a PDF or printed. A consultant can use the PDF or printed report as the diagnostic foundation for a client discussion. WorkflowMD does not currently provide white-labelling, client branding, shareable client links or multi-client workspaces.
How was this analysis produced?
WorkflowMD separates the deterministic score from the AI reasoning layer and applies evidence and validation controls before conclusions reach the report.
See how WorkflowMD reaches a conclusionAssess a Client Workflow
Use WorkflowMD to turn one client workflow description into a structured diagnosis, evidence-linked recommendations and a phased improvement roadmap. Each assessment covers a single workflow.
Understand what should change before you automate it.
Illustrative assessment · Fictional company · No customer results or performance claims
Found this useful?