Your phone buzzes again. The event is six days away and someone senior has just asked, in the group chat, whether the graphics have gone out yet.
That question sounds like a design question. It is not. It is an operations question wearing a design question's clothes.
The real problem is not the artwork
Most events do not die from ugly posters. They die from missing ones.
A speaker is announced before their announcement graphic exists. Sponsor logos arrive after the sponsor banners have gone to print. The registration link goes live with a placeholder image, because the real one was promised "by evening."
None of that is a taste problem. It is a sequencing problem, and it is predictable.
The graphics an event actually needs
Think in three phases, not in file types.
Before the event: posters, speaker announcements, sponsor graphics, registration creatives, countdown posts, invitation cards and passes.
During the event: stage backdrops, welcome signage, standees, roll-ups, screen graphics, speaker introductions and sponsor displays.
After the event: speaker quote graphics, key takeaways, highlights, thank-you posts and recap thumbnails.
That list is the whole game. Everything else is a variation.
The test that prevents the panic
Sit with the list and ask one question per item: when does this need to exist in front of a human?
If the answer is "the week of the event", it needs to be produced before the week of the event. If the answer is uncertain, you have found the item that will cause the 11 PM message.
Why we work the way we do
Krevo exists for the moment described at the top of this article. We take the agreed asset list, confirm it, and run the creative layer of the event against a fixed clock — main visuals inside 48 hours, with three revision rounds included.
The event is not late. The event looks late. Those are different problems, and only one of them is about design.