Ask Foreman

Ask it the jobsite way.

Pick the situation first, then choose Fast, Clean, or Formal wording. Keep the big script bank underneath the simple doorway.

Year pathsWhat belongs in 1st, 2nd, 3rd, and 4th year.Measuring guideOpenings, offsets, rod lengths, VAVs, access, prefab notes.Script bank523 scripts with Fast, Clean, and Formal tone modes.

Simple rule

First years start with measuring, tools, layout, material, and clear questions.

Crane picks, rigging, seismic bracing, grease duct, rated assemblies, and major field changes stay in 4th-year / qualified-person supervised territory.

Situation first

What are you trying to ask?

Do not start by browsing 523 scripts. Pick the situation, then choose Fast, Clean, or Formal wording once the matching cards load.

I messed upDamage, wrong cut, wrong material, or install mistake. Something does not fitAlignment, elevation, reducer, flex, or support issue. Red-zone / rated issueDamper, grease, rated wall, seismic, structure, or stop-work. Print does not match fieldRevision, clash, missing elevation, submittal, or trade conflict.

Need words?

Script bank by apprentice year

Default view starts with 1st-year basics. Each script now gives Fast, Clean, and Formal versions so the ask fits the jobsite culture.

523 scripts

Tone modes

Same field ask, three jobsite versions.

Pick the tone that fits the foreman, the moment, and the paper trail. Fast is for quick text. Clean is for normal foreman talk. Formal is for notes, punch, or documentation.

Fast / JobsiteShort, direct, no corporate paragraph. Best when the lead already knows the area.

Clean / ForemanClear and professional. Best default for asking before cutting, covering, changing, or reworking.

Formal / DocumentMore complete wording for punch notes, emails, red-zone issues, or project record.

Loading scripts…

Field use: Educational aid only — not job approval. Drawings/specs, manufacturer instructions, employer policy, foreman direction, and AHJ/local code win. Safety Terms Privacy

Beta feedback loop

Help shape TinnerFlow without opening a dead forum.

Found a missing field problem, bad search phrase, or jobsite wording TinnerFlow should understand? Send it cleanly. Want early updates or to help later when the first real trade circle forms? Join the beta.

Submit missing field problem Join beta