Stop running the job from fourteen inboxes

Article Documents & communications ~8 minutes

A design package is “in review.” What that means, day to day, is fourteen people forwarding the same attachments with slightly different filenames — plus a comment thread nobody can reconstruct a month later.

That is not collaboration. That is parallel chaos with courtesy. People are working hard. The package itself has no durable shape. Decisions land in private replies. The “final final” that goes for formal issue is assembled under pressure from whoever still has the right zip.

Construction programmes need speed and coherence. Inbox-driven review delivers the first and quietly destroys the second. The bill arrives as rework, missed comments, revision mismatches, and handovers that feel like archaeology.

What good review packaging looks like

Strong teams treat review sets as working trays, not as one-off email events. A tray is a named collection of related controlled documents gathered for a purpose: discipline review, interdisciplinary coordination, client submission, IFC packaging, or a contractor for-information package. Conversation can be lively; the tray remains the thing people open when they ask “what is in play?”

In practice that means:

• Related documents travel together as a named set for a purpose, so newcomers do not invent their own pile from old threads.
• People discuss and mark within a context that stays linked to the register — comments do not orphan themselves from the controlled revisions underneath.
• When the tray is ready for formal send, it becomes a transmittal, not a scavenger hunt for “the final final” across desktops.
• New joiners can open the tray and understand what is in play without hunting last week’s subject lines.
• History of what was in the set matters as much as the latest PDF, because audits and commercial reading ask what was reviewed then.
• Ownership of the tray is clear: someone can close comments, reconcile conflict, and declare the package ready without polling fourteen inboxes.

Good practice does not ban conversation or markup tools. It refuses to let conversation erase the package. Talking fast is still a virtue. Losing the shape of the set is not.

Where projects slip

Inbox-driven review feels fast until it isn’t — usually at the moment the package must leave the building as a formal deliverable.

• Comment rounds fork into private channels; decisions evaporate or contradict each other with equal confidence.
• People review stale revisions because the tray was never authoritative and “the email on Tuesday” won by proximity.
• Packaging for issue starts from “who has the files?” instead of the register and a curated set.
• Auditors ask why revision letters in the submission differ from what site holds — and the only honest answer is that the zip was rebuilt by hand.
• Handovers between review coordinators become weekends of reconstructing threads.
• Parallel disciplines each keep a personal “almost right” folder; interdisciplinary review compares different worlds without saying so.

The project pays twice: once in rework and missed comments, again in reconstruction when someone asks what the review actually decided. Programme pressure then encourages more informal forking, which deepens the same failure. Kindness (“I’ll just forward you what I have”) becomes the engine of divergence.

How Cynilo supports the practice

Cynilo’s Clusters (Sets) are curated trays of documents — for review, sharing, or packaging a transmittal — without replacing the controlled register underneath. The register remains the authority for revisions. The set is how busy teams keep related items together while people still talk quickly.

You gather what belongs together. You keep the conversation near those records. When it is time to issue formally, the tray already points at the revisions that matter, so packaging is not archaeology. Document control, revision clarity, and formal issue stay connected instead of living in three incompatible habits.

Help How-tos cover creating and using sets. Learn’s point is cultural: stop pretending fourteen inboxes are a document control system. Sets do not invent a new industry idea; they reinstate the working package as something the project owns while reviews are still live.

What good looks like in a week

On a team that treats trays as the working unit:

• Active review packages have names the team recognises — not mystery threads titled “FW: FW: drawings.”
• Reviewers open the tray, not a pile of contradictory attachments renamed by each sender.
• Formal issue starts from the set, not from rebuilding a zip under deadline stress.
• Handovers between coordinators stop being archaeology; the next person can see what is still open.
• Cross-discipline comments land against shared contents, so “we approved that” and “we never saw that sheet” become rarer fights.

A practical weekly habit is for the design or document lead to ask: which trays are live, who owns them, and which are ready to become formal packages? If the answer requires opening someone else’s mailbox, the system has slid back to parallel chaos.

A short story from a mixed-use basement package

A basement structure package on a mixed-use job ran three review rounds by email because “everyone already lives in Outlook.” Round two comments from the waterproofing consultant sat in a side thread with the architect. Structural responders never saw them. Round three issued a package the structural team believed was closed. Site later discovered a drainage detail that had been changed in the side conversation but never returned to the package everyone else reviewed.

Nobody had been obstructive. The tray never existed as a shared object — only as overlapping attachments. After that near-miss, the project insisted that live review packages lived as named sets tied to the controlled documents, and that formal issue left from that tray. Comments still happened at speed. The “what are we reviewing?” question stopped depending on which email you opened last.

Closing

Document control, revisions, formal issue, and the letter book all hang together. Trays are how busy teams keep that discipline while people still talk quickly.

Previous: Current for construction — say it clearly

Also useful across this habit: When “send me the latest drawing” fails and Ask it so you can rely on the answer for the questions that follow reviews.