Procedure: Preparing a grant, award or challenge application. Revision 3 — October 22, 2026. Index: https://ancreationoffice.com/sop.txt Kept by: b-government-desk. May write: working files local (one application folder per application, AN-Creation//government/YYMMDD-/, the opportunity's row in opportunities.csv, rows on the action log, and the correspondence log). Publish application-tracker and lead-one-pager per the locked template. Publish by the office-save steps (https://ancreationoffice.com/office-save.txt). Never read Drive for working state. Goes with: https://ancreationoffice.com/government-desk.txt , https://ancreationoffice.com/sop-grant-search.txt , https://ancreationoffice.com/sop-defense-rd.txt , https://ancreationoffice.com/sop-gov-profile.txt , https://ancreationoffice.com/sop-source-check.txt , https://ancreationoffice.com/principle-only-the-government-says-no.txt Read this when the owner picks an opportunity to apply for, and every conversation while an application is open. WHY THIS EXISTS Applications are lost on small things: a missed letter-of-intent date, a page limit, a required form, a section answered the way a template says instead of the way the solicitation asks. Drafts also fail when they claim something the applicant cannot back. This builds the application from the solicitation's own words, keeps every date in front of the owner, and drafts only from what the owner has said and approved. 1. READ THE OFFICIAL TEXT FIRST Open the solicitation, the program's instructions and any amendments, and record each with its date read. From them, not from memory or a template, write checklist.csv in the application folder: every required section, form, attachment and registration; page and word limits; formatting rules; who must sign; how and where it is submitted; and every date (questions due, letter of intent or pitch, registration, the deadline, its time zone). If anything is unclear, it becomes a question for the program office (QUESTIONS). State each requirement again against the full text, what the profile does not yet show, and the route that would meet it (principle-only-the-government-says-no.txt). When no path is left, say "From what I can see, I can't find a way to do this", list what was checked, name the office, and do not draft. 2. THE CALENDAR Work back from the deadline: registrations that aren't done (they come first; a bid or application does not count on SAM.gov until the Entity Status Tracker says active, sop-gov-profile.txt), the letter of intent or pitch, the questions date, a full draft, the owner's read-through, a final check, and submission with a margin of at least two working days before the deadline (portals slow down near deadlines). If the lead time a registration page states runs past the deadline, say so, give the route the pages still allow (a later cycle, a teaming step the solicitation allows), and when none is left use the referral wording. Each date goes on the action log and is mentioned at the start of each conversation while the application is open. An amendment that moves a date replaces the old date on the checklist and the calendar the same turn. 3. THE DRAFTS (starter drafts the owner rewrites and approves) Draft section by section, in the order and under the headings the solicitation uses, answering what each section asks: - From what the owner has said, the profile, and, for an invention, current copies of the Project Manager Bot's sheets (by office-handoff; never retype its numbers). - Plain, specific and checkable: what the problem is, what they'll do, how they'll know it worked, who does it, what it costs, what happens after. - Every claim is one the owner can back. No invented results, data, partners, letters, team members, customers or market figures. A number nobody has given stays a visible blank: "[need: number of test units, from you]". - A budget only from figures the owner gives or quotes they have, built in the format the solicitation requires. - Within the limits on checklist.csv, checked before each draft goes to the owner. - Certifications only as the profile's held rows: a current certificate plus its date. Expired, submitted, approved pending, applied, in progress and pending are not held (sop-gov-certifications.txt). Each draft is a dated file in the application folder; the owner's approved version is marked as approved, with the date. 4. QUESTIONS Questions for the program office or the challenge sponsor are drafted for the owner to send, before the questions date, through the channel the solicitation names. Answers published for everyone (questions and answers, amendments) are read and filed, and the checklist is updated the same turn. A new due date in an amendment replaces the old one. 5. BEFORE SUBMISSION - Re-read the solicitation and every amendment against the final draft; tick each checklist row with where it is met. - For a challenge or any submission that shows an idea: the idea-ownership check (sop-grant-search.txt) and, for an invention, the patent decision first. - Certifications and representations in the application (size, ownership, the requirements the solicitation lists) are the owner's, checked against the profile's held rows; never filled in by the bot. - Say once: "Check this against the solicitation before it goes in; your name is on it." 6. SUBMISSION (the owner does it) The owner submits through the official portal with their own account, after a yes for that submission. The final as submitted, the confirmation and its date and time go into the application folder and the correspondence log. Status "submitted" in opportunities.csv. The bot does not submit. 7. AFTER - Awarded: an award is a binding agreement. Before the owner signs, an attorney or a free APEX Accelerator advisor reviews it (principle-rigor-scales-with-money.txt; library: apex-help). Put its reporting dates on the calendar. For an invention, tell the Project Manager Bot by office-handoff. - Declined: ask the funder for the reviewers' comments if the program offers them; file them; record the reason; note what to change next cycle. A decline is information (principle-fail-forward-faster.txt). Never say an application will win. DONE WHEN The checklist is complete from the official text, every date is on the calendar, an amended date has replaced the old one, the drafts are approved by the owner, the final matches every checklist row, the owner has submitted it, and the submission and its confirmation are filed.