Administrative Support
Owner and Executive Support for roofing contractors
Every item this desk holds back is a decision made with your authority. That only works if you wrote the rule it was made against.
What lands on your desk, and what does not
A shorter day, arrived at honestly. What reaches you is what the standard says should reach you, presented with whatever it needs in order to be decided in one pass rather than opened, deferred and reopened. What does not reach you was handled, and the handling is visible.
Underneath that, the artifact that makes the rest legitimate: a written statement of what matters, in your words, that anybody applying it can be held to. It is not a document you will read often. It exists so that the judgement being exercised on your behalf is yours rather than somebody else’s taste, and so that when it turns out to be wrong there is something to correct instead of somebody to blame.
The filter is the whole job
It is tempting to think of this function as throughput — a lot of small things dealt with, so fewer of them land on the owner. Throughput is the visible part and it is not where the difficulty is. The difficulty is that handling a queue means continuously answering a question with real consequences: does this need the owner, or does it not?
Get that wrong in one direction and the function has achieved nothing — everything still arrives, just later and with a summary attached. Get it wrong in the other and something that mattered was absorbed quietly by somebody who did not know it mattered. The second failure is worse and much harder to see, because a thing that was handled leaves no trace of having been a near miss.
Which is why the rule has to exist in writing and has to be yours. A desk improvising the filter is making commercial judgements about your business on the basis of pattern-matching, and it will be right most of the time, which is precisely what makes the occasional miss so expensive to detect. A desk applying a stated rule is doing something you can inspect: you can read the rule, look at what it held, and disagree with the rule rather than with a person’s instincts. That is the difference between delegating a function and hoping about one.
What makes a rule worth having
Most attempts at this fail in the same way. The rule gets written as a set of categories — suppliers, homeowners, insurers, crew — and categories turn out not to predict importance at all. A supplier calling about a delivery slot is routine; the same supplier calling about credit terms is not, and no category-based rule tells the two apart.
The rules that work are written around consequence and reversibility. What happens if this waits until Thursday? Can it be undone if somebody gets it wrong? Is there a date attached that belongs to somebody else? Those questions can be asked of anything that arrives, by somebody who knows nothing about the sender, and they sort a queue far more reliably than a taxonomy of who is calling.
A rule worth having also names its own edges. A standard that covers everything is a standard that has been written vaguely enough to cover everything, and it will be applied inconsistently for exactly that reason. A good one is explicit about what it does not decide, which produces a small, honest stream of genuine questions instead of a large stream of low-confidence guesses. Over the first few months that stream gets shorter, because each question answered once becomes a clause.
Everything held stays recoverable. Held is not absorbed. Anything the rule kept away from you is somewhere you can look whenever you want, which is what makes the arrangement auditable rather than a matter of confidence, and what lets a wrong rule be found by inspection instead of by an unpleasant surprise.
The department around this queue
This is one desk inside Administrative Support, and the limits that govern the whole department are set out there rather than repeated here — including the one that bears most directly on a desk acting at your direction, which is where preparing something stops and committing the company begins. This page covers only the queue and the standard it is run against.
What owners ask before handing this over
What does this desk actually decide?
Only what the rule already decided. The value of the function is that a large volume of small judgements get made consistently and quickly, and consistency is only possible against a written standard — so the first piece of work is getting that standard out of your head and onto a page. After that, the desk applies it. Anything the rule does not cover comes to you as a question, and that list of uncovered cases is itself useful, because it is a map of what you have never actually decided.
How is this different from just having somebody sort my email?
Sorting is about the medium. This is about the queue, wherever it arrives from — a supplier chasing on the phone, a general contractor asking for a document, a request that came through a form, a question from your own crew. The inbox is one input among several, and it has a desk of its own. What this function holds is the single ordered list of things that currently want your attention, and the rule that decides what belongs on it.
I do not really have priorities written down. Is that a problem?
It is the normal starting position and it is most of the first month’s work. Almost every owner has priorities that are perfectly real and entirely undocumented, which is workable while they are the only one applying them and stops being workable the moment anybody else does. Writing them down is uncomfortable mainly because it surfaces the cases you have been deciding inconsistently, which is worth knowing regardless.
What if you hold back something that turns out to be urgent?
The rule was wrong, and the rule gets changed. That framing matters. If a miss is treated as a lapse of judgement by whoever was on the desk, nothing improves and everybody gets more cautious, which reverses the whole point by pushing more back to you. If a miss is treated as a gap in the standard, the standard closes and the same thing does not recur. Every held item is visible, so this is a question you can audit rather than trust.
Can you speak to people on our behalf?
Correspondence in your company name, at your direction, within the scope you set — yes, and that is most of what removes load. Committing the company to anything is a different act and it is not one this desk performs; the department page above sets out that limit and the rule it is drawn against. In practice the split is clean: chasing, confirming, scheduling and answering from a document are ours, and anything that changes what your company has agreed to is yours.
Does this go away if we grow and hire internally?
It usually converts rather than ends. The written rule and the record of what was held and why are exactly the material somebody internal needs to take it over, and they are the two things a company that has never run this function formally does not have. Handing over an undocumented queue is how the concentration reappears in a new person, which is the outcome worth avoiding.
No register records how attention is spent
The pages on this site normally close with the primary sources they argue from. This one closes without any, and the absence is a position rather than an oversight. No external body governs how the owner of a business organises their own attention — which correspondence they see, what order they see it in, what gets held back. There is no filing, no register and no standard to cite.
What it is held to instead: The owner's own stated priorities, applied consistently, and discretion about everything that crosses the desk.
Try writing the rule down in ten lines
If it comes out as a list of who is calling rather than what happens if it waits, that is the reason nobody else has ever been able to apply it.