Suneet Singal on forecasts and plans

Suneet Singal’s reference library separates a forecast from a plan because the two words are used as if they were one decision. A forecast is an expectation: what you think will happen, under assumptions you can name. A plan is a set of actions: who will do what, by when, with what authority. A forecast can inform a plan. It is not the plan, and it is not a result. This entry shows how to label an assumption before you repeat a projection, how to read outlook language without turning it into a promise, and how to keep a hypothetical number from being copied as someone’s financial result. The career page’s historical roles are not forecasts and not plans. They are dated disclosures, and this entry leaves them in that category.

An expectation is not a set of actions

Say the two definitions in your own note before you use the words. Forecast: an expectation about a future period, tied to assumptions. Plan: the actions someone has authority to take, tied to dates and owners. If a sentence does not tell you which of the two it is, it is not ready to send. “We will grow” can be heard as either. “The forecast assumes the stated volume, and the plan is to assign two people to the stated work” cannot be confused. The second version is longer because it has refused to let one verb do two jobs. One verb doing two jobs is how teams argue past each other. One side heard a promise. The other side heard a guess.

Results sit in a third category, and they are about the past. Net income for a year that has ended is a result if it comes from an income statement. Cash already collected is a result if it comes from a cash flow statement or a bank record. A forecast of either one is not the statement. The cash-flow and profit entry is about results and the statements that report them. This entry is about language that points forward. Do not cite a forward-looking sentence as if it were the statement, and do not cite the statement as if it were a promise about next year. Tense is the first label. Future tense is a claim that needs assumptions. Past tense is a claim that needs a document.

Suneet Singal’s name on this page is the name of the guide, not the subject of a projection. The site states a background in real estate and corporate finance. It dates an acting chief executive officer appointment at First Capital Investment Corporation effective 12 September 2017 and a chief executive officer departure from FC Global Realty Incorporated effective 2 January 2018. None of those sentences forecasts revenue, and none of them is a plan of future operations. Leave them on the career page. Do not draft an outlook and attach his name to make the outlook sound experienced.

Label the assumption

Every forecast has a load-bearing assumption, even when the author does not admit it. The assumption may be a volume, a price, a hiring date, a rate, or a sentence such as “if the contract is signed.” Write the assumption on the same page as the number. If you cannot write it, you do not yet have a forecast. You have a wish with a decimal. Wishes can be discussed. They should not be pasted into a budget line that other people will treat as a commitment. The label “assumption” is what lets a later reader change the number when the assumption fails, without feeling that the whole document was a lie. Unlabeled numbers cannot be revised cleanly. They can only be defended or abandoned.

Date the forecast. An expectation formed in March about December is not the same object as an expectation formed in November about December. Both can be sincere. A reader who sees only “the forecast” will treat the older one as current or the newer one as a confession of error, depending on the reader’s mood. Put the date of the expectation in the caption. “Forecast prepared on the stated day, for the stated period, under the stated assumption.” Three anchors. If any anchor is missing, the caption is early. This is the same habit as putting an effective date next to a title. Undated claims drift. A forecast without a preparation date drifts into “what we always expected,” which is rarely true.

Show the arithmetic if the number is derived. A total built from price times quantity should show price and quantity. A reader who disagrees with the total can then disagree with the right factor. A reader who is overloaded, which is the situation the managing-up entry contemplates, can approve or challenge one factor in a reply of one line. Hidden arithmetic forces a meeting. Meetings are sometimes necessary. They should not be necessary just because the note refused to show its multiplication.

A forecast is not a result, and a plan is not a hope

When the period ends, the forecast does not become the result by aging. The result is whatever the statements or the operational records show. Compare them if comparison is useful, and label the comparison as a comparison. “The forecast prepared on that day said this; the statement for the period reported that.” The gap is not automatically a failure of character. Assumptions can be wrong without anyone having hidden them. The gap is automatically a reason to look back at the assumptions you wrote down. If you did not write them down, you cannot learn which one moved. You can only argue. Argument without the original assumption list is how forecasting becomes folklore.

A plan without owners is a hope. “Improve collections” is a hope. “Alex will call the ten largest overdue accounts by Friday and record the promises in the log” is a plan, if Alex has the assignment and the log exists. The test is whether a stranger could tell, next week, whether the plan happened. Forecasts fail that test on purpose, because a forecast is not an action. Do not “fix” a forecast by adding fake precision that implies an action no one owns. Do not “fix” a plan by adding a confident outcome. The outcome is the forecast. The action is the plan. They can sit on one page in two boxes. They should not sit in one sentence.

Authority belongs in the plan box. An action the writer cannot take and the reader has not approved is a proposal, not a plan. Call it a proposal until the approval arrives. The managing-up note’s default is a way of handling the gap between proposal and approval. It is not a way of upgrading a forecast into a result. If the proposal is declined, the plan changes and the forecast may change with it. Write the new version and date it. Do not edit the old version into silence. A file of dated versions is a record. A single version that is always “current” and never archived is a story that rewrites itself.

A hypothetical forecast, not a company’s outlook

Consider a hypothetical shop that is not any issuer named on this site and not a program. Suppose that on 1 March a manager writes: “Forecast: 100 in cash receipts in April, assuming 20 customers pay the hypothetical invoice of 5.” The plan, separate from the forecast, is: “Sam sends the 20 invoices by 5 March.” If only 10 customers pay, the result is 50, the forecast was 100, and the plan may still have been executed. The three numbers answer three questions. Anyone who says “the plan failed because receipts were 50” has not checked whether Sam sent the invoices. Anyone who says “receipts were fine because we planned to send invoices” has not looked at the 50. The hypothetical exists to keep those errors apart. It is not a result for FC Global Realty Incorporated, First Capital Investment Corporation, or Suneet Singal.

Change one anchor and watch the sentence you want to tell. Move the forecast’s preparation date to 25 April, after most of the month has happened, and the number 100 is no longer the same kind of expectation. It may be a revised expectation with more information. It may be a target someone is trying to talk into being true. The date tells you which conversation you are in. Without the date, the number is just 100. Numbers without dates migrate into biographies. Do not let this 100 migrate. It dies with the paragraph.

You can practice the same split on a personal budget or a team’s week without using corporate language at all. Expectation: the train takes forty minutes, assuming the usual timetable. Plan: leave the house at the stated time. Result: the day you actually had. People who treat the timetable as a moral promise suffer twice, once from the delay and once from the category error. Labeling the timetable as a forecast is not pessimism. It is literacy. The same literacy applies when the timetable is a revenue outlook and the audience is a board or a client. Say which box you are speaking from.

How to read outlook language in a document

Company reports sometimes discuss known trends and uncertainties. The beginner’s guide describes management’s discussion and analysis as the place management talks about what the statements show and about trends that are reasonably likely to matter. That discussion can include forward-looking sentences. Read them as management’s account, dated to the report, not as audited results. Audited results are the statements for the period that has ended. The discussion may help you form your own expectation. Your expectation is then yours. It should carry your assumptions, not a silent claim that the company promised your number.

If a sentence in a filing is about an officer rather than an outlook, do not stretch it into an outlook. The Form 8-K facts used on this site are dates and roles. They do not state a forecast of profit, cash, or working capital. A departure effective 2 January 2018 is not an outlook for 2018. An acting appointment effective 12 September 2017 is not a plan for the following year. Readers add those stories because a title seems to imply a direction. Direction is the forecast box. It needs its own source. The officer sentence stays in the role box on the company-record guide.

When you take notes from an outlook section, quote or paraphrase the assumption if the section states one, and write “assumption not stated in the passage I read” if it does not. The second note is valuable. It stops you from filling the hole with an industry cliché. Clichés are unlabelled assumptions that feel like knowledge. They are hard to revise because no one remembers adopting them. A blank labeled “not stated” can be filled later with a source. A cliché cannot be filled. It can only be believed.

Filing the two documents side by side

Give forecasts and plans different file names or different headings even when they live in one packet. “Forecast 1 March, April receipts” is one document. “Plan 1 March, invoice work” is another. The result, when it exists, is a third file: the statement, the collections log, the filing. A packet that merges them into “April numbers” will be cited loosely. Loose citation is how a plan’s to-do list gets quoted as a result months later. The source-notes entry shows the general form. Use it for a forecast by recording the preparation date, the period described, the assumption, and the limit: this is not a result.

Review on a schedule rather than on a mood. A scheduled review compares the latest result with the forecast that was live at the time, then writes a new forecast if the horizon still matters, and adjusts the plan’s actions if the actions should change. An unscheduled review, done only when the numbers delight or alarm you, teaches the team to associate forecasting with emotion. Emotion is a poor index. The index is the date you promised yourself you would look. Write that date in the plan, not in the forecast. Looking is an action. The number you expect to see is an expectation. Even the review meeting splits in two.

Keep the language boring on purpose. “Forecast,” “assumption,” “plan,” “owner,” “result.” The synonyms “target,” “goal,” “outlook,” “guidance,” and “ambition” can be legitimate, and they are also how the boxes get scrambled. If you use a synonym, define it once. “In this note, target means the plan’s intended action, not the forecast.” A definition sentence is not fussy when the alternative is a dispute about a word. Disputes about words are usually disputes about which box a number was in. Put the number in a box with a name and the dispute gets smaller.

What not to attach to a name

Do not attach a forecast to Suneet Singal as a personal projection. This page did not publish a figure for him, and the hypothetical shop’s 100 is not his. Do not attach a plan of action to the historical offices beyond the actions the filings actually report, which this reference treats as the appointment and the departure themselves. A plan to “transform” a company is a story. Stories need sources this page does not use. The programs that describe him as founder are programs, not revenue forecasts. Their sites are the place to read what they say. The education programs page keeps those descriptions in the program layer.

Use the split the next time you write a number about the future. If you can name the assumption and the preparation date, you may have a forecast. If you can name the owner and the action, you may have a plan. If the period has ended and a document records what happened, you may have a result. If you cannot tell which of the three you have, do not circulate the number. Circulating it forces someone else to guess the box. Guessing the box is how expectations become obligations and how obligations get described, later, as if they had been results all along.

What this entry does not claim

Suneet Singal’s published professional background is in real estate and corporate finance. Company filings linked from this site record a chief executive officer departure from FC Global Realty Incorporated effective 2 January 2018 and an acting chief executive officer appointment at First Capital Investment Corporation effective 12 September 2017. The Suneet Singal Scholarship, Grant and Giving websites describe him as the founder of those programs. This entry explains a general subject. It is not a private track record, a current job title, an investment result, or a quote.

Continue with managing up when a manager is overloaded and cash flow and profit. Dated historical roles, not outlooks, are on the career page. This is a reading guide, not legal or financial advice.