Most contractors will accept an agent drafting a quantity list. Far fewer are comfortable with one anywhere near a lien waiver or a delay notice, and they are right to be careful. Whether the agent touches these documents is the wrong question. Which part of each one it touches is the useful one. Each document below is split into three zones: what the agent drafts, what it flags for a person to decide, and what it never touches.
Lien waivers
What it drafts. Every pay period, the agent assembles the waiver package from the pay application: the sub's name, the project, the through date, the amount paid to date and the matching form, conditional or unconditional, as the contract requires. It fills the blanks from the accounting record and puts the package in a review folder.
What it flags. It flags a waiver whose amount does not match the payment recorded, a waiver requested before the check has cleared, a sub whose prior waiver covers a different through date, and any sub on the list who has not returned a waiver two days before the pay application is due. The accounts payable person decides what to do about each.
What it never touches. It never signs a waiver, never changes a conditional waiver to an unconditional one, and never marks a waiver as received on its own say. The line between conditional and unconditional is where a contractor gives up a right to be paid, and a person with the check in hand makes that call.
Delay notices
What it drafts. The agent reads the daily logs, the schedule update and the weather record, then drafts the notice: the activity affected, the dates, the cause as recorded, the contract clause that requires notice and the days claimed if the logs support a count. It attaches the log entries it relied on.
What it flags. The most useful thing it does is watch the clock. Notice clauses carry deadlines measured in days from the event, and the agent flags every logged event that has no notice drafted and sits inside three days of its window. It also flags a draft where the cause in the log does not match the cause the contract recognizes.
What it never touches. It never sends a notice. It never assigns fault, never writes a sentence that admits responsibility, and never decides how many days to claim when the logs conflict. The project manager sends, and the project manager's name is on it. The rules also differ by contract and by state, which is another reason a person reads the clause.
Scope letters
What it drafts. From the takeoff, the spec sections and the bid addenda, the agent drafts an inclusions and exclusions letter for the trade package: what is in the bid by drawing and spec reference, what is excluded, the alternates and the assumptions. It writes in the estimator's own phrasing, drawn from past letters.
What it flags. It flags a spec section the takeoff never touched, an addendum that changed a quantity after the letter's date, and an exclusion that conflicts with a requirement in the general conditions. These are the lines where scope disputes start six months later.
What it never touches. It never changes a price, never adds a legal term the firm has not already used, and never sends the letter. Anything that moves money or shifts risk stays with the estimator.
The pattern across all three
The agent does the assembly and the watching. A person does the committing. Each document has a point where the firm gives something up, such as a right to payment, a position on fault or a price, and the boundary is drawn there every time.
A practical test is to read a draft and ask what changes if this goes out unread. If the answer is nothing, the agent can have the task. If the answer is a claim, a waiver or a number, the task is still a person's. Put that list on one page, hand it to the office, and revisit it each quarter as the firm grows comfortable with the drafts.