5 exercises — master will, going to, and present continuous for talking about launches, deadlines, plans, and decisions in software project management.
Future tense guide
will → spontaneous decision / formal written docs: "I'll fix it", "The API will return 404"
going to → intention already decided / prediction from evidence: "We're going to refactor it"
A project manager says in a stand-up: "We ___ launch the new billing module next Tuesday — it's already in the release calendar." Which future form is most appropriate?
Are launching (present continuous for future) is most appropriate. When an event is scheduled and already arranged — booked in a calendar, assigned in a project tracker, confirmed with stakeholders — English uses the present continuous. This signals a firm, pre-planned commitment: "We are launching on Tuesday", "The team is demoing to the client on Friday", "The sprint is ending on Thursday."Will launch works too but feels more like a spontaneous decision or prediction. Going to launch implies intention — slightly less fixed than a scheduled event. Present simple (launch) is used for timetabled events: "The conference starts at 9am" — technically valid but less common for software releases. In project management English, present continuous is the natural choice for diary-based plans.
2 / 15
A developer says: "Look at these memory leak graphs — the server ___ crash under tonight's load if we don't patch it." Which form expresses a strong prediction based on current evidence?
Is going to crash is correct. Going to + infinitive is used for predictions based on present evidence — something you can see is clearly heading toward an outcome. The key phrase is "look at these graphs" — visible evidence supports the prediction. Compare: "It is going to rain" (you can see dark clouds). In tech contexts: "The disk usage is going to hit 100% by morning — look at the trend." · "That query is going to timeout — the execution plan is terrible."Will is used for predictions without specific present evidence — general beliefs or forecasts: "I think the migration will take two weeks." The distinction: going to = evidence right now; will = general expectation or spontaneous decision.
3 / 15
A CTO says in a planning meeting: "We ___ migrate all services to Kubernetes by Q3. That's the direction we've decided on." Which future form expresses a firm intention or plan?
Are going to migrate is correct for a firm intention or plan already decided. When a decision has been made prior to the moment of speaking, going to is the standard choice: "We're going to refactor the authentication layer — we decided last week." · "The company is going to adopt a platform engineering model." The phrase "that's the direction we've decided on" confirms this is a pre-existing decision, not a spontaneous one. Will could also work here (and is common in formal written communication), but going to better signals that the decision is already made. Are migrating (present continuous) would imply it's already in the calendar with a specific date — possible, but the Q3 timeframe makes going to more appropriate.
4 / 15
A junior developer messages a colleague: "Can you review this PR? I ___ fix the failing tests while you look at the logic." Which future form signals a spontaneous offer or decision made at the moment of speaking?
'll fix (will) is correct for a spontaneous decision or offer made at the moment of speaking. When you decide something as you say it — not based on a pre-existing plan — use will. Examples: "I'll take care of the merge conflict." · "We'll schedule a call to discuss it." · "I'll open a ticket for that." This is the most common use of will in day-to-day tech communication: responding to a situation in real time. Contrast with going to: "I'm going to fix the tests" implies you already had a plan to do so. Am fixing implies it's already in progress. Will is the natural form for offers, promises, and instant decisions — all extremely common in team communication.
5 / 15
A product manager writes in a roadmap doc: "The API v3 ___ deprecate API v2 automatically after 12 months." Which form is most appropriate for a scheduled, timetable-based future event in documentation?
Will deprecate is the most appropriate form for a scheduled, policy-driven future event in written documentation. In formal written English (roadmaps, specs, RFCs, API documentation), will is the standard future marker because it sounds authoritative and definitive: "Version 3.0 will replace version 2.0." · "This endpoint will return a 410 status after deprecation." · "The feature flag will be removed in the next major release."Going to can sound too conversational for spec documents. Is deprecating implies a specific date already set — possible but less precise for a "12 months from launch" policy. Note the spelling error in option D: depreciates means loses monetary value (depreciation), not technical removal (deprecation) — a common confusion worth remembering.
6 / 15
In a project documentation update, Alex (Technical Writer) states: 'The new logging service will automatically scale based on server load.' Which future tense best describes this scheduled, time-dependent event?
'Will scale' is the most appropriate choice for describing a planned future event that's tied to a specific condition (server load). 'Is going to scale' suggests an immediate action; 'scales' is present tense and doesn't accurately represent this scheduled behavior; 'has scaled' is past tense, referring to a completed action.
7 / 15
In a project documentation update, Alex (Technical Writer) states: 'The new logging service will automatically scale based on server load.' Which future tense best describes this scheduled, time-dependent event?
'Will scale' is the most appropriate choice for describing a planned future event that's tied to a specific condition (server load). 'Is going to scale' suggests an immediate action; 'scales' is present tense and doesn't accurately represent this scheduled behavior; 'has scaled' is past tense, referring to a completed action.
8 / 15
In a project documentation update, Alex (Technical Writer) states: 'The new logging service will automatically scale based on server load.' Which future tense best describes this scheduled, time-dependent event?
'Will scale' is the most appropriate choice for describing a planned future event that's tied to a specific condition (server load). 'Is going to scale' suggests an immediate action; 'scales' is present tense and doesn't accurately represent this scheduled behavior; 'has scaled' is past tense, referring to a completed action.
9 / 15
The project manager, Emily, announces in a standup: 'We are releasing version 2.1 of the application next Friday.' Which future tense best fits this announcement?
'Are going to release' is standard for scheduled releases or planned events when the decision has already been made. 'Will release' implies a more spontaneous intention. 'Shall release' is rarely used in professional contexts and 'is releasing' is present continuous which doesn't fit the context of a scheduled announcement.
10 / 15
Maria (Product Manager) updates the project documentation: "The automated database backups will run daily at midnight.". Which future tense best describes this scheduled event?
'Will be running' is the most accurate and common way to express a regularly scheduled task or process in future documentation. It clearly indicates an action that will happen at a specific time in the future. 'Is going to run' implies a spontaneous decision, while 'are running' describes a current state and 'run' is too simple for a scheduled event.
11 / 15
John (Project Manager) announces during a daily standup: "The new API endpoint will be available for integration by the end of next week.". Which future tense most accurately reflects this announcement?
'Will be available' is the standard and clearest way to state that a feature or resource will be accessible at a future point in time. 'Is going to be available' suggests a more immediate decision, while 'are going to be available' implies multiple individuals are involved. 'Shall be available' is an outdated and uncommon form.
12 / 15
**Scenario:** David, a senior dev, is discussing an upcoming feature release with the product owner. He wants to outline the expected timeline.
**Question:** What future tense would be most suitable for David's statement?
(A) 'We are planning to implement this feature.' (Progressive - suggests ongoing activity)
(B) 'We will implement this feature by next Friday.' (Simple Future – expresses a definite plan with a specific time)
(C) 'I am going to implement this feature.' (Present Continuous – similar meaning to B but less formal)
(D) 'We are scheduling the implementation of this feature' (Passive - shifts focus away from David's role)
Option (B) 'We will implement this feature by next Friday' uses the simple future tense correctly to express a firm commitment and a specific deadline. This is common in project management for conveying scheduled events.
13 / 15
**Scenario:** Emily, a project manager, is documenting an API migration.
**Question:** Which future tense should she use to describe the automatic deprecation of the old API?
(A) 'The API will be deprecated.' (Simple Future – indicates a completed event)
(B) 'The API is being deprecated.' (Present Continuous - suggests an ongoing process)
(C) 'The API has been deprecated.' (Past Simple – describes something that happened in the past)
(D) 'The API is going to be deprecated' (Going to future - expresses a prediction based on current evidence)
Option (A) 'The API will be deprecated' uses the simple future tense correctly to describe a scheduled event—a planned deprecation with a defined outcome. It's standard terminology in technical documentation.
14 / 15
David, a senior dev, is discussing an upcoming feature release with the product owner. He wants to outline the expected timeline.
'We're planning to deploy this new module next Wednesday. It's scheduled to go live after our final testing phase.' Which future tense best describes this statement?
The best choice here is 'We will deploy the module.' This uses the 'will' + infinitive construction to clearly state a planned future event – the deployment itself. The other options use different tenses with incorrect implications for scheduling and intent. It's important to recognize that 'will' often denotes a fixed plan or commitment.
15 / 15
Ben, a lead developer, is creating the PR description for a significant code change.
'The new authentication service ___ integrate with the existing user database by next Friday.' Which form is most appropriate for a scheduled, timetable-based future event in documentation?
'The service will integrate' is the most appropriate. This phrasing clearly communicates that integration is planned and scheduled for next Friday – a concrete timeframe. The 'will' + infinitive construction is ideal for documenting pre-determined timelines and commitments within project documentation, unlike describing ongoing actions or past events.
What will I practise in "Future Tenses in Project Management English | Coders Lingo"?
Practise will, going to, and present continuous for future in project management and engineering contexts. 5 grammar exercises.
How many exercises are in this module?
This module has 15 multiple-choice exercises, each with instant feedback and a full explanation of the correct answer.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall.
Do I need to create an account to do these exercises?
No account is required. Just click an option to answer — your score for this session is tracked automatically in the progress bar above.
What happens if I choose the wrong answer?
You'll immediately see which answer was correct, plus a full explanation covering the grammar rule and reasoning behind it — mistakes are where most of the learning happens.
Can I retry the exercises if I want a higher score?
Yes — use the "Try again" button on the results screen to reset and go through all the questions again.
Is my progress saved if I close the page?
No. Progress is tracked only for your current visit; reloading or leaving the page resets the counter. This keeps the exercise simple and account-free.
Where can I find more Grammar exercises?
Browse the full Grammar hub for related drills, or check the "Next up" link below to continue with a connected topic.
How is this different from reading an article on the same topic?
Articles explain grammar rules in prose; this exercise tests and reinforces those rules through active recall with immediate feedback — the two work best together.
Who writes these exercises?
Every exercise is written by the CoderSlingo team, drawing on real workplace English used in IT roles, then reviewed for accuracy and clarity.