{"id":21763,"date":"2026-07-24T08:28:09","date_gmt":"2026-07-24T12:28:09","guid":{"rendered":"https:\/\/www.sovra.com\/?p=21763"},"modified":"2026-07-24T13:22:44","modified_gmt":"2026-07-24T17:22:44","slug":"multi-cycle-calls-how-to-run-an-annual-solicitation-without-starting-from-scratch-every-year","status":"publish","type":"post","link":"https:\/\/www.sovra.com\/fr\/blog\/multi-cycle-calls-how-to-run-an-annual-solicitation-without-starting-from-scratch-every-year\/","title":{"rendered":"Multi-Cycle Calls: How to Run an Annual Solicitation Without Starting from Scratch Every Year"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Ask any MPO planner what time of year they dread most, and a lot of them will tell you it’s call for projects season. Not because the work isn’t meaningful \u2014 it is \u2014 but because so much of it feels like reinvention. New spreadsheet. New folder structure. New email chain trying to track who submitted what. Same questions you asked last year, re-typed into a new form. Same follow-up calls to sponsors who can’t find the attachment they uploaded three weeks ago.<\/p>

If that sounds familiar, the problem isn’t your process. It’s that your tools weren’t built for a recurring workflow.<\/p>

The annual cycle is predictable. Your system should be too.<\/strong><\/h2>

A call for projects isn’t a one-time event \u2014 it’s a recurring institutional responsibility, often tied to a fixed programming cycle, federal deadlines, and TIP amendment windows that don’t move. The work repeats. The sponsors repeat. The data you need repeats. What doesn’t need to repeat is the setup.<\/p>

When your submission process lives in a true system of record \u2014 rather than a collection of email attachments, shared drives, and spreadsheet trackers \u2014 you’re not starting from scratch each year. You’re opening a new cycle on top of an existing foundation. Past submissions are still there. Sponsors who applied before can reuse and update their applications rather than rebuilding them. The questions you refined last cycle carry forward. The institutional knowledge doesn’t walk out the door when someone retires or moves on.<\/p>

ProjectTracker is built for exactly this kind of recurring workflow. Calls for projects run on annual or multi-cycle schedules within the same system, so each new solicitation builds on the last rather than replacing it.<\/p>

When a project is selected, it shouldn’t have to be re-entered<\/strong><\/h2>

Here’s a moment that happens in every programming cycle: a project gets selected, and someone has to take the information from the application and enter it into the TIP system. By hand. Again.<\/p>

This is where duplicate data entry costs you real time and introduces real errors. The project name gets shortened. The termini get transcribed slightly differently. The cost estimate from the application doesn’t quite match what ends up in the financial constraint table. Small discrepancies that create big reconciliation problems later.<\/p>

In ProjectTracker, selected submissions push directly into funded projects with no re-entry required. The application data becomes the project record. And because the original submission stays attached to the project throughout its life in the TIP, you always have access to what the sponsor originally proposed \u2014 the stated purpose, the scope, the cost basis. When a project comes back for an amendment two years later and someone asks why it was programmed the way it was, the answer is right there.<\/p>

The form should flex to the funding opportunity \u2014 not the other way around<\/strong><\/h2>

Not every call for projects is the same. A Surface Transportation Block Grant solicitation has different eligibility requirements than a Transportation Alternatives set-aside. A highway resurfacing program asks different questions than a transit capital call. When your submission form is a static document \u2014 a Word template or a PDF \u2014 accommodating those differences means maintaining multiple versions, which means more opportunities for the wrong form to end up in the wrong sponsor’s hands.<\/p>

ProjectTracker lets you configure submission questions by funding opportunity. Each call gets the form it actually needs. Scoring criteria can be customized by funding stream so that evaluations reflect the specific goals of each program. You can filter and compare projects by score, geography, work type, or funding request \u2014 within a cycle or across cycles \u2014 without building a new spreadsheet to do it.<\/p>

Attachments: the part nobody talks about until something goes wrong<\/strong><\/h2>

Every project submission comes with documents. Concurrence letters. Preliminary cost estimates. Design plans. Environmental clearances. Right-of-way certifications. Photos of the failing culvert that makes the case better than any written description could.<\/p>

In a folder-based system, these live somewhere \u2014 if you’re lucky, somewhere consistent, with a naming convention that the person who created it remembers. When you need to find a specific attachment six months after submission, you’re either searching through a shared drive or emailing the person who set up the folder and hoping they still work there.<\/p>

ProjectTracker’s attachments feature keeps every document filed directly within the project it belongs to. Request letters, design plans, agency concurrence, photos \u2014 all of it is retrievable from the same place you go to look at the application or the selected project. No folders to navigate. No naming conventions to remember. No wondering whether the file you’re looking at is the final version or a draft from March. When someone other than the original submitter needs to find something, they can find it \u2014 without asking anyone for help.<\/p>

The annual call for projects doesn’t have to feel like a production. With the right system, it feels like a workflow \u2014 one that gets smoother each year because the work you did last year is still there, still useful, and still connected to everything that came after it.<\/p>

That’s what ProjectTracker is built to do.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t
\n \n Schedule a demo <\/a>\n <\/div>\n \t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

Ask any MPO planner what time of year they dread most, and a lot of them will tell you it’s call for projects season. Not because the work isn’t meaningful \u2014 it is \u2014 but because so much of it feels like reinvention. New spreadsheet. New folder structure. New email chain trying to track who submitted what. Same questions you asked last year, re-typed into a new form. Same follow-up calls to sponsors who can’t find the attachment they uploaded three weeks ago. If that sounds familiar, the problem isn’t your process. It’s that your tools weren’t built for a<\/p>\n","protected":false},"author":3,"featured_media":21768,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"inline_featured_image":false,"wds_primary_category":0,"footnotes":""},"categories":[15],"tags":[],"post_folder":[],"positioning":[84,58],"class_list":["post-21763","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","positioning-ecointeractive","positioning-public-sector"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.sovra.com\/fr\/wp-json\/wp\/v2\/posts\/21763","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sovra.com\/fr\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sovra.com\/fr\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sovra.com\/fr\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sovra.com\/fr\/wp-json\/wp\/v2\/comments?post=21763"}],"version-history":[{"count":11,"href":"https:\/\/www.sovra.com\/fr\/wp-json\/wp\/v2\/posts\/21763\/revisions"}],"predecessor-version":[{"id":21836,"href":"https:\/\/www.sovra.com\/fr\/wp-json\/wp\/v2\/posts\/21763\/revisions\/21836"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.sovra.com\/fr\/wp-json\/wp\/v2\/media\/21768"}],"wp:attachment":[{"href":"https:\/\/www.sovra.com\/fr\/wp-json\/wp\/v2\/media?parent=21763"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sovra.com\/fr\/wp-json\/wp\/v2\/categories?post=21763"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sovra.com\/fr\/wp-json\/wp\/v2\/tags?post=21763"},{"taxonomy":"post_folder","embeddable":true,"href":"https:\/\/www.sovra.com\/fr\/wp-json\/wp\/v2\/post_folder?post=21763"},{"taxonomy":"positioning","embeddable":true,"href":"https:\/\/www.sovra.com\/fr\/wp-json\/wp\/v2\/positioning?post=21763"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}