Wedding day schedule
Build the schedule for a wedding day from steps and minutes. The server calculates all times, buffers and overruns, and the AI words each step.
Wedding: Anna and Tom Date: 20 June 2026 Venue: Lindenhof Start time: 09:00 Planned end: 00:30 Steps: id,step,who,minutes,fixed_start W1,Hair and make-up,Anna and stylist,120, W2,Couple pictures in the garden,Photographer,60, W3,Drive to…
A table with from, to, minutes, step, who and fixed time, the buffers, the overrun in minutes and the end time, also as text and Word.
On a wedding day many people depend on one plan. This tool turns steps and minutes into a schedule from the morning to the party. The ceremony and other fixed times stay fixed, gaps appear as buffers, and a late arrival is reported in minutes. An end after the planned end is reported too. The AI words the steps and calculates nothing.
Your texts, pages and images are processed on our own servers in the EU. Trust Center
Who it is for
Couples, wedding planners and venues.
Typical uses
- Plan a day around a fixed ceremony time.
- See where a buffer is missing before the day comes.
- Give photographer, service team and DJ the same schedule.
Example
Input
Wedding: Anna and Tom Date: 20 June 2026 Venue: Lindenhof Start time: 09:00 Planned end: 00:30 Steps: id,step,who,minutes,fixed_start W1,Hair and make-up,Anna and stylist,120, W2,Couple pictures in the garden,Photographer,60, W3,Drive to the church,Tom,30, W4,Guests arrive,Ushers,30,13:00 W5,Ceremony,Pastor,45,13:30 W6,Reception with cake,Service team,75, W7,Group pictures,Photographer,40, W8,Drive to the Lindenhof,All,20, W9,Dinner,Kitchen,120,18:00 W10,Speeches,Best man,45, W11,First dance,Anna and Tom,15,20:30 W12,Party,DJ,240, Notes: The cake comes from the Hartmann Bakery. The DJ brings his own equipment.
Result
A table with from, to, minutes, step, who and fixed time, the buffers, the overrun in minutes and the end time, also as text and Word.
A fixed example, shortened. Real results are AI-generated: please check them.
Price and limits
- Price
- usually 1–3 credits
- Available with
- Free, With package
- Input limit
- One page with up to 30,000 characters of HTML
Privacy
Processed on our own servers in the EU (Poland). Inputs and results are deleted after 7 days (Free) or 30 days (packages), or right after you see the result if you choose not to store them. Images are deleted right after processing.
In the API
Tool name: wedding_day_schedule. Create a job with POST /api/v1/jobs and fetch the result with GET /api/v1/jobs/{id}. You find your API key in your account.
curl -X POST https://do4u.eu/api/v1/jobs \
-H "Authorization: Bearer d4u_…" -H "Content-Type: application/json" \
-d '{"tool": "wedding_day_schedule", "url": "https://example.com/"}'
Questions and answers
How is an overrun calculated?
The server adds up the minutes from the start time. A step with a fixed time waits for that time, and the gap is shown as a buffer. A later arrival is reported in minutes, and so is an end after the planned end.
What does the AI do here?
It words each step and short notes. All times are calculated by the server, and the who column is added word for word. A wording that does not pass the checks is replaced by the text from the table.
What happens past midnight?
Times continue on the next day and are marked with +1. A planned end earlier than the start counts as the next day.
Is my text stored?
Only as long as needed: 7 days on Free, 30 days with a package – or not at all if you choose not to store it. Processing happens on our own servers in the EU (Poland).
Can I use the result right away?
Results are AI-generated. Please read them before you publish or send them.