Administrative support
Administrative support for roofing companies
Inboxes, calendars, documents and written procedure — held as a department, so one person stops being the route everything has to take.
In most roofing companies of any size there is exactly one person through whom everything eventually passes. Not because anybody designed it that way, but because they were there first, and every process that grew afterwards grew a connection back to them.
That arrangement is invisible while it works. The owner knows where the warranty documents are, remembers which supplier the account was opened with, and can answer a question from a foreman in eleven seconds because the answer is already in their head. Nothing about that looks like a problem until the company grows past the point where eleven seconds, repeated, is a working day.
What makes this department unusual is that its failure has no incident attached to it. There is no missed deadline to point at, no lost job, no angry call. There is only a slow substitution of the owner’s attention for systems the company never built, and the cost surfaces as everything else being slightly later than it should be.
This department covers the desks that take that load: general administrative work, owner and executive support, email and calendar management, documentation, data entry and the writing of standard operating procedures. The sections below set out how the concentration forms, what a week actually looks like once it is held elsewhere, and the point at which handling a document stops and committing the company begins — a line drawn by federal rule rather than by our own caution.
-
100+
Contracting companies supported
-
9
Back office departments
-
12
Platforms supported
-
Roofing only
The hours an owner spends inside an inbox appear on no job cost, in no report, and against no line of overhead.
Get in TouchHow one person becomes the only route
The concentration is not a decision. It accumulates, and each individual step is sensible at the time it happens, so the shape only becomes visible once it has finished forming.
It usually begins with the mailbox. A single address handles suppliers, homeowners, insurers, the accountant and whatever arrives from a general contractor, and because it handles all of them it becomes the place where the company’s memory lives. Documents are not filed anywhere; they are findable by whoever can remember the sender and roughly the month. That works precisely as long as one person is doing the remembering.
The calendar concentrates next, and for a subtler reason. Anyone can add an appointment, but only one person knows which of two overlapping commitments actually matters, so in practice only that person is trusted to resolve a conflict. The calendar stops being a schedule and becomes a queue waiting for a particular pair of eyes.
Documents follow the same path in a slower form. A signed contract exists in an inbox, a photograph of a permit exists on a phone, a warranty registration exists in a confirmation email, and none of these is wrong, exactly — each is retrievable. The problem is that retrieval is a personal skill rather than a company capability, and skills leave when people do.
Procedure is the last thing to concentrate and the most expensive. Every established company has procedures; most have never written them down, because the person who knows them has never needed to read them. That is tolerable until somebody new has to do the work, at which point the company discovers it has been running on recollection and has no way to transfer it except by having the busiest person explain things repeatedly.
None of these produce a crisis. They produce a company in which growth creates more work for exactly one person, and where the honest answer to why an owner cannot take a week away is administrative rather than commercial.
A week measured in interruptions
The rhythm here is not a lifecycle with stages. It is a set of recurring moments where attention gets consumed, and the useful question is which of them genuinely need the owner.
The morning triage nobody scheduled
Whatever arrived overnight gets sorted into things that need a decision, things that need an action and things that need only to be filed. Done as a desk, this takes a defined slot and produces a short list. Done by an owner between other work, it expands to fill the morning and still leaves the filing undone, because filing is the part with no deadline attached.
The question that could have been answered from a document
A large share of internal questions are requests for information that already exists somewhere. Every one of those routed to a person instead of a record is a small tax, and the tax is paid by whoever is most likely to know — which is the person whose time is worth the most. Making the record findable is what removes the question, not answering it faster.
The commitment made verbally and recorded nowhere
Agreements to visit, to call back, to send a quote and to hold a date are made constantly and captured inconsistently. They surface later as a homeowner who was expecting something, and the company has no way to know whether the expectation was ever real. A desk that writes commitments down as they are made converts a category of dispute into a category of record.
The end of the week, when the filing was going to happen
Documents accumulate through the week against an intention to organise them on Friday, and Friday is reliably the day that intention loses. Filing done continuously costs almost nothing; filing deferred becomes a project, and projects get scheduled against a week that is already full.
Where our authority over a record ends
Two limits govern this department, and both are drawn by rules that exist independently of any arrangement between us. They are worth stating precisely, because a desk that handles documents is close enough to the boundary that vagueness would be a kind of claim.
Preparing a document is a different act from executing one. Under 15 U.S.C. 7001, with respect to any transaction in or affecting interstate or foreign commerce, a “signature, contract, or other record relating to such transaction may not be denied legal effect, validity, or enforceability solely because it is in electronic form”. An electronic signature is therefore not a lesser instrument or an administrative formality — it commits whoever applies it, exactly as ink would. That is the reason this desk assembles documents, routes them, chases them and files them, and never applies a signature. Committing the company belongs to whoever holds the authority to commit it.
Retention is not one rule, so it cannot be one decision. Two federal rules illustrate how far apart the treatments sit. At 29 CFR 1904.33 the period is stated outright: “You must save the OSHA 300 Log, the privacy case list (if one exists), the annual summary, and the OSHA 301 Incident Report forms for five (5) years following the end of the calendar year that these records cover.” A retention calendar can be built directly against a rule shaped like that.
At 26 CFR 1.6001-1 there is no period at all. Records “shall be retained so long as the contents thereof may become material in the administration of any internal revenue law”. That is a materiality test rather than a clock, and applying it to a particular document is a judgement about that document.
Which is why this desk holds records and does not act as the legal records custodian for them. Custodianship means deciding which treatment a given record falls under and answering for that decision; those determinations sit with you and your advisers. What we do is make the holdings complete, organised and visible, so that when the question is asked it can be answered from an inventory instead of from memory — and so that a schedule you set is actually followed rather than intended.
This describes the limits of our own work and the rules those limits are drawn against. It is not legal advice, it makes no determination about which rules reach your company or which records they cover, and obligations differ by circumstance. Those questions belong with your own counsel or accountant.
The work this department holds
Separable, and more independent of one another than in most departments here — a company can hand over documentation alone, or the inbox alone, and get the benefit of that piece without the rest.
A company where the owner is the only route has an administrative ceiling, and it is usually lower than the commercial one.
Get in TouchWorking inside the systems you already have
In your instance, under your structure. Documents that live somewhere only we can reach would reproduce the original problem with a different person at the centre, which is the opposite of the point. Where a job management platform already holds the filing structure, we work in it; where the useful record is a shared drive, we work there.
- JobNimbus
- AccuLynx
- Buildertrend
- CompanyCam
- ServiceTitan
Roofing Back Office is not affiliated with, endorsed by, or certified by any software vendor named on this site. All product names and trademarks are the property of their respective owners.
Taking this on
An inventory of where things currently are
Before anything moves, we establish what exists and where — including the documents that live in a mailbox, on a phone, or in the memory of one person. This step consistently surprises owners, and it is the reason a migration attempted first tends to relocate the disorder rather than end it.
Escalation and filing rules, written and signed off
What we handle without asking, what gets summarised, what goes straight to you untouched, where each class of document is filed and who is allowed to see it. These are your decisions; our contribution is forcing them to be made explicitly and then holding to them.
A parallel period before the desk holds anything alone
The desk runs alongside the current arrangement for an agreed stretch, so disagreements about judgement surface against real correspondence rather than in a meeting about hypotheticals. After that the routine is ours to run, and what we produce is a record you can inspect at any time.
Roofing paperwork has its own shape
The document set is unusually varied for a company of this size. A roofing business generates supplier documents, insurer correspondence, municipal permits, manufacturer warranty registrations, subcontractor paperwork and homeowner agreements, and each of those has a different counterparty with a different idea of what a record should look like. Very few businesses of comparable headcount deal with that many document classes.
Timing is compressed in a way that punishes deferral. A residential roof is often sold, permitted, built and closed within a period measured in weeks, so a document not captured while the job is live is being reconstructed almost immediately rather than eventually. The window in which filing is cheap is genuinely short.
Seasonality then removes the slack precisely when the volume arrives. The administrative load rises with production, and the capacity available to absorb it does not, because the person absorbing it is also the person handling everything else that a busy season generates. Deferral compounds in the months where it is least recoverable.
And the counterparties are asymmetric. A manufacturer, an insurer or a municipality each has procedures, records and staff dedicated to the exchange, and on the other side of it is often one person doing this alongside four other jobs. Written procedure is what makes that exchange survivable, which is why the least glamorous desk here is the one that changes most.
Questions that come up when the desk changes hands
Does this mean you get access to the owner’s email?
A defined part of it, on terms you set before anything is touched. Most arrangements start with a shared or delegated mailbox rather than the personal one, and with a written list of what gets handled, what gets summarised and what gets forwarded untouched. The point is not to read everything. It is to make sure that the things which need an answer get one without waiting for a gap in somebody’s day.
Who decides what is important enough to escalate?
You do, in advance, and we write it down so the decision survives a busy week. Escalation rules are the single most useful artefact produced in the first month, because they force a set of judgements that had previously lived in one person’s head into a form somebody else can apply consistently. They also get revised — the first version is never quite right.
Can you sign things on our behalf?
No, and the section on authority below explains why that limit is drawn where it is rather than being a matter of caution. We prepare documents, route them to whoever holds the authority to commit the company, track whether they came back, and file them once they have. The act of signing stays with you.
What happens to our filing when we already have three systems?
The first pass is an inventory rather than a migration. Knowing where documents actually live — including the ones living in an inbox and a phone — is usually more valuable than consolidating them, and consolidation done before the inventory tends to move the mess rather than resolve it. Once the map exists, a structure gets agreed and new documents land in it from that day.
Are you going to write our SOPs for us?
We draft them from how the work is actually done, which means watching it and asking, then handing you something to correct. An SOP written from the outside describes an imaginary company. The value is in the drafting and maintenance burden coming off you, not in the document arriving with authority it has not earned.
How long should we be keeping all of this?
That question has more than one answer depending on the record, which is exactly why it is not one we settle for you. The section below cites two federal rules that treat retention completely differently — one names a period in years, the other names none. We hold documents to whatever schedule you or your advisers set, and we make the holdings visible so the question can be answered rather than guessed at.
What does calendar management actually change?
Mostly it changes who absorbs the friction of a change. A moved supplier meeting or an inspection that shifts by a day is trivial to reschedule and expensive to notice late, and the noticing is the part that gets skipped when the calendar belongs to whoever is already busiest. Holding it as a desk means conflicts surface while there is still room to move.
We are small. Is there enough here to be worth it?
The honest answer is that it depends less on company size than on how much of the administrative load currently routes through one person. A smaller company where the owner is the only route is often a clearer case than a larger one with two people already sharing it, because the constraint is attention rather than volume.
The rest of the back office
- All nine departments The other functions a roofing back office absorbs, each with the failure it prevents.
- Customer Support The calls that would otherwise arrive in the same inbox as everything else.
- Estimating and Project Support Where a document stops being correspondence and starts being a priced scope.
- CRM and Job Management The system of record this desk keeps writing into, and who keeps it truthful.
- Compliance and Documentation The subset of documents that carry a date somebody else is counting.
- Finance and Bookkeeping Where a filed document becomes a ledger entry somebody can reconcile.
- HR and Recruiting Personnel files, which follow a different retention logic from job files.
- Working in JobNimbus Documents and job records attached where the rest of the company looks.
- Working in Buildertrend Document storage that sits alongside schedules and purchase orders.
- Every platform we work in The filing structure stays in your instance; we maintain it rather than mirror it.
- Owner resources Longer pieces on the administrative load of running a roofing company.
- About Roofing Back Office Who runs this, and why the roofing work got its own brand.
Authorities named on this page
Each was fetched and read while this page was being written, and every clause shown in quotation marks above was copied out of the document it is attributed to. Where a remembered phrasing disagreed with the text, the text won.
- 15 U.S.C. 7001 — General rule of validity — U.S. House of Representatives, Office of the Law Revision Counsel
- 29 CFR 1904.33 — Retention and updating — U.S. Office of the Federal Register (eCFR)
- 26 CFR 1.6001-1 — Records — U.S. Office of the Federal Register (eCFR)
Stop being the only route a question can take
A half-hour conversation is usually enough to establish which parts of an inbox and a calendar could reasonably sit with a desk, and which genuinely need the owner. Both answers are useful.