A Desk Proofing Exercise for a Regular Reception Greeting After a Quiet Week

Why a written greeting needs a proofing pass after a quiet week

A short break leaves a front desk in an odd state. The room is unchanged, the furniture is where it was, but the written material on the counter may have drifted. A printed card still mentions a closure that has ended. A laminated sheet refers to a queue routine that was retired. A sign-in folder has a page of notes from the week before the break that no longer match how the desk is being run now.

This exercise is about the words only. It is a desk proofing pass, not a systems review. The aim is to separate text that has gone stale from text that is still current and ordinary, so that a visitor reading the counter material gets a plain, accurate greeting rather than a puzzle.

Treat the exercise as editorial housekeeping. You are reading what is written, comparing it with what is true today, and marking each line as keep, revise or retire. Nothing here requires you to change a device, adjust a setting or promise anything to anyone. The output is a marked-up copy and a short list of decisions for whoever owns the front desk.

For context, premises managers in Sarawak often run several small written artefacts at once: a counter card, a visitor slip, a short welcome note in a folder, and a line or two on a noticeboard. Each is easy to write and easy to forget. A quiet week is a good moment to read them together, because the desk is calm and the comparison is unhurried.

Set the scope before you read a single line

Before proofreading, decide what the exercise covers. A narrow scope keeps the pass honest. A workable scope for one sitting is: the counter greeting card, the visitor sign-in cover sheet, the short welcome paragraph in the lobby folder, and any printed line that a visitor is expected to read on arrival.

Leave out anything that is not a greeting. Do not fold in phone lists, staff rosters, access instructions, delivery notes or internal memos. Those belong to other owners and other reviews. If a line mixes a greeting with an operational instruction, mark it for splitting rather than rewriting it on the spot.

Name a single editor for the pass. Two people editing the same card in the same hour tends to produce a third version nobody agreed to. One editor reads, marks and produces a clean copy; a second person reviews the clean copy against the original.

Set a time box. A short, focused session of about forty-five to sixty minutes is usually enough for four short artefacts. This is an author heuristic, not a measured standard. If the material is longer, split the pass across two sessions rather than rushing the comparison.

Finally, agree the test you will apply to each line. A simple test works: is this line still true today, is it still needed by a visitor, and is it written in plain words? A line that fails any of the three goes on the revise or retire list.

The three-bucket sort: keep, revise, retire

Read each artefact aloud, slowly, and place every line into one of three buckets.

Keep means the line is accurate today, useful to a visitor, and plainly worded. These lines form the spine of the new greeting. Do not improve them during the sort; improvement comes later, and only where needed.

Revise means the line is broadly right but carries a stale detail, an awkward phrase, or a reference that no longer matches the desk. Typical examples are a date that has passed, a room name that has changed, or a sentence that assumes the reader already knows the layout.

Retire means the line should not appear in the greeting at all. This is the bucket people resist. A line can be perfectly accurate and still belong in the retire bucket, because it is not a greeting. Instructions about where to wait, what to bring, or who to call are operational text, and they should live where operations text lives, not on a welcome card.

Keep the buckets visible. Use three colours, three columns in a document, or three piles of paper. The physical separation matters, because the most common proofing error is to start rewriting a line while still deciding which bucket it belongs in. Decide first, rewrite second.

When the sort is done, count the lines in each bucket. A greeting that is mostly retire is not a failure; it usually means the card was doing too many jobs at once.

Spotting stale text without guessing at schedules

Stale text has a few recognisable shapes. Look for time references first: a month name, a day of the week, a phrase like after the break or during the closure. Any time reference in a greeting is a candidate for revision, because a greeting should read correctly on any ordinary day.

Next, look for references to a state of affairs rather than a place. A line that says the desk is currently operating from a temporary position is stale the moment the desk moves back. A line that says the counter is open as usual is more durable, provided it is true.

Then look for names and roles. A greeting that names an individual becomes stale when that person changes role. A greeting that names a function, such as the front desk, ages better. This is a wording preference, not a rule, and it should be applied with judgement.

Be careful with anything that looks like a schedule. Do not invent opening hours, do not guess at holiday dates, and do not write a line that implies a promise about when someone will be available. If the original card carried a schedule, the correct move in this exercise is to remove it from the greeting and note that it belongs to a separate, owned document.

Finally, watch for text that has been patched rather than rewritten. A card with a sticker over a date, or a printed line with a handwritten correction beside it, is a sign that the artefact has outlived its design. Mark it for a clean reprint rather than another patch.

Writing the current ordinary greeting in plain words

Once the sort is done, draft the greeting from the keep bucket and the revised lines. Aim for short sentences, one idea per sentence, and no more than a few lines on a counter card.

A workable shape for an ordinary reception greeting is: a welcome line, a line that says what the visitor should do first, and a line that says who will help. That is three jobs, and three short sentences can carry them. Anything beyond that is probably operational text in disguise.

Use plain, neutral language. Avoid words that imply a promise, such as guaranteed, immediate, always or priority. Avoid words that imply a ranking or a comparison with other premises. A greeting is not marketing copy, and it reads better when it sounds like a person at a desk speaking calmly.

Read the draft as a visitor would, standing at the counter with a bag in one hand. If a line requires a second reading to make sense, shorten it. If a line requires knowledge the visitor does not have, rewrite it or move it out.

Where the premises also run security systems, keep the greeting separate from any product or service description. A visitor greeting is not the place to describe CCTV security systems, camera placement or NVR setup. Those belong in project conversations, not on a welcome card. Keeping the two apart makes both easier to maintain.

A second-reader check and a short sign-off note

A greeting proofed by one person is a draft. Give the clean copy to a second reader who did not take part in the sort, and ask them one question: does this read correctly on an ordinary day? Do not ask whether they like it. Liking is a different question and it tends to reopen settled decisions.

The second reader should mark only two things: lines that are unclear, and lines that appear to make a promise. Both are worth catching before the card is printed.

After the second read, write a short sign-off note. The note should record what was proofed, who edited it, who reviewed it, and the date of the pass. It should also list the lines that were retired and where they were moved, if anywhere. This note is an editorial record, not an approval of any system or service.

Keep the note short. A few lines in a shared document is enough. The value is in the trail: six months from now, someone can see why a line disappeared from the card.

If the premises uses a supplier for other work, the sign-off note should not be used to imply that the supplier reviewed the greeting. Keep the two records separate. A supplier relationship is not an editorial endorsement, and a greeting pass is not a project approval.

Where the greeting sits alongside the rest of the front desk

A reception greeting is one small artefact among several. It helps to know which neighbouring documents exist, so that the greeting does not quietly absorb their jobs.

A telephone and keyphone guide is a separate document with its own owner. If the counter card has started to include instructions about using the desk phone, that text should move to the keyphone guide rather than stay on the greeting. The same applies to any line about transferring a call or reaching a colleague.

Security-related text is also separate. A greeting should not describe remote CCTV viewing, smart lock door access or any other system. Those topics belong in their own conversations, with their own owners and their own records. Where a premises manager is planning an ordinary security project, the practical sequence usually starts with a site survey, then camera placement, then installation and NVR setup, with remote viewing agreed as part of the handover. Eyonic Security Systems plans, supplies and installs CCTV systems for homes, offices, shops and industrial sites in Sarawak, and its published service list covers site survey, camera placement, NVR setup and remote viewing. That is useful context for a project conversation, not for a welcome card.

Keep the greeting file labelled and stored with the other front desk artefacts, and review it again after the next quiet period.

A short checklist you can reuse

Use this checklist at the end of the pass. It is an author heuristic, not a validated instrument, and it is meant to prompt a decision rather than produce a score.

Scope agreed and written down. One editor named. Time box set. Every line sorted into keep, revise or retire. Time references removed from the greeting. Names and roles checked against today. Operational text moved out, not rewritten in place. Draft read aloud at the counter. Second reader asked only about clarity and promises. Sign-off note written with date and owner. Retired lines recorded with their new location.

If any item is unanswered, the pass is not finished. Leave the card in draft until it is.

One last point on tone. A greeting after a quiet week should sound like an ordinary day, not like a reopening. The reader was not away; the desk was. Write for the reader, keep the words plain, and let the rest of the front desk documents do their own jobs.