Fix a Gantt chart that looks wrong by correcting its source rows and dates, regenerating the chart, and checking the bars and ticks in the exact preview before download.

In Gantt Chart Maker, accepted data becomes a deterministic UTC calendar chart. A surprising result usually falls into one of three groups: invalid input, a bar that does not match your intended dates, or an axis whose labels are intentionally sampled.

how do i fix a result that looks wrong after i make gantt chart
How to Fix a Gantt Chart Result That Looks Wrong

Identify what kind of wrong result you have

Start by separating a generation failure from a valid chart with an unexpected appearance. This prevents you from changing valid dates merely to make the layout look a particular way.

SymptomWhat it usually meansCorrection
No chart appearsA row has invalid syntax, a date is invalid, an end date precedes its start, or a size limit is exceeded.Correct the whole request and generate again. The tool does not return a partial chart.
A bar has the wrong lengthThe intended period and the inclusive start and end dates do not agree.Correct the date values, remembering that the end date counts.
A bar starts on an unexpected dateThe entered date differs from the intended calendar date.Check the exact YYYY-MM-DD values; accepted UTC dates are not shifted by the browser’s local timezone.
Axis labels look sparseA long schedule is using sampled month ticks rather than a label for every day.Verify that every task and its full width remain present before changing the dates.
An expected task or label is missingThe task was not entered, or its label differs from what you expected.Review the source list. Accepted duplicate labels and overlapping tasks remain separate rows in input order.

Do not treat a missing tick label as proof of a missing task. The bar geometry and the density of the printed axis labels are separate parts of the chart.

Correct the source rows

Use one non-empty row per task, with fields in task,start,end order. Each row must contain exactly two literal commas, producing three fields. Leading and trailing whitespace around fields is trimmed.

  • Do not add full-CSV syntax. Quoted fields, quoted commas, escaped delimiters, additional columns, and multiline fields are unsupported. A task label that needs a comma must be rewritten without one.
  • Check the row count. A valid chart requires 2 to 30 non-empty task rows. One malformed row rejects the entire request; the parser does not silently skip it.
  • Check text limits. A task label can contain at most 80 UTF-16 code units, and the optional title can contain at most 100. The raw schedule data can contain at most 20,000 code units. Exact limits are accepted, while one code unit beyond a limit fails without truncation.
  • Do not use blank lines to bypass the input limit. Blank lines are ignored only after the raw schedule-data budget has been checked.

Dates must be real calendar dates in exactly 10-character YYYY-MM-DD form, using a supported year from 0000 through 9999. They are validated as proleptic Gregorian UTC dates with correct leap-year rules. Slashes, missing zero padding, time text, timezone suffixes, impossible dates, and a February 29 in a non-leap year fail. Each end date must be on or after its start date. This strict calendar-date notation is consistent with the ISO 8601 date and time format.

Read bar lengths and tick labels correctly

The chart describes calendar occupancy. Bar widths and the shared axis are calculated from the accepted UTC dates, so the following interpretations explain most visual surprises.

Chart featureCorrect interpretation
Bar widthThe number of occupied calendar days from the start through the end date, with the end date included.
Same start and end dateThe task occupies one visible day cell.
Shared horizontal domainIt begins at the earliest start and extends through the day after the latest inclusive end.
Day ticksSchedules spanning 62 days or fewer use day labels. The interval expands to keep roughly nine labels while retaining the first and last dates.
Month ticksLonger schedules use a fixed month step calculated from the full month count, keeping the axis readable without removing task spans.
Duplicate labels and overlapping datesThey remain separate tasks in their original input order.

Day labels use YYYY-MM-DD, while month labels use YYYY-MM. Sparse month labels are deliberate axis sampling, not task truncation. Browser locale, the current date, daylight-saving rules, and the local timezone do not alter the layout. For a focused explanation of the inclusive bar rule, see Does the End Date Count on a Gantt Chart Bar?.

Fix the chart in Gantt Chart Maker

  1. List the intended tasks. Put one task on each non-empty line and identify its intended start and end dates before entering the data.
  2. Add the title and paste the rows. Enter an optional title, then paste the schedule in task,start,end order. Confirm that each line has exactly two commas.
  3. Correct every date. Use exact YYYY-MM-DD values, remove any time or timezone text, and confirm that every end date is on or after its start.
  4. Check labels and size limits. Remove commas from task labels that require them, confirm the 2-to-30-row range, and review the label, title, and raw-input limits.
  5. Choose Generate. If validation rejects the request, revise the source data rather than expecting a partial chart. No result is produced from a malformed row.
  6. Verify every bar and tick. Check each task’s start position and inclusive width against its dates. Confirm that overlapping tasks remain separate and that a sparse month axis still contains every complete task bar.
  7. Download the current preview. Select the standalone SVG download only after the visible preview is correct. The downloaded file is created from the exact SVG string used for that preview.

Generate again after changing the title or schedule. The earlier Blob download URL is revoked when the title or data changes, a result is replaced, generation fails, or the tool closes, so an old download link may no longer work.

Check rendering details before exporting

Some issues affect readability rather than date calculations. The chart uses a fixed 1,100-pixel logical width and a height based on the number of rows. Wide output scrolls horizontally in the preview instead of shrinking labels into an unreadable mobile layout, so scroll across the chart before deciding that a bar is misplaced.

  • Task and title text is escaped as safe SVG text. XML-forbidden controls and isolated surrogates become the replacement character U+FFFD.
  • Script-looking text remains visible characters rather than becoming an SVG element.
  • The complete serialized SVG may contain at most 100,000 UTF-16 code units. If it exceeds the limit, the output fails rather than dropping or sampling markup.
  • If Blob or URL creation fails, no stale preview or download remains available.

Parsing, UTC date arithmetic, SVG creation, preview, and download all happen in the current browser tab. The schedule, title, generated SVG, and interaction are not uploaded to Lizely.

Know which planning gaps require other software

A chart can be mathematically correct while still lacking information you expected. This tool represents inclusive calendar occupancy, not hours, business days, work effort, percentage complete, or resource capacity.

It does not parse Microsoft Project files, dependencies, milestones, critical paths, holidays, working calendars, progress, assignees, costs, baselines, or timezone timestamps. It also does not infer whether overlapping work is feasible. If those missing features explain why the result looks wrong, changing the date rows cannot add them. Use dedicated project-management software for dependency planning, collaboration, permissions, audit history, and operational commitments.