Document the steps you use to make a Gantt chart in six parts: the source tasks, date rules, input format, validation checks, visual review, and final export.
A repeatable Gantt chart procedure lets another person trace each bar to its source row and understand which dates are included. It also provides a clear record of what was checked before the chart was approved.
The method below separates the documentation process from the chart itself. It also shows exactly where Gantt Chart Maker fits into a documented workflow without treating a calendar timeline as full project-management software.

What a useful Gantt chart procedure records
Start with a compact runbook. The following values apply to the Gantt Chart Maker workflow used in the steps below.
| Part to document | Exact detail to record |
|---|---|
| Purpose and scope | The tasks represented and a statement that the chart shows calendar occupancy rather than workload, feasibility, or operational commitments. |
| Title | An optional title of at most 100 UTF-16 code units. |
| Task rows | 2–30 non-empty rows in task,start,end order, with exactly two literal commas per row and a task label of at most 80 UTF-16 code units. |
| Raw source | At most 20,000 UTF-16 code units. Blank lines cannot bypass this limit because they are ignored only after the raw input budget is checked. |
| Dates | Exactly 10 characters in YYYY-MM-DD form, representing real proleptic Gregorian UTC dates from 0000 through 9999, with each inclusive end date on or after its start date. |
| Final artifact | A standalone SVG created from the exact preview string, with the complete serialized SVG limited to 100,000 UTF-16 code units. |
The row syntax is CSV-lite, not full CSV. Each non-empty row has three fields: task label, start date, and end date. Leading and trailing field whitespace is trimmed, but quoted fields, quoted commas, extra columns, escaped delimiters, and multiline fields are unsupported. A label that needs a comma must be rewritten without one. One malformed row rejects the whole request, so the tool never produces a partial chart. Duplicate labels and overlapping tasks are allowed and remain separate rows in input order. The stated input and output maximums are inclusive; exceeding a limit fails without truncating the result.
Document the Gantt chart workflow
Use the following sequence to turn chart creation into a procedure someone else can follow and verify.
- Define the purpose and revision. State the decision, report, or planning activity the chart supports. If the purpose is still unsettled, the guide How Do I Decide Whether I Need to Make a Gantt Chart? can help establish the scope before tasks are listed. Assign the schedule a revision name or number so later changes remain distinguishable.
- Preserve the source schedule. Keep the task list and approved dates in a text-based record, not only inside an image. This provides the baseline against which the generated bars and axis will be checked. Retain this source with the finished chart whenever the schedule may need to be reproduced.
- Prepare strict task rows. Enter the optional title separately. Put one task on each non-empty row using the form Research,2026-05-04,2026-05-06. Do not add a header row, quotation marks, or extra columns. Check that the chart contains 2–30 non-empty rows, every row has exactly two commas, each label stays within 80 UTF-16 code units, and the title stays within 100.
- Record the date interpretation. State that dates are inclusive UTC calendar dates without times or timezone suffixes. An end date cannot precede its start date, and a same-day task occupies one visible day cell. Also note that weekends and holidays are not removed because this is not a working-calendar calculation.
- Generate from the reviewed source. Paste the rows into Gantt Chart Maker and generate the chart. Parsing, UTC date arithmetic, preview creation, and download preparation stay in the current browser tab; no schedule, title, or SVG is uploaded to Lizely. If the request is rejected, correct the source and generate again rather than expecting a malformed row to be skipped.
- Review every bar and tick. Match every task row to a labeled horizontal bar. Check the start and end positions, one-day tasks, duplicate labels, overlapping rows, the first and last dates, and the displayed tick labels. The guide How to Check the Result After You Make a Gantt Chart provides a separate visual review checklist.
- Download only after review. Download the standalone SVG once the preview is correct. The download is created from the exact SVG string used for the visible preview, so the exported file reflects the markup that was reviewed. If the completed SVG exceeds its size budget, generation fails rather than dropping or sampling part of the output.
- Close the method record. Add the tool name, operator, preparation date, source revision, date convention, checks performed, reviewer, output filename, and known limitations. Store this note with the raw task rows and downloaded SVG so the full process remains auditable outside the chart itself.
Use a reusable documentation template
Copy this structure into a runbook, project note, ticket, or README:
- Procedure name and revision: Identify the schedule, purpose, and version of the workflow being documented.
- Tool and processing location: Record Gantt Chart Maker, its current-browser-tab processing, and the fact that the schedule and output are not uploaded.
- Input specification: State the optional-title limit, row count, CSV-lite syntax, label limit, raw-input limit, and exact date format.
- Date rule: Explain that both start and end dates are included, dates use UTC, and weekends or holidays are not excluded.
- Validation record: List the row, delimiter, calendar-date, ordering, and size checks that were performed before generation.
- Visual review: Record that every bar and tick was compared with the source, along with the reviewer, review date, and any corrections.
- Output and limitations: Name the standalone SVG, confirm that it matches the reviewed preview, and state that the chart does not establish dependencies, effort, or schedule feasibility.
Check bars and ticks against the source
The visual review should cover both the task bars and the calendar axis. Their underlying rules are deterministic, so a discrepancy usually points to the source rows or an incorrect assumption about the axis.
- Bar mapping: Every accepted task receives one horizontal bar. Duplicate labels remain separate, and overlapping tasks retain their own full date widths and input order.
- Date domain: The axis begins at the earliest task start and ends after the latest inclusive task day. If every task occurs on the same date, the shared domain is one day and every bar remains visible.
- Day mode: A domain of 62 days or fewer uses YYYY-MM-DD tick labels. Spacing expands as needed to keep roughly nine labels while retaining the first and last dates.
- Month mode: Longer schedules use YYYY-MM month labels and deterministic sampling that keeps the first and last dates. Every accepted task and its complete width remain in the chart; fewer axis labels do not mean tasks were omitted.
- Time-zone consistency: Layout does not change with browser locale, the current date, daylight-saving rules, or a local time zone. The documented dates should therefore remain plain YYYY-MM-DD values.
A long preview may scroll horizontally instead of shrinking the labels into an unreadable mobile width. Treat horizontal scrolling as a viewing condition, not as evidence that the exported chart changed scale.
Separate chart facts from planning conclusions
A careful method note distinguishes what the timeline displays from judgments a reader might otherwise infer.
| What the chart records | What it does not establish |
|---|---|
| Inclusive UTC calendar occupancy | Hours worked, business-day duration, work effort, percentage complete, or resource capacity |
| Start and end positions supplied by the source rows | Dependencies, milestones, critical paths, holidays, working calendars, or progress |
| Separate rows for overlapping work | Whether the overlap is feasible, properly staffed, or operationally acceptable |
| Date labels and task names in the SVG | Assignees, costs, baselines, timezone timestamps, or operational commitments |
The tool does not parse Microsoft Project files or infer whether overlapping work is realistic. Dedicated project-management software is better suited to dependency planning, collaboration, permissions, audit history, and operational commitments. Record those boundaries in the method note instead of presenting the Gantt chart as proof that the underlying project plan is workable.
Save and troubleshoot the final deliverable
After the last title or schedule change, generate, review, and download again. Changing the title or data replaces the previous result and revokes its download URL, so an earlier file should not be treated as the final revision. Store the downloaded SVG, the raw rows, and the completed method note together under a clear filename.
- Whole request rejected: Inspect every non-empty row. Confirm that the row count is 2–30, every row contains exactly two literal commas, and no unsupported quoting, extra column, or multiline field is present.
- Date rejected: Check exact zero-padded YYYY-MM-DD formatting, the 0000–9999 year range, real calendar dates, and an end date that is not earlier than the start.
- Input rejected: Check the 20,000-code-unit raw schedule limit, 80-code-unit task-label limit, and 100-code-unit optional-title limit. Blank lines are ignored, but only after the raw budget is checked.
- SVG rejected: The complete serialized SVG may contain at most 100,000 UTF-16 code units. The tool will not trim markup or sample the output to stay under that boundary.
- Unexpected visual result: Recheck the source dates, day-versus-month tick mode, duplicate labels, overlapping rows, and the inclusive end-date rule before changing the chart layout.
A failed request does not create a partial chart to document. Correct the source, repeat the complete validation and visual review, and replace the output file and revision record only after the new result passes every check.