Templates For construction project admin teams

Hand off a task to someone else, for construction project admin teams

Turn a task you do in your head into a plain hand-off for another person, with the materials listed, the steps written, nothing sensitive left in, and a fresh reader's questions answered.

This is the version for construction project admin teams. The steps and checks are the same as in the general template; each prompt carries one added line about your setting, and the examples are from your kind of work.

Sample results: runs and scores on this page are illustrations while testing is set up. How we test

Bring: The task and how you do it, Who is taking it over

Use This TemplatePrepare a prompt for your own AI chat.

Who it is for: Project coordinators and site administrators who hand a recurring project task, such as the submittal log or the weekly pay application, to a relief coordinator or a new hire.
Time: 20 minutes

Edit this version

Other Formats and Files

The Step 1 chat prompt under Use This Template is the quick start. Choose a full prompt chain, checklist, Claude skill or n8n file when that destination fits your work. Checked Instructions, below, run the whole job with a hard check after every step.

Choose one format

Prompt chain
Copy each step into ChatGPT or Claude, one after another.
Checklist
Follow the steps and check off the checks by hand.
Claude skill
A folder Claude loads, so it follows the steps by itself.
n8n file
Import into n8n and connect your own AI account.

This job also comes as Checked Instructions: the whole job in one set, with a hard check after every step. See the Checked Instructions on the general template.

Using a download:How to use this in n8n How to install a Claude skill

The same job, with and without the template

Sample

This comparison uses the Typical sample. Try an input below for a result guide matched to each sample.

One plain prompt

Turn these notes into instructions for the person covering my submittal log. (The same notes are pasted below.)

Submittal log: instructions

Open the submittal log and add the new submittals.
Update the status of anything that came back.
Chase the architect if things are late.
Send the log to the owner's rep each week.

Tip: Stay on top of it and keep the log tidy.

Problem:It drops the 8-day nudge and the 10-working-day rule, loses the same-day hand-off of revise and resubmit items to Mateo, and never warns about the old copy of the log.

With this template

What this task is

Each Monday you update the project's submittal log and send it as a PDF to the owner's rep by noon.

Before you start

Open the spreadsheet "Submittal Log (current)" on the shared drive. A second copy called "Submittal Log (old)" exists for reference only, so check the name. Have the nudge email template open.

Steps

Search your email for anything with submittal in the subject.
For each new one, add a row to the log with the number, the spec section, what it is, and the date it was sent to the architect.
For each submittal still out with the architect, count working days. The architect has 10 working days to answer. If one is still out after 8 working days, send the nudge email: "Hi Colleen, submittal [number] was sent on [date] and is due back on [date]. Can you tell me when to expect it? Thanks."
When a submittal comes back, enter the result in the status column using only these words: approved, approved as noted, revise and resubmit, or rejected.
Give any revise and resubmit item to Mateo the same day, so he can tell the subcontractor.
Save the log as a PDF and send it to the owner's rep by noon on Monday.

Watch for

Use only "Submittal Log (current)". Count working days, not calendar days. A revise and resubmit result must reach Mateo the same day it comes back.

Stop and ask me if

A submittal has no number or spec section.
A result comes back with a word that is not one of the four.
You cannot reach the architect after sending the nudge.

Still to fill in

ASK: Where is the shared drive, and who gives me access to the log and the owner's rep's email? ASK: Which days are holidays that do not count as working days?

Check:Each piece is hand over, keep or decide first: Every piece of the task has one of the three marks.
Check:The list of removed items is there: The line is there and says none were found.
Check:Nothing sensitive is left in: No password, account number, phone number, address or private detail was found.
For your read:You checked it for private details: Go through it line by line as if it might be forwarded.
For your read:A fresh reader could follow it: Could a new coordinator do the first three steps without asking? Two questions are listed under Still to fill in.

Use This Template

Add your material below. Logic Lab prepares Step 1; you copy it into your own AI and check the answer there. The site does not run the workflow.

Example materialSample

Choose a sample

Typical: Keeping the weekly submittal logEasy: Confirming the Monday dumpster pickupTricky: Uploading the monthly pay application

A short, simple weekly chore with a clear routine and nothing private in it; the hand-off mostly needs the steps written in order.

The task and how you do it (needed)Who is taking it over (needed)Files, links or text you can include (optional)

Step 1 Chat Prompt

Review the exact prompt, then paste it into your own AI. For later steps, use the chat chain in Other Formats and Files.

You are an experienced office manager who is good at handing work over.
The task is a routine on a construction project, such as keeping a submittal log or a daily log, and the person taking it over may be new to the project and to construction.

Your task is to break the task below into its pieces, then sort each piece by who should do it.

The task:
Every Friday by 3 pm I email the hauler's dispatch to confirm the dumpster pickup for Monday. If the dumpster is more than three-quarters full I ask for a swap, not just a dump. Then I tell Mateo the pickup time so he can keep the access road clear.

Who is taking it over: A site assistant who has never done it before

Rules:
- Write each piece as a short action.
- Mark a piece "hand over" if the new person can do it with plain steps, "keep" if it needs your own judgment or permission, and "decide first" if you must make a choice before handing it over.
- Add pieces that you do without noticing, such as checking something first or telling someone afterward.
- Do not write the steps yet. Do not invent pieces that the task does not suggest.

Return one markdown table and nothing else:
| # | Piece | Who | Why |
The Who column must say exactly hand over, keep or decide first.

Send to AICopy and open ChatGPTCopies this result and opens a blank chat. Paste and review it there.

Before Step 2, check: Each piece is hand over, keep or decide first.

What This Sample Should Produce

Tell the site assistant to email the hauler's dispatch by 3 pm each Friday to confirm Monday's pickup, ask for a swap instead of a dump when the dumpster is over three-quarters full, and tell Mateo the pickup time.

A result guide for this invented input, not an AI reply.

Want to see where the materials, steps and checks fit? Watch the general template being built.

The steps, and the check on each

Step 1: Sort the pieces
Split the task into pieces and sort each into hand over, keep or decide first.
Hands back: A table that sorts every piece into hand over, keep or decide first.
Check:Each piece is hand over, keep or decide first
A plain rule. If it fails, run the step again (the n8n file does this for you).
Step 2: List what to have ready
List everything the new person needs in hand, and write any short template that is missing.
Hands back: A list of materials to have ready and any short templates or examples.
No separate check on this step.
Step 3: Write the plain steps
Write the hand-over steps in plain words that someone new can follow without asking you.
Hands back: A plain hand-over note with numbered steps, things to watch for and when to ask.
No separate check on this step.
Step 4: Sweep for sensitive information
Find anything private or risky in the hand-over and replace it with where to ask.
Hands back: The hand-over with sensitive items replaced, and a list of what was removed.
Check:The list of removed items is there
A plain rule. If it fails, run the step again (the n8n file does this for you).
Step 5: Read it as someone new
Read only the hand-over, as the new person would, and list everything missing or unclear.
Hands back: A table of questions a fresh reader would have, each pointing to the exact words.
No separate check on this step.
Step 6: Close the gaps
Answer each question from what you wrote about the task, and mark the ones only you can answer.
Hands back: The final hand-over, ready to give to the person, with a short list of what you still need to fill in.
No separate check on this step.

After the last step

Check:Nothing sensitive is left in
A second look by the AI. If it fails, the run stops.
Check:You checked it for private details
You check this one. If it fails, the run stops.
Check:A fresh reader could follow it
You check this one. If it fails, it is flagged for you.

What you need first

The task and how you do it(needed)
Describe the task and how you usually do it, in any order. Include where things are kept and what goes wrong. Rough is fine.
Who is taking it over(needed)
Say who it is and what they already know about the work.
Files, links or text you can include(optional)
Paste any templates, examples or lists you already have. Leave empty if there are none. Do not paste passwords.

Ways to adapt it

If the task has a risky step (money, deleting things, messaging customers), add a line to the Write step's rules that the person must check with you before that step.
To hand off a task to a team, change "who is taking it over" to describe the team and add a step that says who does what.
After the first real run, ask the person what was unclear and add the answers to the task description, then run the template again.
Keep logins and secrets out of the hand-over file. Give them in person or through your password manager.

Change this version in the Editor. Its added context stays in every prompt and the general template stays separate.

Notes for construction project admin teams

Say what each log, spreadsheet or portal is called, as the project calls it, and which copy is the live one.
Spell out the review times and deadlines that drive the task, such as the days an architect has to return a submittal.
Name the person who gets each result (the superintendent, the owner's rep) by role, and say what to tell them.
A login, a password or an access code does not belong in a hand-off. Say who gives access and leave the rest to that person.

The scoring guide

Sample

Each template check has a criterion marked met or not met; a person must still make the handed checks. (The guides in Quality rate a whole piece of work on three levels.) Under each one is how the example run scored.

Download the scoring guide (Markdown)

Each piece is hand over, keep or decide first
A plain rule
Meets:Every piece of the task is marked hand over, keep or decide first.
Does not meet:A piece has no mark, or another word such as maybe.
Example built from the before and after:Met
The list of removed items is there
A plain rule
Meets:The line Sensitive items removed: is there, with what was taken out or the word none.
Does not meet:The line is missing, so you cannot tell whether anything was looked for.
Example built from the before and after:Met
Nothing sensitive is left in
A second look by the AI
Meets:The final hand-over has no password, login, account or card number, personal phone number, home address or private detail about a person.
Does not meet:Any of those is still in the final hand-over.
Example built from the before and after:Met
You checked it for private details
You check this one
Meets:You read the final hand-over line by line, as if it might be forwarded, and there is nothing you would not want a stranger to see.
Does not meet:You find a detail you would not want a stranger to see.
Example built from the before and after:For your read
A fresh reader could follow it
You check this one
Meets:Someone who does not know the task could do the first three steps without asking you anything.
Does not meet:A new reader would have to ask you what a step means or where something is.
Example built from the before and after:For your read

Example built from the before and after: met 3 of 3, plus 2 for your read

Learn how it works:Hand-offs Adapting a template

Practice:Diagnose and fix

How to write it:How to write a handover note

The same job as a tool:How-to guide builder

Which one fits?

Use Break a project into steps when the work has not started and you need a plan to follow, not instructions for someone taking over.
Use Remove personal information when you have a text that names people and need it cleaned before it moves on.
Use Turn meeting notes into decisions and actions when the text is a set of meeting notes and you want its decisions and actions in a table, not instructions for someone taking over.

Related templates

All for Construction project admin

Plan

Scope a job before you start15 min
Each "done" can be checked by looking, not by feeling

Plan

Draft interview questions15 min
Every question ties to the job description; protected topics are flagged

Write

Rewrite for a different reader10 min
Every fact is checked across; no number added or changed

Last run: October 17, 2026: Example built from the before and after (sample run)
Tools and versions: Example built from the before and after
What was checked: The files, against each tool’s import format, and 1 sample run, each check’s finding recorded.
Version: 1.0
What changed: First release.

Report a problem with this template How we test

Hand off a task to someone else, for construction project admin teams

How it runs

The same job, with and without the template

One plain prompt

With this template

What this task is

Before you start

Steps

Watch for

Stop and ask me if

Still to fill in

Runs and scores

Example built from the before and after

Use This Template

Step 1 Chat Prompt

The steps, and the check on each

Step 1: Sort the pieces

Step 2: List what to have ready

Step 3: Write the plain steps

Step 4: Sweep for sensitive information

Step 5: Read it as someone new

Step 6: Close the gaps

After the last step

What you need first

Ways to adapt it

Notes for construction project admin teams

The scoring guide

Which one fits?

Related templates

Plan

Plan

Write