These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Digital Asset Management
- Implementation
How a Digital Asset Management rollout works
Set up one production cycle and verify its decisions before broader use.
Map the work
Choose a representative project, content item, file revision, media version and rights agreement.
Assign responsibility
Name the project owner, Producer, Rights Manager, Editor and Finance Manager for the pilot.
Bring in records
Enter people, project context, items, tasks, rights and versions in dependency order.
Rehearse review
Submit a rendition and file revision, check rights coverage and approve the exact reviewed file.
Rehearse release
Publish the approved item, check the recorded time and linked tasks, then review a draft project cost.
Expand
Compare the pilot's reports with the source records before adding more projects.
What the customer provides
Bring a real production schedule, sample files, agreement terms, version use intervals, an agreed role owner for each decision and the status of any outside publishing or payment systems. A useful pilot includes an amended file and a right nearing its end date so the team can practice a correction and a rights decision.
Changing it afterwards
When a process changes, revisit the project and item ownership rules, review the effect on approval and publication, and rehearse a corrected version before applying the change broadly. Keep earlier file versions and publication records available for comparison. Review any new external connection with its operating owner before depending on its acknowledgement.
Set up Digital Asset Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.