Six desk services, run from the Hefei shop office

The intake sheet bay is where a brief becomes a document. A client brings the requirement, the hardware that already exists and the names of the people who sign off on a change, and the desk writes all of it onto a numbered intake sheet. The sheet records the systems in scope, the data that must move between them, the constraints that cannot be broken and the questions that are still open. Nothing is shortened into marketing language. The sheet is written so that a technician who has never met the client can read it later without asking a question of their own.

Bay sessions are held at the Hefei shop office and last long enough to write a complete sheet rather than a headline. Clients who are not local can join by voice on +13187142262 while the desk writes and reads the sheet back. The bay ends when the client confirms the sheet line by line, which often catches a requirement that had been drifting for months before anyone named it.

A completed intake sheet becomes the root of every later step. Shelf plans, order notes and review rounds all refer back to it, which is why the desk treats the bay as a serious commitment rather than a quick chat.

A shelf plan run turns an approved intake sheet into a build sequence laid out as shelves. Each shelf holds one block of work with its own start gate, its own reviewer and its own test rule, and the shelves are arranged so that a client can see what will be finished early and what must wait. The plan is not a Gantt chart with optimistic dates; it is a written route through the work that can be checked at every shelf boundary.

The desk walks every shelf plan with the client before any shelf is committed. If a shelf depends on material that the restock windows cannot supply, the plan is adjusted on the spot rather than after the work has already fallen behind. When a shelf plan needs to change later, the change is written onto an order note and clipped to the rail, so the plan and its history stay together.

Runs can be booked as a single planning session or as a series spread across a longer engagement. Either way the output is the same: a written shelf plan that names each block of work, each reviewer and each test rule, stored with the intake sheet it came from.

Order notes are the running record of every change during a build. When a client adds a requirement, drops a feature or shifts a delivery window, the note desk writes it down and clips it to the rail so that all hands see the same change on the same day. The desk keeps notes in order, with a reference back to the shelf they belong to, which prevents a small tweak from quietly overwriting an earlier decision.

The order note desk is especially useful on long integration jobs where several workstreams overlap. Without a single note rail, changes multiply across email threads and chat groups until nobody can reconstruct what was actually agreed. With the desk in place, a client can ask at any moment what changed and receive a straight answer from the rail itself.

Notes are reviewed in short standing sessions, and cleared into the pack at handover so that the final documentation carries the full change history rather than a tidy summary that omits the difficult middle.

Restock windows are the recurring short slots when the desk replaces exhausted parts, refreshes test hardware and confirms that the next shelf can actually open. They exist because builds stall for the same reasons again and again: a spare switch runs out, a test terminal fails and the team keeps working on assumptions that are no longer true.

Each restock window is booked against the shelf plan so that material arrives before it is needed rather than the week after. The window records what was consumed, what was replaced and what remains short, and that record feeds directly into the next planning session. Over time the desk uses the restock window history to predict shortages before they bite, which is the difference between a settled build and a frantic one.

Clients on a long engagement can book a standing restock window on a regular rhythm. Short engagements usually need a single window at the midpoint, and the desk will recommend the appropriate cadence when the shelf plan is written.

A listing review round checks the delivered items against the intake sheet line by line. Each promised item must show a matching delivered line, each test rule must show a passing result and each open question must show a resolution or a recorded decision to close it as out of scope. The desk rejects any build that cannot show a matching line for every promise, which keeps the definition of done concrete rather than generous.

Review rounds are scheduled at the end of a shelf and again before the final pack. They are short by design and depend on the intake sheet being complete, which is why the desk insists on a full bay session at the start. A review round that discovers a missing line is an honest failure, and the desk will say so plainly rather than papering over the gap.

The output of each round is a stamped listing sheet that the client keeps. When a build passes all rounds, the stamped listings form the record of what was actually delivered, and that record travels with the pack at handover.

A pack sitting brings the client, the desk and the build hand together in one room to seal the handover. Documentation, credentials, hardware and support notes are packed in a single sitting and signed for on the spot, which removes the slow week of messages that usually follows a project close. The carton at the foot of the desk holds the packed material until the client signs the pack sheet, and then it leaves the shop office with the client.

The sitting also serves as a walkthrough. The build hand explains how each shelf was closed, the desk reads the final review listing and the client asks the questions that are easiest to ask while the system is still fresh. Anything that needs follow up is written as a new order note rather than left as a promise in the room.

Pack sittings can be booked on their own for a system that was built elsewhere, as a way of getting a proper written handover in one session. The desk will read the existing documentation, pack it with the client and produce the signed pack sheet that a clean handover needs.