Construction administration
8 min readAll explainers

Construction administration handoff — a checklist for architects.

What a construction administration handoff package must contain for the architect — an RFI log, an ASI log, a submittal log, and a plan distribution record — the typical 1-3 week cadence before deliverables start landing, how to delegate the inbox churn without dropping deadlines, what week-1 admin support looks like in practice, and how Johnston Admin Management Services runs the package at $45/hour, billed to the exact minute through Clockify.

Written by Johnston Admin Management Services LLC · Virginia HQ, U.S. nationwide.
Section 1

What a CA handoff package actually is

The construction administration phase is the bulk of any project once the bid / negotiation cycle closes and the GC's first notice-to-proceed ships. It is also the phase that runs on paper — RFIs, ASIs, submittals, plan revisions, spec forwards, and the daily round of email between the architect, the GC, and the subs. A “CA handoff package” is the document / log set the architect delivers at the start of that phase. It is what turns “the drawings are out” into “the project is being run.”

Without a coherent CA package, every RFI is an ad-hoc email, every ASI is a re-typed spec change, every submittal cycle is a fresh inbox sweep, and the spec set the GC uses on Day 1 is not the spec set the architect last certified. The package is the operating manual for the project — and it is also the single starting point a CA admin needs to be useful in week 1. The four logs and the distribution record below are the parts of the package that get read every day by someone in the field; everything else (the spec set, the addenda, the contact list) is supporting context for those four.

What the CA package contains

The package delivers four named logs and a distribution record — plus the spec set, addenda, and contacts scaffolding the four logs lean against.

  • RFI log — register for Requests For Information, seeded from the bid-period email, with a numbering scheme and per-question status.
  • ASI log — register for Architect Supplemental Instructions, tied to spec / drawing changes the architect certifies.
  • Submittal log — schedule of every required submittal by spec section, tagged required / submitted / approved / rejected / resubmit.
  • Plan distribution record — per-revision log of who got which drawing set (PDF / print / dwg), when, tied to every addendum reference.
  • Master spec set + addenda + contact list + the per-cycle CAD schedule the architect reviews at each weekly meeting.
Section 2

The four logs — RFI / ASI / submittal / distribution

The four logs are what every CA phase actually runs on. They are the only parts of the package read every day by someone in the field, and they are the only parts that have to stay current for the project to stay on track. Get these four correct, and the rest of the CA package is supporting documentation.

Each log has a specific role: the RFI log is the running register of every question the GC or a sub sends in writing, with a per-question status and a deadline the architect answers against. The ASI log tracks every supplemental instruction the architect certifies — the formal record of any drawing or spec change the architect ships after bid. The submittal logis the schedule the spec set calls for: every shop drawing, product data sheet, sample, and mix design the GC is required to submit, plus the architect's response (approved / rejected / resubmit / approved as noted) on each one. The plan distribution record is the per-revision log of who got which drawing set, when — the audit trail that turns an addendum reference into a verifiable distribution event.

Log #1

RFI log

Every written question the GC or a sub sends, with a running number, a status (open / answered / superseded), a per-question deadline, and the response the architect certifies. Seeded from the bid-period email; the number-1 mistake is allowing the log to drift while RFIs pile up in the inbox.

Log #2

ASI log

Every Architect Supplemental Instruction the architect certifies after bid, with a per-ASI number, an effective date, and a tie back to the spec or drawing change that drove it. The ASI log is what makes a spec change traceable months later when a sub asks “when did this change hit the set?”.

Log #3

Submittal log

The schedule of every required submittal the spec set calls for — organized by spec section (03 30 00, 07 50 00, etc.), each line tagged with the architect's response (approved / approved as noted / rejected / resubmit / received). It is the single source of truth for what is still required before substantial completion.

Log #4

Plan distribution record

A per-revision log of who got which drawing set, when, and in which format — PDF, print, dwg. The record is what makes an addendum reference traceable back to a specific distribution event, and is what the architect cites when a later RFI depends on a revision that has been superseded.

The four logs share a single maintenance cadence — a daily sweep on RFIs (the fastest-moving log), a weekly review on ASIs and the submittal log (the slower, decision-driven logs), and a continuous update on the plan distribution record (every plan revision the architect ships enters the record on the day it ships). Run on the same cadence, the package runs itself. Run on different cadences, the package drifts within a week.

Section 3

Week-1 admin support — three workstreams on a fixed-clock cadence

Week 1 is where the CA handoff package is built. Most architects hit “first deliverable lands” inside 7-14 business days of starting the package, and the work falls into three workstreams that run on a fixed cadence: build the four logs, lock the spec set, and set the inbox cadence that keeps the package current from week 2 onward.

The four-log workstream is the bulk of week 1 — pulling the spec set forward into a searchable index, seeding each log from the bid-period email, formatting the per-revision distribution record, and writing the response-template stubs that will carry the first 30 days of inbox churn. The spec-set workstream (lock the master spec, mark active vs superseded sections, stage the per-cycle CAD schedule the architect reviews every Monday) is shorter but starts in parallel. The inbox-cadence workstream is the daily + weekly + Friday cadence that drives week 2 onward: a daily morning digest of items needing sign-off, a Wednesday mid-week sweep on outstanding submittals, a Friday distribution audit.

The week-1 three-workstream build

The package builds in three workstreams running on parallel clocks.

  • Build the four logs — RFI / ASI / submittal / distribution, seeded from bid-period email, response templates drafted for the first 30 days of inbox churn.
  • Lock the spec set — index the master spec, mark active vs superseded sections, stage the per-cycle CAD schedule the architect reviews every Monday morning.
  • Set the inbox cadence — daily morning digest of items needing sign-off, Wednesday submittal sweep, Friday distribution audit. Week 2 onward the package runs on this cadence.
  • Sign-off the packagewith the architect at the end of week 1 — one “package is live” review meeting that confirms all four logs are seeded, the spec set is flagged, and the inbox cadence is wired.

The first invoice ships at the end of week 1, with the workstreams broken out by minute count per line. Most week-1 handoffs total 8-15 hours of focused admin time on a typical commercial / institutional project, and the steady-state operating cadence drops to 3-6 hours per month once the four logs are current. We run the same package on the firm — at $45/hour, billed to the exact minute through Clockify, with every minute visible on the invoice before the line amount is ever printed. For the full service overview, see our construction administration support for architects.

Section 4

Delegating the inbox churn without dropping deadlines

The single most important decision an architect makes on the CA phase is which parts of the work run in-house and which parts get delegated. The split that works: keep the architectural decisions — the actual stamping, the spec changes, the RFI answers that require judgment — in-house. Delegate the email churn — the inbound RFIs, the distribution confirmations, the spec / drawing forwards — to a CA admin who runs the four logs.

The admin runs the inbox queue: routes each inbound to the right log (RFI / ASI / submittal / distribution), drafts a response template the architect signs off on, attaches the distribution audit to the right revision in the plan distribution record, and surfaces a daily digest of “what needs your sign-off today.” The four logs update as the queue does; the architect reads the digest, signs the few items that need a stamp, and replies — instead of running the inbox cold every morning. The deadline-on-the-floor feeling drops because no inbox item is more than 24 hours old when the digest goes out.

Stays with the architect

Architectural decisions — stamping, spec changes, judgment calls

The seal-bearing work — the actual RFI answers that involve a design call, the spec changes that require a stamp, the RFI-and-ASIs that need a judgment on the project. This is the work the architect trained for; it is the work the client is paying the architect to do.

Goes to the CA admin

Inbox churn — distribution, log updates, response drafts

The email queue — the inbound RFIs that need routing, the distribution confirmations that need logging, the per-day response templates the architect signs off on. The admin does not stamp; the admin runs the inbox queue and surfaces the daily digest of items needing sign-off.

The delegating move works because the four logs are the only artifacts a CA package actually depends on. Once the four logs are kept current, every RFI has a per-question status, every ASI has a per-issue number, every submittal has a per-cycle response, and every drawing revision has a per-distribution audit — and the architect reads the daily digest on the items that need their sign-off, not the inbox on every item. The inbox churn drops from a full-time role to a morning 30-minute review.

Section 5

How the per-hour handoff works — and what we quote

Johnston Admin Management Services runs the CA handoff package from the architect's spec + first drawings forward. The day the spec and the construction-set drawings land in the inbox, we open a Clockify project for the engagement and a recurring weekly task for the steady-state operation. From that point forward every minute we touch the package — building each log, indexing the spec, drafting the per-day response templates, running the distribution audit — logs on its own Clockify line.

Every minute is billed at $45/hour to the exact minute. If 18 minutes go into an ASI log update, you pay for 18 minutes — not a 15-minute block, not a quarter-hour, not a padded estimate. The invoice you receive reconciles line-by-line to the Clockify entries behind it, with no minimum purchase and no surprise billing. Most week-1 handoff packages total 8-15 hours of total admin time on a typical commercial / institutional project; the steady-state operating cadence drops to 3-6 hours per month once the four logs are current.

What the week-1 invoice looks like

Build the four logs + seed from bid-period email

182 min

Lock the master spec + stage per-cycle CAD schedule

96 min

Draft the per-day response templates + sign-off meeting prep

128 min

Set the inbox cadence + distribution audit on every revision

114 min

Architect sign-off review + weekly digest rollout

82 min

Total — 602 min × $45/hr

$451.50

One handoff, one invoice, one $45/hour Clockify-tracked price — every minute visible before the invoice goes out. No padded estimates, no quarter-hour rounding, no minimum purchase, no agency markup.

From week 2 onward the package runs on a smaller monthly recurring for steady-state operation — every minute tracked on the same Clockify cadence, every invoice reconciling line-by-line to the time behind it. We work from the spec set and the construction-set drawings the architect sends, no separate onboarding packet, and we confirm project coverage by zip before the first timer starts. To see the full service menu (CA handoff, CA package maintenance, full-fixture admin support) drop into the services page.

FAQ

Frequently asked questions.

What is a construction administration (CA) handoff?

A CA handoff is the package the architect delivers at the start of the construction administration phase — the bulk of the project once CDs are issued and the bid / negotiation cycle closes. It bundles every document, log, and distribution record the architect and the GC / subs need to run the project through closeout: the spec set, the addenda, the RFI / ASI / submittal logs in their starting state, the plan distribution record, the contact list, and the per-cycle CAD schedule. The package is what turns "drawings are out" into "the project is being run." Without it, RIAs drift across email, ASI numbers get duplicated, and the spec set the GC uses on Day 1 is not the spec set the architect last certified.

What belongs in the architect's CA handoff package?

Four named logs and one distribution record, full stop. (1) The RFI log — a register for Requests For Information, seeded with the in-flight questions from the bid period, with a numbering scheme and a per-question status (open / answered / superseded). (2) The ASI log — a register for Architect Supplemental Instructions, again numbered, with each ASI tied to a decision-traceable spec or drawing change. (3) The submittal log — the schedule of every required submittal the spec set calls for, organized by spec section (03 30 00, 07 50 00, etc.), with each line tagged as required / submitted / approved / rejected / resubmit. (4) The plan distribution record — a per-revision log of who got which drawing set, when, and in which format (PDF / print / dwg), so any later RFI can reference the addendum that supersedes it. Plus the contact list, the per-cycle CAD schedule, and the master spec on the day the bid-cycle closes.

How long does a CA handoff take to set up?

A practical CA handoff package on a typical commercial / institutional project takes 8-15 hours of focused admin work the first week: pulling the spec set forward into a searchable index, seeding the four logs from the bid-period email, formatting the per-revision plan distribution record, and assembling the contact list + per-cycle CAD schedule. Most architects hit "first deliverable lands" inside 7-14 business days of starting the handoff package; the in-flight RFIs and ASIs start getting answered from Day 1, the submittal log starts getting filled in from Week 2, and the plan distribution record stays current from the day the first revision ships. A second-week window is normal — the package is rarely "done" before it stops being a project-critical dependency.

How do you delegate the inbox churn without dropping deadlines?

Delegate the email churn — the inbound RFIs, the distribution confirmations, the spec / drawing forwards — and keep the architectural decisions in-house. The admin runs the inbox queue: routes each inbound to the right log (RFI / ASI / submittal / distribution), drafts a response template the architect signs off on, attaches the distribution audit to the right revision in the plan distribution record, and surfaces a daily digest of "what needs your sign-off today." The four logs update as the queue does; the architect reads the digest, signs the few items that need a stamp, and replies — instead of running the inbox cold every morning. The deadline-on-the-floor feeling drops because no inbox item is more than 24 hours old when the digest goes out.

What does admin support look like in week 1?

Three workstreams, on a fixed-clock cadence. (1) Build the four logs — RFI / ASI / submittal / distribution — and seed each from the bid-period traffic, including any in-flight RFIs the GC already sent. (2) Lock the spec set — index the master spec, mark the active vs superseded sections, and stage the per-cycle CAD schedule the architect reviews at the start of each week. (3) Set the inbox cadence — a daily morning digest of items needing sign-off, a Wednesday mid-week sweep on outstanding submittals, a Friday end-of-week distribution audit that confirms every plan revision sent is showing up in the right log on the right day. Week 1 produces a "package is live" handoff the architect signs off on; Week 2 onward is steady-state operation.

How does the per-hour Clockify-tracked handoff work in practice?

We open a Clockify project on the day the architect's spec / first drawings hit the inbox, and every admin task on the package — building each log, indexing the spec, drafting the per-day response templates, running the distribution audit — logs on its own Clockify line. The first invoice ships at the end of Week 1 with the line items broken out by workstream (logs / spec / inbox cadence) and by minute count per line. Week 2 onward the invoice is a smaller monthly recurring for steady-state operation, billed at the same $45/hour rate, with the four logs current as of the period the invoice covers. Most architects see 8-15 hours of total admin in Week 1, then 3-6 hours per month on a steady-state CA package thereafter.

TL;DR

The 30-second version.

  • A CA handoff package is the four logs (RFI, ASI, submittal, distribution) + the spec set + the per-cycle CAD schedule the architect uses to run the project once the CDs are out.
  • The four logs are the only parts of the package anyone reads every day — every other element (addenda, contacts, spec index) is supporting documentation that backs the four logs.
  • Week 1 builds the package on three parallel workstreams: build the four logs, lock the spec set, set the inbox cadence. Most architects ship a sign-off "package is live" review inside 8-15 hours.
  • Delegating the inbox churn is a one-line move: route every incoming RFI / ASI / submittal into the right log, draft a response template for sign-off, surface a daily digest — and keep the architectural decisions in-house.
  • We run the package on a $45/hour Clockify-tracked cadence, billed to the exact minute, with every invoice reconciling line-by-line to the time behind it.
Who this helps

For architects.

Hand off construction administration with the logs, spec records, and inbox cadence needed to keep project decisions traceable.

Explore support for architects
Send the spec + submittal log, we'll run the CA package

Lock the CA cadence in one inbox handoff.

Drop the spec set, the construction-set drawings, and the bid-period email in the inbox and we'll build the four logs (RFI / ASI / submittal / distribution), lock the spec index, and set the inbox cadence — at $45/hour, billed to the exact minute, every minute visible on the invoice before the line amount is ever printed. Most architect engagements start on a Clockify timer within one business day.

$45/hour · Clockify-tracked · billed to the exact minute
Read next
Architects

The CA package behind every architect's project.

Construction administration for architects: the four logs, the inbox cadence, and the per-hour admin support that keeps the project on the architect's stamping schedule.

Services

The full service menu — $45/hour, billed to the minute.

CA handoff, CA package maintenance, A/R follow-up, full-fixture admin support — Clockify-tracked, exact-minute billing, no minimums. One rate, one time trail, unified invoice.