Graduation operation · Tributes
Every graduation has the moment that makes the family cry, and it usually starts in a group chat and a shared folder counted by eye. Here each tribute has an owner, a deadline and a duration, families submit through a link with no login, image use consent is recorded, the graduation committee approves the final edit and the tribute goes into the Ceremonial script as a screen cue.
The problem and the fix
If any of these situations sounds familiar, it is because they happen in almost every graduation company, until the right system comes in.
Nobody knows which families have already sent their video and which are still missing.
The class coverage view shows, graduate by graduate, who has an approved contribution and who is missing, with invitation resend.
The video was shown and afterwards the family complained they hadn't given consent.
Whoever submits accepts the image and voice use terms right in the link. Without acceptance the content doesn't get past curation, and withdrawing consent removes the item from the edit.
The graduate already sent their childhood photos through Material Submission, and the committee asks for everything again.
File responses from Material Submission come in as tribute contributions, by reference, with no downloading and uploading again.
The video runs seven minutes and the ceremony block is ninety seconds.
Each tribute has a target duration, and the edit adds up the selected clips against it before the material goes to the editor.
The final version was approved over chat and nobody knows which file is the right one.
The editor uploads versions, the committee approves through a link and the approved version is frozen. A new edit becomes a new version.
The ceremonial staff finds out on the spot that there's a tribute to show.
The approved tribute becomes a screen cue in the Ceremonial script, with title and duration, and the showing is recorded.
In practice
Everyday situations at graduation companies, from the problem to the result, using the modules on this page.
The committee wanted a message from every family and had three weeks until the ball.
The campaign generated an invitation per graduate, families submitted through the link and the coverage view showed who was missing every day.
One hundred seventy-two families took part, and the editor received the manifest already in order and within the duration.
A classmate passed away in the fourth year of the program.
The tribute was marked as sensitive, and only curators could view and approve the content sent by friends and family.
The family approved the final version before commencement, and nothing was shown without consent.
Graduates had sent childhood photos through Material Submission for the invitation.
The retrospective imported those photos as contributions, and the committee only filled in what was missing.
The retrospective was finished without asking families for a second submission.
How it works
Every step is a real module, and what comes out of one goes into the next without anyone typing it again.
Module by module
4 modules and 16 features on this page, all running on the same class, graduate and event records.
What the class wants to show, who's in charge and by when.
Family and friends submit through the link, with no login.
Nothing goes on the screen without acceptance and review.
From loose material to a screen cue.
Compare the modules and choose the setup that fits your operation.