5 exercises — signposting language for RFCs, postmortems, and design docs: backward references, forward references, summaries, and section transitions.
0 / 20 completed
1 / 20
A technical design document has three sections: Overview, Implementation Details, and Trade-offs. Which signposting sentence best introduces the Trade-offs section?
Option D is the strongest. It performs three signposting functions simultaneously: (1) it references earlier sections ("as outlined in… detailed in…"), (2) it signals what comes next ("several trade-offs"), and (3) it frames the purpose ("before committing to this approach"). This is the highest-level signposting — connecting the document structure explicitly. Option B is a plain forward reference — acceptable but minimal. Option C is verbose and informal ("this one is no different"). Option A is too casual and direct for a design document. Key signposting functions: backward reference (as discussed above), forward reference (the following section), summary signal (in summary / to summarise), scope declaration (this section covers).
2 / 20
A postmortem begins with a timeline and then moves to root cause analysis. Which sentence best signals the transition?
Option C is the most effective signposting sentence for a formal postmortem. It uses a participial phrase ("Having established…") to acknowledge the completed section, then a forward reference ("the following section") to signal the transition, and names the purpose precisely ("analyses the underlying root cause"). Option A is a bare heading — functional but not signposting; it provides no link between sections. Option B is abrupt and sounds like spoken notes. Option D is too casual ("dig into") for a written postmortem. A well-signposted postmortem helps readers understand the document structure without relying solely on headings. Think of signposting sentences as the "joints" of a document.
3 / 20
An RFC ends its Motivation section and begins the Proposal section. Which signposting phrase is most appropriate?
Option B is the best. "Given the constraints identified above" is a backward reference that ties the proposal to the motivation — the reader understands why the proposal follows. "This proposal describes a solution that addresses…" signals what the section contains and frames it as a solution to a problem. This is the essential pattern for proposal documents: backward reference (problem) → forward reference (solution). Option A is too casual for an RFC. Option C is mechanical — it names the section but builds no logical connection. Option D ("Moving on") is a spoken transition marker, inappropriate in formal writing. RFC and ADR signposting tip: always connect the proposal to the motivation with a backward reference.
4 / 20
A technical guide has covered three configuration steps. Which sentence best summarises before concluding?
Option B is the best. A good summary sentence does three things: (1) signals the summary explicitly ("In summary"), (2) restates the completed actions with specific detail ("configured the database connection, set the environment variables, enabled TLS"), and (3) states the achieved state or what comes next ("The service is now ready to deploy"). This gives the reader a mental checklist and a clear handoff to the next phase. Option A is too casual. Option C is vague ("steps were followed" names nothing). Option D is a prerequisite warning, not a summary. Signposting at section ends: In summary / To summarise / Having completed these steps + specific restatement + achieved state.
5 / 20
An architecture document refers back to a constraint from a previous section. Which version uses backward signposting most effectively?
Option C is the strongest. It names the source section explicitly ("as noted in the Requirements section"), restates the constraint with its specific value ("sub-100ms latency"), labels it precisely ("hard constraint"), and declares the consequence for the current section ("The following design choices are made specifically to satisfy this requirement"). This is the full backward-reference pattern: as [stated/noted/described] in [section/document], [specific detail], [consequence for current section]. Option A uses "as mentioned" without naming where or what — too vague. Option B is too informal ("we talked about"). Option D is casual and imprecise. Strong backward references build logical credibility: they show the reader that each decision is grounded in an established requirement.
6 / 20
During a code review of the new payment processing module, Sarah comments on Mark's implementation: 'Okay, this section handles the initial validation. Now let's discuss how we're handling potential errors and retry logic.' Which word best exemplifies backward signposting in this scenario?
Backward signposting connects the current section with a previous one. In this case, 'now' clearly indicates that the following discussion builds upon the 'initial validation' already explained. The other options misinterpret the purpose of backward signposting, which is to create explicit links between related ideas, not just general context.
7 / 20
You're drafting a Pull Request description for a new feature: 'This PR implements the user profile update functionality. It includes fields for name and email. We've focused on validation to ensure data integrity.' Which phrase would be most effective to use at the end of this paragraph to signal that you will now detail the API endpoint changes?
'Therefore, the following section outlines…' is a classic and clear example of forward signposting. It explicitly indicates that the subsequent content will elaborate on the API endpoint changes, providing a logical transition for the reader. The other options present less direct or less appropriate signals of continuation.
8 / 20
In a Slack channel dedicated to debugging the 'Phoenix' microservice, David writes: 'We've identified a race condition in the data synchronization process. Thread.sleep(100) has been added to mitigate this, but it's proving difficult to scale.' Which sentence best demonstrates an example of forward signposting?
'We're currently exploring alternative solutions.' directly signals that the following message will detail those alternatives. This is forward signposting – it guides the reader to expect further discussion of potential resolutions. The other options describe consequences or observations, not a planned continuation of thought.
9 / 20
During a standup meeting, Alex reports: 'Yesterday, I worked on implementing the new authentication flow. I've created the API endpoints and integrated them with the user database.' Which sentence would be most appropriate for Ben to add immediately after Alex's update, indicating he will now discuss the UI changes?
'I'll now cover the UI implementation details.' clearly indicates a transition in topic and a promise of further information. This is forward signposting – it tells the listener what to expect next. The other options suggest related but distinct topics that would require separate discussion points.
10 / 20
You are writing a technical document about deploying a new version of the 'Hydra' application. The document starts with an overview of the deployment process and then details the specific steps involved. Which sentence best exemplifies backward signposting?
'The deployment process is straightforward.' implies that the preceding sections have provided the necessary context and explanation for understanding this process. This is backward signposting – it references what was previously described to help the reader connect the current information with prior knowledge. The other options are general statements of advice or recommendations.
11 / 20
During a code review of the new payment processing module, Sarah comments on Mark's implementation: 'Okay, this section handles the initial validation. Now let's discuss how we're handling potential errors and retry logic.' Which word best exemplifies backward signposting in this scenario?
Backward signposting connects the current section with a previous one. In this case, 'now' clearly indicates that the following discussion builds upon the 'initial validation' already explained. The other options misinterpret the purpose of backward signposting, which is to create explicit links between related ideas, not just general context.
12 / 20
You're drafting a Pull Request description for a new feature: 'This PR implements the user profile update functionality. It includes fields for name and email. We've focused on validation to ensure data integrity.' Which phrase would be most effective to use at the end of this paragraph to signal that you will now detail the API endpoint changes?
'Therefore, the following section outlines…' is a classic and clear example of forward signposting. It explicitly indicates that the subsequent content will elaborate on the API endpoint changes, providing a logical transition for the reader. The other options present less direct or less appropriate signals of continuation.
13 / 20
In a Slack channel dedicated to debugging the 'Phoenix' microservice, David writes: 'We've identified a race condition in the data synchronization process. Thread.sleep(100) has been added to mitigate this, but it's proving difficult to scale.' Which sentence best demonstrates an example of forward signposting?
'We're currently exploring alternative solutions.' directly signals that the following message will detail those alternatives. This is forward signposting – it guides the reader to expect further discussion of potential resolutions. The other options describe consequences or observations, not a planned continuation of thought.
14 / 20
During a standup meeting, Alex reports: 'Yesterday, I worked on implementing the new authentication flow. I've created the API endpoints and integrated them with the user database.' Which sentence would be most appropriate for Ben to add immediately after Alex's update, indicating he will now discuss the UI changes?
'I'll now cover the UI implementation details.' clearly indicates a transition in topic and a promise of further information. This is forward signposting – it tells the listener what to expect next. The other options suggest related but distinct topics that would require separate discussion points.
15 / 20
You are writing a technical document about deploying a new version of the 'Hydra' application. The document starts with an overview of the deployment process and then details the specific steps involved. Which sentence best exemplifies backward signposting?
'The deployment process is straightforward.' implies that the preceding sections have provided the necessary context and explanation for understanding this process. This is backward signposting – it references what was previously described to help the reader connect the current information with prior knowledge. The other options are general statements of advice or recommendations.
16 / 20
During a code review of the new payment processing module, Sarah comments on Mark's implementation: 'Okay, this section handles the initial validation. Now let's discuss how we're handling potential errors and retry logic.' Which word best exemplifies backward signposting in this scenario?
Backward signposting connects the current section with a previous one. In this case, 'now' clearly indicates that the following discussion builds upon the 'initial validation' already explained. The other options misinterpret the purpose of backward signposting, which is to create explicit links between related ideas, not just general context.
17 / 20
You're drafting a Pull Request description for a new feature: 'This PR implements the user profile update functionality. It includes fields for name and email. We've focused on validation to ensure data integrity.' Which phrase would be most effective to use at the end of this paragraph to signal that you will now detail the API endpoint changes?
'Therefore, the following section outlines…' is a classic and clear example of forward signposting. It explicitly indicates that the subsequent content will elaborate on the API endpoint changes, providing a logical transition for the reader. The other options present less direct or less appropriate signals of continuation.
18 / 20
In a Slack channel dedicated to debugging the 'Phoenix' microservice, David writes: 'We've identified a race condition in the data synchronization process. Thread.sleep(100) has been added to mitigate this, but it's proving difficult to scale.' Which sentence best demonstrates an example of forward signposting?
'We're currently exploring alternative solutions.' directly signals that the following message will detail those alternatives. This is forward signposting – it guides the reader to expect further discussion of potential resolutions. The other options describe consequences or observations, not a planned continuation of thought.
19 / 20
During a standup meeting, Alex reports: 'Yesterday, I worked on implementing the new authentication flow. I've created the API endpoints and integrated them with the user database.' Which sentence would be most appropriate for Ben to add immediately after Alex's update, indicating he will now discuss the UI changes?
'I'll now cover the UI implementation details.' clearly indicates a transition in topic and a promise of further information. This is forward signposting – it tells the listener what to expect next. The other options suggest related but distinct topics that would require separate discussion points.
20 / 20
You are writing a technical document about deploying a new version of the 'Hydra' application. The document starts with an overview of the deployment process and then details the specific steps involved. Which sentence best exemplifies backward signposting?
'The deployment process is straightforward.' implies that the preceding sections have provided the necessary context and explanation for understanding this process. This is backward signposting – it references what was previously described to help the reader connect the current information with prior knowledge. The other options are general statements of advice or recommendations.
What will I practise in "Cohesion and Signposting in Technical Documents — Grammar Exercise"?
Practice signposting language for technical documentation: backward references, forward references, summaries, and transition sentences in RFCs, postmortems
How many exercises are in this module?
This module has 20 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.