Gate. GIS coming online / teaming only until the partner gate is on; ASG wraps scope, narrative, accessibility, and docs. Not hydrology, not a PE seal, not EPC.
The opinion behind it
A map that cannot be read, or a story nobody can pick up after you leave, is not communication. The wrap is the product; the seal is not ours to give.
Same method as the rest of the firm: Understand → map → improve → evidence and a handoff.
- What you already haveNotes, existing maps, the file cabinet.
- The wrapScope, narrative, accessibility, docs. GIS via teammate when the drawing is the work.
- What a room can useStoryMap or inserts, stakeholder packet, turnover notes.
- HandoffYou keep the file. Not hydrology, not a PE seal, not EPC.
Four stacked cards, top to bottom. What you already have comes in first — notes, existing maps, the file cabinet. ASG wraps scope, narrative, accessibility, and the document pack; GIS production, when the drawing itself is the work, is a named teammate and stops at that wrap. What a room can use is a StoryMap or insert set, a stakeholder packet, and turnover notes. The last card is the handoff: you keep the file. Nothing on this sheet is a hydrology model, a PE seal, or an EPC package.
Named outcomes4 things you keep
- A one-topic StoryMap wrap, when the GIS partner gate is on
- A named hazard-set wrap, when the GIS partner gate is on
- Stakeholder evidence a meeting can stand on
- Turnover docs the next person can actually use
Named consultingin resilience & technical communication
StoryMap packages
Coming online / teaming only. No public StoryMap NTE while the GIS partner gate is off.
Govcon capture as advisory method
Honest bid or no-bid. A no-bid is a deliverable. No invented past performance.
Named startersResilience starters — scope still agreed in writing — the scope sheet
One-topic StoryMap
Coming online / teaming only
GIS production is not a live public offer. No priced StoryMap NTE until the partner gate is on.
Multi-map / hazard set
Coming online / teaming only
A set, not a program. Not hydrology, not a PE seal. No public NTE while the GIS partner gate is off.
What this covers7 areas, and where each one bites
- One-topic StoryMapOne topic, narrative and accessibility wrap, a written bound when the GIS partner gate is on. The meeting is the product.
- Multi-map / hazard setA named set, not a program. Bounded in writing. Same wrap, more frames. Coming online / teaming only until the GIS partner gate is on.
- Stakeholder evidenceThe packet a meeting can stand on, sourced, with the gaps named rather than filled in.
- Turnover documentsWhat it is, where it lives, what not to break, who owns it next. Usable, not ceremonial.
- Bid / no-bid advisoryGovcon capture as method, not a fourth practice: read the solicitation, decide honestly, write to the criteria. A no-bid is a deliverable. No invented past performance.
- GIS via teammateProduction drawing when the map itself is the work. ASG does not claim a live GIS factory.
- The wrapScope, narrative, accessibility, docs. That is the ASG product on this sheet.
GIS production via a named teammate; ASG wraps scope, narrative, accessibility, and docs. Not hydrology, not a PE seal, not EPC.
What holds this workstandards we know, not certifications we hold
- Named topicOne StoryMap or a named hazard set, with a written bound when the GIS partner gate is on. Not a standing GIS program. Coming online / teaming only until then.Map work
- WCAG wrapThe narrative and the document pack have to be usable. The map does not get a pass because it is a map.The wrap
- Sourced packetStakeholder evidence is assembled from what you have. Gaps are named. Analysis is not invented.Meetings
- TurnoverThe next person can pick it up. File map, what not to break, named owner.After the meeting
Where it stopsan empty row is work this firm does not take
How those outcomes get hired
The work is the wrap around a named topic or hazard set: narrative, accessibility, a meeting packet, and turnover — not a hydrology model and not a PE seal.
- StoryMaps and map insertsYou keep: A one-topic StoryMap or a named setOne topic, or a named hazard set, wrapped so a room can actually follow it.
- Stakeholder evidenceYou keep: A sourced packetThe packet a meeting can stand on, without inventing analysis you do not have.
- Turnover documentsYou keep: Turnover notesThe notes the next person needs before the last person leaves.
Capacity
ASG is the wrap: scope, narrative, accessibility, docs. GIS production, when the partner gate is on and the drawing itself is the work, is a named teammate. That split is written down before work starts.
A written bound is the capacity line. If the set wants to become a program, that is a different conversation, and often a no.
Start a conversationStraight answer, no deck. What it takes to start.
One standard, more than one practicewhy these are three sheets and not three firms
- Section 508Section 508 — Accessible Public Systems: we write toSection 508 — Operational Systems & Quality: does not applySection 508 — Resilience & Technical Communication: we write to
- ADA Title IIADA Title II — Accessible Public Systems: we write toADA Title II — Operational Systems & Quality: does not applyADA Title II — Resilience & Technical Communication: does not apply
- WCAG 2.1 AAWCAG 2.1 AA — Accessible Public Systems: we write toWCAG 2.1 AA — Operational Systems & Quality: does not applyWCAG 2.1 AA — Resilience & Technical Communication: we write to
- ISO 9001ISO 9001 — Accessible Public Systems: does not applyISO 9001 — Operational Systems & Quality: we write toISO 9001 — Resilience & Technical Communication: does not apply
- NQA-1 / App BNQA-1 / App B — Accessible Public Systems: does not applyNQA-1 / App B — Operational Systems & Quality: we write toNQA-1 / App B — Resilience & Technical Communication: does not apply
- CMMC Level 2CMMC Level 2 — Accessible Public Systems: does not applyCMMC Level 2 — Operational Systems & Quality: we write toCMMC Level 2 — Resilience & Technical Communication: does not apply
- Human sign-offHuman sign-off — Accessible Public Systems: we write toHuman sign-off — Operational Systems & Quality: we write toHuman sign-off — Resilience & Technical Communication: we write to
Human sign-offThe line that crosses all three. Models may draft; a person decides and signs; the record says who. None of the others survive without it.