File selection workflow for agencies: receive, review and deliver without losing versions

The problem: attachments, chats and personal folders break selection

A file selection workflow for agencies starts by recognizing where control is lost. When a client sends logos by email, references by chat and photographs in personal folders, the agency is not working with a set of materials, but with a scattered collection of clues. The usual result is one meeting to ask which file is correct, another to locate the original and a final delivery based on a copy downloaded by the wrong person.

The risk is not only operational. File names can be ambiguous, the type declared by the file may not reflect its real content and a broadly shared folder can expose materials that should not enter review. The solution is not to promise a magic template, but to implement a repeatable pattern: request minimum data, organize by project, select with visible criteria, review with adjusted permissions, preserve history and deliver from a controlled point.

• Warning sign: the team asks in chat which version is the latest.
• Warning sign: the client receives several links with similar files.
• Warning sign: deliverables are exported without a clear date, format or status.

Define the scope before receiving materials

Before opening a folder or sending a link, the agency must define the scope of the workflow. What is received, who can select, who reviews and what is delivered at the end are separate decisions. In a campaign project, for example, brand originals, photographs, approved copy and reference videos may be received; the account manager can validate that the package is complete; art direction can mark candidates; and the client can review only a folder of proposals, not the entire repository.

Apification Cloud fits this pattern as an organized, versioned workspace for files, services and digital projects. The practical rule is to separate work areas: material intake, internal selection, external review and final delivery. That separation prevents a discard from reaching the client, an original from being overwritten during an adaptation or a candidate version from being confused with final artwork ready to download.

• Decision 1: whether the file is intake material, review material, a discard or a deliverable.
• Decision 2: whether the client needs to collaborate inside the space or only download.
• Decision 3: whether the delivery will be the original or a transformed version.

Structured intake: forms with minimum data and validation

Intake should start with a structured request, not with an open phrase such as “send me everything here”. With Apification Surveys and Forms, you can build questionnaires and data capture forms with validation, access controls and exportable responses. In practice, the form should ask for client, project, campaign, owner, target date, material type, usage instructions and a description of the expected files. This turns the request into a searchable record, not a lost conversation.

When intake includes file uploads through the system the agency uses to receive them, browser validation helps reduce omissions: HTML controls can require mandatory fields, and a file field can suggest accepted types or allow multiple files. Even so, that validation is an intake aid, not a guarantee. Server-side validation is still necessary because an invalid request can arrive through other means. It is also advisable to apply an allowlist of extensions required by the business, not rely only on the declared Content-Type, limit sizes and treat the received name as untrusted data. Afterwards, materials must be organized and managed in Cloud.

• Intake checklist: identified project, internal owner, intended use, expected formats, deadline, rights or restrictions indicated by the client.
• Technical checklist: allowed extensions, defined maximum size, captured metadata, server-side validation and internal name generated by the application when applicable.

Organize Cloud by client and project without mixing statuses

Once the materials have been received, the next step is to organize them. In Apification Cloud, the goal is not to accumulate files, but to maintain a shareable, versioned workspace. A useful structure can be client, project, date or phase, and within it subspaces for received originals, internal selection, reviews and delivery. What matters is that the file status does not depend only on the name, because names such as final, final2 or good do not survive a project with several reviewers.

To classify candidates more rigorously, the team can capture and review basic metadata: original name, modification date, size and declared type. These data points do not replace human review or technical validation, but they help detect duplicates, suspiciously small versions or files received after the deadline. If office documents are edited, Apification allows you to create and edit documents, spreadsheets and presentations with ONLYOFFICE while keeping them inside Cloud storage, which reduces local downloads and parallel copies.

• Recommended structure: 01_intake, 02_internal_selection, 03_client_review, 04_delivery.
• Avoid mixing originals with transformed files; the source must always be locatable.
• Do not use a team member’s personal folder as the project’s master archive.

Selection criteria: originals, approved files, discards and candidates

Selection should be based on explicit criteria. An original is the file received or created as a source; a candidate is an option that can move forward; an approved file is one that has already passed review; and a discard is material that should not be used even if it remains available for traceability. This taxonomy seems simple, but it prevents one of the most common causes of error: someone delivering a candidate because it was in the right folder, or deleting a discard that explains a creative decision.

Apification also offers editors to work without breaking the flow. Image Studio allows you to edit images on an integrated canvas with layers, text, shapes, filters and modern export formats. Video Studio allows you to edit video, audio, images, text and subtitles on a multitrack timeline with preview and rendering. Audio Studio allows you to edit recordings and tracks on a multitrack timeline with effects, fades and professional export. The operational decision is clear: the edited file must return to a review or delivery area, not remain lost as a local download.

• Mark as a candidate only what can be presented to the client.
• Keep discards separate so they do not appear in download links.
• Document why a file was approved if there are several similar ones.

Collaborative review: users, groups or download link

Not every review requires the same access. If the client must comment, compare or participate on a recurring basis, sharing with users or groups may make sense. Apification allows items to be shared through links, users or groups, and files and services to be protected with permissions, OTP, external authentication, restrictions and publication windows. The base rule is least privilege: each person or group receives only what they need to fulfill their role. If there is no clear rule that justifies access, it should be denied by default.

Groups are useful when people frequently join and leave, because they allow access to be managed centrally. But sharing a broad folder can expose all its content at the same level, so restricted files must be separated. A download link, meanwhile, is appropriate for a one-off delivery or for reviewers who do not need to browse the project. The typical failure is reusing old links or sending one that points to the wrong folder. Before sharing, review the recipient, scope, permissions, date and whether the link delivers the original or a transformed version.

• Use users or groups for continuous review with defined permissions.
• Use a link when the need is to download a specific package or file.
• Do not share an entire folder if only one file should be reviewed.

Controlled transformations and final delivery with history

Often, the deliverable is not the original file. An agency may receive an editable document and deliver a PDF, receive heavy images and deliver optimized versions, or join and split documents to prepare a review. Apification File Transformation allows you to convert, split, merge, optimize and process documents, images, video, audio and data through a guided assistant. The key is not to transform “over” the original without leaving a trace: the result must be saved as an identified deliverable, with format, date and status.

History closes the workflow. Apification allows you to review the history of Cloud items, download previous versions and restore content safely. This protects the work when someone uploads the wrong variant, modifies a valid document or needs to compare the previous state with the current one. Final delivery should be made from a clean location, with a link or controlled access, and with the appropriate option: original or transformed download when applicable. Before sending, confirm that the file opens, that the format matches what was promised and that the client will not see discards or drafts.

• Final checklist: correct file, correct format, visible date, reviewed permissions, available history, tested link.
• Failure mode: exporting without a date and not being able to distinguish the delivery sent from a later correction.
• Failure mode: restoring blindly and overwriting valid work; first download or review the previous version.

Frequently asked questions