Geospatial Engineer

You are the new geospatial engineer. You produce the maps, imagery products, and terrain analysis that commanders use to decide where soldiers live and die — and right now you are the soldier who does not know where the files go.

You came out of AIT at Fort Leonard Wood with a working baseline on ArcGIS, basic imagery exploitation, map production, and coordinate systems — and your section spent the first month proving you actually learned it. Garrison is workstation maintenance, map archive management, plot-request queue work for the battalion or brigade S2/S3, and the unglamorous details every cherry runs. The meaningful work is learning to produce a usable product under time pressure: a terrain analysis overlay for the BUB, a route-study product for the S3, a CADRG map sheet set formatted to NGA product standards. You will also spend real time learning the data pipeline — how geospatial data moves from the NGA servers through PFPS and the GIS workstation and out to the product that the commander's driver prints the night before a mission.

• 01Operate ArcGIS / ArcMap at the analyst level — add and symbolize layers, run basic geoprocessing, export a product to the unit's standard map template, and handle datum and projection conversions (WGS 84, UTM, MGRS) without getting the math wrong.
• 02Exploit basic imagery in Remote View or SOCET SET — load a NITF frame, measure features, annotate with symbols and coordinates, export a finished imagery product at the correct classification and release markings.
• 03Navigate and query the NGA GEMS database and PFPS (Portable Flight Planning Software) to pull current map data, DTED tiles, and CADRG / CIB imagery for a given AO.
• 04Produce a standard finished map product — military grid reference, title block, legend, scale bar, declination diagram, datum note — to AR 115-11 (Geospatial Information and Services) and the unit's product SOP.
• 05Convert between coordinate systems cold — lat/lon decimal, lat/lon DMS, UTM, and MGRS — on a calculator or by hand, and spot a 10-digit grid that is wrong.
• 06Run media management and metadata tagging on geospatial products per the unit's SOP — wrong classification marking on a finished product is a security incident that ends your morning.

• —AR 115-11 — Army Geospatial Information and Services (the governing regulation for the geospatial enterprise; read the first two chapters before you touch a production workstation).
• —FM 3-34 — Engineer Operations (geospatial engineers operate under this umbrella; understand where your section fits in the engineer task organization).
• —ATP 2-01.3 — Intelligence Preparation of the Battlefield (terrain analysis is a core IPB task; your products feed this process whether you report to S2 or S3).
• —STP 21-1-SMCT — Soldier's Manual of Common Tasks, Warrior Skills Level 1 (you are still a soldier before you are a geospatial analyst).
• —NGA product standards documentation — generalized; your section NCO will point you to the current NGA publications that govern imagery and map product specifications.
• —PFPS / Falcon View user documentation — the mission-planning and map-display system most Army units still run alongside ArcGIS.

• —ACFT 500+ minimum; the 12Y community is engineer-coded and the 12-series battalion runs the same physical standard as the sapper — your fitness is noticed.
• —ArcGIS Desktop (ArcMap / ArcGIS Pro) baseline competency demonstrated by producing a finished product the section chief can use without revising the symbology.
• —Coordinate conversion accuracy — zero errors on the MGRS / UTM / lat-lon conversion check the senior NCO runs on new soldiers before they pull a product request.
• —Classification and handling discipline 100% from day one — wrong header, wrong footer, wrong media label on a finished geospatial product is a security incident, not a training opportunity.
• —Annual OPSEC / SAEDA / cyber awareness training current before the brigade suspense; geospatial products are high-value intelligence targets and the NGA relationship raises the stakes.

• —Publishing a map product with the wrong datum. WGS 84 and NAD 27 look identical until a commander drives 200 meters to the wrong grid. You will be in the section chief's office that afternoon.
• —Mis-marking a finished product's classification. Imagery product with a FOUO header instead of the correct classification marking is a security incident on your section's report and your commander's desk.
• —Deleting or overwriting the only copy of a GIS dataset because you did not check the archive SOP before editing. Geospatial data is slow to replace and the brigade S3 does not wait.
• —Delivering a product without checking the print scale. A 1:50,000 product printed at 1:24,000 scale with the wrong scale bar is not usable — and the soldier in the field with it does not know that.
• —Posting any geospatial product, any screenshot of a GIS workstation, or any imagery from the section to personal devices or social media. The grid coordinates and imagery resolution are exactly what a foreign intelligence service wants.

The good cherry 12Y is the PFC whose finished products go to the section chief without a symbology correction and whose coordinate conversions come back right the first time. By month nine the section sergeant is handing them the routine product queue without checking every output. By month eighteen the S2 knows their name because the terrain analysis overlay for the last CTC rotation came back clean on the first pull.

You are the section's production floor. The section chief sends the new privates to watch how you build a product, and the S3 plot request that came in at 1700 lands on your workstation because the SGT trusts you to have it done by 0500.

You own a piece of the section's product workload — route studies, terrain analysis overlays, imagery exploitation packages, and the map sets for the upcoming exercise or deployment. You train the newest PFC on ArcGIS discipline, NGA database navigation, and the product SOP. You are the bench when the section sergeant is in the BUB or at the range — you run the workstation queue, you cover the plot request, you sign for the section's media on the weekend. If you are CPL-pinned, you own the junior soldiers on the production floor and you run the PCI on finished products before they leave the section. You are also working your BLC packet and starting to understand the difference between what the product SOP says and what the supported commander actually needs.

• 01Build a complete terrain analysis overlay from raw DTED and imagery data — slope, relief, vegetation, trafficability, observation and fields of fire — at the quality level the BN S2/S3 uses in the OPORD annex.
• 02Operate SOCET SET or Remote View for a stereo imagery exploitation task — measure building heights, identify defensive preparations, annotate a finished IMINT product to NGA symbology standards.
• 03Run a PFPS / Falcon View mission-planning dataset update for the aviation element or the BN S3 — pull the current DTED, CIB, and CADRG tiles; load the route; export the mission package.
• 04Produce a standard garrison and field map set — 1:50,000 and 1:250,000 series sheets, custom AO products, route cards — formatted to AR 115-11 / NGA product standards with correct classification markings.
• 05Query the NGA GEMS database and the GEOSERVER enterprise pipeline to pull current vector and raster data for a specific AO, and identify what is stale or missing.
• 06Train a junior soldier on coordinate system conversion, ArcGIS layer management, and classification discipline without the section chief having to repeat it.

• —AR 115-11 — Geospatial Information and Services (know it well enough to answer a question from the supported S2 without looking it up).
• —ATP 2-01.3 — Intelligence Preparation of the Battlefield (you produce inputs to this process; understand how your products are consumed).
• —FM 3-34 — Engineer Operations (the geospatial section's position in the engineer and combined-arms team).
• —TC 3-34.80 — Geospatial Engineering (the Army's geospatial-specific technical publication; verify the current edition with your section chief before citing chapter and verse).
• —NGA product standard documentation — the technical specifications governing imagery, map, and vector product formats your section produces.
• —ArcGIS Desktop / ArcGIS Pro user documentation and ESRI training catalog — the tools you master here determine your civilian market value later.

• —BLC graduate (or packet in motion); promotion points stacking through Foundry / geospatial-specific training seats, ACFT, college credit (GIS certifications count), and correspondence.
• —ArcGIS competency at the SPC level means you can run a full terrain analysis product start to finish without the section chief touching the keyboard.
• —ACFT 540+ minimum; the BEB and the brigade engineer office track section fitness aggregate alongside the maneuver line.
• —Product quality rate measurable — zero rework requests from the supported S2/S3 on products you signed for in the last 90 days.
• —Classification and handling record clean — one mis-marked product on your watch is one too many at the section NCOIC level.

• —Coasting on the junior-soldier safety net. At SPC you own the product before it leaves — a datum error or a wrong classification marking on a product you signed for is yours, not the PFC's.
• —Skipping the BLC packet because "the slot is probably next quarter." Slots evaporate. The 12Y promotion cutoff does not move, and the section chief names names at the board prep.
• —Building a GIS product from a cached dataset without checking the NGA metadata for currency. Stale terrain data runs missions into features that were demolished or moved. The S3 finds out on the ground.
• —Letting imagery exploitation products leave the section without a source metadata record. The analyst who inherits your product six months from now needs to know what sensor, what date, and what resolution.
• —Posting GIS data, imagery, or finished map products outside authorized systems. Geospatial products are classified at the product level for a reason — and the imagery itself carries grid precision that is operationally sensitive.

The good Specialist 12Y is the soldier the section chief hands the overnight plot request to and walks away — product is built, symbolized, classified correctly, printed, and on the S3's desk at 0500. He has BLC in motion, a Foundry GIS course completed, ArcGIS and imagery exploitation skills the section relies on, and the section chief already naming him for the first school slot that drops.

You are an NCO now and the production NCO for a geospatial section. The S2 and S3 put products in front of commanders because you built them — and the junior soldiers produce what you taught them to produce.

You own a 3-5 soldier geospatial production section — a BCT geospatial section, a BEB geospatial element, or a division G2 geospatial production cell. You write counselings on the 14th of every month. You run the product queue, you defend the product quality to the supported S2/S3, you train the SPC and PFC on the full production workflow, and you translate the commander's information requirements into a GIS product specification the section can execute. You will spend more time in the S2 and S3 shops than you expected — understanding what a commander actually needs from a terrain product is different from producing a technically correct one. You will also still be at the workstation at 2100 the night before a rotation kicks off because the product queue never clears itself.

• 01Write a clean, legally defensible DA 4856 counseling for a technical performance issue — Plan of Action specific to the geospatial skill that failed, measurable, signed before the soldier leaves your section.
• 02Brief a terrain analysis to the BN S2 / S3 team — OAKOC framework (Observation and fields of fire, Avenues of approach, Key and decisive terrain, Obstacles, Cover and concealment) — and defend each assessment under questioning.
• 03Run a full imagery exploitation task in SOCET SET or Remote View as the production lead — task assignment, exploitation methodology, product review, finished product classification and release — to NGA-compatible standards.
• 04Manage the section's geospatial data library — NGA GEMS database pulls, currency checks, storage and backup SOP, classification accounting — without letting stale data slip into a finished product.
• 05Build a section training plan tied to the unit's upcoming exercise or CTC rotation — ArcGIS skills progression, imagery exploitation refresher, product SOP compliance — and brief it to the section chief.
• 06Counsel a soldier on a technical deficiency (wrong datum, classification error, imagery source mishandled) in a way that fixes the problem and protects the soldier's career.

• —AR 115-11 — Geospatial Information and Services (own this at the section leader level; you are the subject matter expert the S2/S3 calls).
• —ATP 2-01.3 — Intelligence Preparation of the Battlefield (your products feed every IPB step; understand the framework that consumes your work).
• —FM 3-34 — Engineer Operations (the combined-arms context for geospatial engineer support).
• —AR 380-5 — Army Information Security Program (classification handling at the section level is yours to enforce; this is the reg the SSO cites when something goes wrong).
• —AR 600-20 — Army Command Policy (SHARP / EO / leadership accountability; you are an NCO now and the regulation applies to every counseling you write).
• —ATP 6-22.1 — The Counseling Process; ADP 6-22 — Army Leadership and the Profession (the NCO leadership spine).

• —BLC graduate; ALC packet ready when the slot drops — the 12Y community is small and the ALC seat for engineers fills fast.
• —ArcGIS competency at the section-leader level — you run the hardest production task in the queue and you teach the method, not just the result.
• —ACFT 560+ floor — your soldiers do not respect a sergeant who fails the test they are graded on, and the engineer battalion is watching aggregate.
• —Section product quality rate at or above the brigade geospatial standard — no rework requests from the supported S2/S3 on products your section signed for.
• —Promotion points stacking: geospatial training seats, weapons quals, college (CLEP/DSST, GIS professional courses count), and DLC / structured self-development.

• —Counseling soldiers verbally. If the classification error or the datum mistake is not in writing with a Plan of Action, the incident will come back on you when the next inspection hits the section.
• —Signing off a finished product you did not personally quality-check. At SGT, your signature on a product means you checked it — the S3 finds out at the BN CDR's conference table, not at your workstation.
• —Letting the NGA data library go stale under your watch because "the SPC usually checks that." Stale DTED or outdated CADRG imagery in a product that goes to a commander is a section NCO failure, not a junior soldier failure.
• —Running the section's geospatial production on unauthorized software or personal-account cloud services because the workstation is slow. One unauthorized data export is an Army Cybersecurity incident that rides under AR 25-2 and involves the SSO.
• —Going to the S2 officer with section problems before going to the section chief. The chain runs through your section chief; the S2 OIC finds out within a day if you skipped him.

The good SGT 12Y is the NCO the section chief hands the BN CDR's terrain brief to and trusts it will be OAKOC-accurate, classification-clean, and on-screen before the BUB kicks off. His soldiers pass product quality checks, his counselings are in the system, and his ALC packet is in motion. By month eighteen the section chief has his name on the next school slate and the brigade geospatial officer knows his work by the product quality on the S3's table.

The section is yours. The S2 and S3 call you by name, the brigade geospatial officer briefs the BCT CDR off your products, and the junior NCO you are building will run your section when you move to the Army Geospatial Center or the NGA rotation.

You run a 6-12 soldier geospatial section — a BCT geospatial section, a division G2 geospatial production cell, or a deployed theater geospatial element. You sign for the workstations, the licensed software, the NGA access credentials, the classified media, and the product archive. You build the section's quarterly training plan against the unit's upcoming exercise and CTC rotation. You write three or four NCOERs per cycle. You sit in the brigade S2 / S3 huddle and at the BUB. You will brief brigade-level terrain analysis products to O-5s and O-6s, and you will tell a colonel that his route selection will funnel through an observation dead zone — and back it up with the data. You will also still be at the ArcGIS workstation on the night before the rotation because the section chief is the last quality check.

• 01Build a section-level geospatial training plan aligned to the BCT's METL and the upcoming CTC rotation — ArcGIS production proficiency, imagery exploitation, PFPS/Falcon View mission datasets, terrain analysis framework — resourced against the workstation availability and NGA data access windows.
• 02Defend a finished terrain analysis or imagery exploitation product to the BCT CDR or brigade S2/S3 under questioning — know what the data supports, what it does not, and how to say "the data does not answer that question" without losing the room.
• 03Run the section's NGA relationship and database management — GEMS access accounts, data currency verification, product standards compliance, NGA product deliverable archive — and report status to the brigade geospatial officer honestly.
• 04Mentor your SGTs into ALC-ready, section-chief-capable NCOs — to include the honest conversation about the Army Geospatial Center billet at Fort Belvoir and the NGA civilian pathway.
• 05Operate as the BCT's geospatial SME in the brigade S2/S3 planning process — PHL products, named area of interest development, templating support, geospatial data package for the OPORD annex.
• 06Manage the section's cybersecurity posture — authorized software inventory, user account management, media accountability, classified data destruction — in compliance with AR 25-2 and the SSO inspection standard.

• —AR 115-11 — Geospatial Information and Services (the governing regulation; you brief from it when the S2 OIC asks why the section runs the product standard the way it does).
• —ATP 2-01.3 — IPB; FM 3-34 — Engineer Operations; FM 2-0 — Intelligence (you operate at the seam of engineer and intelligence; know the doctrinal context for both).
• —AR 380-5 — Information Security Program; AR 25-2 — Cybersecurity (classification and cybersecurity on a section that handles NGA-derived imagery is a command-level concern).
• —AR 623-3 — Evaluation Reporting System; AR 600-8-19 — Enlisted Promotions (you write NCOERs that pick the next section-chief slate).
• —NGA product standards and NGA geospatial support agreement documentation — verify current versions; the standards change and your products have to match.
• —TC 7-22.7 — Army NCO Guide; ATP 6-22.1 — Counseling Process; ADP 6-22 — Army Leadership (the NCO leadership spine at the section-chief level).

• —ALC graduate; SLC packet ready when promotion to E-7 enters the conversation — the geospatial section chief is a small community and the SFC board notices the SSG who did not build the packet.
• —Section product quality rate at or above brigade standard — zero rework requests from the BCT S2/S3 on products the section signed for in the current training cycle.
• —NGA access credentials and data library current; no lapsed accounts or stale data libraries on the section's production workstations.
• —ACFT 560+ minimum; your CSM watches section-chief aggregate and the engineer battalion compares against the maneuver line.
• —NCOER bullets on the OFFICIAL achievement list — action-result-impact; the brigade geospatial officer and the BCT S2 both know whether your bullets match what the section actually produced.

• —Writing the NCOER as a wish-list. The BCT S2 NCOIC and the brigade engineer SGM read every 12Y NCOER and remember the SSG who inflated the SGT who could not brief OAKOC under pressure.
• —Letting the section's NGA data library drift stale during a high-OPTEMPO period because nobody had time to run the currency check. One outdated DTED tile in a route-analysis product that goes to a BCT CDR is a section-chief failure.
• —Tolerating unauthorized software on the production workstations because it is faster. One AR 25-2 cybersecurity incident traced to your section pulls the NGA access credentials and the section cannot produce for weeks.
• —Hiding section personnel or product-quality problems from the brigade geospatial officer or the BCT S2/S3 to look good. The colonel finds out at the BUB when the product fails; you are in the room.
• —Treating the Army Geospatial Center rotation and the NGA billet as someone else's career move. The senior 12Y NCOs who rotate through Fort Belvoir come back as the section chiefs the AGC and the NGA call by name. Mentor your SGTs toward that path.

The good SSG 12Y section chief runs a section the BCT S2 OIC names to the BCT CDR as "geospatial is solid." His terrain analysis products get cited in the OPORD annex. His NGA data library is current. His SGTs are ALC-board ready. His soldiers re-enlist or transition with ArcGIS credentials the defense-contractor sitting across the NGA office wants on the resume. He has a conversation with the Army Geospatial Center liaison on the next rotation slate.

You are the senior geospatial NCO in a BEB, a division G2 geospatial element, or the Army Geospatial Center at Fort Belvoir. The engineer battalion CSM and the division G2 both call you by name — the BCT CDR knows your products by the quality that arrives before the BUB.

You run the platoon's or staff's entire enlisted geospatial workforce — training, evaluations, schools, NGA rotation pipeline, ARC Professional Certification mentorship, ALC/SLC sequencing, retention, discipline. You build the lieutenant geospatial officer or the supported S2/S3 OIC into a commander who understands what the terrain products actually say. You write four or five NCOERs per cycle that determine who gets the next section-chief billet across the brigade geospatial community. You walk the production floor during CTC rotations and identify broken systems — stale data in the library, wrong product standards, classification shortcuts — before the NGA liaison or the OC/T finds it. You are also still the senior analytic voice when the division G2 wants a terrain assessment the section chief is too junior to defend alone.

• 01Build the BEB or division geospatial section training plan — ArcGIS production progression, imagery exploitation proficiency, NGA product standards compliance, PFPS/Falcon View mission dataset currency — and defend it at the BEB QTB or the division G2 staff briefing.
• 02Write four NCOERs per cycle that the senior rater can defend at the brigade or division NCOER review.
• 03Run the section through a CTC rotation (NTC, JRTC, JMRC) and a real-world contingency mission without losing product quality, data library currency, or NGA access credentials.
• 04Mentor a section chief candidate through the Army Geospatial Center rotation application, the NGA-affiliated billet packet, or the ESRI / GIS professional certification pathway.
• 05Operate as senior geospatial NCO on a joint task force, INSCOM-adjacent element, or NGA direct support team — speak the language of the supported staff and the NGA geospatial support agreement, not just the home unit SOP.
• 06Run a classification or cybersecurity compliance review on the section's production workstations and data systems — AR 25-2 and AR 380-5 audit-ready, NGA access credentials current, classified media accounted for — before the SSO inspection.

• —AR 115-11 — Geospatial Information and Services (you brief from and enforce this regulation at the BEB / division level).
• —FM 3-34 — Engineer Operations; FM 2-0 — Intelligence; ATP 2-01.3 — IPB (the combined-arms doctrine your section supports; senior NCOs know the framework, not just the product).
• —AR 380-5 — Information Security Program; AR 25-2 — Cybersecurity; ICD 705 — SCIF Accreditation if your section operates in a SCIF environment.
• —AR 623-3 + DA PAM 623-3 — Evaluation Reporting System (you write NCOERs that set the section-chief slate).
• —AR 600-8-19 — Enlisted Promotions; HRC promotion board policy memos (the 12Y community is small; SFC-board visibility at HRC level matters).
• —NGA geospatial support agreement documentation, NGA product standards, and Army Geospatial Center (AGC) guidance published from Fort Belvoir — the technical authority your section's products are measured against.

• —SLC graduate; MLC packet built — required for E-8 board competitiveness in the engineer / geospatial community.
• —ArcGIS professional certification (Esri Technical Certification) or GIS Professional (GISP) certification on record — the visible differentiator for senior geospatial NCOs at the SFC board.
• —Section / platoon ACFT pass rate at or above 95%; BEB and BCT engineering community compare aggregate against the maneuver line.
• —Zero unresolved NGA data-currency findings or AR 25-2 cybersecurity incidents traceable to the section under your tenure.
• —NCOER profile clean and defensible — Top Block / Most Qualified rate consistent with actual section performance, verified by the brigade geospatial officer or the division G2 NCOIC.

• —Letting one section chief drift on product quality because you trust him. That is the section the NGA liaison inspection visits, and a classification or data-standard finding under your tenure is yours.
• —Confusing being aligned with the supported commander with giving the supported commander what he wants to hear. The terrain data says what it says — a senior geospatial NCO who bends the product assessment to please the BCT CDR is more dangerous than no terrain product at all.
• —Carrying a peer friction point with the brigade S2 NCOIC or the supported S3 into the BEB. BEB-level NCOERs notice the SFC who cannot work the joint-fires seam.
• —Stopping personal ArcGIS and geospatial technical currency because you are "too senior for the workstation." The junior soldiers and the NGA liaison both see the senior NCO who cannot answer a production question.
• —Going around the BEB 1SG or the brigade geospatial officer to the BCT CSM. You will be wrong and the relationship does not recover.

The good 12Y PSG or senior geospatial NCO runs a section the BEB CSM sends to the hardest rotation because the product quality will not embarrass anyone — terrain analysis clean, data library current, classification discipline maintained. His LT gets command-tracked. His SSGs make SFC. His soldiers get ArcGIS certifications, AGC rotation slots, and the NGA contractor pipeline finds them the week they ETS. He is on the short list for 1SG of an engineer company or a senior geospatial staff NCO billet at Fort Belvoir before he sits MLC.

You are the standard-bearer for the geospatial engineer force. The 12Y soldiers in your formation know whether the section's product standard is right or wrong by watching how you walk the production floor and how you answer the NGA liaison's question about data currency.

As 1SG you run an engineer company or a geospatial-intensive engineer HHC — 80-130 soldiers, the orderly room, the supply room, the geospatial workstation fleet, the NGA access credential management, and the boundary between what the BEB CO needs and what the section chiefs can deliver. As SGM/CSM you advise the BEB or engineer brigade commander on every enlisted decision affecting the geospatial workforce — which billets produce the next section chiefs, which soldiers have the technical depth for an AGC rotation at Fort Belvoir or an NGA direct-support detail, and where the Army's geospatial enterprise is thin. You write fewer NCOERs but they pick the next 1SG and SGM slate for the Army Geospatial Center, the 130th Engineer Brigade, the 20th Engineer Brigade, and the division G2 geospatial chief seats. The Engineer School at Fort Leonard Wood, the Army Geospatial Center, and NGA's Army liaison element all draw from the senior geospatial NCO bench you represent.

• 01Run a 1SG's call that produces actions, not anxiety — accountability, sick call, training, discipline, family readiness, finance, geospatial-specific NGA access and classification compliance, in 30 minutes.
• 02Build the company or BEB geospatial training and tasking calendar the BEB CO can defend at brigade BUB without surprises — NGA data pulls, CTC rotation geospatial support plan, AGC rotation windows, ArcGIS certification pipeline.
• 03Mentor four section chiefs and the senior geospatial staff NCOs as the next 1SG and SGM cohort — to include honest AGC rotation and NGA career conversations, ESRI / GISP certification pathways, and the GS-series civilian pipeline at NGA and defense contractors (Leidos, Booz Allen, SAIC, Maxar, Planet Labs).
• 04Walk the geospatial production floor during a brigade ARTEP or CTC rotation and identify broken systems before the NGA liaison or OC/T does — data library currency, product classification compliance, workstation cybersecurity posture, NGA access credential status.
• 05Run a Red Cross / casualty notification with the dignity it requires — AR 638-8 procedure, Class A uniform, SECARMY-approved script. The 12Y community is small and units know each other; handle it right.
• 06Brief the BEB and brigade command team on enlisted morale, NGA relationship health, geospatial workforce readiness, and the things they cannot see from the conference room — retention indicators, AGC rotation utilization, civilian-pipeline outflow rate.

• —AR 115-11 — Geospatial Information and Services (the governing regulation you enforce and brief from at the BEB / brigade level).
• —AR 600-20 — Army Command Policy (you and the CO own it together).
• —AR 600-8-2 — Suspension of Favorable Personnel Actions; AR 27-10 — Military Justice (you are in the room).
• —AR 638-8 — Army Casualty Program (every senior NCO must know it).
• —AR 380-5 — Information Security Program; AR 25-2 — Cybersecurity (geospatial sections carry NGA-derivative classified imagery; the classification compliance posture is a senior-NCO-level responsibility).
• —AR 350-1 — Army Training; NGA geospatial support agreement guidance and Army Geospatial Center policy issuances; the 1SG Course / USASMA / SMA-published reading list.

• —MLC graduate; USASMA / SGM-A completion before competing for CSM slate.
• —Company or BEB geospatial section NGA access credentials in good standing, AR 25-2 cybersecurity posture inspection-ready, and zero unresolved classification incidents traceable to the senior-NCO level during your tenure.
• —UCMJ rate, retention rate, and SHARP/EO climate index in the top tier of the BEB or engineer brigade.
• —AGC rotation and NGA direct-support pipeline producing 1+ placed soldier per year from your unit — the geospatial enterprise depends on this pipeline.
• —Zero senior-NCO-level integrity incidents — financial, fraternization, OPSEC, NGA data mishandling. One ends the career permanently; on a section with NGA-derivative imagery access, the investigation is interagency.

• —Going public with disagreement with the BEB CO or the brigade geospatial officer. Take the disagreement in the office; walk out aligned in public.
• —Confusing seniority with technical currency. The NGA liaison, the AGC section chief, and the junior analyst briefing current DTED standards are all closer to the truth than the CSM who has not checked a coordinate conversion in three years. Stay current enough to know what you do not know.
• —Stopping personal physical training because you are "too senior." Engineers carry weight and geospatial soldiers are still soldiers — the formation watches.
• —Treating the AGC rotation and the NGA pathway as perks instead of pipeline. Senior geospatial NCOs who fill those billets come back as the enterprise's next technical and leadership standard-setters. Manage the pipeline like it matters, because it does.
• —Letting a section chief run a bad product-quality or classification-compliance climate because he is your guy. The NGA liaison finds it, the BEB CSM finds it, and the AGC at Fort Belvoir hears about it at the next geospatial enterprise sync.

The good engineer 1SG or geospatial CSM is the senior NCO every 12Y in the formation knows by face and reputation. He is the reason a re-enlistment line forms after a hard CTC rotation — soldiers know he pushed for the AGC slot, ran interference on the bad billet, and told the truth about the NGA pathway. The BEB CO trusts him with the worst news at 0200. The section chiefs trust him to fight for the geospatial product standard even when the BCT CDR wants a different answer. His soldiers ETS into NGA analyst seats, Leidos contractor roles, and GISP-certified civilian positions at Maxar or Planet Labs — and they send the next soldier his way for the reference letter.