Basic Flowchart Template
A standard framework for mapping out processes, decision trees, and system workflows clearly and consistently.
In this resource
§1 Overview
A well-structured flowchart brings shared clarity to complex operational sequences, ensuring that an entire project team understands task dependencies and routing logic.
The KEVOS® Basic Flowchart Template standardises how processes are visualised across project documentation. By restricting the diagram to a fundamental set of universally recognised shapes, we prevent misinterpretation and make the logic accessible to both technical and non-technical stakeholders.
Contents§2 Standard Symbols
To maintain visual consistency across all project processes, this template utilises a strict four-symbol vocabulary. Do not invent custom shapes for internal business processes.
| Symbol Shape | Designation | Application Rule |
|---|---|---|
| Oval (Pill) | Start / End | Indicates the definitive beginning or conclusion of a process map. Every flowchart must have at least one of each. |
| Rectangle | Process | Represents a specific action, task, or operation performed by a human or system. |
| Diamond | Decision | Indicates a branching point where the flow diverges. Every branch leaving a diamond must be labelled (e.g., Yes / No). |
| Parallelogram | Input / Output (I/O) | Shows data entering the process or a material/informational output being generated. |
§3 Worked Example: Defect Handling Workflow
To illustrate the practical application of the blank template, we review a defect handling lifecycle mapped for Mary's Consulting - New Company Website.
This process begins immediately upon a defect being discovered. The workflow relies on clear decision gates to determine task priority and routing:
- Initial Logging: The process begins when a defect is found. It is immediately logged in Jira, capturing the severity, functional area, and reproduction steps.
- Triage Decision: The flow reaches a diamond node asking: Severity 1 or 2?
- Yes path: The issue is assigned immediately, and affected work is blocked.
- No path: (Severity 3 or 4) The defect is assigned to the subsequent sprint without immediately blocking the active development pipeline.
- Resolution: Both triage paths eventually converge on the developer fixing the defect on a dedicated feature branch, followed by code review and automated testing.
- Verification Decision: A final diamond asks: Verified by tester?
- No path: The defect is not reopened; it routes back to the developer to continue fixing.
- Yes path: The defect is closed, reaching the end node of the flowchart.
Note on annotations: As demonstrated in the example above, complex logic that does not fit neatly inside a standard shape (such as defining what happens on a 'No' path during triage) should be handled using a brief external note appended to the flowchart.
§4 Application Guidelines
Single Directionality
Ensure the primary flow of logic travels either top-to-bottom or left-to-right. Avoid tangled crossing lines which confuse the operational sequence.
Closed Loops
Every decision diamond must have its branches cleanly resolved. Do not leave 'No' paths floating; they must route to an end state or loop back to an earlier process.
Consistent Granularity
Maintain a uniform level of detail throughout the map. Do not mix high-level departmental phases with micro-level software clicks in the same diagram.
Handbook application: from concept to controlled practice
Purpose. This expanded section turns the original page into a practical handbook. It preserves the supplied material and adds a repeatable way to apply, check and review Basic Flowchart Template. It does not replace a contract, legislation, a controlled standard, competent engineering judgement or specialist advice.
The operating aim is to make the blank artefact usable by explaining what belongs in each field, who supplies it and how it is reviewed. Read the original explanation first, then use the workflow and checks below to convert knowledge into evidence.
Use Basic Flowchart Template as a decision instrument rather than an administrative form. The subject terms—flowchart, standard, workflow, basic, template—need an explicit connection to the project objective, business value and stakeholder commitments. Before completing the artefact, write one sentence stating who will use it, what decision it supports and when that decision is required.
Apply a disciplined information model. Separate facts supported by evidence, forecasts derived from a method, assumptions awaiting validation, constraints that limit choice, risks that may occur, issues that already exist and actions assigned to people. Each material entry should have an owner, date, status and next review point. Where probability or impact scores are used, define the scale so different reviewers interpret it consistently.
A baseline is useful only when changes are visible. Give the artefact an identifier, version, approval state and effective date. Define which changes require reapproval, how superseded versions are retained and where supporting evidence is stored. During reviews, focus on exceptions, decisions and trends rather than reading every field aloud. Record the decision and rationale, not merely that a meeting occurred.
Close the loop beyond delivery. Confirm acceptance criteria, unresolved items, transferred responsibilities and operational ownership. Where benefits are expected, identify the outcome measure, baseline, target, observation period and owner who remains accountable after the project team disbands. Lessons should describe the condition, consequence and reusable action; a generic statement such as “communicate better” cannot improve the next project.
Step-by-step operating method
- Name the decision. Write the decision, approval, handover or control activity the completed template must support.
- Assign ownership. Nominate one accountable owner and identify contributors, reviewers and approvers.
- Gather evidence. Use records, estimates, stakeholder input and source references rather than unsupported opinion.
- Complete with discipline. Use consistent dates, units, identifiers, status values and version controls.
- Review and maintain. Check completeness and logic, approve the baseline, then update it when trigger conditions occur.
Completion and governance protocol
Start with a short drafting workshop involving the accountable owner and the people who hold the evidence. Complete high-consequence fields first: objective, scope, owner, baseline, acceptance, dependencies and escalation. Mark unknowns as assumptions or actions rather than hiding them behind vague prose. Circulate a review draft, resolve conflicting interpretations, baseline the approved version and place the next review date in an owned schedule.
| Information type | Minimum useful content | Review test |
|---|---|---|
| Outcome | Observable change and intended recipient | Not merely a deliverable or activity |
| Measure | Definition, baseline, target, frequency and source | Two reviewers would calculate it the same way |
| Ownership | One accountable role plus contributors and approver | Authority matches responsibility |
| Uncertainty | Assumption, risk or issue with response and trigger | Status reflects current reality |
| Control | Version, approval, review date and change rule | Current baseline is identifiable |
Common failure modes and recovery actions
1. Watch for
Filling every box even when a field is not applicable instead of recording why.
Recovery: Return to the governing definition or requirement and restate the decision in one sentence.
2. Watch for
Writing vague statements without an owner, measure, date or evidence source.
Recovery: Separate evidence from assumption, assign an owner and set a date for validation.
3. Watch for
Copying a previous project without revalidating assumptions and stakeholders.
Recovery: Run a small counterexample, boundary test, pilot or independent check before proceeding.
4. Watch for
Using the document as a private worksheet when it is meant to support a shared decision.
Recovery: Record the consequence, decision and rationale, then update the controlled baseline.
5. Watch for
Creating an approved baseline but failing to define who maintains it and when.
Recovery: Escalate when the issue affects safety, compliance, acceptance, material value or an agreed tolerance.
Review checklist
- Is the purpose and intended decision clear to a reader outside the team?
- Are owners, dates, measures and sources complete and internally consistent?
- Which fields are assumptions and how will they be validated?
- What event, threshold or review date causes this document to change?
- Are mandatory requirements distinguished from recommendations and illustrative values?
- Are sources, assumptions, units, dates and versions recorded closely enough to reproduce the decision?
- Have safety, legal, ethical, stakeholder and operational consequences been considered at the appropriate level?
- Is there a named owner and a trigger for review, escalation, change or retirement?
Questions for deeper application
What is the most important distinction a practitioner must preserve when applying Basic Flowchart Template?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which assumption about flowchart would change the result most if it proved false?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What evidence would allow an independent reviewer to reproduce or challenge the conclusion?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Which boundary, exception or failure case has not yet been tested?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
What must be handed over, monitored or reviewed after the immediate work is complete?
Answer with a fact or cited source where available. Where evidence is incomplete, record the assumption, consequence, responsible owner and next validation action.
Authoritative references and use notes
The sources below were selected as institutional or primary guidance for the broader practice. They support the handbook method; they do not imply that every statement or clause in a source applies to every project. Confirm the current edition, jurisdiction, contract and application before treating any requirement as mandatory.
- PMI Standards and Publications — Project Management Institute. Used for project, program, portfolio and organisational project management. Accessed 2026-08-13.
- ISO 31000 family — Risk management — International Organization for Standardization. Used for principles and guidance for enterprise risk management. Accessed 2026-08-13.