Module

Remote approval, single or double review

You describe your steps once — single approval, technical and artistic double review, arbitration, reinstatement, auto-approval, a round trip through a clipping or retouching supplier — and the platform enforces them. Your reviewers open lightweight previews in a plain browser, annotate the image or the PDF page, and approve or reject with a predefined reason.

Single or double reviewArbitration & reinstatementAnnotation on image and PDFView guidelines

All modules

What the module does

Decide fast, and prove it

The approval circuit is configured project by project, after the way your organisation actually works.

Previews generated on the fly

HD files stay on the server: the reviewer opens a lightweight preview instead of downloading 80 MB per image.

Annotation on the image

The comment sits exactly where the problem is: a reflection, a crease, an imperfect cut-out.

Artistic review

The art director or brand manager judges framing, lighting and compliance with the brief.

Technical review

In parallel or afterwards, the technical team checks resolution, colour profile and delivery format.

Version comparator

Two versions side by side: you see immediately what the correction changed.

Traceable decisions

Who approved, when, on which version, with which comment: the decision is archived with the media.

Workflows that follow your rules

Single approval, double review, arbitration in case of disagreement, reinstatement of a rejected visual, auto-approval: you compose the path once, the platform enforces it from then on.

View guidelines

For each product family and each channel, the list of expected views, the mandatory ones and the deliverable ones. Requests comply automatically.

Rejection reasons & supplier PDF

Rejection reasons are predefined, so they stay comparable from one project to the next. A rejection PDF is generated for the supplier, annotations included.

How it works

From upload to decision

The file is uploaded

The photographer or the studio uploads online, by FTP or by drag and drop. The application attaches it to its slot and creates a new version.

Reviewers are notified

Only the people concerned by the current step are alerted, by email and inside the application.

The decision is made

Approve, or reject with a reason and an annotation placed on the image. Nothing is left to interpretation.

Everything follows automatically

An approved file moves on to retouching or delivery; a rejected one goes back with its comment attached.

Who it is for

The end of email ping-pong

Wherever someone has to say yes or no to an image, and that decision has to be found again later.

Photo studios — get a clear decision instead of a thread of twenty messages with attachments.
Retail groups — separate the artistic decision from the technical check without doubling the lead time.
Public bodies — have an elected official or a department head approve without giving them access to source files.
Agencies & publishers — the end client approves directly, and the agency keeps the trace of it.
Suppliers — receive an explicit rejection reason rather than a vague "it's not quite right".

FAQ

Frequently asked questions

They are invited with a profile that matches their role. Users are unlimited and cost nothing extra, so no one is left outside the tool for budget reasons.

Yes. The application runs in any modern browser, on desktop, tablet or phone. Previews are lightweight by design, so they load on a mobile connection.

The workflow provides an arbitration step: a designated profile decides, and that decision is traced like any other. A rejected visual can also be reinstated without going through the whole circuit again.

Yes, that is what guidelines are for: for each product family and each channel you define the expected views, the mandatory ones and the deliverable ones. Visual requests comply automatically.

Single approval means one decision closes the step. Double approval separates the artistic decision from the technical check — either in sequence or in parallel, depending on how the project is configured.

Up to 99 versions are kept per media, and any two of them can be compared side by side. Nothing is ever overwritten.

Related modules

Continue the tour