Content and deliverable register
Create a structured list of the creative, media, artwork, document or interface deliverables required by a job.
Content Map & Approvals gives creative and production teams a structured workflow for deliverables, immutable revisions, testing, comments and sign-off. It works internally on its own and can extend into Client Portal when both modules are enabled.
Client approval and creative proofing software should remove ambiguity: which file was reviewed, who approved it, and whether a later revision changed the decision. JobCue keeps that history version-aware.
Create a structured list of the creative, media, artwork, document or interface deliverables required by a job.
Keep each uploaded revision as its own historical record so approval of one version never silently approves the next.
Request review against a specific revision and retain the resulting decision, comments and audit history.
Record relevant testing and structured production checks before artwork or content is released.
Run review and approval inside JobCue even when Client Portal is not enabled.
With Client Portal enabled, deliberately published deliverables can be reviewed externally by authorised contacts.
Preserve the exact version reviewed, record amendments and decisions, and keep acknowledgement history attached to the deliverable that was actually issued.
For designers and account teams handling concepts, artwork, proofs and client feedback.
For teams managing presentation, video, graphic and show-content versions and testing.
For organisations reviewing interface, document and digital deliverables through controlled revisions.
Browse the industries where this feature is especially useful, grouped by sector so you can get to the most relevant workflow quickly.
JobCue keeps the review decision attached to the exact revision that was seen. If the deliverable changes, the next revision starts a new review cycle rather than inheriting an approval it never earned.
Optional modules extend JobCue without becoming accidental dependencies for unrelated workflows.
When an event in Content Map & Approvals matters to delivery, a permission-controlled automation rule can update a related task or programme item. The same organisation, Job and Project context is reused, while Users retain a manual override for exceptions and work completed elsewhere.
Content moves through an explicit review history rather than fragmented email attachments. Approval or amendment events can update related work without replacing human ownership of the final deliverable.
Create a new revision without overwriting history
Notify a task when client approval arrives
Package only approved content for download
Yes. Revision history is designed to preserve what changed and which version received a decision.
No. It can update a specifically linked item, while the team retains control of the wider workflow.
Where configured, OneDrive or SharePoint can hold persistent files as JobCue manages revisions, approvals and the workflow metadata around them.
Choose your Users and modules, see the live monthly price and create your JobCue organisation online.