Assess the submitted version
Open the record supplied with the submission and check its exact version and current status. Review identity, contributions, coverage and declarations as distinct parts of the evidence.
Broadcasters and labelsPublishersPlatforms
For reviewers, buyers and platforms
SEE THE RECORD BEHIND A CREATIVE SUBMISSION.
Assess music and media submissions against DigiBridge’s strict human creation standard. Review selected process evidence, contributor declarations and findings from layered detection and the dedicated AI verification agent, with a separate status for the delivered version.
Human creation verification
Reviewers and Platforms
Assess the record behind a submission and bring current verification status into your workflow.
The problem
A FINISHED FILE LEAVES IMPORTANT QUESTIONS OPEN.
Who contributed? What assistance was used? Does the evidence belong to the version being submitted? DigiBridge brings those questions into a structured review so creators can explain their work and recipients can make informed acceptance decisions.
What DigiBridge does
TURN YOUR CREATIVE PROCESS INTO USEFUL EVIDENCE.
Understand the publishing decision
Check findings about prohibited AI assistance and software generated control against their supporting evidence and review outcome. The dedicated AI verification agent helps explain the record; an AI suggestion alone does not impose a publishing penalty.
Connect review to your platform
Use DigiBridge IDs and authorised API access to bring records into your intake process. Plan for updated statuses and withdrawn publications so decisions use the current record.
How it works
FROM YOUR WORKFLOW TO A CLEARER REVIEW.
- 1
Open the submitted record
Follow the DigiBridge link or scan the QR code supplied with the work. Match the registered project and version to the item you are reviewing.
- 2
Assess the evidence
Read contributor roles, coverage, assistance declarations and the review outcome for any findings. A warning or gap is a reason to check context, not an automatic misconduct decision.
- 3
Make and maintain your decision
Apply your organisation’s acceptance criteria to the record. For platform workflows, discuss API access and how to handle changes or withdrawals after review.
An example from your workflow
THE SUBMISSION AND ITS EVIDENCE, SIDE BY SIDE.
A broadcaster can match a submitted programme to its project record and review contributors, assistance declarations and unresolved questions before making its own editorial decision.
Share selected evidence for the version under review. Your creative source files and typed content stay private.
Project evidence
Review before publicationDocumentary: broadcaster submission
Submitted cut v3
- Project registration
- Registered with DigiBridge
- Version evidence
- Selected sessions and contributors
- Verification status
- Under review
- Reviewer next step
- Check coverage and declarations
Registration connects the project to its history. The version’s verification status is shown separately.
A standard with follow through
CLEAR RULES PROTECT THE VALUE OF THE RECORD.
The strict programme excludes prohibited AI assistance and software generated control acting in place of the contributor. Layered checks and your dedicated AI verification agent examine permitted activity, support detection and connect findings to evidence. You can add context and challenge a finding; confirmed incidents follow the publishing rules below.
Act on a warning
Warnings identify the issue and its evidence. The first confirmed incident holds the affected recording or version from programme publication, with a route to review.
Keep the standard meaningful
Three distinct confirmed incidents disqualify the project from directory publication. Attributable private account marks and reviewed action address repeated abuse.
Keep review fair
Explain your workflow and challenge the evidence if it is wrong. A recording gap or an AI suspicion alone does not count as a confirmed incident.
Why this matters now
SUBMISSION VOLUME IS CHANGING. REVIEW NEEDS CONTEXT.
Generated media, incomplete credits and evolving provenance standards make context valuable at intake. A music master, programme or news package needs a review tied to its specific project and version.
Context 0116 SEP 2026
~90k
DAILY AI GENERATED UPLOADS ON DEEZER
In its September update, Deezer reported nearly 90,000 fully AI generated tracks arriving daily in June 2026. At peak levels, they represented more than half of new uploads.
Scope: ONE STREAMING SERVICE
Why it matters: Upload share differs from listening share: Deezer reported these tracks at 1 to 3% of streams.
Deezer NewsroomContext 0214 APR 2026
20%
LACKED WRITER INFORMATION
The UK Intellectual Property Office reported that 20% of recordings with usage in the participating DSP data lacked writer information.
Scope: PARTICIPATING DSP DATA
Why it matters: Five DSPs contributed quantitative data. Capturing contribution details during creation gives teams information to review before delivery.
UK Intellectual Property OfficeContext 03SPECIFICATION 2.2
Origin
MEDIA HISTORY HAS A STANDARD
C2PA defines a way to attach signed information about the origin and history of digital media. Its model makes the source of a claim visible.
Scope: CONTENT PROVENANCE
Why it matters: DigiBridge focuses on the creative process, people and publishing decision behind a submitted version.
C2PA explainerFREQUENTLY ASKED QUESTIONS
Does “Registered with DigiBridge” mean verified?
Registration connects a project to its permitted history. Check the separate verification status for the submitted version and read the evidence selected for that review.
What makes a submission ineligible?
The programme prohibits AI assistance and software generated control that replaces the contributor under the applicable tool policy. The first confirmed incident holds the affected recording or version from publication, and three distinct confirmed incidents make the project ineligible for the public directory. Check the current status and any review or correction before making your own acceptance decision.
Do reviewers need to install the Mac app?
Reviewers use the shared web record. The Mac app is for contributors recording work in their creative tools.
How do platforms connect?
Start with your submission workflow, access requirements and the decisions you need to support. DigiBridge can scope API access, version checks and status change handling with your integration team.
Start your DigiBridge record
GIVE YOUR REVIEW TEAM MORE TO WORK WITH.
Bring the recorded process into submission review, with clear permissions and a current status for each version.