Client portal guide
How your DJ's GigOps client portal works
GigOps gives couples a private planning workspace connected directly to their DJ. Instead of juggling email threads, PDFs, spreadsheets and song lists, you can keep the details your DJ needs in one place and update them as plans change.
1. Your DJ sends secure access
Your DJ creates your event and sends a portal invitation. You can use a magic link or the backup access flow to reach your private planning space.
2. You fill in the event details
Work through music, timeline, ceremony, vendors, contacts, files and planning questions at your own pace. Save changes and return later.
3. Your DJ sees the same plan
What you submit becomes part of the DJ's event workflow, reducing duplicate questions and helping the DJ prepare from the same source of truth.
4. The portal locks near the event
Your DJ can enforce final planning deadlines so the production plan stops changing right before the event. Your portal shows the current status and any final lock timing.
Putting it into practice
How this fits into a real wedding-planning workflow
Couples rarely make every event decision in one sitting. Music changes after a family conversation, a photographer suggests moving portraits, the venue adjusts dinner timing, and a parent remembers a tradition that suddenly needs a song and an announcement. That is why a useful client portal should support gradual planning rather than forcing you to finish one giant form and hope nothing changes. The best way to use this part of GigOps is to add the decisions you know now, return as new information becomes available, and treat the portal as the shared working version of the plan.
For this guide, focus first on your dj sends secure access and you fill in the event details. Those choices tend to influence the rest of the event and give your DJ useful context early. Then work through your dj sees the same plan and the portal locks near the event as the event gets closer. If a decision is still uncertain, it is better to leave a clear note than to enter a guess that someone later mistakes for a final answer.
A practical example is a couple planning a Saturday wedding with a ceremony, cocktail hour and reception. They might confirm ceremony songs months in advance, add first-dance and parent-dance selections later, then update the reception timeline after the venue finalizes dinner service. Their DJ does not need ten separate emails describing those changes. The value of the portal is that the latest planning information remains attached to the event and can be reviewed alongside the rest of the DJ's preparation.
Use the Event Concierge for questions that come up while you are working, but keep major contractual, payment or production decisions between you and your DJ. AI can help explain options and spot missing details; it should not silently make commitments on behalf of either side. The goal is a calmer planning process and a cleaner handoff into event day, with fewer surprises created by outdated documents or details buried in old messages.
Explore more couple planning guides
Ready to use your actual event portal?
Use your invitation or recovery flow to open the private planning workspace connected to your DJ.
Access Your Portal