Dated Project Timeline Builder

How to use Dated Project Timeline Builder

Explain a small project’s calendar plan without turning it into an automatic scheduling model. You supply valid Gregorian dates and progress; the tool places inclusive task bars and single-date milestones on a common daily axis. The vector and printable exports retain complete original labels and date evidence, so a shortened chart label never becomes the only surviving source.

1. Enter one to forty distinct-ID CSV rows with task or milestone type and exact YYYY-MM-DD dates.
2. Supply progress as a 0–100 decimal with at most two fractional digits; milestones use zero.
3. Choose vector or printable source, then review the complete row evidence and actual print preview.

Good to know

• At most 40,000 CSV characters, 40 rows and 366 inclusive Gregorian dates across the whole chart. Exactly id,label,type,start,end,progress headers are required. IDs are distinct, nonblank and at most 40 characters; labels are at most 200. No arbitrary markup or style is accepted.
• Years 0001–9999 use the proleptic Gregorian calendar. Task start and end are inclusive. A milestone requires equal start/end dates and is centered within that day. Dates are validated without Date.parse normalization or timezone conversion.
• Progress is authored data, not measured completion. It has at most two decimal places and is checked as exact hundredths before geometry conversion. SVG geometry uses bounded ordinary numbers after date and progress validation; no physical-size accuracy is claimed.
• Chart labels preview 16 Unicode scalars plus an ellipsis; full labels remain in SVG title elements, JSON and the printable table. Original SVG is generated from fixed shapes and escaped text. No holidays, dependencies, resources, critical path, optimization, project account or external fetch is inferred.
• Printable source is an original landscape A4/Letter document with at most twelve chart rows per page and a separate complete row table. Actual fonts, page scaling and printer behavior require review. This is a static artifact workflow; no submitted plan or delivery status is created.
• Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.